Page 1 of 1
master audio out (Windows)

Posted:
Wed Jun 23, 2021 5:38 pm
by johnford
Somehow my audio output gets mapped to both channels, even if only one (stereo) channel is active (that is, only one of the two channels in the mixer of the Master bus is lighting up).
I've checked the channel mapping in the the "Preferences / Speaker Setup. It doesn't make a difference if I "Use System Settings" or manual setup.
Am I missing something?
Re: master audio out (Windows)

Posted:
Wed Jun 23, 2021 6:03 pm
by Reynaud Venter
Can you detail which audio device is configured in:
Resolve > Preferences > Video and Audio I/O
A screenshot of the manual settings in Speaker Setup may be a good first step to diagnosing the issue.
Any change patching Control Room Monitor Direct?
Fairlight menu > Patch Input/Output and patch as follows:
Source = Control Room Monitor Direct
Destination = Audio Device Outputs
Re: master audio out (Windows)

Posted:
Sat Jun 26, 2021 2:04 pm
by johnford
By testing with another program I found out that this is actually a Windows problem. It happens with the built in speakers, an external (USB) DAC and when connecting headphones through Bluetooth.
Windows seems to pan both the left and right channels to the centre, so even when I set the balance (in the audio program) to "left", the output plays through both channels.
I still couldn't figure out what is causing the problem. Maybe there is someone out there on Windows 2004 who could check if this is my "personal" problem or not?
Re: master audio out (Windows)

Posted:
Sat Jun 26, 2021 3:50 pm
by Charles Bennett
It might be worth checking the balance setting in Windows Sound.
Re: master audio out (Windows)

Posted:
Sat Jun 26, 2021 4:22 pm
by johnford
This is how it looks in my case:
Re: master audio out (Windows)

Posted:
Sat Jun 26, 2021 9:02 pm
by johnford
After hours of googling, I found the problem: there is a "hidden" option in W10 to turn all audio "mono". It is not part of the audio settings, but of the accessibility settings. I had never changed it, but it was activated. Disabling it resolved the problem.