feat(video): expose Seedance mixed references and render controls - #45
Open
KillerQueen-Z wants to merge 1 commit into
Open
KillerQueen-Z wants to merge 1 commit into
KillerQueen-Z wants to merge 1 commit into
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
1 participant
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.
Expose typed video/audio references and output controls, allow 30 images on Seedance 2.5, and map the supported camelCase controls in both generate and generateFromContent. Retain frame/reference validation and expose last-frame response fields.
Validation
9 video unit tests passed; TypeScript checking, ESLint, CJS/ESM/declaration build, and git diff checks passed.
Rollout and limits
This PR does not deploy or change
R2V_ENABLED. Existing production 503s caused by an explicit off switch require a separate controlled enablement. Publish client changes after the gateway changes are deployed.No new paid upstream renders were performed. New request/response behavior is validated against the captured public upstream parameter schema and mocked contract/payment tests; perform a small paid render smoke test before production enablement. Automatic duration, editing/extension, 2.5 reference video/audio and 1080p, callbacks and draft/flex remain held pending cost/output or lifecycle validation.
See
SEEDANCE_CAPABILITIES.mdfor input examples and capability limits. No authentication, signed-quote format or settlement formula changes.Related PRs