On Sat, Nov 6, 2010 at 5:13 PM, Joel Roth <joelz@email-addr-hidden> wrote:
> Although ignorant about many things JACKish, I would expect
> that it's fair for a JACK client manage its ports as allowed
> under JACK's API.
its entirely fair. what's not going to work is to have multiple
clients fighting to control the same set of connections.
> I'd appreciate any suggestions, as I'm about at the end
> of rope (at least without plunging into jack.plumbing
> and Ecasound's sources.)
your problem is in jack.plumbing. its really quite simple code, but
its not part of "official" JACK. put another way, jack,plumbing really
needs to know if the connections it wants to make are for active
clients, but there is (currently) no way to do this. most clients
become active immediately after port registration, but its not an
error for them not to do so. your setup is just exposing this weak
link in the chain, but its not clear where the "fix" should be.
--p
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-user
Received on Sun Nov 7 00:15:01 2010
This archive was generated by hypermail 2.1.8 : Sun Nov 07 2010 - 00:15:02 EET