-
Notifications
You must be signed in to change notification settings - Fork 421
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
0x888900A (Unknown Error) #56
Comments
Some players like Spotify or Chrome's HTML5 do not like when you try to switch audio devices while playing. In these cases, playback must be completely stopped before you can switch audio devices, or you risk losing all audio output from that player. That is not Audio Router's fault, it is their implementation's fault. But Routing Pending being stuck after that is indeed a bug. |
It gets better. I'm not even PLAYING anything even after restarting, and I still get that bug... the only reason why this ever happened was because I had an issue with VoiceMeeter... I haven't been able to properly stream because of this and I need this routing to succeed... |
Could your output be in exclusive mode by any chance? The error code is signaling a DEVICE_IN_USE - it tends to happen with either primarily ASIO devices rejecting WASAPI connections, or with WASAPI devices being in exclusive mode. |
@Discookie I've removed Exclusive mode from all of my I/O, And it appears to have worked. Hats off to you. It's something I'd never have tried until you've mentioned it. |
Anyone who has this issue, please use @Discookie's comment. Thank you. <3 |
Routing functionality may not be available until target process restart.
^ To be clear, I've restarted spotify countless amount of times, and when I try to reroute again, this happens... Please fix.
This is very frustrating!
Update: (Routing Pending) WHAT PENDING DOES IT NEED TO DO!?
The text was updated successfully, but these errors were encountered: