I would say over 90% of the applications that I’ve seen don’t use the
eCategory…too many to list here. That’s the long-term solution and it’s not
backwards compatible for Win7 which I still need to support and be in feature
parity with Win10. We are still seeing over 30% of users on Win7.
Bob
On Nov 14, 2018, at 11:56 AM, Matthew van Eerde (Redacted sender
"Matthew.van.Eerde" for DMARC) <dmarc-noreply@xxxxxxxxxxxxx> wrote:
Please don’t. Instead, let’s get everyone using
AudioClientProperties.eCategory.
Do you have any particular applications in mind?
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on
behalf of Robert Dalton Jr. <bob@xxxxxxxxxxxx>
Sent: Wednesday, November 14, 2018 11:53:35 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: identify application creating APO
Ideally some processing could change depending on the application. Many
(most) Win10 applications don’t use the Application Processing Modes and this
isn’t available on Win7 / Win8. I’d like to change the processing based on
the application type in these cases.
On Nov 14, 2018, at 11:43 AM, Matthew van Eerde (Redacted sender
"Matthew.van.Eerde" for DMARC) <dmarc-noreply@xxxxxxxxxxxxx
<mailto:dmarc-noreply@xxxxxxxxxxxxx>> wrote:
No; why do you want this?
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx> <wdmaudiodev-bounce@xxxxxxxxxxxxx
<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>> on behalf of Robert Dalton
<bob@xxxxxxxxxxxx <mailto:bob@xxxxxxxxxxxx>>
Sent: Wednesday, November 14, 2018 11:18:45 AM
To: wdmaudiodev@xxxxxxxxxxxxx <mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] identify application creating APO
Is there any way to identify the audio session or application (by pid?) that
the SFX APO is being created for?
Bob
