fix(playback): await video readiness and prepare frames before cuts - #187
Merged
dazzatronus merged 2 commits intoSep 15, 2026
Merged
Conversation
Contributor
|
@bfreskura thanks for reporting and providing a fix. |
github-actions Bot
pushed a commit
that referenced
this pull request
Sep 15, 2026
## [2.19.5](v2.19.4...v2.19.5) (2026-09-15) ### Bug Fixes * **playback:** await video readiness and prepare frames before cuts ([#187](#187)) ([6295fa9](6295fa9))
|
🎉 This PR is included in version 2.19.5 🎉 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
2 participants
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.
Why this change was needed:
Browser previews can flash stale frames after changing a video's trim or speed and seeking backward. A runtime trace showed
loadEdit()returning while replacement videos were still loading.What changed:
reconcileInitial().The equivalent local patch was confirmed to resolve the reported playback glitch in the consuming application using SDK 2.17.0, including trim/speed changes with incremental updates and subsequent loops.
Problem solved:
Fresh initialization now waits for player readiness, and future video clips prepare their required frames before their cuts. Trim and speed changes continue to use the existing incremental update path.