The Digestive System Explainer recipe is scenes you swap, not a new Omni board
/workflows/digestive-system-explainer is a locked scene list. Recreate it; do not storyboard it again in Kling Omni.
/workflows/digestive-system-explainer is a locked scene list. Recreate it; do not storyboard it again in Kling Omni.
The public recipe is a kid-friendly 9:16 science reel: a boy bites a cheeseburger and the camera follows the food through mouth, saliva, esophagus, stomach, small intestine, large intestine, and a thumbs-up outro. That is a scene graph — prompts, a character still, model, durations — not a vibe. Opening Kling 3 Omni and asking for "six shots of digestion" is a new film that happens to contain the word stomach.
Eleven named scenes, forty-four seconds
The workflow object is specific:
- Aspect: 9:16
- Scenes: eleven, four seconds each, forty-four seconds of finished tape
- Cast: one locked boy reference on the bite and the outro — messy light-brown hair, yellow star t-shirt — not "a kid"
- Model on the recipe: Kling 3 Turbo Image to Video
- Credit estimate: 396 at preview resolution, 495 at full. Read a workflow's credit estimate before you run it: scene count is not the bill. The video model is.
Each scene is a pair: a still, then that still animated, then a stitch. The Big Bite, Teeth Crushing, Saliva Mixing, Down the Esophagus, Into the Stomach, Stomach Churning, Small Intestine, Nutrients Absorb, Large Intestine, The Exit, Thumbs-Up Outro. Interior shots have no face on purpose. The boy still is attached where the face has to hold.
Recreate is not "make something like this." It is "materialise this graph." The published figure covers the scenes and the stitch. It does not automatically cover captions, dubbing, or rerolls.
Recreate clones the graph. Omni invents a bumper.
Recreate a viral template is the agent verb: browse the public catalog, clone scenes, style, and model into your account, then run or remix. Cloning is free. Running is priced like the generation it is. You see the cost before anything dispatches. It is saved but not auto-run — swap the food still, keep the cuts.
Recreate the workflow, not the screenshot is the same rule in conversion form. A screenshot of a digestion reel tells you the captions were big. It does not tell you the model, the stills, the eleven-scene list, or 396 credits.
Kling 3 Omni multi-shot is not Movie Mode is the other confusion. Omni takes one prompt and returns up to six distinct shots inside a single generation, usually a 15-second file. You still pay for seconds. Identities have to survive inside that generate. There is no scene planner, no chain off scene four's last frame, no combined 44-second export of mouth-then-stomach-then-outro. You get one bumper with cuts in it.
Useful for a three-beat gag. Not useful for a boy-plus-ten-interiors with a locked ref and a narration line per beat. Omni restages. Restaging is drift. The workflow already named the people and attached their stills.
Swap the burger. Keep the cuts.
Once the format works, the workflow is the product. Clone it. Change the food. Keep the 4-second anatomy beats, the interior POVs, the thumbs-up close. Do not go back to an Omni storyboard every Monday because the last clip performed.
If the clip you care about is not in /workflows, you do not have a recipe. Build one: stills first, then I2V, then save your graph. Do not use Omni's six-shot syntax as a substitute for a scene list you never wrote. The boy still is the expensive identity. Swap the sandwich, not the face, unless you are replacing the character asset on purpose.
FAQ
Is Recreate the same as generating "digestive system" in Omni?
No. Recreate clones the public workflow — eleven scenes, the boy reference, Kling 3 Turbo Image to Video, 396 / 495 credits when you run it. Omni is one generate with internal cuts, typically ~15 seconds, up to six shots. Different objects. Different files.
Does cloning the Digestive System Explainer spend the 396 credits?
No. Clone is free. Credits apply when you run it, at the cost shown before dispatch. Edit the food and swap assets while it is still a draft.
Why is an 11-scene recipe cheaper than some 3-scene ones?
Because the estimate is counting the video model, not the scene count. Kling 3 Turbo Image to Video at 396 / 495 for eleven 4-second scenes is a different unit from a premium I2V row across three scenes. Read the model line on the workflow page before you approve the run.
Can I use Omni under the hood and keep the eleven-scene structure?
Not as this recipe. Omni multi-shot lives inside one short generate. The explainer is eleven discrete I2V scenes with a locked ref, stitched. Even if a scene happened to render on a Kling family model, the object is still the scene list, not Omni storyboard syntax.