I believe the intent of this audio subsystem check is to ensure it's not stepping on any DirectKS clients' toes. You could presumably attempt to sabotage the intent (for example by registering your own KSPROPERTY_PIN_GLOBALCINSTANCES handler and returning failures), but this begins to wander into "unsupported" territory. Can you help me understand the scenario that requires simultaneous DirectKS and audio subsystem clients for a given pin? That will help inform future OS decisions. -----Original Message----- From: wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Eugene Muzychenko Sent: Thursday, August 14, 2014 6:13 AM To: Matthew van Eerde Subject: [wdmaudiodev] Re: Shared mode recording doesn't work if CurrentCount is nonzero Hello Matthew, > if CurrentCount < PossibleCount, but CurrentCount > the number of > instances the audio subsystem has itself opened, it will likewise fail > with "device in use", since something outside of the audio subsystem > is using the device. Therefore, to avoid this check and let Audio Subsystem use any available pin instance, it is enough not to support KSPROPERTY_PIN_CINSTANCES? Regards, Eugene ****************** WDMAUDIODEV addresses: Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx URL to WDMAUDIODEV page: http://www.wdmaudiodev.com/ ****************** WDMAUDIODEV addresses: Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx URL to WDMAUDIODEV page: http://www.wdmaudiodev.com/