13 Aug
2011
13 Aug
'11
9:09 p.m.
On 08/13/2011 09:03 PM, Paul Davis wrote:
On Sat, Aug 13, 2011 at 2:56 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
Ok, so the problem is that
JackSession starts and stops the 'wrapped'
JACK app, but doesn't save the state of it (and doesn't give you a warning).
\r
On 08/13/2011 08:54 PM, Paul Davis wrote:
all it does is to
record the command that it started, and when told to
restart, it uses that same command again. so, if the command involved
a client that really did have state, the client would not get to save
its state or restore it. this is why you can use it, for example, to
include a non-JACK application in a jack session. On Sat, Aug 13, 2011 at 2:46 PM, rosea
grammostola
<rosea.grammostola(a)gmail.com> wrote:
Thanks. Could you
explain a bit more e.g. why doesn't it work correctly with
clients with state and what's going wrong in practice? Makes me wondering, is this tool doing anything
'nasty' in the view of
JackSession developers, for either apps with or without state?
its only useful for
clients with no state. clients with state will not
work correctly with it and are not intended to be used with it.