[wdmaudiodev] Re: Remote desktop audio problem in different windows sessions.
- From: Tim Roberts <timr@xxxxxxxxx>
- To: wdmaudiodev@xxxxxxxxxxxxx
- Date: Wed, 03 Jun 2009 16:02:14 -0700
Jose Catena wrote:
>
>
>
> Ø How can i solve this problem, I want to route audio of only one
> session to the one established connection.
>
> The problem is that if your virtual driver is the default device, it
> receives all audio sent to the default audio device already mixed, so
> I don’t think it could separate what’s coming from different sessions.
> It may switch on or off depending on the user or whatever, but on will
> be on for everything at any given time (I mean everything that plays
> to that default audio device).
>
Jose, you are using an unrelated question as an opportunity to climb
back on your soapbox. The issue of audio routing in Terminal Services
sessions is fundamentally unrelated to the default audio device issues
you were complaining about.
Terminal services does have the ability to forward a session's audio to
the RDP client for playback on the client machine, but I'm not convinced
that ability is exposed in any way. RDP audio mapping is disabled by
default on the server. There are lots of web logs that describe how to
re-enable the audio mapping using the Terminal Services Configuration
tool, tscc.msc:
http://www.terminalserviceslog.com/blog/index.php/2008/10/07/terminal-services-redirecting-audio-to-client/
--
Tim Roberts, timr@xxxxxxxxx
Providenza & Boekelheide, Inc.
Other related posts:
