Repository navigation
[2/3] feat: hold the nearest baked html5 frame while playing - #272
Merged
Merged
Conversation
dazzatronus
changed the title
dazzatronus
force-pushed
the
derk/html5-progressive-2-held
branch
from
October 29, 2026 01:07
e56d4c2 to
c0dc65d
Compare
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 29, 2026
# [2.30.0](v2.29.5...v2.30.0) (2026-10-29) ### Bug Fixes * give html5 and rich-caption clips their own look on the timeline ([#275](#275)) ([7a7eb39](7a7eb39)) ### Features * hold the nearest baked html5 frame while playing ([#272](#272)) ([4f50166](4f50166)) * play html5 frames as they bake ([#271](#271)) ([7e837e6](7e837e6)) * tell viewers when html5 playback is buffering ([#274](#274)) ([65098cf](65098cf))
|
🎉 This PR is included in version 2.30.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
A playing html5 clip still rendered a full-size still at every frame its bake hadn't drawn yet. Stills share the main thread with the bake, so pressing play slowed the bake that playback was waiting on.
A playing clip now holds the latest baked frame, provided it is at most 7 frames behind the playhead (233 ms at 30 fps). Further back than that, it renders a still as before. The frame on screen stays up until a newer one lands. Playback never steps back to an older frame, and it never decodes the frame it already shows. Paused or scrubbed, a clip shows the exact frame, so pausing on a held frame renders the exact one.
The measurements below cover this PR and [1/3] together. The edit has 15 overlapping html5 clips. Each run covers the first 30 s of play straight after opening, in headless Chrome with the GPU. There were 5 runs, with each clip weighted by how much of the picture it covers.
Squash subject:
[2/3] feat: hold the nearest baked html5 frame while playing. This cuts a minor release.Verify:
npx jest tests/html5-player.test.ts -t "hold|held|7 frames|steps back|pauses". Then press play straight after opening an edit with html5 clips. Motion should be choppy where the bake is thin and should never jump backwards. Pausing should show a sharp frame.Risk: low. Where no baked frame is within 7 frames, stills take over as before.