Video buffering in IE/Edge using Media Source Extensions

Won’t fix Issue #5800353


Dec 10, 2015
This issue is public.
Reported by 28 people

Sign in to watch or report this issue.

Steps to reproduce


Repro Steps:

Append a ISO BMFF Byte Stream ( frame by frame to a MSE SourceBuffer.

I’ve spent some hours setting up a reproducing example for you. Hope you can take a look and get back to us!

Link to repro:
Download the mp4 here if needed:

This example simulates receiving frames over websocket by having a setTimeout emitting the frames. Hope you can follow the contrived example :)
The example logs the time from first frame is added to the sourcebuffer until the video element starts playing.
When pushing the play button it takes < 30 ms in safari and Chrome on Android. In Chrome on desktop I’m getting around 300 ms. For edge and IE i get above 3200ms, which is not acceptable for live video.

What we would want is a way to make IE start playing when the first frame is appended.

Expected Results:

The video start playing when the first frame is appended to the buffer

Actual Results:

Dev Channel specific:



0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Jerry S.”

    • Greetings! Has there been any progress on this issue? Is it being actively worked on?

    • This can also be seen on the following site

    • The reproducing example link is 404, it can be found here instead:

    • Hi, is this issue planned to be fixed in IE & Edge in a near future?
      This feature is critical for our real time project, otherwise our new product won’t be able to support IE & Edge.
      Please, I need to know the status of this issue to adapt our strategy, thanks

    • I have the same problem with MSE on IE and Edge too. They are both delay 3~5 seconds. Any process guys?

    • Microsoft Edge Team

      Changed Status to “Confirmed”

      Changed Status from “Confirmed”

      Changed Assigned To from “Jerry S.” to “Gurpreet V.”

      Changed Status to “Not reproducible”

      Changed Status from “Not reproducible” to “Won’t fix”

    • How come 'Not Reproducible’? It reproduces fine (the problem is seen) on the Edge that comes in Windows 1703…
      See both with Edge and with Chrome!

    • I agree. Easily reproducable and a big issue for both stability and live-streaming use cases. Labelling as Won't fix should not be an option.

    • I agree. Please fix this issue.

    • I agree. too, We can’t use edge for our product by this issue.

    • Why was the status changed to “Not reproducible” and "Won’t fix"? How to reproduce is already revealed. And the guys from this topic know how serious this issue.
      I beg Edge Team to check this issue and reproducible again.
      Unfortunately and sadly, no one will be able to use a use cases like live-streaming on IE/Edge forever if Edge team will not fix.

    • We are a global market leader in network video cameras and want to be able to support Edge for live streaming video in web browsers. Unless this issue is fixed we can not recommend our customers and clients using Edge. We don’t see this issue with your competitors web browsers.

    • This bug is also critical for our real time project. Our customers are not able to use our product with Edge. This bug easily reproduces on the latest version of Edge.
      Which Edge version did you use to say ‘Not reproducible’ ?

    You need to sign in to your Microsoft account to add a comment.

    Sign in