Closed sneakernets closed 10 months ago
Looks really odd :thinking: No wonder from such of glitches are appear on Windows oftenly with each update.
I think I found out the problem, it's when I'm changing the output device to something that can be removed (like a Bluetooth device for example)
I think I found out the problem, it's when I'm changing the output device to something that can be removed (like a Bluetooth device for example)
I see, then, it's probably a case of RTAudio
that won't be dropped into another device automatically. With a case of PulseAudio on Linux that happens easily: the current audio output gets to be dropped into another output device if the current gets being suddenly removed :thinking:
@sneakernets , try 64bit build of OPL3-BE I made recently, it should work.
Alright, I will check this this weekend. thank you!
This has been fixed as far as I can tell. sorry for the long delay on this!
I may have spoken too soon. Same issue is happening again with Bluetooth headphones. Here are the current Reg values that are causing the crash:
I mean, I can "fix" this by nuking the registry every time but man that's a bummer. I wonder if this is a QT bug?
I guess it's a crash because the RtAudio library fails to use a non-existing audio device. I should add the check for audio device availability until to start its usage.
The question: does that happen during the workflow? Or just in a moment when you try to restart the program after you unplugged the device?
it's happening when I try to start to program after I unplugged.
Okay, the fact a thing does work on Windows 8.1 fine when I unplug my USB headphones and do plug them back, and the application does still work when I unplug my USB-headphones while the program working. I'll try to bypass the device through my USB filter into my Windows 10 VM and see the result...
It's a high change that the crash is an exception thrown by RTAudio.
The best idea is to put try-catch around audioOut->openStream
and extract the message.
Closed because of no response for a long time.
Here's the report from windows Log Viewer:
Deleting the registry keys fixed the issue. I will update this if I run into the issue again.