linuxaudio.org

On Thu, 2009-04-09 at 14:34 -0400, Paul Davis wrote:

quoted text
> On Thu, Apr 9, 2009 at 2:28 PM, Justin Smith  wrote:

> Off the top of my head, something could be put together with a shell

> > script using the jack_connect program. If you are OK with a single

> > purpose script that runs and connects two specific known programs,

> > this will be easy, making it work with arbitrary programs provided as

> > arguments is better done with something like lash, or patch-bay

> > persistence.

>

> to be more specific:

>

>

> ----------------------

> #!/bin/sh

>

> jackd ... jack arguments here ... &

> sleep 2

> clientNumberOne &

> sleep 2

It'd be nice to have a utility in jack that would work like this:
jack_waitForClient clientNumberOneName
or something similar... returns when the named port is available

(hopefully signalling that the application is ready, at least from the

point of view of jack connections)
-- Fernando
> client NumberThree &

quoted text
> sleep 2

>

> jack_connect system:playback_1 clientNumberOne:in_1

> jack_connect system:playback_2 clientNumberOne:in_1

> jack_connect system:playback_1 clientNumberTwo:in_1

> jack_connect system:playback_2 clientNumberTwo:in_2

>

> ----------------------

>

> signal handling to shut down jackd and the two clients is left as an

> exercise for the interested.

>

> --p

>

>

>

>  _______________________________________________

> > Linux-audio-dev mailing list

> > Linux-audio-dev@lists.linuxaudio.org

> > http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev

> >

> _______________________________________________

> Linux-audio-dev mailing list

> Linux-audio-dev@lists.linuxaudio.org

> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev

_______________________________________________

Linux-audio-dev mailing list

Linux-audio-dev@lists.linuxaudio.org

http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev