[LAD] should JACK programs autostart the server?

Rui Nuno Capela rncbc at rncbc.org
Thu Sep 20 16:48:45 CEST 2018

On 2018-09-20 13:02, Fons Adriaensen wrote:
> On Thu, Sep 20, 2018 at 03:30:31AM +0000, bill-auger wrote:
>> the debian maintainer of freewheeling suggested that it should
>> autostart the server if it is not running (change JackNoStartServer to
>> JackNullOption)
>> i have my opinion; but i am interested in others
> Definite NO.
> People who suggest autostarting usually don't understand what
> Jack is and how it is used.

may i add my 2-point not-so-extreme-stance-of-sorts?

there it goes:

a. jackdbus *do* auto-start the jack-server if not already running;

b. legacy jackd *do* auto-start exactly what's in "~/.jackdrc" file; 
fwiw. i do have this "/absolute/path/to/qjackctl --start" in there, so 
that qjackctl pops up whenever a(ny) jack client application is called 
;) (*)

both of the above scenarios are summoned as soon jack_client_open() is 
called *without* the JackNoStartServer option set.

rncbc aka. Rui Nuno Capela

(*) ps. i often test over recent jack2/jackdbus "enabled" distros (read 
ubuntu, debian, whatever) and as a matter of fact the .jackdrc "hack" 
seems to work there too; that is, qjackctl pops up whenever jack-server 
is called in; even though it's configured to talk with jackdbus 
service... advantages to that bizarre situation goes like the 
jack/pulseaudio bridge becomes fully "automagic" then, as to a full 
desktop UX ootb. ;)

More information about the Linux-audio-dev mailing list