Mixing 24 fps Seedance clips with 30 fps footage in Sume Timeline
Set output.fps to 24, 25, 30 or 60 in Timeline 1.0. If you omit it, the job matches the sources, and a mismatch returns output_fps_resamples_sources.

When a holiday ad mixes AI clips with phone footage, set output.fps explicitly in Sume Timeline 1.0. The allowed values are 24, 25, 30 and 60. Without it, the job matches the sources, and if they differ it returns the warning output_fps_resamples_sources with the rate the sources wanted.
What the docs say
From the Timeline docs, as of 2026-10-08.
| Setting | Value |
|---|---|
| output.fps | 24, 25, 30 or 60 |
| Default size | 1080x1920 |
| width / height | even, 256 to 2160 |
| fit | cover, contain, stretch or blur |
| Price | $0.10 per ceil(output minute) |
| Plan endpoint | not billed |
Picking a rate
Seedance renders at 24 fps in Sume's cost model, and many phone clips are 30. Choose the rate of the majority of the footage, or the rate the destination wants. 30 suits social placements, 24 suits a film look, and 60 is for UI captures. Shopify's help page recommends 60, 30 or 25 fps for product video (read 2026-10-08), so 30 fits both a Seedance mix and a store page.
- Run the plan endpoint first; it costs nothing and shows warnings.
- Treat output_fps_resamples_sources as a decision prompt, not an error.
- Use fit: cover for full-bleed, blur for letterbox backgrounds.
Checks before a batch
Join two clips with a plan call, read the warnings, then render. Once the rate is set, fix it in your template so 1,200 renders carry the same value.
Where it goes wrong
The common mistake is leaving fps unset and letting a 24 fps clip and a 60 fps screen recording fight over the output rate. The warning tells you the rate the sources wanted, so read it and decide, rather than accepting what the job picked.
Another is mixing sizes. fit controls how a clip that differs from the output frame is placed: cover crops, contain letterboxes, stretch distorts and blur fills the bars with a blurred copy.
- Plan call first; it is not billed.
- Set output.fps in the template.
- Keep one fit value for the whole timeline unless a clip is an exception.
Before you scale
A fixed template also makes batch cost predictable. Because Timeline bills $0.10 per ceil output minute, a 45-second render and a 60-second render cost the same, and a 61-second render costs $0.20. Trim to just under the minute where the ad allows it, and set the fps and the size once so every SKU renders under the same rules.
Sources
Related posts
More in Media tools
- Timeline output fps: omit it to follow your clips, or get a warning
Leave output.fps out and Timeline 1.0 follows your longest video sources. Force 30 on 24 fps clips and the job warns output_fps_resamples_sources.
- A 7:30 Timeline render bills 8 minutes: cut 30 s to save $0.10
Timeline 1.0 charges $0.10 per ceil(output minute). A 450-second render is 8 minutes, $0.80; trimming it to 420 seconds bills 7 minutes, $0.70. Table and code.
- Timeline render_strategy_unsafe: why single fails above 12 slots
Timeline returns render_strategy_unsafe when strategy single is used with over 12 slots. Leave it on auto, which chunks past 12 segments. Limits and the fix.
- Timeline too_many_chained_transitions: 8 fades, then a hard cut
Sume Timeline allows at most 8 adjacent fades and returns too_many_chained_transitions past that. Each fade is 1 s or less and 50% of the shorter slot. The fix.
Written by Sume