Amen. I don't want to argue about an ideology and the hierarchy it leads to.
The reality is that ODMs, driver and codec vendors still make unilateral
decisions on user and listening experience in regards to a particular system. I
don't see Microsoft controlling much here, moreover the situation is somewhat
acknowledged by dropping audiodg protection and not banning widely used
IPolicyConfig. The claim about apps being in charge of the audio settings is a
tunnel vision not realizing that most browsers and apps are cross platform and
don't care about providing correct processing modes to APO or simply don't want
to incorporate the complexity of audio content type detection.
As for 'high-end professionals', those don't listen to laptop acoustics unless
causally when it's a Macbook 16' or similar in quality that hardware and driver
vendors managed to build. Pro-audio users always used low latency, clock-sync
ASIO drivers coming with professional audio interfaces. So, the audience
Microsoft should care about is a regular consumer by helping vendors build
quality systems. Providing process info to SFX is a minor effort on Microsoft's
part to help write less convoluted code for solutions that market demands and
that's all about it.
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Tim Roberts
Sent: Monday, May 25, 2020 1:36 PM
Subject: [wdmaudiodev] Re: Obtaining application or audio session info for APO
Edward Abramian wrote:
The task at hand is also choosing right preset, so information about the app
may come in handy.