Skip to content

Conversation

@mohithshuka
Copy link

@mohithshuka mohithshuka commented Jan 28, 2026

In raising this pull request, I confirm the following (please check boxes):

  • I have read and understood the contributors guide.
  • I have checked that another pull request for this purpose does not exist.
  • I have considered, and confirmed that this submission will be valuable to others.
  • I accept that this submission may not be used, and the pull request closed at the will of the maintainer.
  • I give this submission freely, and claim no ownership to its content.
  • I have mentioned this change in the changelog.

My familiarity with the project is as follows (check one):

  • I have never used CCExtractor.
  • I have used CCExtractor just a couple of times.
  • I absolutely love CCExtractor, but have not contributed previously.
  • I am an active contributor to CCExtractor.

{pull request content here}

mbro added 2 commits January 27, 2026 13:57
- Implements HTML/CSS/JS visualization tool for -out=report output
- Parses report.txt and displays subtitle pages as cards
- Shows timestamps, types, and subtitle activity
- Includes Chart.js timeline visualization
- Resolves CCExtractor#1689
- Added documentation for existing --timestamp-map CLI option
- Explained usage for HLS workflows vs standard WebVTT
- Added example usage and default behavior
- References issue CCExtractor#1127

Fixes CCExtractor#1127
@mohithshuka
Copy link
Author

Description

This PR documents the existing --timestamp-map command-line option for WebVTT output that was previously undocumented.

What this PR does

  • Documents the --timestamp-map option in README.md
  • Explains when the X-TIMESTAMP-MAP header is needed (Apple HLS workflows)
  • Clarifies default behavior (disabled unless explicitly enabled)
  • Provides usage example

Background

The --timestamp-map functionality was already implemented in the codebase (as seen in src/lib_ccx/ccx_common_option.c and src/lib_ccx/ccx_encoders_webvtt.c), but was not documented in the README. This led to confusion and the long-standing issue #1127.

Testing

  • Documentation-only change
  • No functional changes to code
  • Verified option exists and works as described

Related Issues

Fixes #1127

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant