You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I set up jack-pulseaudio bridge using cadence by following the wiki.
When jack is up and running, supercollider(which uses jack) plays audio, so I guess it means jack works fine, but then I can't play youtube in firefox, the youtube player pauses and shows something like "can't play on device".
If I use bluetooth headphones, then run jack, then jack plays on laptop speaker and youtube plays on headphone.
I wonder:
Does this happen because each device(like the speaker and the headphone) must be owned by either jack or pulseaudio but not both at the same time even with bridge? Are these expected behavior?
If yes, well, I initially thought the bridge would let jack send audio(from supercollider) to pulseaudio, then pulseaudio collects audio from jack and other programs(like browser playing youtube) and send it all to a single device, so everything from both jack and pulseaudio could play on same device. Is such setup possible?
The text was updated successfully, but these errors were encountered:
From your description, I can not really conclude that this is a problem with JACK.
In fact, this sounds to me more like your applications use the ALSA PCM devices directly and only one device can use a hardware device at a time.
Usually if you want to use JACK with an application that supports JACK and ALSA, you have to either start JACK first and or configure the application to actually use JACK.
I set up jack-pulseaudio bridge using cadence by following the wiki.
When jack is up and running, supercollider(which uses jack) plays audio, so I guess it means jack works fine, but then I can't play youtube in firefox, the youtube player pauses and shows something like "can't play on device".
If I use bluetooth headphones, then run jack, then jack plays on laptop speaker and youtube plays on headphone.
I wonder:
The text was updated successfully, but these errors were encountered: