-
Notifications
You must be signed in to change notification settings - Fork 767
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
Unable to expand Audio Device Selection dialogue #3921
Comments
Same issue, windows10 version 2004. |
How do you access the Settings menu? I don't see any way to access it. |
Also experiencing this issue suddenly where it had been working previously. I'm not sure when the issue started, as I don't usually go check the audio device output selection. Playback is still working but I'm unsure which of the two devices are being used. |
I just did a fresh windows install and I am having this issue also. I even tried copying in old config settings in appdata but audio still comes out wrong device. |
Checklist:
I have checked that there are no issues with similar or the same content
YOU SHOULD CHECK CLOSED ISSUES AS WELL
[X ] I have checked the FAQ (https://github.com/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-/wiki/FAQ) and the answer I am looking for is not there
[X ] I have double checked and can reproduce the issue
debug_info.zip
OS:
Windows 10 20H2
GPMDP Version:
4.7.1
Issue Descriptions:
While using the app, I am unable to select the Audio Output Device the app will use, as the Devices list never loads and I am unable to expand the dropdown menu, resulting in GPMDP to use the system default
Steps to Reproduce:
With my situation I only have to just go to the Audio Device list and try to use it at all, I have tried restarting and re-installing GPMDP and manually setting the desired output device in the
.settings.json
fileI am unsure if this is happening on other systems or if it's just a really bizarre edge case.
This happens on a completely fresh install of GPMDP and persists after restarting Windows.
The text was updated successfully, but these errors were encountered: