Re: [FFADO-user] more dbus mystery

[Jonathan W. <jw...@ju...>]

Forwarded to the list, minus large screenshot PNGs.

On Mon, Dec 16, 2013 at 08:15:23PM -0600, fra...@mi... wrote:
> 
> -----Original Message-----
> >From: Jonathan Woithe <jw...@ju...>
> ...
> >Is qjackctl meant to work with jackdbus?  I've never used either so I don't
> >know.  In many ways qjackctl and jackdbus implement two different ways to
> >control jackd and it would not surprise me if they don't coexist well.
> >
> >A quick read of
> >
> >  http://trac.jackaudio.org/wiki/JackDbusPackaging
> >
> >includes the phrase "non-dbus aware tools (like qjackctl)", so I'm guessing
> >that you can't use qjackctl when jackdbus is running.  Note however that
> >this is only a guess.
> 
> Jonathan,
> 
> the explanation was helpful. thank you.
> 
> the short answer is "qjackctl did it." Launching -- but not necessarily starting --
> qjackctl starts /usr/lib/qjackctl/qjackctl.real, whatever that is; which launches
> /usr/bin/jackdbus auto. See attached screen capture; 'ps -auxw' is in the lower right hand
> window. the one above is running "dbus-monitor"; on the left is a grep of qdbus for
> ff, which shows up when ffado-mixer is launched, but without input signal; and jack, which
> shows up when qjackctl is launched, but without signal.
> 
> 
> there are settings for qjackctl that control the dbus elements -- which is the reason
> I've been trying to join jack-devel list. there appear to be some "inconsistencies" 
> between the application interface and the documentation, putting it as nicely as I
> care to. clearly, while the documents might leave a different impression -- qjackctl
> is "meant to work with dbus" after all.
> 
> My qjackctl setting for Server Path was <set to> blank, which apparently does not do what 
> one might expect; "no server". 
> 
> Instead, it might/must default to the first menu entry, which as shown on
> the second screenshot is ... 'jackdbus auto'. Note the lack of check mark in the Realtime
> setting box. Viewing the .log/jack/jackdbus.log file, shown in the upper left window,
> one might think that jackdbus is actually working. It may, in fact be -- hence my earlier
> message "I need to make some patch connections and check this out" ... Once upon a time
> I had patchage and pulseaudio co-existing, on some box. I'll be darned if I can figure it
> out, at a glance. It will take a little digging.
> 
> the "realtime/non-realtime" mode message MUST come from STARTING qjackctl with jackdbus running.
> I've chosen not to start qjctl same at this time in an attempt to simplify the debugging.
> 
> hope this is clearer. the ps -aux also helped, yielding the full path executable. I'm off to try
> and figure out what qjackctl.real is, and does.
> 
> --f
> 
> p.s. I'm aware that the attachments will get filtered by the list server.