question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

CEA-608 captions are garbled

See original GitHub issue

Have you read the FAQ and checked for duplicate open issues? Yes

What version of Shaka Player are you using? v2.5.9 (uncompiled)

Can you reproduce the issue with our latest release version? Yes

Can you reproduce the issue with the latest code from master? Didn’t try

Are you using the demo app or your own custom app? Using the demo app. https://shaka-player-demo.appspot.com/demo

If custom app, can you reproduce the issue using our demo app?

What browser and OS are you using? Chrome - Version 80.0.3987.100 (Official Build) (64-bit) OS - macOS 10.14.6 (18G2022) For embedded devices (smart TVs, etc.), what model and firmware version are you using? Roku, Apple TV and alternate HTML5 players do display the captions correctly.

What are the manifest and license server URIs? Will send the manifest and license server url via email with bug number in the subject line. What did you do? Played the stream sent via email by populating the Custom Content button.

What did you expect to happen? 608 captions should have been displayed accurately.

What actually happened? 608 garbled via Shaka on Chrome - 1

608 garbled via Shaka on Chrome - 2 Screen Shot 2020-02-13 at 11 08 27 AM

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:17 (12 by maintainers)

github_iconTop GitHub Comments

1reaction
ppatlolla-turnercommented, May 18, 2020

Confirming that 608 captions have been fixed.

608 after fix
1reaction
joeyparrishcommented, Apr 21, 2020

So far, the mux.js team doesn’t know what is wrong with their CEA parser on this content, and neither do we.

If you have access to an open-source CEA parser in any language that works with this content, we could compare it with mux.js and see if we can identify the issue.

In the mean time, while we wait on either the mux.js team to provide a resolution or a working CEA parser to compare with, we will have to remove this issue from the v2.6 milestone.

We apologize for the inconvenience.

Read more comments on GitHub >

github_iconTop Results From Across the Web

CEA-608 captions are garbled · Issue #2395 · shaka ... - GitHub
Played the stream sent via email by populating the Custom Content button. What did you expect to happen? 608 captions should have been...
Read more >
What is 608 & 708 Closed Captioning? - 3Play Media
608 closed captions (also known as CEA-608, EIA-608, or Line 21 captions) were the standard for analog television. 608 captions are compatible ...
Read more >
Troubleshooting Digital Captioning Problems Beyond the TV
An example of such a known problem is missing and/or garbled captioning problems caused by an untouched Evertz 608 to 708 captioning bridge...
Read more >
Reading CEA-608/708 closed captions from SDI - Flussonic
Initially, closed captions were designed for deaf and hard of hearing people. Closed captioning information is encoded within the stream and a viewer...
Read more >
Need to change Caption Stream from CEA-608 to CEA-708
I'm getting .scc files from a captioning service for a half-hour show I'm working on. The show is now being edited in 1080i,...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found