mirror of
https://github.com/CCExtractor/ccextractor.git
synced 2026-02-03 21:23:48 +00:00
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?
📋 Pull Request Information
Original PR: https://github.com/CCExtractor/ccextractor/pull/1464
Author: @emkman99
Created: 12/13/2022
Status: ✅ Merged
Merged: 12/14/2022
Merged by: @cfsmp3
Base:
master← Head:timestamp-map📝 Commits (4)
e10e4e4[FIX] WebVTT X-TIMESTAMP-MAP header placement (#1463)130b374Fixed --no-timestamp-map flag9ae9da9Disable X-TIMESTAMP-MAP by default3d8cac3Write second WebVTT newline when timing info is missing📊 Changes
7 files changed (+26 additions, -19 deletions)
View changed files
📝
docs/CHANGES.TXT(+2 -1)📝
src/lib_ccx/ccx_common_option.c(+1 -1)📝
src/lib_ccx/ccx_common_option.h(+1 -2)📝
src/lib_ccx/ccx_encoders_common.c(+1 -2)📝
src/lib_ccx/ccx_encoders_common.h(+0 -2)📝
src/lib_ccx/ccx_encoders_webvtt.c(+18 -8)📝
src/lib_ccx/params.c(+3 -3)📄 Description
In raising this pull request, I confirm the following (please check boxes):
My familiarity with the project is as follows (check one):
This fixes issue #1463. If enabled, the X-TIMESTAMP-MAP header is placed on the second line. There are always two newlines between the headers and body.
This also fixes the --no-timestamp-map option, which wasn't disabling the header.
I added on the commit to disable X-TIMESTAMP-MAP header by default since it is not valid WebVTT. It doesn't make sense to generate invalid WebVTT by default, especially when the input is not MPEG-TS. This is a breaking change (--no-timestamp-map becomes --timestamp-map).
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.