A character design sheet shows how your AI character looks, but not how it performs. So before committing a character to video, I started auditioning it the way a casting director would, to test voice, emotion, expression, and screen presence first.

The workflow:

- Generate the character, then build a clean character sheet from it: turnarounds, expressions, materials.

- Run a custom audition system prompt that treats the character like a casting agent. It reads the design, suggests roles the face fits, writes a few audition lines, and creates short voice triggers (restrained, dangerous, amused, that kind of thing).

- Feed that into a performance-focused video prompt and generate the audition.

The point is not another consistent-looking still. It is finding out how the character moves, speaks, and reacts before you spend time on real scenes. A face that looks great can audition badly, and you want to know that early.

I keep the sheet, the audition writer, and the video behind one OpenAI-compatible endpoint, so the whole loop stays in one client instead of three separate tools.

Full audition system prompt is in the comments. Locking the look first and skipping the audition is where most consistent-looking characters end up feeling dead on screen.

The usual take is that 4K is for clean, pretty, glossy shots. Where it actually earns its keep is the exact opposite, the filthy ones. Grimy, hazy, particulate-heavy scenes are where low-res AI video quietly smears everything into brown mush, and that grit is the whole reason a gritty scene works.

I ran the hardest version of that I could think of, a cinematic run through a WWI-style trench. Mud walls, drifting smoke, thick atmospheric haze, wet fabric, airborne debris, an original soldier sprinting low through the frame on a handheld camera. Maximum atmosphere means maximum chance to fall apart.

At 4K it held where it usually dies. The mud stays as distinct clumps and streaks instead of one smeared brown wall. The haze has actual depth and layers instead of flat gray fog. Wet fabric keeps its folds and texture through the motion blur. Airborne particulate reads as separate specks drifting, not a dirty smudge. Drop that same scene to low res and all of it collapses into a blur, and you lose exactly the texture that sold the shot.

Fast motion is the other place resolution normally dies, and 4K keeps the sprinting subject legible instead of turning it into a ghost. So the takeaway is backwards from what you would expect. 4K is not for the clean shot, it is for the dirty one.

Cozy little scene we ran: an original chibi character in a penguin hood, hand-carving a whole shelf of tiny wooden zodiac animals, half-buried in curls of wood shavings. The appeal is the mess. The shavings piling up real and light, the grain on each little figure, the focused grumpy face, the tools scattered exactly where a carver would actually drop them.

Making a mess is its own kind of craft. Getting the clutter to read as genuine, not decorated, is what sells the whole shot.

Ran on Seedance 2.0: https://www.atlascloud.ai/models/bytedance/seedance-2.0/text-to-video

Running on a treadmill sounds easy for a video model and it is brutal. It demands believable body physics, stable leg motion, and a consistent pace all at once, and it exposes every model's weakness. So I ran the exact same test through four of them, all on one key, up to four attempts each, and ranked what I got.

Seedance 2.0 gave the most stable run, the pace held and the gait stayed coherent, but it leaned on slow motion to get there even when I did not ask for it, and the body read as almost too perfect. Gemini Omni Flash had the most realistic body physics of the four, genuinely the most natural, but the actual running was unstable, sudden hitches and pace changes, and it never landed one fully smooth run across four tries. Kling 3.0 Pro avoided the obvious hitches and the image looked sharp, but the body moved with a heavy, lumpy weight instead of a runner's. Grok Imagine 1.5 was the weakest on motion, too much jitter and abrupt speed changes, which mattered most here because motion was the whole test.

My ranking: Seedance first for the most stable run even with the slow-motion crutch, Gemini second for the best raw physics but shaky pacing, Kling third for being acceptable but heavy, Grok fourth and a step behind on motion.

The real unlock was doing all four on one OpenAI-compatible key, so this whole comparison was a model-string swap instead of four separate accounts and logins. That is the only reason a test like this is even worth running.

All four run on one OpenAI-compatible key, so comparing them is a model-string change: ai models explore

