Audio Device Bug on Windows *Fixed*

After updating to Beta3, whenever I switch my windows audio device, DR does not automatically track with the switch and output the audio to the correct device.

It comes up with an error dialogue saying DR cannot find the selected audio device.

The workaround is close DR and then reopen, problem solved.

Erik

This is still an issue on DR17B3.

Erik

I switch my windows audio device

Patient: "Hey Doc, it hurts when I do this."

Doctor: "So don't do that."

Agreed, there is a bug. In my case, DR on entry is playing to the wrong audio device... it's off by one in the list of four that Windows shows on my speaker selection list. Other system sounds go to #2; DR plays to #1. If I change the system to #3, DR plays to #2.

This is what it looks like if you activate a new audio source in Windows while DR17 Beta6 is open.

Not experiencing this on 17b6, with a Sound Devices MixPre 6 II. What is your audio device? Have you made sure to select it as the default device in Windows and is it set to 24bit 48KHz for both play and record? I have an Ultrastudio Mini 4K connected as well and use an ESI Moco A/B monitor switch for Resolve/Avid too.

AudioEngine D1 is the audio device I use for playback on my Davinci Resolve software and general computer work. I turn it off each night when powering down and back on in the morning. It's when I forget to turn it on and I open DR first that I get the error.

The thing that bugs me is that all of my other software on the computer has no problem updating when I turn on the AudioEngine D1 system. Resolve on the other hand can't figure it out and I have to shut down Resolve and open it again. For large projects, this can be 10 minutes of lost time.

Erik

Can someone at BMD acknowledge this bug please? I see others on Facebook DR talking about the same problem.

Erik

Hello Erik,

Were you eventually able to solve this problem with the audio device not being found? I experience a similar issue when I connect my bluetooth headphones. I upgraded to DR17.1.1, hoping it would fix the issue but to no avail. The issue persists. I googled around and didn't find any solutions to this bug.

Thank you.
Dmitry

Hi Dmitry,

There is no solution yet. I have yet to see anyone from Blackmagic acknowledge the bug that was introduced with version 17. Not a good sign.

Congrats to BMD team for finally fixing this audio device bug in version 17.2!