Restyle a clip longer than 30 seconds: trim, then Genjutsu
Genjutsu takes 4 to 30 second sources. For a longer clip on Sume, cut ranges with video trim, restyle each range, then join them with Timeline.

Genjutsu Restyle works on reference videos from 4 to 30 seconds, and Sume's Genjutsu model accepts the same 4 to 30 second window. For a longer clip, cut it into ranges of 30 seconds or less with POST /v1/video-trim, restyle each range as its own job, then join the results with Timeline 1.0.
The 4 to 30 second range is from Higgsfield's September 30 changelog and Video Router; the trim rules are from Video trim, read 2026-10-01.
How do I cut a range with video trim?
Video trim takes one workspace media.sume.com clip plus a range and returns a new MP4 holding only [start, end); the source is untouched. Send video_url, start, and exactly one of end or duration, with an Idempotency-Key. Import off-host media first with POST /v1/media-imports. Poll with GET /v1/jobs/:id/status and read GET /v1/jobs/:id/result.
curl -X POST https://api.sume.com/v1/video-trim \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: trim-part-1" \
-d '{
"video_url": "https://media.sume.com/artifacts/artf_demo/long.mp4",
"start": 0,
"duration": 30
}'What can go wrong with the range?
Trim refuses a request with neither end nor duration as video_trim_range_required, and a range with end at or before start, or longer than 900 seconds, as video_trim_range_empty. Your 30-second ranges sit far below that cap. Keep each range at 4 seconds or more, the model's documented minimum.
| Step | Limit |
|---|---|
| Trim range | duration 0.2 to 900 seconds; source up to 1800 seconds |
| Genjutsu source | 4 to 30 seconds |
| Join | Timeline 1.0 takes Sume-hosted clips |
How do I put the restyled parts back together?
Each Genjutsu result is a Sume-hosted clip. Place them in order in Timeline's video[] and supply an audio spine, since Timeline needs one; you can attach the original soundtrack there, or declare audio.mode as silence. Details are in Timeline compose and audio.
Will the seams between ranges show?
The docs make no promise that independently restyled ranges match at the cut. Style can drift between jobs, so use the same reference images and prompt for every range, and cut on a scene change where you can. Check the first join before you run the whole clip.
Sources
Related posts
More in Developers
- Retool concurrency 100, burst 200, and Sume bulk runs
Retool cloud workflows list concurrency 100 and burst 200. Sume bulk runs take 1-100 items at concurrency 1-16, so one bulk call fits a Retool budget.
- Retool resource block 10-minute limit and Sume async jobs
Retool async resource blocks stop at 10 minutes. Submit the Sume job in async or webhook mode, return the job id, and finish in a separate step or workflow.
- Rime Arcana retired: use Coda; Sume TTS Router model_not_found
Rime retired Arcana on 2026-08-15 and serves arcana ids with Coda. Sume's TTS Router fails unknown model ids with 400 model_not_found; check the catalog.
- Rime Coda 180 s audio limit vs Sume TTS 1200 s limit
Rime Coda 1.0.5 uses a 180-second maximum audio duration. Sume TTS 1.0 fails audio past 1200 seconds with tts_duration_exceeded; join parts for longer audio.
Written by Sume