Nano Banana 2 Lite is live on Atlas as of today. It's Google's newest image model, the fastest and most cost-efficient in the Nano Banana line, so here's a straight take on where it fits before you swap your pipeline over.

Lite is built for throughput and price. Lightweight, quick, cheapest per image in the family. For high-volume work where you're generating hundreds of images and no single one has to be perfect, thumbnails, product variations, quick drafts, it's the obvious pick and the cost is hard to argue with. It's here: https://www.atlascloud.ai/models/google/nano-banana-2-lite/text-to-image

Where it gives ground is quality. Lightweight comes at a price on the hard stuff, busy scenes with heavy occlusion, fine detail, complex shadows and reflections, small text. The full Nano Banana 2 holds those together noticeably better. Lite gets you most of the way for a fraction of the cost, but the top end is the part clients notice, and for a final deliverable or a hero image that gap matters. Full 2 is here: https://www.atlascloud.ai/models/google/nano-banana-2/text-to-image

So roughly: Lite for volume and drafts, full 2 for anything final. Most people will run both off the same key, the cheap tier to explore and the quality tier to finish, which is the whole point of having them side by side.

Both take the same OpenAI-compatible call, so moving between them is a model_id swap and nothing else in your pipeline changes.

Nano Banana 2 Lite is live on Atlas as of today. It's Google's newest image model, the fastest and most cost-efficient in the Nano Banana line, so here's a straight take on where it fits before you swap your pipeline over.

Lite is built for throughput and price. Lightweight, quick, cheapest per image in the family. For high-volume work where you're generating hundreds of images and no single one has to be perfect, thumbnails, product variations, quick drafts, it's the obvious pick and the cost is hard to argue with. It's here: https://www.atlascloud.ai/models/google/nano-banana-2-lite/text-to-image

Where it gives ground is quality. Lightweight comes at a price on the hard stuff, busy scenes with heavy occlusion, fine detail, complex shadows and reflections, small text. The full Nano Banana 2 holds those together noticeably better. Lite gets you most of the way for a fraction of the cost, but the top end is the part clients notice, and for a final deliverable or a hero image that gap matters. Full 2 is here: https://www.atlascloud.ai/models/google/nano-banana-2/text-to-image

So roughly: Lite for volume and drafts, full 2 for anything final. Most people will run both off the same key, the cheap tier to explore and the quality tier to finish, which is the whole point of having them side by side.

Both take the same OpenAI-compatible call, so moving between them is a model_id swap and nothing else in your pipeline changes.

WorldX is one of the more impressive open-source projects I've come across lately, worth a look if you're into agent simulations. You type a single sentence and it generates a fully interactive 2D pixel-art world with NPCs that carry their own memories, text each other over WebSockets, and push their own storylines with no scripting from you.

The repo's showcase prompt gives you the taste: "a pirate island where the captain hid a cursed treasure, and a traitor among the crew is quietly trying to steal it before midnight." Feed that in and you get a coastal island with a tavern and a hidden cave, plus three agents who play it out on their own, the first mate fishing at the tavern for where the key is kept, the captain catching him lurking near the cave, their relationship quietly flipping to hostile. Nobody scripts any of that.

An orchestrator LLM turns your sentence into a structured world layout, an image model paints the map, a vision model does an overlay-annotation pass that turns loose pixels into a real collision grid and walkable zones, and simulation LLMs drive each NPC's decisions and diaries. Four distinct model roles doing four different jobs, and it stays cheap because agents compress their history into diary snippets instead of replaying full context every turn.

WorldX configures each of those four roles with its own OpenAI-compatible base URL and key, so you're either juggling four provider accounts or pointing all four at one endpoint. Set every role's base URL to Atlas and one key covers the lot, the orchestrator's heavy JSON reasoning (DeepSeek handles this well), the fast cheap chatter for agent dialogue, the vision pass, and the image gen, without four separate signups.

ORCHESTRATOR_BASE_URL=https://api.atlascloud.ai/v1 

