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

PrevNext  Index
DateSun, 17 May 2009 10:57:09 +0200
From Fons Adriaensen <[hidden] at kokkinizita dot net>
ToStéphane Letz <[hidden] at grame dot fr>
CcLinux Audio Developers <[hidden] at lists dot linuxaudio dot org>, JACK Developers <[hidden] at jackaudio dot org>
In-Reply-ToStéphane Letz Re: [LAD] [Jack-Devel] more jack/qjackctl madness
Follow-UpStéphane Letz Re: [LAD] [Jack-Devel] more jack/qjackctl madness
Follow-UpNedko Arnaudov Re: [LAD] [Jack-Devel] more jack/qjackctl madness
On Sun, May 17, 2009 at 09:36:12AM +0200, Stéphane Letz wrote:

> I really appreciate your feedback...,  but AFAICS Qjackctl is *absolutely* 
> not using the DBUS layer!

Then please tell what this is:  (ps -ef output)

fons      2444     1  0 10:43 ?        00:00:00 /usr/bin/jackdbus auto

Killing this makes qjackctl behave normally again,
and allows me to start the server configured in it
Setup window instead of getting a different one.

> And I guess Rui can better answer the points concerning "~/.jackdrc," and 
> son on.

Qjackctl is not involved in autostarting jackd, so I
repeat the first question:

   Which parameters are used for such an autostart ?
   Certainly not the ones in ~/.jackdrc, these would
   have been correct.

Given the usual convention of  "APPNAME" using 
"~/APPNAMErc" for default settings, why does jackd
not do this ? I know the file is created by qjackctl,
but qjackctl completely ignores the settings there,
so the file is cleary not meant for its own use.

Ciao,

-- 
FA

Io lo dico sempre: l'Italia è troppo stretta e lunga.
PrevNext  Index

1242551181.10435_0.ltw:2,a <20090517085709.GA2959 at zita2 dot kokkinizita dot net>