Video buffering in IE/Edge using Media Source Extensions

Fixed Issue #5800353

Details

Created
Dec 10, 2015
Privacy
This issue is public.
Fixed in build #
18.18226
Reports
Reported by 30 people

Sign in to watch or report this issue.

Steps to reproduce

URL:

Repro Steps:

Append a ISO BMFF Byte Stream (http://www.w3.org/2013/12/byte-stream-format-registry/isobmff-byte-stream-format.html) 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:
https://ea7e83c432c066554d3ef3e6580aa1af9bd594a1.googledrive.com/host/0BwqnHXhKkJ7mfjF5clFzSUFSY3pjSzhxZlA0TnpIeEo2bHlaY2FZd3RhWDFHY1o2eXZsYXc/ie_5s_buffer.html
Download the mp4 here if needed:
https://ea7e83c432c066554d3ef3e6580aa1af9bd594a1.googledrive.com/host/0BwqnHXhKkJ7mfjF5clFzSUFSY3pjSzhxZlA0TnpIeEo2bHlaY2FZd3RhWDFHY1o2eXZsYXc/ie_5s.mp4

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:

No

Copied from Description when changed from Task to Bug

Please Note:
This bug was filed through our public Connect
program and will require a customer ready message
for any issue resolved as : Won’t fix or By Design
.
- Please review the following example template to get started. http://aka.ms/iefeedback
- With the customer ready message please provide a timeframe or release when the information can be disclosed.

  • You can work with the feature PM for the explanation as it will be shared as is on Connect
    ********Problem Information********
    ISSUE AREA: Audio / Video

REGRESSION: <Untriaged>

DESCRIPTION:
Greetings!
We are trying to use MSE (Media Source Extensions) to show real time video on a website. We are sending frames over websocket and trying our hardest to keep latency down.
Our current prototype is streaming very well in IE, Edge, Chrome, Safari etc.
The issue we have is that IE and Edge insists on buffering around 3-5 seconds before starting to play the video. This is not acceptable in our use case (live video from security cameras).
We are wondering if there is some property or similar (we have tried setting preload=none, with no success) which removes this buffering?
All other browsers happily plays when the first frame arrives over the socket, and we want the same behavior from IE/Edge.
Is there any other workaround you can suggest for us?

********CONTACT INFORMATION********
HANDLE: oskarbjs
SITE NAME: ECO Readiness: Internet Explorer Beta Feedback Program
FEEDBACK ID: 1714826

========== 08-26-2015 ibrahim ==========

No Repro

 MS Edge  20.10240.16384.0
 IE11          11.0.10240.16431
 Firefox      40.0.2
 Chrome    44.0.2403.157

Windows 10

============== 12-10-2015 ibrahim ===============

Repro

MS Edge               25.11078.0.0 

No Repro

Google Chrome     47.0.2526.80
Mozilla Firefox       42.0 (x86 en-US)

Microsoft Windows 10 Enterprise

Copied from Repro Steps when changed from Bug to Task

URL:

Repro Steps:

Append a ISO BMFF Byte Stream (http://www.w3.org/2013/12/byte-stream-format-registry/isobmff-byte-stream-format.html) 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:
https://ea7e83c432c066554d3ef3e6580aa1af9bd594a1.googledrive.com/host/0BwqnHXhKkJ7mfjF5clFzSUFSY3pjSzhxZlA0TnpIeEo2bHlaY2FZd3RhWDFHY1o2eXZsYXc/ie_5s_buffer.html
Download the mp4 here if needed:
https://ea7e83c432c066554d3ef3e6580aa1af9bd594a1.googledrive.com/host/0BwqnHXhKkJ7mfjF5clFzSUFSY3pjSzhxZlA0TnpIeEo2bHlaY2FZd3RhWDFHY1o2eXZsYXc/ie_5s.mp4

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:

No

Attachments

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?

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

    • This can also be seen on the following site https://www.w3.org/2010/05/video/mediaevents.html

    • The reproducing example link is 404, it can be found here instead:
      Example: https://oskbor.github.io/ie_5s_buffer.html
      mp4-file: https://oskbor.github.io/ie_5s.mp4

    • 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 https://oskbor.github.io/ie_5s_buffer.html 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’ ?

    • Microsoft Edge Team

      Changed Status from “Won’t fix”

      Changed Assigned To from “Gurpreet V.” to “Angelo L.”

      Changed Steps to Reproduce

      Changed Assigned To from “Angelo L.” to “Rafael V.”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed”

      Changed Status to “Confirmed”

    • Is there plan for this issue or if there has any test version, I can try.

    • Still not working…

    • Microsoft Edge Team

      Changed Assigned To from “Rafael V.” to “Stephen E.”

      Changed Status from “Confirmed” to “Not reproducible”

    • Hello,

      Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge 17704 and is available in our Insider Preview build on the fast ring.

      Best Wishes,
      The MS Edge Team

    • Hello,

      I still reproduce the issue using Edge 43.17713.

      Edge 17713: 1812 ms
      Chrome 67: 80 ms
      Firefox: 72 ms

    • Microsoft Edge Team

      Changed Status from “Not reproducible”

      Changed Assigned To from “Stephen E.” to “Matthew H.”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed” to “In code review”

      Changed Assigned To from “Matthew H.” to “James M.”

      Changed Status from “In code review” to “Fixed”

    • Hello, MS Edge Team,

      Could you tell that what version of IE or Edge has the fix?
      I wanna try but I cannot because I don’t know the version.

      Best regards,

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

    Sign in