I still have not figured out what is really at stake in this Creator's
Update related issue. The problem is very visible and quite annoying for
the end user, so any help, even the smallest clue, would be highly
appreciated. As at least 3 companies have had that very same behavior in
their products since the Creator's I cannot be 100% sure the root issue
lies in my own code.
2017-05-24 11:34 GMT+02:00 Paul Allais <paul.allais81@xxxxxxxxx>:
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