[LAD] Jack MTC/MMC slaving

Ralf Mardorf ralf.mardorf at alice-dsl.net
Mon Nov 24 17:52:57 UTC 2008

Stéphane Letz wrote:
> Le 24 nov. 08 à 18:35, Jack O'Quin a écrit :
>> On Mon, Nov 24, 2008 at 11:28 AM, Alex Montgomery
>> <apmontgomery at gmail.com> wrote:
>>>> I think this kind of tools is a good candidate to be developed as  
>>>> an "in
>>>> server" JACK client. With the dbus based dynamic access of  
>>>> available "in
>>>> server" clients installed on a machine, it will be quite easy to  
>>>> load/unload
>>>> this kind of tool when needed (Netjack2 uses this model of "in  
>>>> server"
>>>> clients).
>>> Ok, so Nedko and I got a release out that supports goto/locate MMC  
>>> messages
>>> and command-line parameters. We're going to switch it over to using  
>>> JACK
>>> midi instead of ALSA midi next. Should we start thinking about  
>>> making this
>>> an "in server" client now? Could someone familiar with this stuff  
>>> comment on
>>> this?
>> I recommend making it a normal external client.  That will be easier
>> to code and test, and easier to make work with both jack1 and jack2
>> servers.
>> -- 
>> joq
> Maybe you can structure the code to  have the "parameter parsing" part  
> clearly separated from "opening/activating the jack client" part. Then  
> it will be easier to make it as an internal client.
> Stephane

I don't know how you coders have to handle things, but for users it will
be more comfortable, if such functions are not some external
applications, it should be part of JACK, if this won't cause to much
troubles for you.

-------------- 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/20081124/a7e086fa/attachment.pgp>

More information about the Linux-audio-dev mailing list