Question: Control Windows 11 Speaker Audio Enhancement ON/OFF

[woogi-kang]

[Issue Description]
Currently in Windows 11, the automatic speaker/audio enhancement feature is turned ON by default for each audio profile. However, when this is enabled, recording with the record package captures audio with Windows 11's filters already applied, making it impossible to capture the desired raw audio.
Is there a way to disable the audio enhancement feature directly within the record package settings, without having to manually turn it off in Windows 11 system settings?

[Environment]
OS: Windows 11

[Expected Behavior]
The record package should be able to capture raw audio without Windows 11's audio enhancements applied, or provide an option to programmatically disable these enhancements during recording.

[Current Behavior]
Windows 11's audio enhancement filters are applied to recordings made with the record package.

[llfbandit]

Thanks for the report.

Honestly, I don't know if there's a way to workaround this feature, at least with the current implementation.
I'm also surprised that it is applied if you ask for PCM...

After a little digging, there's no obvious way to achieve this.

[woogi-kang]

Hi @llfbandit

Thanks a lot for looking into this and for the quick feedback.

It's disappointing to hear that there's no obvious way to work around this in the current implementation, but I appreciate you confirming the difficulty.

I agree, it's very surprising that the enhancement is applied even when explicitly requesting PCM (raw uncompressed data), as PCM should ideally bypass any intermediate processing filters. This suggests the filter is being applied at a lower level in the Windows audio stack (perhaps before the data reaches the API the record package uses).

Could you confirm if the package currently uses the WASAPI (Windows Audio Session API) or a higher-level API? Knowing this might help me understand if we need to look into an "Exclusive Mode" capture, which usually bypasses these Windows enhancements, although I understand that might introduce other complications.

For now, I'll update the issue description to reflect that the current solution is to manually disable the feature in Windows settings.

Thanks again for your time!