19 Dec
2018
19 Dec
'18
2:31 a.m.
Hi all.
I'm running jackd1 (0.125.0) on debian 9 (stretch) and its
"auto-starting" facility works perfectly whenever I use jack-play. I
now want to use pulseaudio-module-jack, but "pactl load-module
module-jack-sink channels=2" fails (the command returns "Failure:
Module initialization failed" and I see "jack_client_open() failed" in
the journal).
Is this a bug, or is it "intended/expected behaviour"? (I don't
understand how jack-play starts jackd1. Is it dbus magic, or something
else?)
Many thanks, Jaime
20 Dec
20 Dec
1:07 p.m.
On Wed, December 19, 2018 3:30 am, Jaime T wrote:
I'm running jackd1 (0.125.0) on debian 9 (stretch)
and its
"auto-starting" facility works perfectly whenever I use jack-play.
I am not positive I remember the details correctly, but I believe the auto
start behavior is a function of the application, not the jackd server.
now want to use pulseaudio-module-jack, but
"pactl load-module
module-jack-sink channels=2" fails (the command returns "Failure:
Module initialization failed" and I see "jack_client_open() failed" in
the journal).
Perhaps pulse expects jackd to be running when the module loads. You may
have to start jackd manually, or switch to jackd v 2.
understand how jack-play starts jackd1. Is it dbus
magic, or something
else?)
Something else, jackd v2 has dbus support, jackd v1 does not. I believe
that applications are supposed to check ~/.jackdrc to determined the
desired default command line for the non-dbus version, I'm not sure how an
application would determine if the dbus version was available. I guess it
could try starting the dbus version first, and if that did not work look
for a .jackdrc command, and if that was not available start jackd and
accept the default behavior.
--
Chris Caudle
1948
days inactive
1949
days old
jackaudio@lists.linuxaudio.org
1 comments
2 participants
participants (2)
-
Chris Caudle -
Jaime T