-
Notifications
You must be signed in to change notification settings - Fork 31
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
Update timeBase attribute to accept full list of values #230
Comments
@claylevering did you spot that IMSC only permits the Having said all that, I'd be really interested to know what your use case is, i.e. which other timeBases you would like to see support for, and why? |
Hi @nigelmegitt - I am not sure I can share the use case directly, I can only assure you that we are seeing timed text files that we need to render in the browser as accurately as they might in a commercial app such as Telestream Switch / etc. This is a QA / QC control as these are valid values, and modifying them to display in browser would invalidate the test itself (as one would be testing a timed text file that is inconsistent with the actual timed text file) |
Hi @claylevering an IMSC validator should show you that such documents (with other timeBase values) are not conformant IMSC documents. |
You are 100% correct and that is unfortunate / unexpected. After reading this section of IMSC 1.1's abstract:
I would have expected IMSC to be a superset of the TTML2 standards (not a limit upon them). I will note that while Please feel free to close / reject this PR if you would like, we will continue to leverage our fork in the interim. |
For what it's worth, we use TTML documents that have SMPTE timebase all the time - they're a delivery requirement for EBU-TT profile files as defined by the BBC Subtitle Guidelines - which are not IMSC conformant files. They have value within particular workflows, especially in broadcast systems when synchronisation against video media timecodes is needed at playout time. However, we convert to media timebase for distribution to web clients. It's also worth noting that the treatment of frame based time expressions changes in TTML when the timeBase is If there were a case for permitting other timebase values, the changes needed would be much more significant than just permitting the two other values defined in TTML for timeBase. |
@claylevering I invite you to join our IMSC/imscJS discord at https://discord.gg/d53nHf2g The biggest issue with supporting Looking forward to better understanding your use case. |
Update timeBase to TTML2 specifications
Please see TTML2 timeBase specification supporting multiple values (not singularly
media
)The text was updated successfully, but these errors were encountered: