Skip to content

Show nick when no routes are available#58

Open
WhyNotHugo wants to merge 1 commit into
tsowell:mainfrom
WhyNotHugo:nick-without-routes
Open

Show nick when no routes are available#58
WhyNotHugo wants to merge 1 commit into
tsowell:mainfrom
WhyNotHugo:nick-without-routes

Conversation

@WhyNotHugo

Copy link
Copy Markdown
Contributor

On my laptop, with the Pro Audio configuration, wiremix shows 5 different outputs all named "sof-hda-dsp", with "No route selected". I.e.: they're impossible to tell apart.

Apparently, this is always the case with Pipewire's Pro Audio configuration: each output is its own node, and there are no routes for them.

When no routes are available, show the output's nick instead, which are determined based on the underlying ALSA description. For my same laptop mentioned above, these would show "Pro", "HDMI 1", "HDMI 2", "HDMI 3" and "Pro 31". These names aren't great, but I can tell them apart. Improving the names generated by PipeWire is a separate task which I hope to complete soon, but is merely complementary and non-blocking for this change.

@WhyNotHugo

Copy link
Copy Markdown
Contributor Author

Before:

image

After:

image

@WhyNotHugo
WhyNotHugo force-pushed the nick-without-routes branch from 8c0336a to 15af463 Compare June 30, 2026 16:39
@WhyNotHugo

Copy link
Copy Markdown
Contributor Author

v2: formatting

On my laptop, with the Pro Audio configuration, wiremix shows 5
different outputs all named "sof-hda-dsp", with "No route selected".
I.e.: they're impossible to tell apart.

Apparently, this is always the case with Pipewire's Pro Audio
configuration: each output is its own node, and there are no routes for
them.

When no routes are available, show the output's nick instead, which are
determined based on the underlying ALSA description. For my same laptop
mentioned above, these would show "Pro", "HDMI 1", "HDMI 2", "HDMI 3"
and "Pro 31". These names aren't great, but I can tell them apart.
Improving the names generated by PipeWire is a separate task which I
hope to complete soon, but is merely complementary and non-blocking for
this change.
@WhyNotHugo
WhyNotHugo force-pushed the nick-without-routes branch from 15af463 to fd14e2d Compare June 30, 2026 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant