Volume config uses Pulseaudio port name instead of description

[milaq]

Volume config uses Pulseaudio port name instead of description

[mikelward]

Sorry this broke you @milaq

From memory, I couldn't find a way to change the description that would persist logouts/reboots.

Trying pavucontrol just now, the UI seems to only support renaming the port, not changing the device description, and it doesn't work with Pipewire on my system.

But I'm fine with reverting.

Thanks

[milaq]

That's correct.

Maybe an option to switch between both behaviours in i3status.conf would be worth a future implementation.
What also could be an option is to combine device description and port name or even exposing both entities as variables in the config so that every user may decide on their own which one takes priority or even combining it in a appropriate string themselves. E.g.:

format = "Vol: %devicename/%deviceport %volume"

For now though, I deem the use-case very narrow as most people switch between distinct PA sinks.
Furthermore with modern audio backends like PipeWire, port renaming is not as straightforward as device description renaming.

[johannesneyer]

I have the same problem, both of my devices are named Speakers now. PipeWire allows changing the device description property but I did not find a way to change the port description.

[milaq]

Same for me.

Ever since I used Pipewire with both pipewire-media-session and Wireplumber, the port ID renaming is not as straightforward as changing the device description, even impossible in some configurations.
Furthermore, in pavucontrol, when assigning output/input devices, the port name does not show up, only the device description.

For a streamlined behavior, as the device description is shown in many places around the OS, I think it'd be best to revert.

@mikelward Thanks for your reply and understanding. Pavucontrol does not work in every regard with PipeWire. But you may automatically change the device description based on rules. This also persists reboots.
For Wireplumber see https://wiki.archlinux.org/title/WirePlumber#Changing_a_device/node_property

Personally I use something like this

rule = {
  matches = {
    {
      { "alsa.card_name", "matches", "Xonar DGX" },
    },
  },
  apply_properties = {
    ["node.description"] = "Headphones",
  },
}
table.insert(alsa_monitor.rules,rule)

rule = {
  matches = {
    {
      { "alsa.card_name", "matches", "Yealink*" },
    },
  },
  apply_properties = {
    ["node.description"] = "Yealink",
  },
}
table.insert(alsa_monitor.rules,rule)

rule = {
  matches = {
    {
      { "api.alsa.path", "matches", "iec958*" },
    },
  },
  apply_properties = {
    ["node.description"] = "AVR",
  },
}
table.insert(alsa_monitor.rules,rule)

You may customize the dev description based on various sink or source attributes.
You may inspect them with:
wpctl status and wpctl inspect <num> respectively.

[milaq]

I just created a revert PR for the discussed behavior.
Thanks to everyone for their input.

[johannesneyer]

But this still does not work on computers where all you want is switch between ports right? Like on a laptop where the speakers and headphone jack are on two different ports on the same device.