15 Feb
2016
15 Feb
'16
8:53 p.m.
On Mon, 15 Feb 2016, jonetsu(a)teksavvy.com wrote:
At boot time means before session start, which means by some other user
than you :)
You may mean at session start which is different than at boot. Look for:
/etc/xdg/autostart/cadence-session-start.desktop as a place this might
happen. If that is so you should be starting and changing jack params in
cadence not qjackctl. The Cadence autostart can be disabled by running
Cadence and unchecking the box just below Stop on System tab.
--
Len Ovens
www.ovenwerks.net
There's an obvious conflict in execution between
the jackd that gets
launched at boot with the -p256 option, and the stored configuration in
qjackctl that shows buffer size 128.
Jack is not launched at boot. It would not work if it was as it would be
owned by root.
My suspicion goes around pulse audio since the pulse
jack sink is
activated. An emacs grep-find through all /etc/ and its subdirectories
PA does not start jackdbus, it just detects if it is running. Seeing
jackdbus -auto as a process does not mean it is "runnning" BTW. run
jack_control status to see.
only reports two instances of the string
'jackd', in limits audio.conf
and default.pa (that one being jackdbus). Still a mystery where jackd
gets launched, where are the parameters stored. And, why aren't the
qjackctl params observed (where would these be stored ?)
Do you have Cadence installed? it may start jackd (or jackdus) at session
start (not boot).
The pulse jack sink allows use of, for instance vlc
and firefox for
audio output.
Yes it does, I use it here.
In general,
starting JACK at boot time is a mistake.
Why would that be ?