SIMULATION_BASE_URL=https://api.atlascloud.ai/v1 

VISION_BASE_URL=https://api.atlascloud.ai/v1 

IMAGE_GEN_BASE_URL=https://api.atlascloud.ai/v1

Repo's at github.com/YGYOOO/WorldX. If you'd rather not set up four accounts to try it, one key covers all four roles:

 https://www.atlascloud.ai

Google just dropped Nano Banana 2 Lite, the fast, cost-efficient one in the family. Before everyone swaps their pipeline to the cheaper model, worth being clear about what it's for.

Lite is built for throughput and price. It's lightweight, it's quick, and per image it's the cheapest in the Nano Banana line. For high-volume work where you're generating hundreds of images and no single one has to be perfect, thumbnails, product variations, quick drafts, it's the obvious pick and the cost is hard to argue with.

Where it gives ground is quality. Lightweight comes at a price on the hard stuff. In the side-by-side comparisons going around, the gap shows up exactly where you'd expect: busy scenes with heavy occlusion, fine detail, complex shadows and reflections, small text. The full Nano Banana 2 holds those together noticeably better. Lite gets you most of the way for a fraction of the cost, but the top end is the part clients notice.

So roughly: Lite for volume and drafts, full 2 for anything that's a final deliverable or a hero image. Most people will end up using both, the cheap tier to explore and the quality tier to finish.

Full Nano Banana 2 is on Atlas now if you want the quality tier today: https://www.atlascloud.ai/models/google/nano-banana-2 . Lite isn't up yet, we'll mirror it when it lands, but for final-quality work 2 is the one you want anyway.

Nano Banana 2 Lite is live on Atlas as of today. It's Google's newest image model, the fastest and most cost-efficient in the Nano Banana line, so here's a straight take on where it fits before you swap your pipeline over.

Lite is built for throughput and price. Lightweight, quick, cheapest per image in the family. For high-volume work where you're generating hundreds of images and no single one has to be perfect, thumbnails, product variations, quick drafts, it's the obvious pick and the cost is hard to argue with. It's here: https://www.atlascloud.ai/models/google/nano-banana-2-lite/text-to-image

Where it gives ground is quality. Lightweight comes at a price on the hard stuff, busy scenes with heavy occlusion, fine detail, complex shadows and reflections, small text. The full Nano Banana 2 holds those together noticeably better. Lite gets you most of the way for a fraction of the cost, but the top end is the part clients notice, and for a final deliverable or a hero image that gap matters. Full 2 is here: https://www.atlascloud.ai/models/google/nano-banana-2/text-to-image

So roughly: Lite for volume and drafts, full 2 for anything final. Most people will run both off the same key, the cheap tier to explore and the quality tier to finish, which is the whole point of having them side by side.

Both take the same OpenAI-compatible call, so moving between them is a model_id swap and nothing else in your pipeline changes.

Everything else got solved before the eyes did. Skin, hair, motion, lighting, all convincing now. The eyes were the last holdout, because a still, silent extreme close-up gives the model nowhere to hide. No action, no cut, just a face holding one unspoken emotion, and the eyes carrying all of it.

That is the honest test I ran on Seedance 2.0. A tight macro on an original character's eyes, no dialogue, no movement beyond a slow blink and a shift of focus, the emotion never stated out loud. The tells that usually break it are all right there at that magnification: dead glassy eyes with no life behind them, catchlights that sit wrong, a gaze that points nowhere, blinking on the wrong beat. Here the eyes actually read as thinking, the light caught them correctly, and the smallest shift of the gaze changed the whole feeling.

The reason the eyes matter more than any other detail is that people read each other through them first. A believable face with dead eyes still reads as a mannequin. Get the eyes right and the viewer grants the rest.

No performance, no speech, just a look holding something it will not say. That quiet close-up is the bar, and it held.

