Repository navigation
Correct motion-stack recipes and verify video export presets - #33
Merged
Merged
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.
The bake recipe could leave a paused video waiting for a decoded-frame callback before initiating the seek that produces that frame. The advertised 1080p preset also retained the input resolution. Correct those instructions and the integration/licensing errors found in the motion-stack references.
Validation:
npm test, skill validator, link and whitespace checks passed.Reference-only change: this does not claim new end-to-end tests of every third-party engine or measured LLM routing accuracy. No release/version bump is included.