Re: Jack Bridge 4.01.7z
Sharolyn Uriegas
Hmmmm. I see that somewhere you use the command "load-module module-jack-sink". I use that to route Jack --> Pulse so I can see Jack's stuff in apps that use Pulse, like pavucontrol (Pulse's mixer). Not the other way around, i.e. to see Pulse's stuff in Jack. Confusing, isn't it?
I am under the impression that you actually want to do just that: see Pulse's stuff in Jack (i.e with qjackctl). I don't think that's going work. I don't think that Pulse --> Jack will work your way. As a matter of fact I don't know if there's a way to do that at all...
im also on mx-linux 21. If you are trying to get the whole jack and pulse thing going (sorry i only skimmed through your post, I have a narrow attention span at the moment ) , I'd like to share my settings which i've set once after install and never had any issues since. I use reaper and before launching anything, I launch qjackctl. When done and exiting reaper , I quit qjackctl so to utilize pc native sound ports. ( I don't need studio monitors for anything other than music production).
Installed are:
qjackctl
jackd2
pulseaudio-module-jack
a2jmidid
As a matter of fact, pacmd set-default-sink jack_out routes PulseAudio output to Jack.
In Qjackctl, this gives a "PulseAudio JACK Sink" plug with stereo output, which you can then connect to a Jack application. All pulseaudio sound is routed through this stereo plug. There are no individual pulseaudio application outputs. For that you'll probably need Pipewire.
On my (linux mint 20.2, qjackctl 0.9.7) system manually invoking pacmd is not even necessary anymore though: just installing pulseaudio-module-jack is enough to get both the PA JACK Sink and PA JACK Source available in Qjackctl.
If Pulse+Jack can be setup so easily just by installing pulseaudio-module-jack, and running qjackctl with jackdbus enabled, who cares about 'the most experienced and demanding users of JACK' dissuading it, if it works just fine that way?
Thanks for clarifying, this is exactly what I wanted to do and I'm doing this for years now without any issues. I used Cadence in the past where it is set up automatically, but now I'm using Qjackctl.
yeah, that was absolutly not my point.
My point is, that from my view here, pipewire seems so much more advanced then pulse audio, that it is clear for me, that you want to ride a dead horse.
Take the long way home
If you've switched it back to PA Jack Sink in Pavu, try the same experiment again, but without changing any pulseaudio settings yourself anymore. The behaviour you describe occurs on my system only if I f-ed around in pulseaudio's settings. If I then reselect Jack Sink in the pulseaudio settings, all works again as long as I don't f* around with pulseaudio settings anymore.
After which there is no sound when I run jack, and spotify says it can't even play any sound. I guess I should revert that.
pavucontrol looks like this (I have tried to leave the top-most device both muted and unmuted), and both devices are completely silent.
At some several points during all my attempts, there was only a "Dummy output" here, but a reboot would 'fix' that.
Invariant through all these different runs, Xruns keeps going up, whether there is any sound or not.
It looks like in Cadence your Device/Interface (greyed out by the look of it) is an analog device and I'm guessing that that's probably why you're getting loads of xruns since the CPU can't process the analog.
From ALSA alone, without JACK and Pulseaudio, what is your default sound card?
Do you get the same quality audio when you run speaker-test -c 2?
I'm pretty sure 2 is the one I'm using then. It's the one I should use for output.
What's the problem with an analog device? I tried to change it to the Digital entry in the dropdown list but then Jack fails to start. Logs:
> Do you get the same quality audio when you run speaker-test -c 2?
Yes and now I hear clearer what is actually happening. It sounds like it's rapidly altering between volume 100% and volume 0% (perhaps at 10 Hz).
It's good idea to see what output you get with speaker test using ALSA alone just to make sure your ALSA is using the default card you intend to use, and that the sound is OK.
You should be able to kill pulse and restart as you wish. Try killall pulseaudio. You might need to find out what's spawning it automatically.
From `aplay -l` it seems like Generic is card number 1. Why does aplay -L say "default:CARD=Generic" though? If it was default why would I have to specify it on speaker-test?
How can I find which card ALSA uses now (which does not work)?
The default card with the pulseaudio-alsa config tries to invoke a pulse server. but reads weird that it tries to invoke a dmix. FWIW, what is your end goal here? The mentioned applications so far don't really benefit from jack and you are introducing a lot of complexity for potentially little gain. Generic is also often a strange default codec to have what do you get for
I'm installing JACK so that I can use Ardour and produce sounds and music. I want it to play well with other apps like Firefox, Spotify and Discord, so that's what I'm testing first, and that's why I need Pulseaudio as well.
In that case it's probably best to concentrate in having ALSA and JACK working together first then adding Pulse later.
I won't worry about your snowball for now. It's important you get ALSA right with the correct sound card. When your JACK is setup properly later on, it will be easy to add devices, including the snowball.
Now that snd_hda_intel is set to index 0, that should be the default card. What is the output of the simple speaker test?
I have no idea how to read the systool output V1del suggested by the way.
but all of that is just skirting around the underlying issue. If you now start jack, therefore without the pulseaudio bridge/support, do you still get warnings/xruns? For the realtime permissions to be properly set up it should probably be sufficient to install the realtime-privileges package (and rebooting/relogging at the least)
ALSA + Pulseaudio thus works together now (at some point it didn't, before I copied back the old asound.conf and .asoundrc). And when I try to start JACK through Cadence with the pulseaudio bridge, then it all seems fine: no Xruns, and I can see volume bars moving in pavucontrol. However, I don't hear any sound.
Then, under the Playback tab, I tried to change the output device(?) of Firefox from "Jack sink ..." to "Family 17h ..." which is what normally outputs sound I think. But then Firefox cannot output sound anymore (video stops playing).
I'm not sure how I'm supposed to do this.
Here is a screenshot from Catia if it helps:
Double check in cadence that the pulse sink that's connecting to your jack daemon is being routed to the correct card (ah wait apparently you did that, does refreshing the firefox tab after doing that help?). I'd completely expect that switching the sink to the "usual sound producing family sink" will not produce sound anymore, because jack is now handling that device. Maybe post during that situation
The screenshot from Catia shows the default configuration (I didn't touch anything). I don't know how to ensure that it's routed to the correct card but if you think the routing in Catia looks good would that be sufficient?
Refreshing tab or restarting Firefox does not help.
(inadverently) restarting pulseaudio has _some_ effect: in pavucontrol there is now only the "Jack sink" output device, not the Family one.
(what really happened was: In Cadence I pressed "force restart", after which pulseaudio stopped working so I had to kill it and restart it, after which I could "Start" JACK in Cadence)
Edit: as it is a less common situation where I have to force restart pulseaudio, this is the output after I reboot, start firefox, play a song, start JACK through Cadence, and set the output sink of Firefox to the Jack sink. Quite a lot more verbose, as it usually has 2 sinks:
Minimize (or even eliminate) lane closures around the construction zone by using Travelift to straddle traffic and operate within very narrow aisleways. Travelift gives you the speed you need for faster bridge construction, widening and reconstruction projects, rewarding you with higher profit margins, and making work and travel safer and faster for workers and commuters alike.
Whenever I launch hydrogen it breaks my audio in all other applications which use Pulse, for example, I can no longer play videos in Chrome after having launched Hydrogen once, until I restart my PC or do sudo alsa force-reload. I have found people with similar issues, but no actual guide to fix this, often there are links to _and_jack (which has moved to _and_jack.html )I am using Ubuntu Studio 14.04 64bit.
And that's it. Pulseaudio will recognize (through D-Bus) that JACK started, and automatically will route audio to it. When JACK is stopped Pulseaudio will revert to normal routing and start sending audio directly to card again.
A complicated way to use Jack and pulseaudio software at the same time is to install "pulseaudio-module-jack" (also install qjackctl (gui for jackd) and pavucontrol if not present). Restart pulseaudio pulseaudio -k.
Now close audio apps (Jack and pulseaudio),
run jackd using qjackctl (click start button) (dbus option must be selected in qjackctl settings last tab).
In Pavucontrol "output device" tab, clic green "default device" button near "jack sink"
Now pulseaudio software and Hydrogen should run at the same time.