Teams Meeting room devices (MTR) - Choppy Video Content Sharing via HDMI

Amandeep Singh 0 Reputation points
2026-06-17T11:12:29.6933333+00:00

It appears that this is not an isolated issue, as similar concerns have been raised by multiple users since 2024.

At present, Microsoft Teams Rooms (MTR) on both Windows and Android platforms are unable to consistently support 30 fps video during content sharing. When video is shared via HDMI or USB-C ingest, the frame rate is typically limited to below 15 fps, resulting in noticeably choppy playback. This impacts all meeting participants, regardless of whether they are joining via the Teams desktop client or another MTR device.

Currently, the only partial workaround is the use of PowerPoint Live (supported on MTR on Windows only). However, this approach requires an additional participant to join the meeting and mute both microphone and speakers to avoid audio feedback. This is not a practical or scalable solution in most production environments.

Additionally, PowerPoint Live performance on MTR on Android devices is inconsistent and unreliable. In many cases, video playback appears unstable, exhibiting stuttering and duplicated frames, which further degrades the user experience.

Given the volume of community discussions and forum threads on this topic, it is evident that this limitation is affecting a broad range of organizations. Despite this, there has been no clear resolution or guidance provided to date.

I have raised multiple support tickets regarding this issue, but the response has remained consistent:

“After reviewing the feedback from the Engineering team, they have identified this issue as a service-side error caused by a request timeout. Specifically, the GetSnapUrl failure occurred due to a timeout in the Snap service’s GetDownloadUrl.ashx front-end handler. The Engineering team has acknowledged the issue and has already identified a corresponding bug/work item. They are currently working on resolving this behavior on MTR devices.”

With approximately 1,500 MTR devices deployed across our client estate, this limitation is having a significant operational and user experience impact. A clear resolution timeline, or at the very least a reliable and scalable workaround, would be greatly appreciated

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Screen sharing
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Tamara-Hu 16,940 Reputation points Microsoft External Staff Moderator
    2026-06-17T12:54:48.6966667+00:00

    Hello Amandeep Singh,

    Thank you for taking the time to share such a detailed analysis. I can clearly see the impact this is having, especially given the scale of your MTR deployment.

    Based on my findings, the behavior you’re seeing (low frame rate during HDMI/USB-C ingest, especially for video playback) has been observed in other environments as well. The findings generally point to how HDMI content is processed within the MTR pipeline, which can result in reduced frame rate for high-motion content such as videos.

    I completely understand the impact this is having, especially given the scale of your deployment, and your request for a clear timeline or a reliable workaround is absolutely reasonable.

    At the same time, I’d like to be transparent that I don’t have access to internal engineering roadmaps, release timelines, or the ability to validate scalable workarounds in an environment comparable to yours.

    As part of the Q&A forum, my visibility is limited to publicly available information and similar reported cases, rather than direct coordination with the product group. You can also consider me an end user as well, providing guidance based on experience and documented processes. 

    Because of this, I’m not able to confirm an official resolution timeline or provide a workaround that is guaranteed to meet production requirements at your scale. The most accurate and up-to-date information would come through your existing support case, as the support team can engage directly with engineering and provide validated guidance based on your specific scenario.

    For more definitive guidance, I would recommend continuing to rely on updates from your active support case, as the support team can validate solutions directly with engineering and your exact environment.

    In parallel, I would strongly encourage submitting feedback through Microsoft’s official channels. This helps ensure the Product team is aware of the broader impact and can prioritize accordingly, especially for large-scale deployments like yours: Microsoft Teams · Community

    User's image

    Microsoft’s product team actively reviews customer submissions, and many improvements have been introduced based on user demand and real‑world usage scenarios. Submitting and upvoting feedback is the most effective way to help prioritize this for future updates.    

    Thank you again for documenting the issue so thoroughly and I genuinely appreciate your feedback and share your goal of making Microsoft Teams better and more user-friendly.        

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.