Presets Autoloading doesn't work with Pro Audio virtual devices

[edwloef]

EasyEffects Version

7.1.0

What package are you using?

Arch (easyeffects)

Distribution

Arch Linux

Describe the bug

When switching between different virtual sinks created through the pipewire Pro Audio profile, preset autoloading doesn't work between them. umc404hd_setup_outputs.conf Switching between the speaker and headphone outputs doesn't change the loaded preset.

Expected Behavior

Switching between the headphone and speaker output changes the loaded preset.

Debug Log

log.txt pw-dump.txt

Additional Information

No response

[violetmage]

afk for today, but I noticed that your speakers don't have a profile associated with them. If you assign them a profile as well, does the switching work then?

[wwmm]

The autoload relies on PipeWire notifying us about device routing changes. That is what we show in the profile field if I am not mistaken. I do not know if PipeWire implements routing on virtual devices.

Doing the autoload based on the node name does not work on many devices. So we do not use it.

[edwloef]

afk for today, but I noticed that your speakers don't have a profile associated with them. If you assign them a profile as well, does the switching work then?

How would I go about doing that in pipewire.conf?

[violetmage]

Sorry, reread my last post; I meant to type preset, instead of profile.

[wwmm]

I had time to look at you pw-dump output now. What you have isn't a virtual device in the usual meaning if the word in PipeWire's context. You just have your soundcard in the Pro Audio mode. At this moment our preset autoloading code does not work with the Pro Audio mode because PipeWire does not configure routing for them by design. They have intended the Pro Audio mode for a very different use case.

I think I will have to do some serious redesigning of our code to make the autoloading work when cards are in the Pro Audio mode. But I have no idea about when I will have time for this. Do you have a special reason to use the Pro Audio mode?

[edwloef]

Sorry, reread my last post; I meant to type preset, instead of profile.

The preset is just named "None" since it doesn't contain any effects.

[edwloef]

I had time to look at you pw-dump output now. What you have isn't a virtual device in the usual meaning if the word in PipeWire's context. You just have your soundcard in the Pro Audio mode. At this moment our preset autoloading code does not work with the Pro Audio mode because PipeWire does not configure routing for them by design. They have intended the Pro Audio mode for a very different use case.

I think I will have to do some serious redesigning of our code to make the autoloading work when cards are in the Pro Audio mode. But I have no idea about when I will have time for this. Do you have a special reason to use the Pro Audio mode?

I just use it to split the four inputs and two outputs of my audio interface: https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Virtual-Devices#behringer-umc404hd-speakersheadphones-virtual-sinks Since my headphones need EQ and my speakers don't I'd like for it to automatically switch when I switch audio output.

[LebedevRI]

Question: is the current preset autoloading supposed to only trigger when EE is already running and something changes, or should the preset also get autoloaded when EE first starts? I'm guessing it's the latter? In which case i guess i'm also seeing this.

[wwmm]

Question: is the current preset autoloading supposed to only trigger when EE is already running and something changes, or should the preset also get autoloaded when EE first starts? I'm guessing it's the latter? In which case i guess i'm also seeing this.

On my computer the autoloading is applied in EE initialization too if there is an autoloading profile for the device EE is using as output.

And the limitations for the Pro Audio profile still applies as far as I am aware.