Re: [LAD] [Jack-Devel] more jack/qjackctl madness : some comments

PrevNext  Index
DateMon, 18 May 2009 12:50:50 -0400
From Paul Davis <[hidden] at linuxaudiosystems dot com>
ToFons Adriaensen <[hidden] at kokkinizita dot net>
CcNedko Arnaudov <[hidden] at arnaudov dot name>, Linux Audio Developers <[hidden] at lists dot linuxaudio dot org>, JACK Developers <[hidden] at jackaudio dot org>
In-Reply-ToFons Adriaensen Re: [LAD] [Jack-Devel] more jack/qjackctl madness : some comments 
On Mon, May 18, 2009 at 12:34 PM, Fons Adriaensen <[hidden]> wrote:
>
> Jack-dbus is not just an (optional) server using
> the C API and providing access to it via dbus.
>
> I don not know what exactly is happening but it
> interferes even if clients are just using the
> C API. And it breaks it.

as far as we can tell, this is true *only* for the auto-start
situation, and that is because of the substantive difference that i
outlined in a previous message about what "auto-start" means in two
different run-time environments. and it showed up for you, as best as
can be determined, because of packaging/build issues that we hope have
been fixed.

everyone involved (i think) agrees that the current way this has to
come to be (a dbus-specific version of libjack) is not the right
solution. we are discussing ways to fix this on #jack at present.
PrevNext  Index

1242665471.16141_0.ltw:2,a <eb4b5e1d0905180950m3b3792c2t7804c10e00147782 at mail dot gmail dot com>