Indiegogo video 2-4 min: assemble 30 s clips in Timeline
An Indiegogo main video runs 2-4 minutes. Generated clips top out at 30 s on some Sume models, so assemble them with Timeline 1.0 at $0.10 per output minute.

An Indiegogo main campaign video is 2 to 4 minutes, per Indiegogo support, as summarized in search results; confirm on the page. A single generated clip is much shorter, so you assemble it: on Sume, seedance-2.5 accepts 4 to 30 seconds per clip, and Timeline 1.0 joins clips and one audio track into one MP4 at $0.10 per output minute.
The arithmetic
Timeline bills per ceil output minute, and reserves ceil(audio duration / 60) minutes. The clip counts below assume full 30 s clips; shorter clips need more of them.
Clip duration limits and the Timeline rate are from the Sume docs; the docs also say to confirm the rate live in the catalog.
| Output length | Clips of 30 s | Timeline minutes billed | Timeline cost |
|---|---|---|---|
| 2:00 (120 s) | 4 | 2 | $0.20 |
| 3:00 (180 s) | 6 | 3 | $0.30 |
| 4:00 (240 s) | 8 | 4 | $0.40 |
Plan first, render second
Timeline has an unbilled plan route that compiles your document and returns duration, segment count and estimated cost without creating a job. Use it before you spend. Render needs an Idempotency-Key, and every URL must already be a media.sume.com artifact or asset from your workspace; import first.
Declare each slot start on the audio spine. The first start must be 0, later starts must increase, and a transition goes on slots after the first. Slot coverage may trail the spine by at most 0.5 seconds.
curl -X POST https://api.sume.com/v1/timeline-1.0/plan \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"audio": { "url": "https://media.sume.com/artifacts/artf_demo/voiceover.wav", "duration_seconds": 120 },
"video": [
{ "source_url": "https://media.sume.com/artifacts/artf_demo/c1.mp4", "start": 0, "duration": 30 },
{ "source_url": "https://media.sume.com/artifacts/artf_demo/c2.mp4", "start": 30, "duration": 30, "transition": { "type": "fade", "duration": 0.25 } },
{ "source_url": "https://media.sume.com/artifacts/artf_demo/c3.mp4", "start": 60, "duration": 30, "transition": { "type": "fade", "duration": 0.25 } },
{ "source_url": "https://media.sume.com/artifacts/artf_demo/c4.mp4", "start": 90, "duration": 30, "transition": { "type": "fade", "duration": 0.25 } }
]
}'Limits worth knowing
- Timeline audio runs 1 to 1800 seconds and video takes 1 to 200 slots.
- Past 12 segments the default strategy chunks the render; single is refused above 12 slots.
- Poll GET /v1/jobs/{id}/status and read GET /v1/jobs/{id}/result for the video_url.
- Check Indiegogo's current page for the file and format requirements, which I did not verify.
Sources
Related posts
More in Media tools
- LinkedIn video thumbnail under 2 MB: pull the frame with Sume
LinkedIn video ad thumbnails are JPG or PNG up to 2 MB. Pull a still from your clip with Sume's video frames endpoint and check its size before upload.
- LTX-2.5 48 fps option: conform frame rate on Sume
LTX-2.5 offers 24/25 fps or 48/50 fps. Sume's video catalog has no fps field, but Timeline output.fps conforms a clip to 24, 25, 30 or 60.
- Lyria 3.5 output: MP3 or WAV at 44.1 kHz, and what Sume returns
Google lists MP3 by default or WAV, 44.1 kHz stereo, with a SynthID watermark. Sume's music docs say the artifact is typically audio/mpeg. Check it in code.
- Lyria 3.5 prompts: [Verse] tags or [0:00-0:30] time ranges?
Google's Lyria 3.5 docs show [Verse], [Chorus] and [Bridge] tags. Sume's music docs show time-range markers. What each says, and how to test both on one brief.
Written by Sume