[LAU] Ecasound and jack.plumbing don't play well (j.p dies)
torbenh at gmx.de
Mon Nov 8 08:08:59 UTC 2010
On Sat, Nov 06, 2010 at 05:29:16PM -0400, Paul Davis wrote:
> On Sat, Nov 6, 2010 at 5:13 PM, Joel Roth <joelz at pobox.com> 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.
recent (as in svn version with jack-session) versions of jackd delay
advertising of ports until they are active.
this will fix the described problem.
More information about the Linux-audio-user