19 May
2009
19 May
'09
2:06 a.m.
Lee Revell wrote:
On Mon, May 18, 2009 at 11:00 PM, Patrick Shirkey
<pshirkey(a)boosthardware.com> wrote:
Further testing reveals that it's been identified as a problem for a while.
https://tango.0pointer.de/pipermail/pulseaudio-discuss/2008-November/002603…
Does anyone here know of the reasoning behind not making pulse audio
handle this process by default?
Cheers.
Patrick Shirkey
Boost Hardware Ltd
I have got a problem with pulseaudio and jack not
playing together. More
importantly I have got a problem with pulseaudio being the default sound
server and not having automated functionality to connect with jack. If
after 10 years of running Linux audio, I have issues with getting
pulseaudio to play nicely then pulseaudio is failing to meet it's main
objective of making things easy for desktop users.
I would really like to encourage the pulseaudio people who are reading
here to make pulse gracefully and automatically cede control to jack and
then auto configure itself as a jack interface.
Pulse includes "pasuspender" to handle this use case. From the man page:
pasuspender is a tool that can be used to tell a local
PulseAudio sound server to temporarily suspend access to the audio
devices, to allow other applications access them directly. pasuspender
will suspend access to the audio devices, fork a child process,
and when the child process terminates, resume access again.
I guess this should be integrated into qjackctl & friends.