The Podcast Clip — Versely recipe is scenes you swap, not a new Omni board
/workflows/versely-podcast-promo is a locked scene list. Recreate it; do not storyboard it again in Kling Omni.
/workflows/versely-podcast-promo is a locked scene list. Recreate it; do not storyboard it again in Kling Omni.
The public recipe is a 9:16 talking-head reel in a cozy studio: one host, a boom mic, a plant, a warm circular wall light. Scene one teases that she stopped hiring editors. Scene two names Versely. That is a scene graph — prompts, a character reference, model, durations — not a vibe. Opening Kling 3 Omni and asking for "six shots of a podcast girl" is a new film that happens to contain a microphone.
Two eight-second scenes, already locked
The workflow object is specific:
- Title on the recipe: Podcast Clip — Versely
- Aspect: 9:16
- Scenes: two, eight seconds each, sixteen seconds of finished tape
- Cast: one locked character asset (
podcast_character) — not "a girl in a cardigan" - Chain: scene two continues from scene one
- Model on the recipe: Kling Video V3 Pro Image to Video
- Credit estimate: a flat 270
Each scene is a pair: a still, then that still animated, then a stitch. Hook, then reveal. Same host. Same couch. Same boom. Native spoken lines in the prompts, not a VO pass you add later.
Recreate is not "make something like this." It is "materialise this graph." Read a workflow's credit estimate before you run it: scene count is not the bill. The video model is. Two scenes at 270 is a different unit from a cheaper I2V row across fifteen scenes.
Recreate clones the graph; Omni invents a bumper studio
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 tease, swap the host still, keep the cuts.
Recreate the workflow, not the screenshot is the same rule in conversion form. A screenshot of a podcast clip tells you the caption was big. It does not tell you the model, the still, the two-scene list, or 270 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. Identity has to survive inside that generate. There is no scene planner, no chain off scene one's last frame, no combined 16-second export of a hook and a reveal as two reviewed takes. You get one bumper with cuts in it.
Useful for a three-beat gag. Not useful for one host across two locked I2V scenes with a named character still. Omni restages. Restaging is drift. The workflow already named the person and attached the still.
Swap the tease. Keep the boom.
Once the format works, the workflow is the product. Clone it. Change the line. Keep the mid-shot, the boom in the foreground, the eight-second beats. 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 workflows catalog is the rest of the map. This page is only Podcast Clip — Versely.
FAQ
Is Recreate the same as generating "podcast girl in a studio" in Omni?
No. Recreate clones the public workflow — two scenes, one character reference, Kling Video V3 Pro I2V, 270 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 podcast template spend the 270 credits?
No. Clone is free. Credits apply when you run it, at the cost shown before dispatch. Edit the tease and swap the host still while it is still a draft.
Can I use Omni under the hood and keep the two-scene structure?
Not as this recipe. Omni multi-shot lives inside one short generate. The podcast clip is two discrete I2V scenes with a locked ref, scene two chained from scene one, stitched. Even if a scene happened to render on a Kling family model, the object is still the scene list, not Omni storyboard syntax.
Why is a 2-scene recipe 270 credits?
Because the estimate is counting the video model, not the scene count. Kling Video V3 Pro Image to Video across two eight-second scenes is a different unit from a cheaper I2V row across a longer cut. Read the model line on the workflow page before you approve the run.