Editing an AI Adult Script Beat by Beat

A generated 剧本 is a first draft, and the director does not always guess your intent. Edit mode lets you pull the storyboard back as an editable draft, rewrite beats, retime shots, reorder the scene list, and only then pay for the render. It is the difference between gambling a full render on the director's first pass and shipping a scene you actually approved.

Edit mode is video-only and requires a duration over 15 seconds — the length where a scene becomes a stitched multi-shot storyboard worth editing. Here is the loop.

Why edit before you render#

Rendering is the expensive step; storyboarding is nearly free. Edit mode moves all your decisions — what each shot does, how long it runs, what order they play in — to the cheap side of the line. You approve a plan, then spend once on a render you already trust.

Request an editable draft#

Submit a video task with mode set to edit and a duration over 15s. The task drafts a storyboard and parks at status planned with the plan under a scene field instead of rendering.

curl -s -X POST "$TOKENSTORE_URL/api/v3/contents/generations/tasks" \
  -H "Authorization: Bearer sk-..." -H "Content-Type: application/json" \
  -d '{ "model": "seahorse-480p", "duration": 60, "mode": "edit",
        "content": [{ "type": "text", "text": "a slow bedroom scene" }] }'
# poll GET /api/v3/contents/generations/tasks/:id until status is "planned"

What is in the draft#

Poll the task until status is planned. The scene field carries a segmentCount, a characterImage preview, and a segments array — each segment with an index, its script (the beat), a durationSeconds, an explicit flag, a people-free backgroundImage preview, and any pinned frames. That is the whole storyboard, laid out for editing.

Revise the beats#

Edit each scene's short action beat and let the server re-expand it into a full prompt — you do not rewrite the expanded text yourself. Send a structured edit with only the segments you are changing; each carries a beat plus optional explicit, duration_seconds (4–15), and frame or background overrides.

curl -s -X PUT "$TOKENSTORE_URL/api/v3/contents/generations/tasks/cgt-.../plan/structured" \
  -H "Authorization: Bearer sk-..." -H "Content-Type: application/json" \
  -d '{ "segments": [
        { "index": 1, "beat": "she wakes and stretches toward the window", "duration_seconds": 10 },
        { "index": 2, "beat": "he joins her; they undress each other slowly", "duration_seconds": 8, "explicit": false }
      ] }'

Re-expansion runs asynchronously — the call returns 202, then you poll until the scene is planned again with the refreshed script on each segment. The full field list is under storyboard modes.

Reorder, add, and remove scenes#

In a structured edit the segments array is the authoritative ordered set. Segments are reconciled by index: a missing index is removed, an entry with no index is inserted, and array order becomes the final order. So reordering, adding an insert shot, or dropping a scene are all free — just send the array you want, remembering the durations still have to sum to the locked total.

Render it, or cancel#

Happy with the draft? Submit POST …/tasks/:id/render and the task renders like any other — poll to succeeded for the video URL. Changed your mind? POST …/tasks/:id/cancel refunds the full charge immediately. A draft you never touch is auto-refunded after 24 hours either way. Both endpoints, plus the advanced segments shape you can supply up front, are in the storyboard docs.

Where to go next#

• Writing beats that render as real acts? See explicit scene beats that render.
• Keeping one cast across a long edit? See keeping characters consistent.