Pulse changes in 20.04 strange with jack bridge

[wolftune]

I'm on KDE Neon 20.04 now. When pulse starts, it now defaults to built-in hardware instead of the jack bridge. But the bridge is available to choose right in the UI. In cadence, when I click "stop" on Pulseaudio, it immediately starts itself again but again has the non-jack output and input settings.

This is probably a pulse or Jack upstream issue, but can you confirm that or direct me to where I should report / request this work differently? Or is this something Cadence could handle by somehow adjusting pulse to choose the Jack bridge?

[jonpatterns]

What happens if you set the jack sink/source the 'fallback' out/input device? (this is set using the tick symbol, top right of device in pauvolume).

[wolftune]

@jonpatterns I don't have pauvolume, what's that? I don't see any place where I can set the fallback.

EDIT: Ah, I installed pavucontrol-qt (the non-qt version would work too) and I found the option you refer to. Unfortunately, that doesn't resolve things. The original behavior I described remains.

[jonpatterns]

This will list current default device (indicated by '*'):

pacmd list-sources | grep -e 'index:' -e device.string -e 'name:' -e 'available'
* index: 1

This lists some of the default behaviour:

pactl list |grep default

[wolftune]

aha! that indeed shows:

  * index: 3
        name: <alsa_input.platform-snd_aloop.0.analog-stereo>
                device.string = "front:1"
                analog-input: Analog Input (priority 10000, latency offset 0 usec, available: unknown)

and

$ pactl list |grep default 
        Name: module-default-device-restore
                module.description = "Automatically restore the default sink and source"

I don't know how to turn off that restore setting or how to change the default