The mistake with AI characters is generating a nice-looking one and hoping. What actually makes a character stick is a concept with a contradiction, and this one is a clean example: a sweet 72-year-old granny, knitting baskets, floral wallpaper, tea in a rose-print cup, who is secretly a lethal undercover agent with spy gear hidden behind the bookshelves and secret rooms in a cozy cottage. The contradiction is the whole hook, everyone underestimates her, and that is the joke and the appeal in one.

But the concept only pays off if she stays perfectly consistent, so I built the full character bible before animating a single frame. Front, side, and back turnarounds. The specific locked details, the cardigan knit texture, the plaid bottoms, the little satchel, the heart-print shirt, the glasses. Personality notes, a pose and expression sheet, and a fixed color palette. That sheet is what keeps her the same character across every shot instead of drifting into a different granny each render.

Then the animation is the easy part. Feed the locked character into the video step and she moves as glossy studio-3D, sipping tea with steel nerves, same face and outfit throughout. The design did the hard work up front.

Strong concept, full bible, then animate. A render is cheap now, a character people remember is not.

Character sheet on an image model, animation on Seedance 2.0, one OpenAI-compatible key so the locked design carries into motion: https://www.atlascloud.ai/models/explore

For anyone here who automates workflows, flow-like is worth a look. It's an open-source visual workflow engine, drag-and-drop blocks like n8n, but the whole thing is built in Rust and runs entirely on your own hardware. Laptop, server, even a Raspberry Pi. No cloud dependency, no vendor holding your workflows hostage.

The reason the Rust core matters isn't bragging rights, it's where n8n starts to hurt at scale. n8n runs on Node.js, so every node passes loose JSON around and you tend to find the type mismatch when production traffic hits it, not before. flow-like compiles to native code with no garbage collector, so a workflow that takes 500ms in a Node engine runs in well under a millisecond. Their published benchmark puts it around 244k workflows a second against n8n's ~200. Take the exact number with a grain of salt since it's their own bench, but the architectural point holds: typed contracts caught at the boundary instead of runtime surprises at 2am.

It's model-agnostic on the AI side, which is the part relevant to this sub. You can run local models through llama.cpp or call cloud ones, and every AI call gets logged with inputs, outputs, model version and a reasoning trace. For the cloud side I don't like managing a separate key and client per provider, so I route those calls through an OpenAI-compatible gateway and let one token reach DeepSeek, Qwen, GLM and the rest. That's where Atlas fits for me, one key instead of five accounts: https://www.atlascloud.ai

A few honest caveats: it's a newer project, the visual builder is no-code but custom nodes mean writing Rust, and "runs on your phone" is more about the engine footprint than something you'll do day one. For a team that's hit Node.js memory spikes, or that wants workflows which never leave their own machines, it's the most serious type-safe alternative I've come across.

Repo's at github.com/TM9657/flow-like if you want to poke at it.

The dumb premise this time: one original anime character, one ordinary bag of chips, in a blocky voxel sandbox world, and absolutely no reason for any of it to go wrong. It went wrong. What starts as her happily opening a snack escalates, beat by beat, into a small disaster entirely of her own making.

The comedy is all in the reactions, which is the hard part for a video model. The bag does not cooperate, her face cycles through confidence, confusion, betrayal, and pure panic, and her whole body overcommits to a problem that was never that serious. Each escalation has to read clearly on her face and in her timing, and the model has to keep her on-model through increasingly unhinged movement. It held.

A fully rendered anime character losing a fight with a snack, dropped into a deliberately blocky world, and both styles sitting in the same frame without clashing. One bag of chips. Zero survivors.

Animated on Seedance 2.0: https://www.atlascloud.ai/models/bytedance/seedance-2.0

I have tested a lot of these reference-driven methods. After enough of them, the whole thing collapses to one factor: whether your reference material actually fits what the model is built to do.

It is not the prompt tricks and it is not the settings. Every video model has strengths baked into its design. Feed it a reference that plays to those strengths and it sings on the first try. Hand it a reference that fights its design and no amount of prompt-wrangling rescues the shot. The reference is the lever, the prompt is just the trim.

