Unfortunately this is not going to be useful to you, since it only works in the context of being a Remote Desktop service provider. E.g., Remote Desktop itself; PC Anywhere; VNC; GoToMyPC; Cisco's remote PC control software, etc. For "normal" audio scenarios, Kernel Streaming is the only way to go. ________________________________ From: Robert Bielik<mailto:robert.bielik@xxxxxxxx> Sent: 9/10/2014 1:20 AM To: wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx> Subject: [wdmaudiodev] Re: WASAPI feature request I've been looking at this and it seems like the way to go, since I won't need to debug in kernel mode anymore :) In the case of an output audio endpoint, I'm not sure I figured out which party is the "driving" agent ? In case of a normal event driven audio endpoint, it is the endpoints responsibility to set the event (i.e. be the driving agent), whereas for IAudioEndpointRT::ProcessingComplete it would indicate it is the Window audio server which is "pushing" data to the endpoint ? I'm wondering how to synchronize the data stream to the target audio endpoint. Are there any code examples (as for Slate VAD) provided for this, so I can quickly test if this is for me ? Regards /Robert Matthew van Eerde skrev 2014-09-09 18:47: > FWIW, you can actually do this in the context of a Remote Desktop plugin: > > http://msdn.microsoft.com/en-us/library/dd379706(v=vs.85).aspx > > -----Original Message----- > From: wdmaudiodev-bounce@xxxxxxxxxxxxx > [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Robert Bielik > Sent: Tuesday, September 9, 2014 1:28 AM > To: wdmaudiodev@xxxxxxxxxxxxx > Subject: [wdmaudiodev] WASAPI feature request > > To be able to add virtual audio devices dynamically, much like the server > plugin architecture of OS X CoreAudio. > > These VADs should then reside in user-land only. > > Regards > /Robert > ****************** > > 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/ > ****************** 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/