FFmpeg xfade has 59 transitions: which does Sume Timeline take?
FFmpeg's xfade page lists 59 transition values, including custom. Sume Timeline 1.0 accepts six: fade, wipeleft, wiperight, slideup, slidedown and dissolve.

FFmpeg's xfade filter page lists 59 values for transition, custom included. Sume's Timeline 1.0 accepts six on a video[] slot: fade, wipeleft, wiperight, slideup, slidedown and dissolve. All six are names FFmpeg also lists, so a six-type look ports; the other 53 do not exist on Sume, and a circleopen or zoomin has no Timeline field.
FFmpeg facts are from the Filters Documentation, read 2026-10-02. Sume facts are from the Timeline 1.0 docs.
What does FFmpeg require for xfade?
The page says both inputs must be constant frame-rate and have the same resolution, pixel format, frame rate and timebase. duration ranges from 0 to 60 seconds (default 1) and offset sets the start relative to the first input (default 0). A custom transition takes an expr expression. In a raw FFmpeg command you compute each offset yourself.
How does Sume's Timeline handle the same job?
You declare each slot's on-spine start and duration and an optional transition on slots after the first. The docs say declared starts are authoritative and the compiler compensates for the crossfade; you never pre-shift. Transition duration must be at most 1 second, at most 50% of the shorter neighbouring slot, and at least one output frame. More than 8 adjacent fades is refused as too_many_chained_transitions; insert a hard cut. A transition on video[0] is transition_on_first_segment.
Resolution and rate are set once: output.width / output.height (even integers 256 to 2160) and output.fps (24, 25, 30 or 60), with fit per slot (cover, contain, stretch, blur). Mixed-size sources do not need matching first.
{
"audio": { "mode": "silence", "duration_seconds": 12 },
"video": [
{ "source_url": "https://media.sume.com/artifacts/artf_demo/a.mp4", "start": 0, "duration": 6 },
{ "source_url": "https://media.sume.com/artifacts/artf_demo/b.mp4", "start": 6, "duration": 6,
"transition": { "type": "wipeleft", "duration": 0.5 } }
]
}Which names overlap?
Send the body to POST /v1/timeline-1.0/render with an Idempotency-Key; POST /v1/timeline-1.0/plan is the unbilled preflight.
| Value | On the FFmpeg xfade page | On Sume Timeline |
|---|---|---|
fade | Yes (default) | Yes |
wipeleft, wiperight | Yes | Yes |
slideup, slidedown | Yes | Yes |
dissolve | Yes | Yes |
wipeup, slideleft, circleopen, zoomin | Yes | No |
custom with expr | Yes | No |
Sources
Related posts
More in Comparisons
- FLUX 3 Image reference size: 256 px to 16 MP, and Sume URL rules
BFL says each FLUX 3 Image reference is 256x256 px to 16 MP, 1 to 10 images. Sume lists FLUX.2 ids; its reference rules are public HTTPS and a catalog count.
- Gemini batch create is not idempotent: two jobs vs Sume bulk replay
Gemini's docs say sending the same batch creation request twice creates two batch jobs. Sume bulk runs replay the old queue for the same Idempotency-Key.
- Flow charges 7 to 15 credits for Omni Flash; Sume bills dollars
Google Flow prices Gemini Omni Flash 720p at 7 to 15 credits by length. Sume bills the same model per second in dollars; clip costs from 3 to 10 seconds.
- Flow video edit costs 40 credits a try; Sume bills per second
Flow charges 40 credits per Gemini Omni video edit. Sume's video_url edit bills output seconds: $0.625 for 5 seconds, $1.25 for 10 at 720p.
Written by Sume