-
-
Notifications
You must be signed in to change notification settings - Fork 519
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
Master issue: Missing sessions when audio device, session enumerator, etc. are invalidated #1305
Comments
#846 is also describing the same issue. |
@lockcole Perfect, thanks! |
Is issue #574 also related to this? |
Yup, good eye @HydrantHunter! |
I made sure to mark that one with |
Thank you, @riverar - hopefully the workaround is of use to others, even if it is just to avoid the relatively minor effort of restarting EarTrumpet. Apologies for the ping, but it looks like you linked to this issue (1305) rather than 574 on the list above. |
Fixed, thanks again. |
Thanks for linking this issue here, and also I've forgot to mention that the spatial audio software keeps switching to off on all devices connected while using after restarting. |
Hi,
|
This bug is still a thing, also the workaround in #574 may not work anymore, it was working for while but suddenly wont work now. I think due to permissions in the WindowsApps folder |
Sorry for asking, but is the team making any progress on this issue? |
…plications disappear when users login back after user switching. The workaround try to detect user re-connecting to its login session and do a refresh (delete and re-create) its device list.
@Beet4 Don't be sorry, it's been a long time without an update. My focus was on moving the entire project to .NET 8+ (done in |
Tracking issues related to our mishandling of scenarios where the audio device, session enumerator, etc. become invalidated. The "turn everything off/on again" procedure we need to implement is documented at https://learn.microsoft.com/windows/win32/coreaudio/recovering-from-an-invalid-device-error.
#483
#529
#574 (contains workaround)
#587
#814
#846
#848
#902
#940
#977
#1049
#1072
#1131
#1252
#1281
#1314
#1329
#1339
#1384
#1407
#1487
#1533
The text was updated successfully, but these errors were encountered: