Document existing --timestamp-map option for WebVTT output #2065
+16
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In raising this pull request, I confirm the following (please check boxes):
My familiarity with the project is as follows (check one):
Description
This pull request documents the existing
--timestamp-mapcommand-line option for WebVTT output.The functionality to enable the
X-TIMESTAMP-MAPheader already exists in the codebase and is disabled by default.However, it was not documented in the README, which led to confusion and the long-standing open issue #1127.
What this PR does
--timestamp-mapoption in the READMEX-TIMESTAMP-MAPheader is needed (e.g. HLS workflows)What this PR does NOT do
Testing
Closes #1127