-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MEDIA.BUFFER_READ_OUT_OF_BOUNDS in cea_decoder parsing captions from h.265 content #3659
Comments
Im also facing the same issue. Here is the error log:
I checked the previous versions and it seems the last version with which it worked is 3.0.13. From version 3.1.0 and later "BUFFER_READ_OUT_OF_BOUNDS" occurs. The problem occurs on both firefox and chrome (on Ubuntu 18.04.5 LTS). Also playback works fine with latest dash.js. Edit: Just noticed this bug was reported for h.265. I'm seeing this error for h.264 as well. |
I just checked-out master, recompiled and can confirm it is happening with latest master. |
Yes I just ran it against the nightly build from your appspot demo. I assume that is built from latest master. It is still happening there. |
…t#306) * [PATCH] fix(dash): fix race condition in segment template (shaka-project#5842) Fixes shaka-project#5760 * fix(cea): Fix not rendering CEA-608 Closed Captions (shaka-project#4683) Also added H265 support and a framework for future TS CEA parser support. Fixes shaka-project#4605 Fixes shaka-project#3659 Co-authored-by: Joey Parrish <[email protected]> * fix(cea): Fix not rendering CEA-608 on encrypted mp4 segments (shaka-project#4756) Fixes shaka-project#4605 Co-authored-by: Joey Parrish <[email protected]> * fix: CEA 608 captions not work with H.265 video streams (shaka-project#5252) Fix parsing of CEA 608 captions in H.265 video streams by handling 2 byte nal unit header. Fixes shaka-project#5251 * fix: seeking in segment timeline returns incorrect index (shaka-project#5716) Resolves shaka-project#5664 --------- Co-authored-by: Albin Larsson <[email protected]> Co-authored-by: Álvaro Velad Galván <[email protected]> Co-authored-by: Joey Parrish <[email protected]> Co-authored-by: Aidan Ridley <[email protected]> Co-authored-by: Casey Occhialini <[email protected]>
Have you read the FAQ and checked for duplicate open issues?
It is possibly related to #3634, but I am not sure. I can send some sample content which the others cannot provide.
Not sure if the problem is with the content, or shaka. A couple of interesting things to note though
1 - There are no actual captions in the content until about 1 minute in, but the cea_parser error occurs at about 20 seconds into the content
2 - Exoplayer does not have any issues with the content.
What link can we use to reproduce this?
I will send the content to your private address
What version of Shaka Player are you using?
v3.2.0-uncompiled
What browser and OS are you using?
Windows 10 - Edge - With HEVC decoder plugin
What did you do?
Playback content
What did you expect to happen?
Uninterrupted playback
What actually happened?
Attempting to buffer the 6th segment, this error occurs
Error: Shaka Error MEDIA.BUFFER_READ_OUT_OF_BOUNDS ()
at new shaka.util.Error (https://shaka-player-demo.appspot.com/lib/util/error.js:94:17)
at shaka.util.DataViewReader.outOfBounds_ (https://shaka-player-demo.appspot.com/lib/util/data_view_reader.js:267:12)
at shaka.util.DataViewReader.readUint8 (https://shaka-player-demo.appspot.com/lib/util/data_view_reader.js:83:18)
at shaka.cea.CeaDecoder.extract (https://shaka-player-demo.appspot.com/lib/cea/cea_decoder.js:120:16)
at shaka.media.ClosedCaptionParser.parseFrom (https://shaka-player-demo.appspot.com/lib/media/closed_caption_parser.js:89:24)
at shaka.media.MediaSourceEngine.appendBuffer (https://shaka-player-demo.appspot.com/lib/media/media_source_engine.js:547:52)
at shaka.media.StreamingEngine.append_ (https://shaka-player-demo.appspot.com/lib/media/streaming_engine.js:1571:51)
at async shaka.media.StreamingEngine.fetchAndAppend_ (https://shaka-player-demo.appspot.com/lib/media/streaming_engine.js:1261:9)
The text was updated successfully, but these errors were encountered: