On Tue, 26 Feb 2013 20:28:21 +0100, Håken Hveem
<480...@bugs.launchpad.net> wrote:
> I have the same problem with Pulseaudio blocking access to the
> soundcard, so jackd does not work from the box.
>
This bug was about qjackctl blocking pulseaudio, not PA blocking jack.
There is in fact a bug
I have the same problem with Pulseaudio blocking access to the
soundcard, so jackd does not work from the box.
Jackd error output:
Tue Feb 26 20:01:59 2013: Starting jack server...
Tue Feb 26 20:01:59 2013: JACK server starting in realtime mode with priority 10
Tue Feb 26 20:01:59 2013: [1m[31m
Using the following guide I have managed to configure my system (Ubuntu
10.04) so that jack restarts PulseAudio so that sound from PulseAudio
clients is routed through jack. It works marvellously.
See http://sync-signal.com/2009/12/configuring-jack-and-pulseaudio-on-
ubuntu-9-10/
In summary:
1.
Is this an example of a bug which becomes much easier to fix now that
jackd has been moved into "main"? That is, many things, including
PulseAudio, have code to be able to run "on top of" jackd in the sound
stack, but that code could not be enabled when jackd was not in the
"main" repository. If Pu
Looks like this issue actually consists of 2 parts:
1) jackd takes total control over a device. This is desirable for
performance reasons, but leaves non-jack-aware apps (like pulseaudio
applications) out in the cold. The ideal solution would be to include
module-jack-sink in pulseaudio and switch
Good point. Moving back to triaged, as I'd forgotten about the
pasuspender call. I'm not sure how we can set up the packages in a way
that works well for all use cases without being able to compile pulse-
jack: suggestions welcome.
** Summary changed:
- Alsa not working while jackd is running
+
