Re: [LAD] Jack MTC/MMC slaving

"Alex Montgomery" <apmontgomery@email-addr-hidden> writes:

> Currently jackctlmmc supports the "play", "stop", and "rewind" messages from
> MMC, and I'm going to play with the code to see if I can add support for
> "locate" using jack_transport_locate() so that players can have a primitive
> seek-to type of function. I think that even this limited subset of MMC
> functionality is very desirable for linux audio engineers. I just want to be
> able to sit at my 8-track with my guitar and play/stop, rewind, and maybe
> seek around without having to keep clicking a mouse on a JACK app.

I already have git repository for jackctlmmc. If you are interested I
can make it public. Before importing it to git, I had the source of the
quickly hacked tool in my local filesystem (no version control at all).

> I'm surprised that jackctlmmc doesn't seem to be that widely used (I can't
> find any packages for it in the major linux distros, and it only seems to be
> distributed via source code) when it provides such useful functionality. I'd
> love to see it's functionality integrated into a GUI app like QJackCtl
> (which already has JACK transport buttons for play, rewind, fast-forward)
> instead of being a console application, but that's a subject for another
> email.

I think jackctlmmc can be made to be compilable as inprocess client too.

Paul, Stephane and others, do you think we should have different
directories for jack1 and jack2 drivers/internal clients?

-- 
Nedko Arnaudov <GnuPG KeyID: DE1716B0>

_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev