Repository navigation
Consume fixed H264 scaling lists and preserve full V3 parser records - #34
Merged
Merged
Conversation
antono3
changed the title
This was referenced Oct 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes
Validation
H.264 regression tests passed stable Linux/Windows and strict V3/TinyCC CI. The standalone current-V3 struct-copy reproducer fails with sizeof(variable) and passes with sizeof(explicit type); stable V also passes the explicit-type form. The complete local player suite now passes 3/3 using clean upstream V 0dc6a69 with strict V3/TinyCC and current public dependencies. Full downstream Linux/Windows CI is running on this revision. Windows hardware playback remains deferred. No release is published.