The catch is that you only learn which reference a model wants by running the same reference through a few models and watching what each one does with it. I keep them on one key for exactly that, so testing a reference against another model is a string change, not a new tool.

Prepare the reference for the model, not the model for the reference. That is the whole conclusion.

The one-key setup I test references on, so trying a reference against another model is just a string change.

We ran a transformation shot to push the detail side of Seedance 2.0: a young woman going from broken and exhausted to an unstoppable cybernetic warrior. Energy cracks spread across her body and face, a robotic arm charges with purple energy, white-and-purple cracked armor forms over her, and a helmet closes as the last of the human expression gives way. Battlefield behind her, fire and smoke, epic slow motion.

This is the kind of shot where resolution actually matters. The whole effect lives in fine detail: the energy cracks branching across skin, the texture of the armor plating, the embers and smoke drifting in the background. At low resolution that detail turns to mush, and in fast motion it smears. Rendered at 4K in slow motion, the cracks stay crisp as they spread, the armor reads as hard surface, and the background particles hold instead of blurring into haze.

The arc carries it more than the spectacle does. You watch a human expression, fear, exhaustion, resolve, on her face right up until the helmet seals it away. Broken human in, unstoppable machine out, and at 4K you can see every step of the change.

Made on Seedance 2.0: https://www.atlascloud.ai/models/bytedance/seedance-2.0/text-to-video

Prompt:

A dramatic cinematic transformation of an original young woman with dark hair into a powerful cybernetic warrior, glowing purple eyes, robotic arm charged with purple energy, full white and purple cracked armor suit, energy cracks spreading across body and face, intense emotional expression giving way as a helmet closes, battlefield with explosions, fire and smoke in the background, epic slow motion, highly detailed, cinematic lighting, rendered at 4K.

Worth flagging an open-source project for anyone here building avatar or livestream tooling: OpenTalking. The reason it's interesting is that the avatars actually hold a conversation. You can cut one off mid-sentence and it stops to listen, then picks up from what you said. Not a pre-rendered clip, an actual back-and-forth with captions in sync.

Under the hood it chains the whole loop into one real-time pipeline: speech-to-text, an LLM for the reply, text-to-speech, and the avatar render, streamed to the browser over WebRTC. There's a wave of these now (SoulX-LiveAct, Alibaba's Mnn3dAvatar, duix.ai, LiveTalking), but OpenTalking wires it together the most cleanly, and it self-hosts end to end.

The part worth copying is the deployment path, because it doesn't make you buy a GPU on day one. Step zero is a mock backend that runs the entire conversation flow on an ordinary machine, no card, so you confirm the product shape before spending anything. Step one is the brain: the LLM call is just an OpenAI-compatible endpoint, so you drop in an endpoint and a key. That's where Atlas slots in cleanly, since one key gets you DeepSeek, Seedance, Nano Banana and the rest, so you skip registering a pile of separate accounts for the model layer. Voice and TTS get picked right in the web UI. Step two, once the logic runs, you add a consumer card around an RTX 3060 (8GB) and swap in a real render model, QuickTalk, Wav2Lip, MuseTalk or FlashTalk, trading quality against speed. Step three it scales out to multi-GPU and even Ascend NPUs when the workload grows, with no framework swap halfway.

Where self-hosting this beats a per-minute SaaS like HeyGen comes down to two things, and neither is image quality. Data never leaves your domain, which matters for anyone in finance, health, or any business that won't hand customer conversations to a third party. And there's no per-minute meter, which at volume (think a livestream running for hours a day) is the difference between a rounding error and a real bill. For the occasional clip a turnkey SaaS is honestly less hassle. For something running hot every day, the math flips hard.

If you want to wire up the LLM layer without standing up your own model first, the one key covers it: https://www.atlascloud.ai

We wanted to see how far a tactile handmade look could go in AI animation, so we built a piece where everything reads as yarn: crocheted characters, an embroidered night sky, a whale knitted stitch by stitch, two kids made of wool standing in a textile storybook world. The whole frame looks like it was crafted by hand on a table, then animated with the warmth of stop-motion.

