Ubuntu
jack-audio-connection-kit package

  1. Bug #480103
  2. Comment #3

Comment 3 for bug 480103

Revision history for this message
Emmet Hikory (persia) wrote : Re: Alsa not working while jackd is running

OK. I understand now. ALSA is working fine, but totem isn't able to get to the output channels. More specifically, jack is controlling the card directly, so other clients cannot use it. Totem may be attempting to send data to alsa, or to pulseaudio, or to gstreamer, or even to xine, depending on how it is configured. None of these will allow it to access the sound card controlled by jack.

The workaround for now is to use two audio interfaces: have JACK control one, and leave the other for general sounds (probably managed through pulseaudio).

In the future, it may be that JACK interfaces for gstreamer or pulseaudio can be built that would allow this to work.

I'm marking this "Won't Fix" against the jack-audio-connection-kit package, as there is nothing in JACK that will change to support this feature. There are outstanding bugs to address some of these issues, but they may not completely address them (needs testing), and in any case, are not yet available.

If this issue persists in 10.04 after release, please file a new bug against totem (or other specific affected software) requesting that they be made to work with JACK.