-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Error thrown in CEA 708 window when indicated row count in packet is 15 #3634
Comments
@pcruiksh Do you have a stream with the error? |
@avelad I am following up with our content team to see if I can get a piece of content in the clear, and to see if I am actually allowed to share any of our content in the first place. May I ask if content sent to [email protected] is only distributed within google? |
I am not a member of the ShakaPlayer team, I just wanted to help solve this problem faster. If you send it to that mailing list, as far as I know, only the ShakaPlayer team (no one else from google) has access. |
@joeyparrish Can you confirm what I have put about the mailing list? |
That is correct. The group is configured so that only the members of the group (e.g. the Shaka Player team) can view the messages within it. |
Can you please send us some sample content? The mailing list ([email protected]) is private and we won't share it outside the team. |
@TheModMaker Sorry for the slow response. I am unable to send you the specific content we identified that exhibits the issue but I can break it down more granularly (bearing in mind my flaky knowledge of the spec). The row count byte can indicate a value in a range from 0-15, and the spec specifies you add 1 to this value when you define the properties of the window in your decoder. I'm not really clear why that is the case but in the example where that byte indicates a row count of 15, and we define a window row count of 16 per the spec, This then creates a TypeError when setCharacter is called when the window is at that row since Currently our content works just fine if I simply increase MAX_ROWS but I am not sure if this is an "appropriate" solution, or if maybe this is a content issue. |
@pcruiksh I'm working on many fix and features for CEA in the Shaka, if you can share your stream to me, I can work on a fix for it. Thanks! |
I am reading on Wikipedia that the rows range is 0-15 so MAX_ROWS needs to be 16. Thanks for found it! |
I'll work on a PR to fix it. Thanks! |
Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
3.2.0
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from
master
?Yes
Are you using the demo app or your own custom app?
Custom
If custom app, can you reproduce the issue using our demo app?
N/A
What browser and OS are you using?
MacOS 11.5.2 + Chrome 92
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
What are the manifest and license server URIs?
N/A
What configuration are you using? What is the output of
player.getConfiguration()
?N/A
What did you do?
Play content with embedded captions
What did you expect to happen?
Captions display and content plays correctly
What actually happened?
A type error from Cea708Window.setCharacter is thrown: cannot set property of undefined
The CEA 708 spec seems to allow for a max row count of 15 which is reflected in the number of rows created in a cea 708 window instance (indexed 0-14). I see that the spec specifies you should add 1 to the window row count , which is done when the row count byte is read from the packet (cea708_service.js, line 594). This creates a situation where if the indicated row count is 15, a row count of 16 is defined on the window, which means a carriage return allows the row index pointer to be moved to a non-existent index of the memory array (as only 0-14 are created initially) since the row index is still less than the configured row count. This causes a subsequent setCharacter() operation to throw.
The text was updated successfully, but these errors were encountered: