> Restarting JACK is not a very satisfactory recovery scheme.
Well, running clients could remember the ports which they have
been connected to and auto-reconnect as soon JACKd appears
again (»active sensing« ;-). Clients could also do so
persistentely by saving the last used ports to the config
file. If the port isn't available any more, no auto
connection gets made. Just an idea. Hydrogen already can do
so, AFAIR. Very convenient.
> JACK does not work very well without RT privileges.
So, it'll still need some time until the security issues are
addressed and prohibited.
> JACK is not designed for sharing between users. Any
But I could not start two sessions for two different users and
both having sound support on the same card? OK, thanks, I
> One-at-a-time sequential use of a single card by multiple
Perhaps, some day, jack will be able to run as root and allow
different users with priviledges to do so to make connections
to it :) .
> This is currently supported in JACK CVS, but not in any
I already heard about it. I'm wondering how much the drift
between the different cards would be, let's say, in a period
of one hour. Perhaps I can try this out some day.
> Yes, we'll see. Am I just hallucinating this or did
AFAIR I have heard the users always work as root. I really do
not want to support this design.
> Steve is right that this is the hard part. And, something
Well, I think a server between the common desktop applications
and jack is absolutely the best thing. But I really like the
idea that JACK is always present for the user, so if the user
wants to run an audio application (like a guitar FX rack) he
only needs to start it and it will connect to JACK directly
instead of using the 'desktop' soundserver.
> If I had time, I'd play around with gstreamer and try to
I still didn't understand gstreamer completely (OK, I only
spend some minutes on the website). But AFIR gstreamer is not
a soundserver like arts or esound.
Thanks a lot for your wothy information.