You should not offer a KSNODETYPE_AUDIO_LOOPBACK pin unless you are prepared to
deliver functional audio loopback data.
* I don't want wasapi and any other api to capture system audio. As
confidental data is being streamed
Do you mean DRM? I will assume yes. If the answer is no, please elaborate.
The usual solution is for the app who owns the “confidential data” to use the
PlayReady APIs. This allows setting various policies about turning on HDCP and
disabling loopback etc. There is a PlayReady sample app here:
If you’re curious, under the covers PlayReady calls into the
IMFOutputTrustAuthority APIs. There’s a sample of how to manipulate the
PEACTION_PLAY policies like HDCP here:
To control loopback, the app would set PEACTION_EXTRACT policies instead. The
sample does not show how to do this exactly, but it is similar.
So I think you should remove the KSNODETYPE_AUDIO_LOOPBACK pin and tell whoever
the app is to use PlayReady.
If you have other reasons to provide hardware loopback (e.g., because you
support offload), then in addition to the app using PlayReady, your driver
needs to implement KSPROPERTY_AUDIOENGINE_LOOPBACK_PROTECTION as described here:
There are tests in the HLK which will validate this.
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on
behalf of eno rocky <binoddummy@xxxxxxxxx>
Sent: Thursday, August 16, 2018 9:51:37 PM
Subject: [wdmaudiodev] Disable wasapi loopback capture from WDM Audio Driver
I am trying to create custom virtual audio driver from sysvad sample. In which
I don't want wasapi and any other api to capture system audio. As confidental
data is being streamed. Even though the loopback pin is disabled, wasapi is
able to capture it as explained in
I am able to give silent buffer with KSNODETYPE_AUDIO_LOOPBACK pin for win8.1
and win10 but its not working for win7 and win8 cause
KSNODETYPE_AUDIO_LOOPBACK pin is not available for them ( as per i have
Is there any way to prevent wasapi or any other capturer from capturing stream
through driver itself?