[wdmaudiodev] Re: MSVAD as capture device

  • From: Ahmed Osama <wiseman_tm@xxxxxxxxx>
  • To: wdmaudiodev@xxxxxxxxxxxxx
  • Date: Mon, 15 Feb 2010 03:30:28 -0800 (PST)

Thanks for the reference , 

but I need to know how to implement CopyFrom() to put the data to the Capture 
stream ?

I really appreciate your help as I need to develope a virtual audio cable too.

Thanks a lot for your time

From: Michail Nikolaev <michail.nikolaev@xxxxxxxxx>
To: wdmaudiodev@xxxxxxxxxxxxx
Sent: Mon, February 15, 2010 1:05:12 PM
Subject: [wdmaudiodev] Re: MSVAD as capture device

 for details.

2010/2/15 Ahmed Osama <wiseman_tm@xxxxxxxxx>

>I want to change MSVAD(simple) code to use it as virtual capture device, I 
>just need to copy the buffer I recieve inside CopyTo , to an application that 
>selects MSVAD as capture device, simply whatever you render on MSVAD can be 
>seen as Capture , I tried in many ways as follows:
>1- I keep a copy from the source buffer recieved in CopyTo in a FIFO buffer.
>>2- when CopyFrom is called I try to overwrite the m_pvDmaBuffer  using 
>>RtlCopyMemory , the problem is that the buffer never changes it's contents 
>>all the sound I get from Windows sound recorder is (sha...sha...sha) like 
>>sound more like garbage data.
>3- I tried changing the returned address in 
>CMiniportWaveCyclicStreamMSVAD::PhysicalAddress to point to my FIFO buffer , 
>but still not working.
>>4- in AllocateBuffer I tried to fill m_pvDmaBuffer with ZERO so I won't get 
>>any sound but again nothing happens.
>>Note: in CopyTo the ByteCount is 840 bytes , while in CopyFrom it's 48 bytes 
>>, I can't change that behavior also to make the buffers match?
>>I'v been working for nearly a month now and can't find any information to 
>>help me , it's very urgent Please help me.
>>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

Other related posts: