[LAD] Jack MTC/MMC slaving

[Ralf Mardorf]

> no, silly because if QTractor wants to control JACK transport, its not
> going to plan on doing it by sending MMC.

That's true, but if JACK transport should send/receive MMC by MIDI
to/from an external device, there is the need to connect the ports, that
transmits/receive the MMC commands, to the hardware MIDI out/in ports.
So it would be fine, if this is possible by the Qtractor GUI, resp. it's
silly, because I didn't know that Qtractor is transmitting MMC by itself
and that's why there isn't the need to do this by Qtractor. BUT if JACK
will be the source and receiver for MMC, than applications like Qtractor
don't need to be able to know MMC by them self. If this is only done by
JACK and it's fine, than nobody has to fear, that an application is a
broken MMC master/slave. Also it's silly to run more than one
application, that is able to know MMC, if they all are JACK transport
compatible. It's antithetic to say Linux is flexible, because we can
choose the applications that we need, without running things we don't
need and on the other side, we run more than one application, that is
MMC able. JACK should be the instance that knows MMC and not the HD
recorders and sequencers.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <http://lists.linuxaudio.org/pipermail/linux-audio-dev/attachments/20081125/fb770649/attachment.pgp>