Forced subtitle DASH support checking for wrong Role@value #3767
Labels
status: archived
Archived and locked; will not be updated
type: bug
Something isn't working correctly
Milestone
Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
3.2.1
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?
N/A
If custom app, can you reproduce the issue using our demo app?
N/A
What browser and OS are you using?
N/A
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
N/A
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?
The 4th edition of ISO/IEC 23009-1 (publicly available here) has this change:
Shaka added support for forced narrative signalling from DASH in #2938.
What did you expect to happen?
The signalling of forced narrative track would be detected via
roles.includes('forced-subtitle');
.This is defined in Table 31 —
Role@value
attribute for scheme with a value"urn:mpeg:dash:role:2011"
Role@value
forced-subtitle
text
What actually happened?
The signalling of forced narrative track is detected via
roles.includes('forced_subtitle');
.The text was updated successfully, but these errors were encountered: