-
-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HDMI output "forgotten" after audio hardware powers off [nVidia HDMI] #1113
Comments
Similar here. HDMI output disappearing at random until restart. I think it started after gpu driver update. |
I have this exact same issue, which has never happened before until a few days ago (I've been using SoundSwitch for a long time--it's fantastic). It's my monitor (through which I output sound to speakers) that keeps getting forgotten by SoundSwitch every time the monitor turns off. Restarting SoundSwitch resolves this temporarily. I also have an NVIDIA card through which my monitors go through. Thank you for making this fantastic app and I hope this gets fixed soon. |
Hello, Stop SoundSwitch and replace the files of SoundSwitch with the content of the zip. If that fixes the issue, I'll release it. |
That seems to have done it. I think there was also a graphics driver update in the mix, so I suspect it was an NVIDIA change, yes? Just a coincidence in the timing. Thanks for the good work. Love your program. |
Seconding dethzord. All looks good over here. The NVIDIA HDMI output now properly shows as "Disconnected" when the AVR is off or using a different input. When powering the AVR back on and switching to the PC's input, the NVIDIA HDMI output now shows as active and is able to be selected. Thanks again for the quick fix! |
## [6.5.4](v6.5.3...v6.5.4) (2023-02-09) ### Bug Fixes * **Device::Refresh:** Fix issue where the list of device wouldn't be properly refresh after new device added/removed. ([cbb7d25](cbb7d25)), closes [#1113](#1113) ### Languages * **Chinese (Simplified):** Translated Settings using Weblate ([fccb108](fccb108)) * **Polish:** Translated Settings using Weblate ([be6880a](be6880a)) * **Serbian:** Translated Settings using Weblate ([2b70f3e](2b70f3e))
🎉 This issue has been resolved in version 6.5.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
## [6.5.4](v6.5.3...v6.5.4) (2023-02-09) ### Bug Fixes * **Device::Refresh:** Fix issue where the list of device wouldn't be properly refresh after new device added/removed. ([cbb7d25](cbb7d25)), closes [#1113](#1113) ### Languages * **Chinese (Simplified):** Translated Settings using Weblate ([fccb108](fccb108)) * **Polish:** Translated Settings using Weblate ([be6880a](be6880a)) * **Serbian:** Translated Settings using Weblate ([2b70f3e](2b70f3e))
What happened?
SoundSwitch "forgets" my HDMI audio output (via NVIDIA card) after powering off HDMI devices (a soundbar, then out to a display). Rather than becoming a disconnected device, SoundSwitch no longer sees the HDMI output at all, either as selectable from the icon or as an option in settings. I would expect the output to move to a "Disconnected" status within SoundSwitch.
Upon powering back up, SoundSwitch continues to not see the output, even though sound is playing through the output. Also, if I manually change the default output via Sound/Playback, SoundSwitch will pop a notification indicating the HDMI output is selected, but still does not list it as an option. I would expect the HDMI output to return to a "Selected" status in the SoundSwitch options, as well as become available again when clicking the systray icon.
This issue may have began with 6.5.2, I am uncertain due to how closely they were released.
Do note that restarting the application restores the missing HDMI output, until again turning off the display/soundbar.
Step to reproduce
To recreate, I simply power off my soundbar and display, then turn them back on.
Version
v6.5.3
What version of Windows are you seeing the problem on?
Windows 10
Relevant log output
No response
The text was updated successfully, but these errors were encountered: