mirror of
https://github.com/CCExtractor/ccextractor.git
synced 2026-02-03 21:23:48 +00:00
[BUG] Incorrect placement of X-TIMESTAMP-MAP in WebVTT #726
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bbgdzxng1 on GitHub (Dec 13, 2022).
Summary
When ccextractor is generating webVTT output,
X-TIMESTAMP-MAPdoes not immediately follow theWEBVTTheader.tl;dr: Propose that
12b9f939feis reverted.Reference
According to Roger Pantos, the author of the HLS RFC...
"To be clear, what HLS expects (and what the VTT spec defined prior to that 2016 change) is for the
X-TIMESTAMP-MAPline to be among a set of non-blank lines immediately after theWEBVTTheader line, followed by two or more line terminators, followed by the rest of the body."Here is Roger's full statement, clarifying the expected behavior https://mailarchive.ietf.org/arch/msg/hls-interest/4vmLpEsV-EnmkEwMQZkzbGQai_4/ clarifying the background around the . Roger is the authoritative reference on HLS RFC8216.
See also:
https://github.com/w3c/webvtt.js/issues/38
https://github.com/w3c/webvtt/issues/485
Expected Behavior
Note that there is no blank line after the WEBVTT statement.
Current Behavior
Command to replicate...
Where CNN.ts is taken from CNN.ts from "US TV recordings, 10 minutes samples, HDHomeRun" located at https://ccextractor.org/public/general/tvsamples/.
Details
Here is the pull request where the regression occurred.
https://github.com/CCExtractor/ccextractor/pull/1332/files
12b9f939feI'm confident that @emkman99's PR was well-intended, however, the link above from Pantos confirms the expected behavior, with absolute authority. @emkman99 - I hope that the snippet from Pantos is helpful.
Conclusion
12b9f939feshould be reverted to ensure that WebVTT output aligns with HLS RFC.[ My personal view is that ccextractor should not generate X-TIMESTAMP-MAP by default, but it should be enabled through a
--timestamp-mapoption, but that is a subjective opinion would be a change of functionality. I have tried to limit the bug report to an objective clarification of the standards, quoting the author of the HLS RFC.]Thanks - I hope this is not a contentious topic.
@bbgdzxng1 commented on GitHub (Dec 20, 2022):
Closing the end-user facing ticket, because of the awesome work included in https://github.com/CCExtractor/ccextractor/pull/1464 will now track it. You guys don't want open tickets hanging around.
As ever, many thanks @emkman99 for the very sensible enhancement and @cfsmp3 for the project.