for applications willing to provide audio services,
Exclusive mode is also used to reduce latency and get best performances.
(the WDM share mode for playback device is unstable, that’s why many
applications use exclusive mode to manage playback device with WDM interface).
For your DSP app, you may consider doing your APO like the Equalizer APO, with
the possibility to run it as regular user application connected to Voicemeeter
(or through an ASIO interface or through the Voicemeeter Audio Callback).
Voicemeeter API / SDK is free:
De : wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] ;
De la part de Culann mac Cabe
Envoyé : lundi 19 avril 2021 23:48
À : wdmaudiodev@xxxxxxxxxxxxx
Objet : [wdmaudiodev] Re: [EXTERNAL] Offloaded DSP APO not instantiated when
device in Exclusive Mode
Thanks for this contribution Tim. I understand the point of Exclusive Mode and
the supposed and real benefits of it from an audio DSP development perspective.
The fact that my User can, unwittingly or intentionally, remove my offloaded
APO from the processing chain is what causes difficulties for me and so,
because I can't prevent the scenario from being created, I'm looking at ways to
know that it's happening with no luck yet... any thoughts/suggestions on this
On Mon, 19 Apr 2021 at 21:41, Tim Roberts <timr@xxxxxxxxx> wrote:
Culann mac Cabe wrote:
That's it, out simply. I can mitigate the problem by modifying the DSP
tuning to not have such a dramatic level change between DSP On/Off but
that comes at a cost of reducing the quality of the DSP process
itself. Hence the request for info on a mechanism that our GUI App
could know whether the device is in Exclusive Mode - if we knew that
we could kick in a mitigating/correcting DSP...