auto loading preset with wildcard

[funny0facer]

Is there a way to use wildcards when autoloading presets? Everytime, I log out and in again, the number of alsa_output.pci-0000_12_00.6.analog-stereo.2 increases by 1.

I tried to add a wildcard (*) at the end of the name, but it was not successful

Is there a way to use a wildcard in the device name?

thanks!

[wwmm]

Honestly I am not sure if it is doable. We do check if the name contains the bus id from the device that went through routing changes https://github.com/wwmm/easyeffects/blob/b26f456cfc4f8035d2c513cbbee842ab9cd03f4e/src/application.cpp#L162C100-L162C106. But I am afraid that in a system with 2 or more soundcards a wildcard approach may get the wrong device.

As PipeWire is right now the autoloading is a little tricky to do. We have to listen to routing changes in device objects. But what the user actually selects are what are called node objects. When the routing changes we have search through the node list and finding which is the corresponding device.

[funny0facer]

I can confirm. I just switched back to pipewire-media-session and the behavior is gone.
it is just "alsa_output.pci-0000_12_00.6.analog-stereo" now.

[violetmage]

@funny0facer Thanks for the help

Will definitely have to do some more investigating when I have time.

[wwmm]

I can confirm. I just switched back to pipewire-media-session and the behavior is gone. it is just "alsa_output.pci-0000_12_00.6.analog-stereo" now.

I would never have suspected wireplumber. If installing the legacy session manager fixes it it is worth to open an issue at wireplumber's page asking about if this is the expected behavior or a bug.

[funny0facer]

created a ticket there. If you want to follow: https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/669

[wwmm]

created a ticket there. If you want to follow: https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/669

Thanks! I've enabled notifications for messages there so I can see what they say.

[funny0facer]

Nevermind, I found a good enough workaround by renaming the node.name by myself with wireplumber rules.

monitor.alsa.rules = [
  {
    matches = [
      {
        device.name = "alsa_card.pci-0000_12_00.6"
      }
    ]
    actions = {
      update-props = {
        device.description = "Motherboard"
      }
    }
  },
  {
    matches = [
      {
        node.description = "Motherboard Analog Stereo"
      }
    ]
    actions = {
      update-props = {
        node.name = "alsa_output.pci-0000_12_00.6.analog-stereo"
      }
    }
  }
]