Hello,
I am currently working on an Audio Processing Object (LFX/SFX+GFX/MFX) for
audio playback devices. After the Redstone 2 update, I noticed an issue:
When opening the audio playback device dialog, I am warned that audio
enhancements were disabled, and I am asked whether I want to re-activate
them. They run perfectly afterwards.
As far as I know, this scenario is linked to an issue in the early APO
initialization and test at OS startup.
A workaround I finally came up with is to short-circuit a few calls in the
LockForProcess() of the very first audio stream handled by the LFX APO.
Further investigations showed that at least 3 important APO providers are
also affected: Their APOs started to cause the same warning message after
upgrading to Redstone 2.
I would like to know whether Redstone 2 introduced some behavioral change
that could jeopardize the APO initialization and test phase, or lead in
some other way to Windows warning the user of an issue with audio
enhancements.
Best regards,
Paul Allais
