Repository navigation
docs(hero): 4x sped-up README hero GIF - #217
Merged
Merged
Conversation
Re-encode of the 115 s source capture at 4x speed (28.7 s), 640x340 at 12 fps with a full-stats palette, 3.3 MB. The source is variable frame rate (PTS gaps 0.033-0.446 s), so the chain normalises to CFR before scaling PTS: fps=30,scale,setpts=PTS/4,fps=12.
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.
Replaces
docs/clai-hero.gif(the README hero) with a 4× sped-up re-encode of the 115 s landing capture. No README change: the path is unchanged.NETSCAPE2.0, loop_count=0)Why the filter chain looks like this
The source capture is variable frame rate — measured PTS gaps range from 0.033 s to 0.446 s (~20.7 fps average).
setpts=PTS/4alone works on presentation timestamps and does not normalise variable timing, so the chain resamples to CFR first, then scales PTS:Deviation: 640 px wide at 12 fps, not 720 px at 15 fps
720/15 came out at 4.92 MB — under the 5 MB ceiling but far from the ≤3 MB ideal and ~83% heavier than the asset it replaces. Measured fallback ladder (width → fps → dither, as specified):
Bayer dithering barely helped on this content (dense UI text), so it was not used. 640×12 is the smallest variant that stays recognisable: dropping to 10 fps saves only 0.05 MB and makes the already-4×-fast motion visibly choppy, so 12 fps is the stopping point. The GIF is rendered at
width="100%"in the README, so the narrower intrinsic width costs no layout change.Verification
NETSCAPE2.0application extension (loop_count=0) and the0x3Btrailer.