On Sat, May 16, 2009 at 6:17 PM, drew Roberts <zotz@xxxxxxxxxxx> wrote: > On Saturday 16 May 2009 11:52:18 alex stone wrote: >> Did the Jack >> team run over someone's cat? > > I love jack. Especially the routing flexibility. > > But I just switched one of my station loggin boxes from rotter which uses jack > to darkice because I wanted to go from loggin one station on the box to > loggin two. > > The box is a 1u rack mount machine with no onboard sound card. I hooked up two > different usb sound cards to it. To do what I wanted with jack and rotter, I > would have needed to be able to run two instances of jack on the box at the > same time and have rotter designed to deal with that possibility. (Hmmm, I > just had an idea. I will hold off until after I ask the list though.) > > So, does anyone know how I could have done what I needed to with jack in the > mix and the hardware I had on hand? > > all the best, > > drew > _______________________________________________ > Linux-audio-user mailing list > Linux-audio-user@xxxxxxxxxxxxxxxxxxxx > http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user > from man jackd: $JACK_DEFAULT_SERVER specifies the default server name. you can actually run two instances of qjactl which will each control a seperate jack instance if you start from the shell and have that parameter defined. Your client program can use setenv() to change default servers in order to have connections with both. It is up to you to deal with the possibility of different buffer sizes or clock skew etc. of course. _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
