r/AtlasCloudAI

Most of the time we fight tooth and nail for realism. Sometimes it is a lot more fun to go the other way and make something gloriously impossible. This is a city that bends and folds in on itself, and the wrongness is the entire point.

A dense downtown at dusk, skyscrapers curving and leaning over the street like they are slowly melting toward each other, a river of yellow taxis flowing through the intersection, one small figure crossing below. Every surface is photoreal, the glass, the stone, the wet asphalt, but the space they sit in is impossible. That contrast is the whole trick.

The thing that keeps it dreamlike instead of just broken is to break only the geometry and keep everything else grounded. Photoreal textures, believable lighting, real reflections, correct motion blur on the cars. If you warp all of it at once you get glitch soup that reads as an error. If the materials stay honest and only the space bends, the brain reads it as a dream, not a bug. Controlled wrongness beats random noise.

Motion seals it. A slow, floaty, slightly-too-smooth camera drift gives it dream logic, like you are moving through it rather than filming it. Realism is one lane. Deliberate impossibility is another, and honestly it is the more fun one to drive.

The one setting that decides dream vs glitch: lock the material and lighting realism high and only let the geometry/space distort, otherwise it collapses into noise. Ran it on Seedance 2.0 through an OpenAI-compatible endpoint.

The instinct with AI video is to frame the impossible like a movie poster, centered, lit, heroic. I got a stronger result doing the opposite, framing a cosmic event like someone caught it by accident on a normal camera. The scale reads as real precisely because the shot is not trying to be a shot.

The scene is a mundane harbor at dusk, fishing boats, a hazy city skyline, ordinary water and mist. Then something enormous and wrong rises out of the water, a vast structure unfolding like a slow mechanical flower, water sheeting off its arms. What sells it is the framing. The camera is low, slightly off, half-obscured by spray, not tracking the thing cleanly the way a director would. It reads as a bystander who lifted a phone too late and does not fully understand what they are looking at.

That accidental-witness feeling is the whole trick. A clean epic shot invites you to admire the CG. A shaky, badly-composed, ordinary-location shot tricks you into believing it happened, because that is what real footage of a disaster actually looks like. Mundane setting plus bad-on-purpose framing beats spectacle.

Do not stage the impossible. Film it like an accident, in a boring place, and the scale does the rest.

Ran on Seedance 2.0

Everyone tunes the picture and forgets the audio. The thing that actually made this little cooking clip feel real is the sound, and specifically the one thing I left out of it.

The scene is simple, a young woman cooking a pack of instant noodles in her apartment kitchen at dusk, handheld documentary framing, warm Portra 400 film look, soft grain, shallow focus. Fifteen seconds of quiet slice of life. On the picture alone it is pleasant. What makes it read as a real memory is the audio I wrote into the prompt, shot by shot.

Only diegetic sound, nothing else. Water slowly coming to a boil, the low hiss of the gas burner, the sharp sizzle the moment garlic and chili hit the hot oil, the clink of utensils on the pan, a soft television murmuring in another room. And the deliberate part, no background music at all. A score would instantly turn it into an ad. The absence of music is what leaves room for the kitchen to sound like an actual kitchen.

Two more small things carried it. The dialogue is in her own language with subtitles instead of dubbed flat English, which always sounds more real, and the same face, hair, and clothes hold across every shot from one storyboard reference so she never drifts into a different person.

The picture gets you halfway. Write the room's own sound, and cut the music, and it stops looking generated.

Ran on Seedance 2.0

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

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.

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.

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.

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

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

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.

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 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.

Making an animated short used to need a room full of people. What changed for me is that the whole thing is now a pipeline one person can run. Here are the exact five stages I use, in order.

1. Script. I have a model write the episode as a shot list: scene description, dialogue, narrator lines, tone notes, each scene timed for read-aloud. Treat it like a brief, not a chat. The more direction you write in, the less you fix later.

2. Stills. I turn each scene description into frames with an image model, a few variations per shot, then upscale the best. A character sheet up front keeps the look consistent across the whole series.

3. Motion. I animate the chosen stills into clips, short and deliberate: a slow push-in, a head turn, a glow that pulses then fades. Six to eight seconds per shot beats one long unstable take.

4. Voice. A TTS tool for the lines. The trick is writing the performance into the prompt, the pause, the flat delivery, the half-second hold, instead of just pasting text.

5. Music. One score track that opens quiet, swells once, and resolves, plus a tenser underscore for the action beats.

The thing that actually simplified this for me: stages 1 to 3, the writing, the stills, and the motion, all run through one OpenAI-compatible key, so going from script to image to video is just swapping the model name. Voice and music are the two separate tools on top.

For me stages 1 to 3 (script, stills, motion) all run on one OpenAI-compatible key, so I never leave one setup.

Wanted to see if Seedance 2.0 could do quiet instead of spectacle, so no action, no camera tricks, just a warm afternoon room with slanting light, a girl sitting on the tatami, and a little cat. Hand-drawn anime look, the cozy slice-of-life kind.

Then I gave it a tiny story: the cat finds the crunchy snack I was supposedly saving for tomorrow and absolutely demolishes it, shredded paper everywhere, zero remorse. The fun is that the whole gag reads from one calm scene, the mess, the cat's posture, the girl's quiet defeat, no dialogue needed.

The hard thing about this style is not the prettiness, it is restraint, holding warmth and stillness without overcooking it. Soft light, a cat with no regrets, and a snack that was never going to make it to tomorrow.

Tried the sports-anime hype format in Seedance 2.0: two original rival strikers, the locker-room charge-up before an epic match, all that exaggerated shonen energy. The fun is leaning all the way into the genre instead of fighting it.

What made it land:

- Commit to the genre look. Spiky stylized hair, dramatic rim light, sweat and steam, the over-the-top intensity sports anime lives on. Half-measures read as generic 3D.

- Stage the hype before the action. The locker-room charge-up, fists clenched, glowing aura, sells the match before a ball is even kicked. The build-up is the hook.

- Keep two clearly distinct rival designs so the matchup reads instantly, opposite color energy, opposite posture.

- One continuous escalating beat rather than quick cuts, so the intensity ramps instead of resetting.

Animated in Seedance 2.0, original characters so nothing is borrowed.

What sport would you give the full anime-hype treatment?