-
Notifications
You must be signed in to change notification settings - Fork 507
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
TTML: wrong attribute "imagetype", camel case expected. #908
Comments
Thanks for the bug report. Would you like to submit a PR to fix it? @TheModMaker FYI. |
Yes, no problem. I'm struggling since about an hour ago to have my github fork updated so I could send a pull request. As soon as I fix that, will push the quick fix for this. |
Great. Thanks. |
Careful: this seems to also affect shaka player. I was doing some tests today, and shaka player doesn't show the TTML images after the change in this ticket. I believe the right way of handling this is changing both packager and player, as otherwise legit TTMLs would not play correctly on shaka player, and shaka packager generated files would not play correctly on other TTML-compatible players. |
Here's the spec mentioned in the first comment: https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=7291854 |
@joeyparrish @TheModMaker FYI. @Canta You may want to file a bug to Shaka Player and discuss the player issue there. |
We will fix Shaka Player to accept both versions, so existing Packager-generated content with the lowercase attribute name will still function. Thanks! |
System info
Operating System: Ubuntu 20.04
Shaka Packager Version: f0a52cb
Issue and steps to reproduce the problem
While testing some DVBSUB-to-TTML conversions with shaka packager, I could see at playback time the following message using DASH reference player:
Error : SMPTE 2052-1:2013 defines the attribute name as "imageType" and does not define "imagetype"
Checking out some text segment/chunk, I can see the attrubute (note the lowercase
t
):Packager Command:
What is the expected result?:
The same, but with that attribute in camel case format, as expected by the spec (which I didn't read: I'm trusting the player here).
What happens instead?
The error quoted above.
Looks like an easy thing to fix.
The text was updated successfully, but these errors were encountered: