[wdmaudiodev] Re: Multiple instances of MSVAD sample

  • From: pritesh gajjar <gajjar.pritesh@xxxxxxxxx>
  • To: wdmaudiodev@xxxxxxxxxxxxx
  • Date: Thu, 29 Jan 2009 15:53:50 +0530

Hi,
     I am also searching for the same thing. If anyone knows what are the
things required to have multiple instances of same driver, please reply. Do
we need modification  in PropertyHandlerComponentId () routine ? VAC does
the same thing. I saw its inf file. All Topo and Wave interfaces are
repeatively written do we need any driver code to invoke them ?

Thanks...

On Wed, Jan 28, 2009 at 4:30 PM, Vipin Kumar <vipin@xxxxxxxxxxxxxx> wrote:

> Hi,
>     I don't need Sound Over RDP because
>   (i) Closed Sourced
>   (ii) Since i am developing it for someone else( they might/will ask the
> complete source)
>   (iii) i want to gain some more knowledge in the process.
>
> If any such stuff exists, in the open source domain, i will be happy to
> know about it.
>
> Anymore suggestions are welcome.
> Thanks
>
> Regards,
> Vipin
>
>
> On Wed, Jan 28, 2009 at 3:07 PM, MASTER_ZION (Jairo Linux) <
> master.zion@xxxxxxxxx> wrote:
>
>> download sound over rdp
>>
>> 2009/1/28 Vipin Kumar <vipin@xxxxxxxxxxxxxx>
>>
>> Hi,
>>>     i would take the data from the client's mic, wrap it as  RDP protocol
>>> and send it to TS,.
>>>    On the server,my app/services will take the data, and feed it to the
>>> driver( user specific instance of virtual mic), thus the application's can
>>> get the microphone.
>>>
>>>   I just want to get the audio in support ( via microphone) for the
>>> Terminal server clients.i don't think there is open-source code to do that.
>>>
>>>   Let me know if my approach is wrong or if you have a better approach.
>>>
>>> Let me your ideas.
>>>
>>> Thanks for your reply
>>>
>>> Regards,
>>> Vipin
>>>
>>>
>>> On Tue, Jan 27, 2009 at 11:29 PM, Tim Roberts <timr@xxxxxxxxx> wrote:
>>>
>>>> Vipin Kumar wrote:
>>>> >
>>>> >     i  would like to create multiple instances of MSVAD.Actually i am
>>>> > try to create a Virtual audio in support for Terminal server
>>>> > clients.Since MS doesn't provide it. So, AFAIK if we create virtual
>>>> > nodes, one per user and set it up in audio devices, then it should
>>>> > work.Let me know if my approach is wrong
>>>>
>>>> No, it isn't that easy.  Think about it for a moment.  How would
>>>> Terminal Services know that it was supposed to assign one node per
>>>> client?  It wouldn't.  You would end up with a bunch of audio devices on
>>>> the console, with none on the clients.  It takes special code in
>>>> Terminal Services to get a device exposed within the TS clients.  There
>>>> is a custom display driver, a custom keyboard driver, and a custom mouse
>>>> driver for Terminal Services that redirects everything through TS to the
>>>> console.  You would need a similar thing: a special Terminal Services
>>>> audio driver that gets instantiated once per client.  Unfortunately,
>>>> it's been so long since I dug into Terminal Services that I don't
>>>> remember where that's done.
>>>>
>>>>
>>>> > Or, if there is other way round such as 1 single node is enough to
>>>> > fulfil all requests( of course we will use different buffers for each
>>>> > user).
>>>> >
>>>> > What would be your approach if you are asked to do it ?
>>>>
>>>> What do you plan to DO with the audio data?
>>>>
>>>> --
>>>> Tim Roberts, timr@xxxxxxxxx
>>>> Providenza & Boekelheide, Inc.
>>>>
>>>> ******************
>>>>
>>>> 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/
>>>>
>>>>
>>>
>>
>


-- 
Thanks and regards
Pritesh

Other related posts: