New issue
Advanced search Search tips

Issue 854578 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Playback Error - HLS Encoded Streams

Project Member Reported by msnoxell@chromium.org, Jun 20 2018

Issue description

Chrome Version: 64.0.3282.190, other versions tested.
Chrome OS Version: 10176.76.0
Chrome OS Platform: Ninja

Also tested on Windows: Chrome version:67.0.3396.87 (Official Build) (32-bit)
Windows 10 version 1703

Customer reports that playing back a HLS encoded video stream on Chrome OS or Windows results in the stream stalling with the error message:
"The media playback was aborted due to a corruption problem or because the media used features your browser does not support".

Steps To Reproduce:
(1) Start a video stream encoded using HLS on either Chrome OS or Chrome on Windows
(2) Video will stall and produce the error message above.

Customer has tested the same stream with VLC on Windows - plays without error.

Expected Result: Smooth video playback, no error messages and stream plays continuously.

Actual Result: Playback of stream fails with error message as above.

How frequently does this problem reproduce? Always

Please provide any additional information below.

Customer believes this may be a codec related issue.



 
Sample screen grab of error message.
photo7537261304193317742 (1).png
2.9 MB View Download
Status: WontFix (was: Unconfirmed)
Chrome doesn't support HLS. To use HLS you'll need an intermediary library like Shakaplayer, HLS.js, video.js, etc.
Is there any public documentation that I can point the customer to that covers this in any detail?

Some more information would be nice for people fielding questions from customers:

Are there any plans to add HLS support?

If so, can you give details on prioritization on timelines?

If not, can you share why?
 issue 761506  has the most discussion on it. There's no plan to add support. Chrome's position is that this should be handled in JavaScript. We provide primitives to handle the media parsing, but the manifest should be handled in JavaScript.

Sign in to add a comment