3 Oct
2016
3 Oct
'16
11:50 a.m.
Hi Bill,
I guess you're running pulseaudio per default (or you desktop
environment - from your description, I'm guessing you're using gnome).
Running Qjack (jack) then exculsively grabs the audio device and
prevents pulseaudio from accessing the device directly.
Take a look at jack2-dbus and pulseaudio-jack (package names may vary
depending on your distro). In the end, you'll need to configure
pulseaudio to use jack as sink when this sink becomes available. On
archlinux, pulseaudio is already configured in a way that should create
a jack-sink when you run jack-dbus.
The pulseaudio module "module-switch-on-port-available" is helpful to
automate the switching part. You also need to tell qjackctl to utilize
jack-dbus (use jackstart as "Server prefix" and enable the "D-Bus"
interface in the "Misc" panel of qjackctl).
Good luck!
Mathias
On 09/27/2016 11:19 AM, Bill Purvis wrote:
Hi, I set up my laptop to initiate Calf Plugin
(Fluidsynth) and Qjackctl
at login.
When I then login, I get no sound from various apps. The
preferences->Sound->test sound
also produces nothing. Running Totem, just hangs - no output and the
progress bar stays at 0.
I've now disabled Calf and Qjackctl at login and it all works again. Can
anyone explain
what is going on?
Output from aplay -l:
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
(this is with it working, but it looked the same when not working)
Thanks,
Bill