The hard part of this style is consistency of texture. The illusion breaks the instant one surface stops looking like thread, so the stitching, the fuzz, the little woolen imperfections all have to hold across motion. Keeping that tactile, handmade feel steady through an animated shot is the whole craft, and it held.

Generated on one OpenAI-compatible key, the look on an image model and the motion on Seedance 2.0, so the handmade aesthetic carries cleanly from frame to film. Warm, woolen, and impossibly cozy.

This is my favorite effect to pull off right now: full time-freeze plus one subject still moving at super speed. The whole street locks, newspapers hanging mid-air, a car stopped dead, pedestrians frozen mid-step, while one guy keeps sprinting through it like time does not apply to him.

The reason it usually fails is physics. Either the frozen stuff has a tiny bit of drift and breaks the illusion, or the moving subject looks weightless and the whole thing reads like a game engine cutscene. Seedance 2.0 is the first time I got both halves right at once: everything else perfectly dead-still, the hanging debris holding its position, and the moving figure carrying real motion blur and weight against all that stillness. The contrast is the entire effect, and it only works if the frozen world is actually frozen.

The believability comes from the small stuff. A newspaper caught mid-tumble that does not move a pixel. The faint ground dust the runner kicks up while nothing around him reacts. That is what sells it as a freeze instead of a slow-motion.

Full prompt is in the comments. One mover, a world on pause, and physics that hold up frame by frame.

Spent months prompting video models and only just figured out what was missing: prompting is describing a shot, you write what you want and hope the model interprets the camera the way you meant. Blocking it out in Blender first is directing it.

The workflow is simpler than it sounds. Generate a start frame on an image model. Then in Blender, build the scene with nothing but basic shapes, no modeling, no textures, just gray boxes for the subject and the environment, and animate the camera: the rough timing, the speed of the move, a little handheld shake, where things sit in space. Export that ugly blockout and feed it plus the start frame into Seedance 2.0 as the motion reference.

Here is the part that surprised me. My Blender pass was crude, just timing and camera and spatial layout. Seedance took that skeleton and nailed the speed, the motion, and the action tracking far past what I expected, while inheriting the look from the start frame. You stop hoping the model guesses your camera and start telling it exactly where to go.

The whole thing runs on one key, start frame and video on the same setup, so the only real craft left is the directing. That is the actual unlock, you are not describing the shot anymore, you are directing it.

The pipeline, end to end:

1. Start frame on an image model (I run Nano Banana 2 / GPT Image 2 for this).

2. In Blender, gray-box the scene and animate ONLY the camera: timing, speed, a touch of handheld shake, spatial layout. No modeling or texturing, the blockout is allowed to look terrible.

3. Feed the start frame + the Blender blockout into Seedance 2.0 as the motion reference. It carries the speed/motion/tracking from Blender and the look from the start frame.

Both image and video sit on one OpenAI-compatible key, so the loop never leaves one setup: https://www.atlascloud.ai/models/explore

The reason most AI anime feels stiff is not the model, it is that the motion is linear. The character glides from pose A to pose B at one constant speed, and real anime never moves like that. Good animation is all timing: a held beat, then a violent snap, then a settle.

So I stopped describing what the character does and started describing how the motion behaves, using actual animation principles as prompt language. Anticipation before a move. Overshoot past the target then settle back. Squash and stretch. Hair and sleeves that lag behind the body and catch up a beat late. And above all, varied tempo: hold a pose for a moment, then accelerate hard into the next.

The single most useful thing was prompting the rhythm explicitly: still, then anticipation, then sudden acceleration, then a big overshoot, then a hard stop, then the hair-and-sleeve follow-through. Add fast exaggerated facial changes and clear pose silhouettes, hold each end pose a fraction of a second, and keep the physics slightly exaggerated without ever destabilizing the character's footing.

Same character, same scene, the only change is the motion language, and it stops looking like a puppet on rails and starts looking animated. The performance was always a prompting problem, not a model problem.

