I currently have to switch manually each time I plug my HDMI cable. It's a cumbersome manual process that should happen automatically when HDMI cable is plugged in: - When HDMI cable is plugged in -> switch to Digital Stereo (HDMI) output profile - When unplugged, switch back to previous profile or to Analog Stereo Output Note that I am talking about the _profiles_, on the _same_ audio card.
The fix for bug 93946 should fix this bug too. I'll mark this bug as depending on 93946 (there's no inherent dependency, but otherwise I probably won't remember to mark this bug fixed when the other bug gets marked as fixed).
http://www.intel.com/support/motherboards/desktop/wizards/NUC_multi-display/ What will happen when user connect two or three hdmi?
I noticed that pavucontrol recognizes that a hdmi cable is plugged in and appends that information to the profile line in the GUI. Based on that already recognized event, the system should just switch the profile (and back to previous profile when unplugged). Raymond, I do not have the case of more than one hmdi plugged in but wouldn't it be logical to switch to the profile managing the latest hmdi port plugged in?
when you have two or more display, they are most likely permanently connected, those display ports are daisy chained
(In reply to quentin.denis from comment #0) > I currently have to switch manually each time I plug my HDMI cable. It's a > cumbersome manual process that should happen automatically when HDMI cable > is plugged in: > - When HDMI cable is plugged in -> switch to Digital Stereo (HDMI) output > profile > - When unplugged, switch back to previous profile or to Analog Stereo Output > > Note that I am talking about the _profiles_, on the _same_ audio card. Those nuc only has headset, hdmi and display port. Do it mean it will switch back to analog even when headset is not plugged?
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/523.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.