Repository navigation
[8/10] fix: default the output frame rate to the render's - #256
Merged
Merged
Conversation
This was referenced Oct 26, 2026
dazzatronus
force-pushed
the
derk/sdk-motion-default-fps
branch
from
October 26, 2026 23:34
e1430ed to
76ed0a1
Compare
dazzatronus
force-pushed
the
derk/sdk-motion-default-fps
branch
from
October 27, 2026 00:00
76ed0a1 to
a1f4b65
Compare
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 27, 2026
## [2.29.2](v2.29.1...v2.29.2) (2026-10-27) ### Bug Fixes * apply effect and transition presets over keyframes in preview ([#254](#254)) ([8ee2542](8ee2542)) * capture html5 clips animated only by their markup ([#258](#258)) ([78c88b6](78c88b6)) * default the output frame rate to the render's ([#256](#256)) ([16d560e](16d560e)) * **deps:** use shotstack-canvas 2.14.1 ([#257](#257)) ([8db1111](8db1111)) * hold the first keyframe value and ease gaps like the render ([#253](#253)) ([0039a74](0039a74)) * let keyframed clips take effects and transitions in the toolbar ([#255](#255)) ([a4127fe](a4127fe)) * preview slide effects with the render's distances ([#252](#252)) ([4afc59a](4afc59a))
|
🎉 This PR is included in version 2.29.2 🎉 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.
Studio fell back to 30 fps when
output.fpswas omitted, but the render uses 25, or 12 atpreviewresolution. Playback, html5 capture and export now use the render's default, so the preview steps through the same frames the render produces. Tests that relied on 30 now set it.Verify:
npm test(2360, +3).shuffle*previewsMerge bottom-up, retargeting each PR after its predecessor lands. Since #248 the release workflow skips the release when the merged PR's title starts
[n/m]with n < m, so 1/10 to 9/10 hold, and 10/10 releases the stack as one version.Merge subject:
[8/10] fix: default the output frame rate to the render's. The repo squashes a single-commit PR under its commit message, so type this in the merge dialog.