I submitted the feedback, here is the link: https://aka.ms/Ko7vyz
2017-06-06 20:19 GMT+02:00 Paul Allais <paul.allais81@xxxxxxxxx>:
Thanks for your quick answer! I can do it tomorrow, I send you the link
ASAP.
2017-06-06 20:12 GMT+02:00 Matthew van Eerde <dmarc-noreply@xxxxxxxxxxxxx>
:
Since you have a consistent repro: can you file a “problem report” in the
Feedback Hub, with “media issues” logs of the problem, without your
workaround?
https://blogs.msdn.microsoft.com/matthew_van_eerde/2016/09/2
6/report-problems-with-logs-and-suggest-features-with-the-feedback-hub/
Once filed, use the “Share” widget to grab a direct link to the problem
report.
Send me the direct link.
*From: *Matthew van Eerde <dmarc-noreply@xxxxxxxxxxxxx>
*Sent: *Tuesday, June 6, 2017 11:03 AM
*To: *wdmaudiodev@xxxxxxxxxxxxx
*Subject: *[wdmaudiodev] Re: Audio enhancements problem with Redstone 2
update
Windows tracks successes and failures when calling into an APO. If an APO
fails too frequently, Windows will disable it with this warning.
When Windows itself is updated, this counter is reset. So after any
Windows update, the APO will be re-enabled, and (if it still fails a lot)
will be disabled again (with the same warning.)
*From: *Paul Allais <paul.allais81@xxxxxxxxx>
*Sent: *Tuesday, June 6, 2017 10:57 AM
*To: *wdmaudiodev@xxxxxxxxxxxxx
*Subject: *[wdmaudiodev] Re: Audio enhancements problem with Redstone 2
update
Hi all,
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.
Best regards,
Paul Allais
2017-05-24 11:34 GMT+02:00 Paul Allais <paul.allais81@xxxxxxxxx>:
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
