On Mon, Jun 15, 2009 at 10:12:14PM -0400, Paul Davis wrote:
> On Mon, Jun 15, 2009 at 6:25 PM, Fons Adriaensen<
fons@...> wrote:
> >
> > I'll repeat this: if dbus becomes a dependency for Jack, I will
> > fork Jack.
>
> And I'll repeat: JACK will not depend on non-POSIX interfaces for any
> essential functions unless the platform requires it, which it does not
> in this case.
>
> Good grief, Fons. Get a grip. We're trying to figure out how to make a
> system installed by more and more distributors can play nice with
> JACK.
maybe that is exactly the problem? jack is for pro-audio, right?
shouldn't a pro know when jack needs to be started and other
audio device users stopped? why not just have jackd run on top
of pulse, or vice-versa? why would pulseaudio even exist in
a pro-audio setup?
basically, why is complexity being added to jack to deal with
desktop usage issues? maybe because you yourself said jack backends
should not be added to "desktop" applications, that that job
is for pulse?
--
jakemsr@...
SDF Public Access UNIX System -
http://sdf.lonestar.org_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
