Hi,
I was used to switching between laptop speakers and Bluetooth speaker on the normal audio menu.
But one day, I needed to use a TV's speakers through HDMI, and couldn't find it, so I initially thought it was a driver issue, but never found a fix, so I had to use a friend's Windows laptop at the last minute because people were waiting to watch something.
Today, months later, I have the same issue, but on a different laptop with more recent hardware, so I was hoping to have better luck, and I didn't... Until I accidentaly notice that the HDMI device is available under a submenu of the laptop's speakers, WTF ?
Attached to this post is a screenshot showing a Bluetooth speaker, the laptop's speakers and HDMI speakers. Why isn't the latter available at the same location as the former two ?
The submenu could be kept for selecting between 2.0/5.1/7.1, just like for Bluetooth devices it's used to select between aptX/LDAC/SBC, but I don't understand what's a whole different device doing in that submenu of the laptop's speakers.
Thanks
I understand what you're getting at, but I feel like that's doing a disservice to plasma. They absolutely can (software!) display what they want, but it would require a paradigm shift.
I've struggled with this sort of thing for many years. Multiple audio devices (switching between speakers/headphones/headset), complex input/output schemas (e.g. audio passthrough for a console mixed with the podcast on my PC, or from the endurance race on a Chromecast (obligatory "π peacock") mixed with the game I'm playing on the PC), echo cancellation between various sources and the selected output, etc.
Audio management is complex, but I think OP is getting at one of the weaker points in "year of the Linux desktop" adoption.
I'm managing only because I've spent so much time figuring things out over nearly 20yrs of Linux use. My setup is currently a combination of plasma (I think the app is just "volume"), qpwgraph, and individual app settings.
The thing is : I want my laptop to never have sound when using speakers, but always when connecting anything, e.g. Bluetooth or HDMI.
So, I mute
Built-in Audio Analog Stereo, but I don't muteTurn It Up Wireless Speaker: then, when I connect the latter, it has sound, but when I disconnect it, the former stays muted, therefore I never risk being surprised by sound.Except, when I need to use HDMI, I actually have to unmute
Built-in Audio Analog StereobecauseDigital Stereo (HDMI) Outputis considered to be the same item by Linux, therefore when I unplug it, it turns back toBuilt-in Audio Analog Stereobut stays unmuted, which leaves me at risk of being surprised by sound.Yeah, I can see how it would be confusing. Your internal sound "card" is managing several outputs (profiles) and settings are per device rather than profile.
I'm sure there's a way to detect the HDMI plug/unplug and script an action to un/mute the audio. If you're connected to the other external speaker, that action could be confused, so you'd have to account for that.
I'm not expert in that department, but udev is where I'd start.
Here's a link to someone trying to trigger action on HDMI events that could get you started down the right path: https://forums.raspberrypi.com/viewtopic.php?t=343614