27 Dec
2018
27 Dec
'18
11:41 p.m.
On Fri, 28 Dec 2018, Nedko Arnaudov wrote:
Not true. For years I have the same setup on different Linux computers:
- "autospawn = no" in /etc/pulse/client.conf
- "load-module module-jack-source" and "load-module module-jack-sink"
in
/etc/pulse/default.pa
- A shell script running under my userid started by my desktop
environment that starts jackd and then pulseaudio
(Alternatively you can start qjackctl that starts jackd and
pulseaudio)
That means jack is my main audio system and always active. Pulseaudio is
always active, too.
Therefore,
Do you have a suggestion how I should approach the startup of these
daemons.
To my knowledge PulseAudio works better with jackdbus over D-Bus
than with jackd. I'm even surprised it works at all with jackd. After
all jackdbus is "jack server" that can be autolaunched, controlled and
monitored over D-Bus :)