17 May
2009
17 May
'09
2:19 p.m.
Brent Busby wrote:
On Sun, 17 May 2009, Rui Nuno Capela wrote:
not at all. ardour and qjackctl can coexist peacefully as ever.
the original issue on debate, as brought by Fons, was due to a probable
mishap caused by the new d-bus stuff in jack2 (aka jackdmp): apparently,
jackdbus is auto-starting the jackd service without regard to what's in
~/.jackdrc. it doesn't matter whomever wrote that file in the first
place, either ardour, qjackctl or even jackd itself. jackdbus is just
making a fool out of it :)
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
otoh, the only other jack application i know of
that writes to
~/.jackdrc is ardour; have a look at your use case when starting jackd
from behind ardour's open session dialog...
Newbie question: Is it harmful to have QJackctl and Ardour both running
at the same time? Do they have to potential to fight eachother, or to
make changes to the Jack environment that will be made by one but not
realized by the other, either in regard to jackd parameters, or in
regard to the connection patchbays?