Re: [ecasound] jack-session (was: Re: RIFF header problem)

[Philipp Ü. <hol...@la...>]

Excerpts from Joel Roth's message of 2010-09-15 21:09:29 +0200:
> On Wed, Sep 15, 2010 at 01:34:35PM +0200, Philipp ??berbacher wrote:
> > Oh, I talked to Torben Hohn, the head behind jack-session, a few weeks
> > ago. The automatic shutdown of the engine do get in the way of
> > jack-session and he said the problem could be solved by decoupling the
> > jack part, or something, but apparently it's not trivial. Well, there's
> > hope that he'll do it and add jack-session support sometime. This would
> > likely happen in a way that ecasound handles the low-level stuff and
> > exposes what's necessary for frontends to handle the rest.
> 
> Thanks for the update. Could you explain what you mean
> by 'automatic shutdown' and how it influences
> jack-session?

Changes to aio of a connected CS and possibly others require the CS to
be disconnected, which in turn means the engine gets shut down and the
jack connections are lost.

It's not the purpose of jack-session to reconnect the client in such a
case. Jack connections are supposed to be under the users direct
control, using a connection manager of sorts. Jack-sessions also assumes
this is the case. It's not designed to make non-persistent connections
'magically' persistent. Therefor to make ecasound work with jack-session
ecasound must first behave properly, which means it needs persistent
jack connections.

Sorry if that's a little long and complicated :)

> > I'm looking forward to it, but I guess I'll have to show some active
> > development on my part first ;)
> 
> At least you've got your hands dirty :-)

And more dirt to come :)
-- 
Philipp

--
"Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu
und alle Fragen offen." Bertolt Brecht, Der gute Mensch von Sezuan