mirror of
https://github.com/CCExtractor/ccextractor.git
synced 2026-04-18 12:03:00 +00:00
[PR #1827] [CLOSED] Fix SCC timing by accounting for EIA-608 transmission bandwidth #2578
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/1827
Author: @DhanushVarma-2
Created: 12/15/2025
Status: ❌ Closed
Base:
master← Head:fix/scc-accurate-timing📝 Commits (4)
399b939fix: scope SCC timing to encoder context (fixes test failures)6f013b7fix: use original display time for transmission end tracking154a4f1fix: apply SCC accurate timing to 608 encoder pathaad0d78style: apply clang-format to modified files📊 Changes
4 files changed (+73 additions, -1 deletions)
View changed files
📝
src/lib_ccx/ccx_decoders_708_output.c(+31 -0)📝
src/lib_ccx/ccx_encoders_common.c(+1 -0)📝
src/lib_ccx/ccx_encoders_common.h(+2 -0)📝
src/lib_ccx/ccx_encoders_scc.c(+39 -1)📄 Description
In raising this pull request, I confirm the following (please check boxes):
My familiarity with the project is as follows (check one):
This PR fixes inaccurate SCC timing by accounting for the 2-bytes-per-frame
EIA-608 transmission limit (29.97 fps).
Changes:
This makes SCC output compliant with broadcast rules and fixes #1221.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.