fix: Properly handle ATSC CC in private MPEG-2 streams #1930
+11
−24
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.
Summary
Changes
1. ATSC CC in private MPEG-2 streams now works
Previously,
CCX_PRIVATE_MPEG2_CCbuffer type was created but never properly implemented. It would dump raw data and return placeholder bytes instead of actually processing the captions.Fix: Both private MPEG-2 streams (0x06) and user-private streams (0x80-0x8F) with ATSC CC codec now return
CCX_PESbuffer type and use the same processing path.2. Debug output no longer floods terminal
Several
dump()calls were usingCCX_DMT_GENERIC_NOTICESwhich is enabled by default, causing binary hex dumps to appear during normal operation.Fix: Changed to appropriate debug-only masks:
avc_functions.c: SEI error dumps →CCX_DMT_VERBOSEgeneral_loop.c: Unrecognized header dumps →CCX_DMT_PARSETest plan
🤖 Generated with Claude Code