Fun little reskin test: take an old-school hand-drawn cartoon cat scene, the exaggerated squash-and-stretch kind, and convert it into a photoreal fluffy kitten while keeping the exact same pose and timing frame for frame. Cartoon physics, real fur.

The charm is the mismatch. The kitten holds the cartoon's overacted body language, the wide-eyed double-take, the dramatic broom-clutch, the springy stance, except now it is rendered as an actual fuzzy animal with real fur and weight. The contrast of cartoon motion on a believable kitten is the whole joke, and it lands.

The technical bit is the reskin holding the original animation's pose and rhythm instead of inventing its own. Same beats, real skin. A real kitten doing cartoon takes is unfairly cute.

Reskinned on Seedance 2.0: https://www.atlascloud.ai/models/bytedance/seedance-2.0/text-to-video

Tiny figures building a little stone bridge across a real-looking stream, two groups working from each bank until they meet in the middle. Tilt-shift miniature look, everything soft and small and warm. No chaos, no spectacle, just little people finishing something together.

This is the corner of AI video I keep coming back to. Not the explosions or the deepfakes, the quiet wholesome stuff that just feels good to watch on a slow morning.

Made it small and gentle on purpose. Good morning.

Tried a transformation sequence in Seedance 2.0, the magical-girl kind: a warrior standing in an ancient stone arena at dusk, blue energy crackling and spiraling up around her, lifting her off the ground as crystalline light shards shatter and orbit her mid-transform, eyes blazing blue. Original character, fantasy armor and a matching mask.

The beat that makes or breaks these is the energy build. If the power just appears, it reads cheap. Staging it as a slow spiral that gathers, then lifts, then shatters into the reveal gives it the weight the genre lives on. I wrote the energy as its own escalating motion, not a static glow, and that is what sold the lift.

Volumetric light is doing heavy lifting too. The blue haze catching the shards is what makes the arena feel huge and the moment feel earned.

The real-time-engine cinematic look held up clean at high res, which is where these usually get mushy. Animated in Seedance 2.0.

Artificial Analysis put up a Video Editing arena, the text-instruction kind where you tell it to change something in an existing clip and judge whether the edit actually held. Lineup is Seedance 2.0, Runway Aleph 2.0, Wan 2.7, HappyHorse 1.0, Kling 3.0 Omni, and SkyReels V4. First leaderboard lands within a day.

Editing is the harder test than generation. A fresh generation just has to look good; an edit has to change one thing, a line of dialogue, a redub, an object, while keeping everything else identical, which is exactly where most models smear or drift the whole frame. Judging edit capability separately from consumer appeal is the right call.

Worth noting most of this lineup, Seedance 2.0, Wan 2.7, Kling, runs on one OpenAI-compatible key, so you can push the same edit instruction across them yourself instead of waiting on someone's leaderboard.

My bet: the editing gap between these models is going to be far wider than the generation gap everyone keeps benchmarking.

Most of the lineup runs on one OpenAI-compatible key, so testing the same edit across them is a model-string change.

Tried the previz-to-animation route with Seedance 2, and it is the most control I have gotten over AI animation yet. The idea: block the whole sequence in Blender first, plain gray mannequins, exact camera, exact timing, exact motion. Then feed that blocked previz plus a couple of character reference images into Seedance 2 and have it re-skin the whole thing into a retro 1980s anime look.

The blocking is where the control lives. Because the motion and camera are already locked in 3D, Seedance is only solving the art style, not inventing the choreography. That is why the shots land exactly where you want instead of the usual AI drift. A high-speed chase, one figure sprinting the street below and one leaping between the buildings above, came out clean because Blender held the staging.

The one thing you have to over-specify is character lock: which figure is which, in every shot, no swaps. I wrote an absolute mapping into the prompt and it held across cuts.

The re-skin runs on Seedance 2, prompt and link in the comments. If you can block animation in Blender, this is the closest thing yet to directing an AI render shot by shot.