How to improve RDP Streaming Audio Performance

Remote audio playback has always tried to automatically adjust its bandwidth usage based on the current network conditions. This allows audio to work pretty well on anything from a 56k modem up through 10 gigabit Ethernet connection, but this flexibility comes at a cost. Adjusting the bandwidth on the fly requires the server to delay audio a little longer for processing before sending it to the client, which can cause the audio to be out of sync with the images on the screen.

Sometimes, you know you are on a network that’s fast enough to handle the best quality audio always. For these cases, you can now change the audio quality mode. This tells the server to assume the network can handle the best quality audio, and to send it as soon as it’s ready. Since the server processing doesn’t delay the audio, the synchronization between audio and video are much improved, and the audio sounds better too.

Enabling this feature requires changes to both the server- and client-side configuration. On the server, the easiest way to enable this feature is from the Group Policy editor.
Go to Computer Configuration:Administrative Templates:Windows Components: Remote Desktop Session Host:Device and Resource Redirection.
The policy in question is “Limit audio playback quality.” Set this to “Enabled,” and then set the “Audio Quality” option to either Medium or High.

On the client side, you need to add the audioqualitymode setting to the RDP file. The three possibilities for this setting are:
• audioqualitymode:i:0 -> Dynamic quality
• audioqualitymode:i:1 -> Medium quality
• audioqualitymode:i:2 -> High quality

Dynamic quality uses the old behavior and attempts to provide the best quality with the available bandwidth. Medium uses a single audio format, which allows reasonable quality, low latency, and doesn’t use too much bandwidth. On the other hand, high quality uses uncompressed audio for the best sound quality while also having low latency.

Leave a Reply

Your email address will not be published. Required fields are marked *