Sound and video not working properly on thin client. RRS feed

  • Question

  • This is for an HP T5550 THINCLIENT running on Windows Server 2008 R2. Audio is setup fine, with max volume on both, client and windows environment of the TS. Internal speaker is not enough to put audible sound of her liking. She had non-powered speakers that were not boosting sound levels to an adequate level. Recommend ordering powered speakers

    Attached external speakers. The sound problem is when accessing and running videos to include website. Video playback is perfect, little lag, audio drops out severely. Does not appear to be a codec issue, possible misconfiguration, not impeding from network lag.

    Verified desktop experience was installed on TS. Modified the group policy to allow audio redirection.

    Local reboot to verify on sound. Improvements are there from the Desktop Experience install and GP, but still lags, only now affecting video quality. The larger the video, the worse it is. For instance, on a website that has a video running but is a small-sized window, plays fine. For YouTube videos, it will play just fine if the tab that it is in, is in the background, not the focused tab.
    Friday, March 23, 2012 8:06 PM

All replies

  • Hi,

    You can try to change the audio quality modes to see which option is the best. For more details information, please refer to the link below.

    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 audio quality mode 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.

    Looking forward to your feedback.


    Technology changes life……

    Monday, March 26, 2012 8:24 AM
  • Hence why for this new post. I have searched the forums and tried each of those "fixes" to no avail. That one was one of the first ones that I have looked at and the network is more than capable enough to be able to handle the load.

    Since video playback is perfect on a page where the window of the video is small (like on a local news station page that has video playing on the side bar/corner) but gets worse on pages with a bigger window, to include videos on YouTube. Putting the video in Full Screen (when available) made it worse. This is where it has me to believe that maybe the Thin Clients HP T5550 are the actual culprits in just not being able to handle it.

    Monday, March 26, 2012 10:51 AM