On 08/14/2011 01:24 AM, Paul Davis wrote:
On Sat, Aug 13, 2011 at 3:15 PM, rosea grammostola
<rosea.grammostola@xxxxxxxxx> wrote:
On 08/13/2011 09:12 PM, Paul Davis wrote:
On Sat, Aug 13, 2011 at 3:09 PM, rosea grammostola
<rosea.grammostola@xxxxxxxxx> 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).
its not a problem. if the app is going to get state saved/restored,
then it has to participate in some kind of "exchange" with something
else. that participation is called "JACK Session" and the something
else is the session manager (via the jack server). adding a *new*
method to get the state saved/restored would be ... uh ... pointless.
Ok not ideal maybe, but you can save the wrapped apps (with state) by hand
(press save in wrapped app), right?
you can do that without JACK Session too.
But the advantage of using js_wrap is that the application is started in
a session, with the Jack connections restored.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user
