Repository navigation
Version Packages - #512
Merged
Merged
Version Packages#512
Conversation
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@vosjs/elements@0.12.2
Patch Changes
FrameAccurateVideoSource.seekTodecodes through oneVideoDecoderand collects its frames through one handler, and nothing kept two calls from overlapping: a render loop that seeks every frame (live playback, which does not wait for a decode the way a capture does) started a decode before the last one ended, so the two stole or dropped each other's frames and the video showed frames out of order while the decoding piled up. Now decodes run one at a time, a seek made while one runs only replaces the target of the next run (the frames in between are skipped, never queued), every call still resolves once the canvas shows its frame or a newer one, and a seek to the frame already drawn decodes nothing. A capture, which awaits each seek before the next, decodes exactly as before. Measured on a live program seeking two 1080p videos every frame under 4x CPU throttling: wrong frames went from 5 in 40 samples to none.