<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Yihui AI Lab]]></title><description><![CDATA[Building AI-powered products and sharing my journey as an indie developer.
I write about AI engineering, LLM applications, generative AI, software development, ]]></description><link>https://hashnode.yihui.dev</link><image><url>https://cdn.hashnode.com/res/hashnode/image/upload/v1593680282896/kNC7E8IR4.png</url><title>Yihui AI Lab</title><link>https://hashnode.yihui.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Thu, 20 Aug 2026 09:08:23 GMT</lastBuildDate><atom:link href="https://hashnode.yihui.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[AI Video Prompt Guide: Fix Seedance 2.5 Failures]]></title><description><![CDATA[Cross-posted from the MkAnime blog. I build and write for MkAnime; this is one of a series of Seedance 2.5 workflow guides.
An AI video prompt guide should help you diagnose a failed clip, not just of]]></description><link>https://hashnode.yihui.dev/ai-video-prompt-guide-fix-seedance-2-5-failures</link><guid isPermaLink="true">https://hashnode.yihui.dev/ai-video-prompt-guide-fix-seedance-2-5-failures</guid><category><![CDATA[AI]]></category><category><![CDATA[AI Video Generation]]></category><category><![CDATA[Anime]]></category><dc:creator><![CDATA[Pat Lee]]></dc:creator><pubDate>Thu, 20 Aug 2026 08:05:43 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6a74646f0785c746efc919b8/21b6dea2-3442-4983-baf1-d110141a296d.webp" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><em>Cross-posted from the <a href="https://mkanime.ai/guides/fix-seedance-2-5-character-camera-ending">MkAnime blog</a>. I build and write for MkAnime; this is one of a series of Seedance 2.5 workflow guides.</em></p>
<p>An <strong>AI video prompt guide</strong> should help you diagnose a failed clip, not just offer a longer prompt. When Seedance 2.5 changes the character, spins the camera, breaks the action, loses the ending, or mistimes the sound, find the earliest failed control and revise only that part.</p>
<p>This troubleshooting workflow uses observable symptoms. It avoids the vague instruction to "add more detail," because more detail can create new conflicts while leaving the original cause untouched.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161700Z-image-01-98dccd50.webp" alt="Matched rooftop frames diagnosing identity drift, camera-axis confusion, broken motion, and an unlocked ending" /></p>
<h2>Diagnose the Failure Before Rewriting the Prompt</h2>
<p>Watch the clip once without pausing, then review it frame by frame and record the first moment the shot becomes unusable. Later problems may be downstream effects.</p>
<table>
<thead>
<tr>
<th>Symptom</th>
<th>Likely control</th>
<th>First question</th>
</tr>
</thead>
<tbody><tr>
<td>Face, hair, or clothing changes</td>
<td>Identity anchors or conflicting references</td>
<td>Did the subject change before the action began?</td>
</tr>
<tr>
<td>Camera spins or changes direction</td>
<td>Camera instruction</td>
<td>Did the prompt assign more than one camera job?</td>
</tr>
<tr>
<td>Body skips between poses</td>
<td>Action chain or duration</td>
<td>Is the visible cause missing, or are too many beats compressed?</td>
</tr>
<tr>
<td>Ending introduces a new action</td>
<td>End-state instruction</td>
<td>Did the prompt define a final composition and settle time?</td>
</tr>
<tr>
<td>Sound arrives before or after the event</td>
<td>Audio timing</td>
<td>Is the sound tied to a visible cause?</td>
</tr>
</tbody></table>
<p>Save the prompt and settings with the failed result. A diagnosis without the original inputs cannot support a controlled comparison.</p>
<p>The <a href="https://mkanime.ai/guides/seedance-2-5-anime-test">Seedance 2.5 anime tests</a> are useful as model evidence, but they do not predict every subject or shot. Review your own output against the decisions written in its prompt.</p>
<h2>Fix Character Drift With Fewer Identity Anchors</h2>
<p>Character drift often comes from ambiguity or contradiction, not from a shortage of adjectives. Reduce the identity line to visible facts that must remain stable: hair shape and color, face cues, silhouette, clothing construction, one signature accessory, and the reference image if the project uses one.</p>
<p>Weak:</p>
<pre><code class="language-text">Beautiful mysterious anime girl, extremely detailed, many emotions, elaborate fashionable clothes, cinematic.
</code></pre>
<p>Stronger:</p>
<pre><code class="language-text">Original adult courier with a short copper bob, amber eyes, teal rain jacket with one white zipper, silver camera strap from right shoulder to left hip, compact silhouette. Preserve the same face, hair length, jacket construction, and strap side throughout the shot.
</code></pre>
<p>Do not repeat the identity paragraph inside every beat. State it once, then mention a vulnerable anchor only when the action affects it. If several reference images disagree, remove the weaker ones instead of asking the prompt to reconcile them.</p>
<h2>Fix Camera Chaos With One Movement and One Axis</h2>
<p>Camera chaos begins when the prompt treats every camera term as a quality enhancer. Orbit, pan, zoom, handheld, crane, and tracking are different movement systems; combining them in a short shot gives the frame no stable rule.</p>
<p>Choose one job and define its boundaries:</p>
<pre><code class="language-text">Camera: begin in a locked waist-up three-quarter view. Make one slow push-in along the same axis, ending in a close-up when the character turns. No orbit, no cut, no change of screen direction. Stop moving for the final two seconds.
</code></pre>
<p>If the subject also moves, state who owns each direction. "The character runs left to right while the camera tracks laterally at a stable distance" is clearer than "dynamic camera follows the action."</p>
<p>Use the <a href="https://mkanime.ai/seedance-2-5-prompts">Seedance 2.5 prompt examples</a> to inspect how a camera instruction sits beside the rest of a tested prompt. Compare structure and result; do not assume that copying a camera phrase will produce the same shot with a different subject.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161701Z-image-02-51a3bc5b.webp" alt="Top-down rooftop map comparing a tangled camera instruction with one controlled push-in axis and final hold" /></p>
<h2>Fix Broken Motion With Cause and Effect</h2>
<p>Broken motion looks like teleportation, pose popping, or an object moving before contact. Rewrite the action as a physical chain: trigger, preparation, main movement, contact, reaction, settle.</p>
<p>Instead of:</p>
<pre><code class="language-text">She jumps dramatically over the railing and lands heroically while debris flies.
</code></pre>
<p>Use:</p>
<pre><code class="language-text">The warning light flashes. She looks toward the lower roof, plants both feet, and grips the satchel strap. She pushes off once, clears the railing, lands on both feet with bent knees, then steadies upright. Dust lifts only after her shoes contact the roof and falls as she becomes still.
</code></pre>
<p>If the selected duration cannot show every phase, remove a beat or choose a longer duration. Do not compress a preparation, jump, landing, dialogue line, camera orbit, and new reveal into five seconds.</p>
<h2>Fix Weak Endings With a Locked Final Composition</h2>
<p>A weak ending often starts a new action because the prompt explains what happens but never says where the shot stops. Define the last frame as carefully as the first.</p>
<p>Include subject pose, framing, important prop state, background anchor, light, and motion state:</p>
<pre><code class="language-text">Final frame: stable medium close-up from the front. The courier is upright and still, left hand holding the red satchel strap, blue rooftop door closed behind the right shoulder, face fully readable in late-afternoon light. Camera, hair, clothing, dust, and background motion settle during the final two seconds. No new action or character enters.
</code></pre>
<p>If a precise destination is essential, use a project last-frame reference. Text can describe the goal, but a visible frame gives the generation a more concrete boundary.</p>
<h2>Fix Audio Mismatch With Explicit Sound Timing</h2>
<p>Tie sound to a visible event and state what continues underneath it. "Footsteps, wind, dialogue, music" names ingredients but not a sequence.</p>
<p>Use causal timing:</p>
<pre><code class="language-text">Audio: low rooftop wind throughout. One shoe scrape begins as the character plants the foot. The landing impact occurs at visible contact, followed by a short fabric rustle. After the character becomes still, she says, "Made it." No music and no additional impact sounds.
</code></pre>
<p>If dialogue overlaps the main action, move it after the settle or shorten the line. If effects are correct but a generated voice is not usable, keep the picture and replace the voice in post-production rather than discarding the whole shot.</p>
<h2>Retry One Variable and Compare the Result</h2>
<p>Open the failed result in the <a href="https://mkanime.ai/tools/seedance-2-5-video-generator">Seedance 2.5 video generator</a>, retain its ratio, resolution, duration, and unrelated prompt text, then change only the diagnosed control.</p>
<p>Use a revision log:</p>
<table>
<thead>
<tr>
<th>Version</th>
<th>Observed failure</th>
<th>Single change</th>
<th>Result</th>
</tr>
</thead>
<tbody><tr>
<td>V1</td>
<td>Camera orbits during the turn</td>
<td>Replaced four camera verbs with one push-in axis</td>
<td>Compare framing only</td>
</tr>
<tr>
<td>V2</td>
<td>Character changes after the landing</td>
<td>Reduced identity line and removed conflicting reference</td>
<td>Compare identity only</td>
</tr>
<tr>
<td>V3</td>
<td>Ending continues into a second action</td>
<td>Added final pose and two-second settle</td>
<td>Compare final three seconds only</td>
</tr>
</tbody></table>
<p>Do not improve several categories at once unless the prompt is being rebuilt from scratch. A prettier result is not useful evidence if you cannot tell which change caused it.</p>
<h2>Know When to Regenerate a Shorter Shot</h2>
<p>Shorten the shot when the core idea remains good but the duration contains too many independent beats. Keep the most important action and ending, then move the setup or aftermath into another storyboard panel.</p>
<p>Regenerate a shorter shot when:</p>
<ul>
<li>the character stays stable until a late location or costume change;</li>
<li>the camera works until a second unrelated move begins;</li>
<li>the first action resolves but a new action breaks the ending;</li>
<li>audio stays synchronized until a second dialogue or effect sequence;</li>
<li>one local failure forces you to discard an otherwise successful long clip.</li>
</ul>
<p>Troubleshooting ends when the shot has one clear job and passes the review criteria for that job. The best fix may be a more precise prompt, a better reference, or a shorter generation boundary, not more words.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161702Z-image-03-8e7463f1.webp" alt="Overloaded 30-second rooftop scene compared with three reviewable shots for setup, jump, and landing" /></p>
<hr />
<p><em>This post first appeared on the <a href="https://mkanime.ai/guides/fix-seedance-2-5-character-camera-ending">MkAnime blog</a>. AI assistance was used to help draft and organize the article; the steps and product behavior described were checked against the live product.</em></p>
]]></content:encoded></item><item><title><![CDATA[Vertical Video: Seedance 2.5 Anime Shorts Workflow]]></title><description><![CDATA[Cross-posted from the MkAnime blog. I build and write for MkAnime; this is one of a series of Seedance 2.5 workflow guides.
A vertical video is not a horizontal anime shot with the sides removed. When]]></description><link>https://hashnode.yihui.dev/vertical-video-seedance-2-5-anime-shorts-workflow</link><guid isPermaLink="true">https://hashnode.yihui.dev/vertical-video-seedance-2-5-anime-shorts-workflow</guid><category><![CDATA[AI]]></category><category><![CDATA[AI Video Generation]]></category><category><![CDATA[Anime]]></category><dc:creator><![CDATA[Pat Lee]]></dc:creator><pubDate>Thu, 20 Aug 2026 07:54:04 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6a74646f0785c746efc919b8/c117aac9-2c95-4d6e-a883-1323e029058f.webp" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><em>Cross-posted from the <a href="https://mkanime.ai/guides/seedance-2-5-vertical-anime-shorts">MkAnime blog</a>. I build and write for MkAnime; this is one of a series of Seedance 2.5 workflow guides.</em></p>
<p>A <strong>vertical video</strong> is not a horizontal anime shot with the sides removed. When you generate a 9:16 scene with Seedance 2.5, character position, action direction, camera movement, story rhythm, and audio all need to work inside a narrow frame from the start.</p>
<p>This workflow focuses on model-specific staging and review for vertical generation. For the broader process of choosing an idea, building several shots, adding voice, and publishing across platforms, use the existing guide to <a href="https://mkanime.ai/guides/how-to-make-ai-anime-shorts">AI anime shorts</a>.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161658Z-image-01-fc883fd3.webp" alt="Rooftop courier action composed natively for a 9:16 frame with safe and overlay-risk zones" /></p>
<h2>Start With the Publishing Frame, Not a Wide Crop</h2>
<p>Choose 9:16 before you write the shot. The frame changes what can be shown at once: less horizontal geography, more vertical depth, and less room for two characters to separate sideways.</p>
<p>A wide rooftop chase might place one character on each side and use a lateral track. In 9:16, that same idea can stack the pursuer above on a fire escape and the runner below in the street, or stage both on a diagonal staircase. The action becomes native to the canvas instead of surviving a crop by accident.</p>
<p>Use the <a href="https://mkanime.ai/tools/seedance-2-5-video-generator">Seedance 2.5 video generator</a> to select the vertical ratio at the generation stage. Do not rely on a later crop to rescue a composition whose important action begins outside the center.</p>
<h2>Block Characters for a 9:16 Composition</h2>
<p>Give each character a vertical lane and a depth position. One can occupy the upper third while another enters through the lower third; a foreground shoulder can frame a full-body figure deeper in the shot. Avoid placing both faces at opposite horizontal edges.</p>
<p>For one character, decide where the face begins and ends. A waist-up performance can move from lower-center to upper-center during a rise or push-in. A full-body action needs space above the head and below the feet so the model does not repeatedly crop limbs during movement.</p>
<p>When two characters interact, use overlap and depth rather than maximum separation. Keep the speaking face clear, make eyelines plausible, and give the responding character a readable silhouette without requiring the camera to swing across the entire width.</p>
<h2>Keep Faces, Hands, and Action Inside Safe Zones</h2>
<p>Platform interfaces can cover the top and bottom of a vertical video with captions, account controls, descriptions, or calls to action. Keep critical information away from those edges even before final platform-specific overlays are added.</p>
<p>Use a practical staging check:</p>
<ul>
<li>Keep the primary face near the central vertical band.</li>
<li>Keep hand-held props inside the frame during the full action, not only at the start.</li>
<li>Leave breathing room above heads and below landing feet.</li>
<li>Avoid putting a reveal, subtitle-dependent object, or final expression at the extreme bottom.</li>
<li>Keep background landmarks strong enough to survive phone-size playback.</li>
</ul>
<p>Safe zones are not a universal pixel template; platform interfaces change. The principle is to protect the story from likely overlays and edge crops.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161659Z-image-02-d47c4ffb.webp" alt="Three vertical storyboard frames for dialogue, upward reveal, and landing with overlay-risk bands" /></p>
<h2>Choose Motion and Camera Moves for Vertical Space</h2>
<p>Vertical space favors rising, falling, approaching, and depth-based motion. An elevator reveal, jump between levels, object dropping into frame, character standing from a crouch, or push toward a face can use the full canvas.</p>
<p>Give the camera one job:</p>
<ul>
<li>Tilt upward to reveal height.</li>
<li>Track vertically with a jump or fall.</li>
<li>Push in along depth while keeping the face centered.</li>
<li>Hold steady while the character crosses from the lower to upper third.</li>
</ul>
<p>Avoid fast horizontal orbits that repeatedly lose the subject at the sides. If the environment must be revealed horizontally, use a slower reframe and keep a central anchor visible throughout.</p>
<p>Describe secondary motion that supports the vertical direction: coat tails pulled downward during a rise, dust falling after impact, rain traveling through a deep frame, or signs passing behind a moving character. Supporting motion should clarify speed and gravity rather than fill every corner.</p>
<h2>Plan a Short Hook, Escalation, and Ending</h2>
<p>A vertical short needs a visible change immediately, but the first moment still has to be understandable. Start with a question already inside the frame: a hand reaching from below, a warning light above the character, or a courier hanging from a ledge with one strap slipping.</p>
<p>For a 15-second scene, use three beats:</p>
<table>
<thead>
<tr>
<th>Time</th>
<th>Beat</th>
<th>Vertical staging</th>
</tr>
</thead>
<tbody><tr>
<td>0-4s</td>
<td>Hook</td>
<td>Subject and immediate risk centered</td>
</tr>
<tr>
<td>4-11s</td>
<td>Escalation</td>
<td>Movement travels through vertical depth or height</td>
</tr>
<tr>
<td>11-15s</td>
<td>Ending</td>
<td>Camera settles on a clear expression or changed state</td>
</tr>
</tbody></table>
<p>For 30 seconds, add one complication and one decision, not a second unrelated story. The ending should stop on a composition that can loop, cut cleanly, or lead into the next shot.</p>
<h2>Generate Audio for Phone Playback</h2>
<p>Phone speakers reduce low-frequency detail and compete with noisy viewing environments. Put the most important information in a clear voice, a distinct midrange effect, or a recognizable rhythmic change rather than relying only on deep ambience.</p>
<p>Write audio around visible beats: one alert at the hook, a rising wind layer during the vertical move, a landing impact at contact, and a short line after the character becomes still. Leave enough space for captions if dialogue is essential.</p>
<p>Do not fill every second. A brief drop in sound before a landing or reveal can create contrast that remains readable on a small speaker. Review once on headphones and once through the phone speaker before deciding the mix works.</p>
<h2>Review the Clip as a Short, Reel, or TikTok</h2>
<p>Watch the result at phone size, not only in a large desktop player. The existing <a href="https://mkanime.ai/guides/seedance-2-5-anime-test">Seedance 2.5 vertical scene test</a> provides one piece of evidence about model behavior; your production review still needs to test the specific clip and destination.</p>
<p>Check five things:</p>
<ol>
<li><strong>First-frame comprehension:</strong> can a viewer identify the subject and problem without context?</li>
<li><strong>Center retention:</strong> do face, hands, and important props stay visible during movement?</li>
<li><strong>Motion readability:</strong> does the camera reinforce the vertical action instead of fighting it?</li>
<li><strong>Ending value:</strong> is the final state clear enough to cut, loop, or continue?</li>
<li><strong>Audio resilience:</strong> do dialogue and key effects survive phone playback?</li>
</ol>
<p>If the core action leaves the frame, revise staging or camera direction and regenerate. If the action works but the platform crop or caption placement is the only issue, preserve the clip and solve that in editing. The useful result is a shot designed for vertical viewing, not merely delivered in a vertical file.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161659Z-image-03-7ae7c5a8.webp" alt="Weak widescreen crop compared with a native vertical rooftop action composition" /></p>
<hr />
<p><em>This post first appeared on the <a href="https://mkanime.ai/guides/seedance-2-5-vertical-anime-shorts">MkAnime blog</a>. AI assistance was used to help draft and organize the article; the steps and product behavior described were checked against the live product.</em></p>
]]></content:encoded></item><item><title><![CDATA[AI Video Generator With Audio: Seedance 2.5 Anime]]></title><description><![CDATA[Cross-posted from the MkAnime blog. I build and write for MkAnime; this is one of a series of Seedance 2.5 workflow guides.
An AI video generator with audio has to direct two timelines at once: what c]]></description><link>https://hashnode.yihui.dev/ai-video-generator-with-audio-seedance-2-5-anime</link><guid isPermaLink="true">https://hashnode.yihui.dev/ai-video-generator-with-audio-seedance-2-5-anime</guid><category><![CDATA[AI]]></category><category><![CDATA[Video Generation]]></category><category><![CDATA[Anime]]></category><dc:creator><![CDATA[Pat Lee]]></dc:creator><pubDate>Thu, 20 Aug 2026 07:46:07 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6a74646f0785c746efc919b8/bc461dc5-a89e-4e8b-a2b0-41b87d91ea34.webp" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><em>Cross-posted from the <a href="https://mkanime.ai/guides/seedance-2-5-audio-prompts">MkAnime blog</a>. I build and write for MkAnime; this is one of a series of Seedance 2.5 workflow guides.</em></p>
<p>An <strong>AI video generator with audio</strong> has to direct two timelines at once: what changes in the frame and what the audience hears. For anime scenes in Seedance 2.5, useful audio prompts connect dialogue, ambience, effects, music, and silence to visible events instead of listing sounds at the end.</p>
<p>This article focuses on audio generated with the video. It does not replace the separate workflow for final voice casting, dubbing, and lip-sync revision.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161654Z-image-01-bb5a9b68.webp" alt="Anime train-platform scene planned with aligned action, camera, dialogue, ambience, and sound-effect tracks" /></p>
<h2>Native Audio and Post-Production Dubbing Solve Different Jobs</h2>
<p>Generated audio is useful when sound is part of discovering the shot. A footstep changes the rhythm of a turn, a door slam motivates a reaction, or an interrupted line determines when the camera should stop. Generating picture and sound together lets you test that relationship early.</p>
<p>Post-production dubbing is better when the voice must remain consistent across an episode, the exact performance needs approval, another language will be recorded, or lip timing needs local repair. In that workflow, picture timing becomes the source of truth and dialogue is produced against it.</p>
<p>Use generated audio for scene exploration and tightly coupled effects. Use a dedicated <a href="https://mkanime.ai/guides/how-to-dub-anime-with-ai">AI anime dubbing workflow</a> when voice identity, reusable casting, language versions, and final lip sync matter more than getting a complete first pass from one generation.</p>
<h2>Write Dialogue for Timing and Performance</h2>
<p>Write only the dialogue the duration can hold. A ten-second shot with setup, reaction, and camera movement may have room for one short line, not a paragraph.</p>
<p>Name four things:</p>
<ol>
<li><strong>Speaker:</strong> which visible character speaks.</li>
<li><strong>Exact line:</strong> quote the words rather than paraphrasing the intent.</li>
<li><strong>Delivery:</strong> quiet, breathless, steady, dry, interrupted, or another playable cue.</li>
<li><strong>Timing:</strong> the event that starts the line and the beat where it ends.</li>
</ol>
<p>For example:</p>
<pre><code class="language-text">At 6s, after the elevator light turns red, the woman looks up and says quietly, "That is not our floor." The line ends before 9s. Leave one silent beat after it.
</code></pre>
<p>Avoid loading the performance with several conflicting emotions. "Terrified but calm, angry, relieved, laughing, and close to tears" does not give a performer one readable choice. Pick the emotion that changes the scene.</p>
<h2>Prompt Ambience That Supports the Scene</h2>
<p>Ambience tells the viewer where the scene continues beyond the frame. It should be stable enough to connect cuts and quiet enough to leave room for important events.</p>
<p>Describe a bed with source and distance: "low ventilation hum inside an empty elevator, faint rain against the exterior shaft, no crowd." Then identify whether it continues, fades, or changes. If the elevator stops, the hum can cut out to make the silence itself visible.</p>
<p>Two or three environmental layers are usually enough. A long list of traffic, voices, birds, alarms, wind, machinery, rain, and music creates competition unless the scene is specifically about overwhelming sound.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161655Z-image-02-21fce93e.webp" alt="Elevator cutaway mapping close clothing sound, ventilation, distant rain, and a red light cue" /></p>
<h2>Synchronize Sound Effects With Visible Actions</h2>
<p>Attach each important effect to a visible cause. The audience should hear the latch after the hand reaches it, the shoe impact when the foot lands, and the fabric movement during the turn.</p>
<p>Use a cause-and-effect line:</p>
<pre><code class="language-text">The red indicator flickers, then emits one dry electronic chirp. She turns toward it. Her jacket sleeve brushes the metal rail during the turn. When the elevator stops, the motor hum cuts out and the doors give one restrained mechanical knock.
</code></pre>
<p>This wording defines order and prevents a pile of unrelated effects. It also gives you observable checkpoints when reviewing: did the chirp precede the turn, and did the mechanical knock happen when the doors reacted?</p>
<p>For fast action, prioritize the sounds that explain contact or direction. One clean landing, one blade deflection, and one debris fall are more readable than a continuous wall of impacts.</p>
<h2>Control Music, Silence, and Audio Density</h2>
<p>Music should have a narrative job. It can establish expectation, carry momentum, or change at a reveal. If it does none of those, ambience and performance may communicate the scene more clearly.</p>
<p>State whether music is present, when it enters, and what it must not cover. "No music until the doors stop; one low sustained synth tone enters under the final close-up, below the dialogue" is more useful than "epic cinematic soundtrack."</p>
<p>Silence is also direction. Ask for the ventilation hum to stop before the line, or leave the final second without dialogue or effects so the last expression can land. Audio density should decrease around the most important words and increase only when the scene benefits from pressure or scale.</p>
<h2>Copy-Ready Audio Prompt Patterns</h2>
<p>Use these patterns as modules inside the full visual prompt.</p>
<h3>Quiet dialogue scene</h3>
<pre><code class="language-text">Audio: low room tone and light rain throughout. At 5s, the visible character takes one breath and says softly, "[SHORT LINE]." Keep the voice close and natural. No music. Leave the final second silent after the line.
</code></pre>
<h3>Action synchronized to contact</h3>
<pre><code class="language-text">Audio: restrained street ambience. Synchronize one shoe scrape with the first pivot, one sharp impact when the staff touches the railing, and falling metal vibration after contact. No extra impacts before or after the visible actions. No dialogue.
</code></pre>
<h3>Reveal with a changing sound bed</h3>
<pre><code class="language-text">Audio: continuous ventilation hum until the warning light turns red. At that visible change, the hum stops and one electronic chirp sounds. The character whispers, "[SHORT LINE]," after turning. A low musical tone begins only under the locked final frame.
</code></pre>
<p>The <a href="https://mkanime.ai/seedance-2-5-prompts">Seedance 2.5 prompt examples</a> let you compare written direction with playable results. Adapt the relationship between event and sound; do not copy story details that do not belong to your own scene.</p>
<h2>Review Lip Timing, Clarity, and Playback</h2>
<p>Review picture and audio separately before judging them together. First mute the clip and confirm that the mouth movement, gesture, and action timing are readable. Then listen without watching and check whether dialogue is intelligible, ambience is stable, and effects have distinct shapes.</p>
<p>Finally, watch normally and mark:</p>
<ul>
<li>when the mouth begins and stops relative to the line;</li>
<li>whether the line fits the character's visible energy;</li>
<li>whether effects coincide with their causes;</li>
<li>whether ambience jumps or changes without a scene reason;</li>
<li>whether music covers dialogue or the final beat;</li>
<li>whether phone speakers still reproduce the important information.</li>
</ul>
<p>Test the prompt in the <a href="https://mkanime.ai/tools/seedance-2-5-video-generator">Seedance 2.5 video generator</a> with generated audio enabled. Keep the visual settings unchanged when comparing audio wording so you can attribute the difference to the sound direction.</p>
<h2>When to Keep or Replace Generated Audio</h2>
<p>Keep generated audio when it supports the shot's rhythm, the dialogue is clear enough for the intended use, effects align with visible events, and the sound bed remains stable. A rough concept clip does not need final-series voice continuity if its job is to prove staging.</p>
<p>Replace or rebuild the audio when a recurring character sounds different from neighboring scenes, the exact line or language matters, lip timing breaks the performance, or one wrong effect makes an otherwise good clip unusable. Preserve the successful video and treat sound as a separate production layer.</p>
<p>The decision is not whether native audio is inherently better. It is whether the generated track already performs the job this version of the scene needs.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161657Z-image-03-f04d0e14.webp" alt="Matched elevator frames comparing generated native audio for concept review with replaced audio for final production" /></p>
<hr />
<p><em>This post first appeared on the <a href="https://mkanime.ai/guides/seedance-2-5-audio-prompts">MkAnime blog</a>. AI assistance was used to help draft and organize the article; the steps and product behavior described were checked against the live product.</em></p>
]]></content:encoded></item><item><title><![CDATA[Reference Video AI: Seedance 2.5 Anime Workflow]]></title><description><![CDATA[Cross-posted from the MkAnime blog. I build and write for MkAnime; this is one of a series of Seedance 2.5 workflow guides.
Reference video AI becomes useful for anime production when a shot must inhe]]></description><link>https://hashnode.yihui.dev/reference-video-ai-seedance-2-5-anime-workflow</link><guid isPermaLink="true">https://hashnode.yihui.dev/reference-video-ai-seedance-2-5-anime-workflow</guid><category><![CDATA[AI]]></category><category><![CDATA[AI Video Generation]]></category><category><![CDATA[Anime]]></category><dc:creator><![CDATA[Pat Lee]]></dc:creator><pubDate>Thu, 20 Aug 2026 07:38:59 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6a74646f0785c746efc919b8/f6a1cf0f-92d9-4706-8f1f-f0352ab1681a.webp" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><em>Cross-posted from the <a href="https://mkanime.ai/guides/seedance-2-5-reference-workflow">MkAnime blog</a>. I build and write for MkAnime; this is one of a series of Seedance 2.5 workflow guides.</em></p>
<p><strong>Reference video AI</strong> becomes useful for anime production when a shot must inherit decisions that prose alone cannot reliably protect. With Seedance 2.5 inside a MkAnime project, a creator can connect first and last frames, motion guidance, character material, and storyboard context to the shot instead of describing everything again from memory.</p>
<p>The goal is not perfect pixel identity. It is a reviewable continuity workflow: decide what must remain stable, provide the smallest consistent reference set, generate, and compare the output against those references.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161649Z-image-01-42b161cb.webp" alt="One copper-haired anime heroine kept consistent across a station, bicycle lane, and rooftop with a compact reference set" /></p>
<h2>The Continuity Problem in Recurring Anime Scenes</h2>
<p>A character can look correct in one frame and still fail as a recurring character. Hair length shifts, an accessory changes sides, jacket construction simplifies, or the face becomes a different person when the camera moves wider.</p>
<p>The same problem affects scenes. A doorway moves to another wall, daylight changes direction, or a prop disappears between storyboard panels. These are not isolated beauty defects; they break the viewer's belief that the shots belong to the same world.</p>
<p>Prompt repetition helps, but prose cannot fully define a face, silhouette, spatial layout, and movement rhythm. The practical response is to separate stable identity from shot-specific change, then make each kind of reference perform one clear job.</p>
<h2>Build a Reference Set Before Video Generation</h2>
<p>Start with an approved visual source of truth. For a recurring character, prepare one readable portrait or three-quarter view, one full-body view, and only the additional angle needed by the next shot. Remove conflicting experiments from the working set.</p>
<p>You can use the <a href="https://mkanime.ai/tools/anime-character-creator">anime character creator</a> to develop an original design, then save the approved images with a short identity contract:</p>
<pre><code class="language-text">Permanent: short copper bob with one longer strand at the right cheek; teal rain jacket with white zipper; silver camera strap worn from right shoulder to left hip; amber eyes; reserved posture.
Variable: facial expression, pose, camera distance, weather interaction, scene lighting.
</code></pre>
<p>For a location, keep a simple orientation frame or storyboard panel that shows entrances, major props, and light direction. The set should be small enough that every item agrees.</p>
<h2>Choose First Frame, Last Frame, or Motion Reference</h2>
<p>Different references solve different risks.</p>
<table>
<thead>
<tr>
<th>Reference</th>
<th>Use it to protect</th>
<th>Do not expect it to solve</th>
</tr>
</thead>
<tbody><tr>
<td>First frame</td>
<td>Initial pose, framing, wardrobe, location state</td>
<td>The exact ending or full action path</td>
</tr>
<tr>
<td>Last frame</td>
<td>Destination pose, final composition, object state</td>
<td>How the motion travels between frames</td>
</tr>
<tr>
<td>First + last frames</td>
<td>A visible start and destination</td>
<td>Every intermediate drawing decision</td>
</tr>
<tr>
<td>Motion reference</td>
<td>Rhythm, body mechanics, camera or subject movement</td>
<td>Character identity unless identity is also supplied</td>
</tr>
<tr>
<td>Character reference</td>
<td>Face, hair, silhouette, clothing construction</td>
<td>Shot timing or spatial blocking</td>
</tr>
<tr>
<td>Storyboard context</td>
<td>Beat order, shot purpose, neighboring continuity</td>
<td>Fine motion inside one generated clip</td>
</tr>
</tbody></table>
<p>Use a first frame when the opening composition carries the continuity burden. Add a last frame when the ending must land on a specific pose or handoff. Use motion reference when the important decision is how movement unfolds, not merely where it starts and ends.</p>
<p>The public <a href="https://mkanime.ai/features/seedance-2-5">Seedance 2.5 reference workflow</a> describes how these inputs fit into the project path. The standalone text generator remains useful for prompt experiments, but it does not accept the same project references.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161652Z-image-02-d1e2faf1.webp" alt="Matched bicycle action comparing first-frame, first-and-last-frame, and motion-reference guidance" /></p>
<h2>Connect Character References to Storyboard Shots</h2>
<p>A reference is most useful when it is attached to a specific shot decision. The storyboard says what the shot must accomplish; the character reference says who performs it; the frame or motion reference says how the visible action is constrained.</p>
<p>Inside an <a href="https://mkanime.ai/features/ai-storyboard-generator-for-anime">AI storyboard generator for anime</a>, review the sequence before generating video. For each shot, record:</p>
<ul>
<li>the story beat and expected duration;</li>
<li>the approved character references required by that beat;</li>
<li>the first frame and optional last frame;</li>
<li>the camera role and motion direction;</li>
<li>the prop or location facts inherited from the neighboring shot.</li>
</ul>
<p>This prevents a common failure: using a strong character reference on a shot whose staging still contradicts the prior panel. Identity consistency cannot repair a broken eyeline, reversed exit direction, or missing handoff prop.</p>
<h2>Use References Without Overconstraining the Scene</h2>
<p>More references do not automatically create more control. If two portraits disagree about the hair fringe or two location frames place the door on opposite walls, the model must choose between them. The output may average the designs or switch during the shot.</p>
<p>Keep the set hierarchical:</p>
<ol>
<li>One approved identity reference defines the character.</li>
<li>One first frame defines the current shot.</li>
<li>One last frame or one motion reference defines the main transition when needed.</li>
<li>Storyboard context explains why the shot exists.</li>
</ol>
<p>Remove any reference that does not resolve a named risk. If the shot is a close-up conversation, a full running-motion clip may distract from facial performance. If the shot is a jump, the motion reference may matter more than a second portrait.</p>
<h2>Review Identity, Props, Space, and Motion</h2>
<p>Review in layers. First check identity: face, hair, silhouette, clothing, and signature accessory. Then check props: presence, side, hand, color, and state. Next check space: entrances, screen direction, background landmarks, and light direction. Finally check motion: trigger, body mechanics, camera path, and settle.</p>
<p>A simple scorecard keeps the review factual:</p>
<table>
<thead>
<tr>
<th>Layer</th>
<th>Pass condition</th>
<th>Example failure</th>
</tr>
</thead>
<tbody><tr>
<td>Identity</td>
<td>Character is recognizable at the widest required framing</td>
<td>Hair and face change after the turn</td>
</tr>
<tr>
<td>Props</td>
<td>Required prop remains present and correctly placed</td>
<td>Strap moves to the opposite shoulder</td>
</tr>
<tr>
<td>Space</td>
<td>Geography supports the storyboard handoff</td>
<td>Character exits right but enters the next shot from the wrong side</td>
</tr>
<tr>
<td>Motion</td>
<td>Action follows the intended cause and rhythm</td>
<td>Jump begins before the visible trigger</td>
</tr>
</tbody></table>
<p>Do not combine these into one vague "consistency" judgment. The failing layer tells you which reference or prompt decision to revise.</p>
<h2>Decide What to Regenerate and What to Edit</h2>
<p>Regenerate when the shot's core visual logic is wrong: the character is no longer recognizable, the prop changes state, the camera crosses the intended axis, or the ending cannot connect to the next panel. Edit when the generated clip is structurally sound and only needs timing, sound, color, or a clean cut around a weak moment.</p>
<p>Change the smallest input that owns the failure. Replace a conflicting character image for identity drift. Clarify the last frame for a weak handoff. Simplify the motion reference when body mechanics become noisy. Revise the storyboard when the shot itself asks for incompatible actions.</p>
<p>The useful result is not a clip that never varies. It is a clip whose important differences are intentional and whose remaining variation can be handled in the next production step.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161653Z-image-03-23ec329b.webp" alt="Layered continuity review for identity, prop placement, direction, and motion settle in a referenced anime shot" /></p>
<hr />
<p><em>This post first appeared on the <a href="https://mkanime.ai/guides/seedance-2-5-reference-workflow">MkAnime blog</a>. AI assistance was used to help draft and organize the article; the steps and product behavior described were checked against the live product.</em></p>
]]></content:encoded></item><item><title><![CDATA[30 Second Video: Plan a Seedance 2.5 Anime Scene]]></title><description><![CDATA[Cross-posted from the MkAnime blog. I build and write for MkAnime; this is one of a series of Seedance 2.5 workflow guides.
A 30 second video gives an anime idea enough room to develop, but it also gi]]></description><link>https://hashnode.yihui.dev/30-second-video-plan-a-seedance-2-5-anime-scene</link><guid isPermaLink="true">https://hashnode.yihui.dev/30-second-video-plan-a-seedance-2-5-anime-scene</guid><category><![CDATA[AI]]></category><category><![CDATA[AI Video Generation]]></category><category><![CDATA[Anime]]></category><dc:creator><![CDATA[Pat Lee]]></dc:creator><pubDate>Thu, 20 Aug 2026 07:32:45 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6a74646f0785c746efc919b8/eec9ce86-ea64-4894-9cb6-af51280355a5.webp" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><em>Cross-posted from the <a href="https://mkanime.ai/guides/plan-30-second-anime-scene-seedance-2-5">MkAnime blog</a>. I build and write for MkAnime; this is one of a series of Seedance 2.5 workflow guides.</em></p>
<p>A <strong>30 second video</strong> gives an anime idea enough room to develop, but it also gives continuity mistakes more time to appear. Before generating with Seedance 2.5, turn the idea into visible beats, decide what must stay fixed, and design an ending the scene can actually reach.</p>
<p>This workflow is for planning one continuous scene. It is not a claim that every idea should be generated as one take; the final section explains when separate storyboard shots are the more controllable choice.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161612Z-image-01-59891b2b.webp" alt="Six planned beats across a 30-second rooftop courier scene, from setup to resolved final frame" /></p>
<h2>Decide Whether the Idea Needs One Take</h2>
<p>One take works when every beat happens in a connected place and the camera can observe the progression without teleporting. A character hears a signal, crosses a rooftop, reaches a door, hesitates, and opens it: the action has one spatial line and one emotional turn.</p>
<p>Do not force a one-take scene when the idea requires several locations, costume changes, large time jumps, or unrelated camera positions. Those are editorial cuts disguised as prompt instructions. A long prompt cannot make them physically continuous simply by adding "then."</p>
<p>Use this test: sketch the camera path as one unbroken line. If the line must jump across space or time, plan separate shots. If it can move, hold, or reframe through the scene, a 30-second generation may be worth testing.</p>
<h2>Map the Story Into 0-30 Second Beats</h2>
<p>Divide the scene by changes the viewer can see, not by sentences in the script. Each beat should alter action, information, emotion, or composition.</p>
<table>
<thead>
<tr>
<th>Time</th>
<th>Story job</th>
<th>Visible event</th>
<th>Checkpoint</th>
</tr>
</thead>
<tbody><tr>
<td>0-5s</td>
<td>Establish</td>
<td>Character and goal are readable</td>
<td>Viewer knows where to look</td>
</tr>
<tr>
<td>5-10s</td>
<td>Trigger</td>
<td>A signal or obstacle changes the situation</td>
<td>Cause of the next action is visible</td>
</tr>
<tr>
<td>10-17s</td>
<td>Action</td>
<td>Character responds and crosses space</td>
<td>Motion direction remains coherent</td>
</tr>
<tr>
<td>17-23s</td>
<td>Complication</td>
<td>A second event forces a choice</td>
<td>Scene escalates without changing location</td>
</tr>
<tr>
<td>23-27s</td>
<td>Decision</td>
<td>Character completes the key action</td>
<td>Camera prepares the ending</td>
</tr>
<tr>
<td>27-30s</td>
<td>Resolve</td>
<td>Motion settles on the final composition</td>
<td>No new story information appears</td>
</tr>
</tbody></table>
<p>The ranges are planning guides, not frame-accurate promises. Their value is diagnostic: if the output spends twelve seconds establishing the rooftop, the action has too little time because the prompt did not prioritize the trigger.</p>
<h2>Lock Character, Prop, and Location Anchors</h2>
<p>Write a short continuity line before the timeline. Keep only visible facts that would make the scene feel broken if they changed.</p>
<p>For example: "Original teenage courier with short black hair, yellow windbreaker, red canvas satchel worn across the left shoulder; one brass key in the right hand; school rooftop at bright late afternoon; blue utility door at the north wall."</p>
<p>Repeat an anchor only when a later beat makes it vulnerable. If the character turns, specify that the satchel remains on the left shoulder. If the key opens the door, mention that the same brass key stays in the right hand until the lock turns. Do not restate every detail in every beat.</p>
<p>If approved images already define the character or location, the <a href="https://mkanime.ai/features/seedance-2-5">Seedance 2.5 workflow</a> can carry those references inside a MkAnime project. References reduce ambiguity, but they should agree with the written anchors.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161614Z-image-02-6fec05cd.webp" alt="Rooftop courier continuity sheet covering character, costume, brass key, blue door, and storyboard progression" /></p>
<h2>Give Each Beat an Action and Camera Role</h2>
<p>The action tells the character what changes. The camera tells the viewer how to understand that change. Write both for each major beat, but keep one continuous camera logic across the scene.</p>
<p>A usable progression might be:</p>
<ul>
<li>Hold a wide three-quarter view while the courier notices a blinking light near the door.</li>
<li>Track laterally as they cross the rooftop, keeping the door ahead in the frame.</li>
<li>Ease into a medium shot when the light shuts off and the character stops.</li>
<li>Make one slow push-in as the key enters the lock.</li>
<li>Stop all camera movement on the final close view of the opening door.</li>
</ul>
<p>This is still one camera journey: establish, follow, narrow, settle. An orbit, overhead cut, handheld shake, crane move, and sudden close-up would ask for several incompatible journeys.</p>
<h2>Design Audio Across the Full Scene</h2>
<p>Give the scene one continuous sound bed, then place only the events that matter. Rooftop wind and distant traffic can connect all thirty seconds. A radio chirp triggers the action, shoes scrape during the crossing, the key clicks at the decision, and the door hinge resolves the scene.</p>
<p>Keep dialogue short. One line at the complication or decision point is easier to time than a conversation spread across the whole clip. If the character says, "This was never locked," reserve a quiet beat before the line and avoid covering it with a loud music cue.</p>
<p>Sound should confirm visible causality. If the radio chirp makes the character turn, place the chirp before the turn. If a sound has no visible or narrative source, decide whether it adds atmosphere or merely fills space.</p>
<h2>Build the Seedance 2.5 Prompt</h2>
<p>Combine the plan into one readable production brief:</p>
<pre><code class="language-text">30-second continuous anime scene. Original teenage courier with short black hair, yellow windbreaker, red canvas satchel on the left shoulder, brass key in the right hand. Bright late-afternoon school rooftop, blue utility door on the north wall, clean contemporary 2D anime linework, luminous sky and readable faces.

0-5s: wide three-quarter view; the courier stands near the stairwell and notices a blinking red light beside the blue door.
5-10s: a radio chirp sounds; the courier turns toward it.
10-17s: the courier crosses the rooftop; track laterally at a stable distance, keeping the door ahead.
17-23s: the light turns off; the courier stops, grips the same brass key, and says quietly, "This was never locked."
23-27s: move into one slow push-in as the key enters the lock and turns.
27-30s: the door opens a few inches into warm white light; all motion settles.

Audio: continuous rooftop wind and distant traffic; radio chirp at the trigger; footsteps during the crossing; clear key click and restrained hinge sound; no music.
Final frame: stable medium close view from behind the courier, red satchel still on the left shoulder, hand on the key, blue door partly open, no new action.
</code></pre>
<p>Set 30 seconds in the <a href="https://mkanime.ai/tools/seedance-2-5-video-generator">Seedance 2.5 video generator</a>, choose the delivery ratio, and enable audio only if you want to test the sound plan in the same pass. Read the displayed credit quote before starting.</p>
<h2>Review Continuity, Timing, and the Ending</h2>
<p>Review in three passes instead of deciding whether the clip "feels good."</p>
<p>First, mute it and check continuity: hair, jacket, satchel side, key hand, door color, and rooftop orientation. Second, watch the timeline: each trigger must precede its response, and no beat should consume the time needed by the next. Third, watch the final three seconds: the camera and character should settle on the promised frame.</p>
<p>Then listen separately. Check whether the radio, steps, line, key, and hinge occur near their visible causes. Record the earliest failure and revise that control first; later problems may be consequences of the same timing drift.</p>
<h2>When to Split the Scene Into Separate Shots</h2>
<p>Split the scene when continuity cannot survive the amount of change, when one failed beat makes the whole clip unusable, or when you need precise editing control. A six-shot sequence costs more planning, but it lets you regenerate the door close-up without discarding a successful rooftop crossing.</p>
<p>The <a href="https://mkanime.ai/guides/script-to-anime-storyboard-with-ai">script-to-anime storyboard workflow</a> explains how to turn story beats into separate, reviewable shots. Use one 30-second scene for discovery when the spatial journey matters; use a storyboard when local revision, pacing, and shot-to-shot continuity matter more.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161615Z-image-03-20fa28f1.webp" alt="One continuous rooftop take compared with six separately editable storyboard shots" /></p>
<hr />
<p><em>This post first appeared on the <a href="https://mkanime.ai/guides/plan-30-second-anime-scene-seedance-2-5">MkAnime blog</a>. AI assistance was used to help draft and organize the article; the steps and product behavior described were checked against the live product.</em></p>
]]></content:encoded></item><item><title><![CDATA[Seedance 2.5 Prompts: Control Every Shot]]></title><description><![CDATA[Cross-posted from the MkAnime blog. I build and write for MkAnime; this is one of a series of Seedance 2.5 workflow guides.
Good Seedance 2.5 prompts do more than describe an attractive anime frame. T]]></description><link>https://hashnode.yihui.dev/seedance-2-5-prompts-control-every-shot</link><guid isPermaLink="true">https://hashnode.yihui.dev/seedance-2-5-prompts-control-every-shot</guid><category><![CDATA[AI]]></category><category><![CDATA[AI Video Generation]]></category><category><![CDATA[Anime]]></category><dc:creator><![CDATA[Pat Lee]]></dc:creator><pubDate>Thu, 20 Aug 2026 07:26:09 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6a74646f0785c746efc919b8/493c976d-6082-4290-ab92-7ff025975643.webp" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><em>Cross-posted from the <a href="https://mkanime.ai/guides/seedance-2-5-prompt-guide">MkAnime blog</a>. I build and write for MkAnime; this is one of a series of Seedance 2.5 workflow guides.</em></p>
<p>Good <strong>Seedance 2.5 prompts</strong> do more than describe an attractive anime frame. They direct a shot through time: who is present, what changes, how the camera observes it, when each beat happens, and what the audience hears.</p>
<p>This guide gives you a reusable prompt structure for those controls. It does not repeat a library of generic motion templates; the goal is to help you combine motion, camera, timing, and audio without creating contradictory directions.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161609Z-image-01-4850e749.webp" alt="Four-frame anime station sequence annotated as subject, camera, timing, and audio controls in a Seedance 2.5 prompt" /></p>
<h2>A Seedance 2.5 Prompt Is a Shot Brief</h2>
<p>A useful prompt reads like a compact assignment to a cinematographer, animator, performer, and sound designer. It describes one coherent result instead of stacking unrelated visual adjectives.</p>
<p>Build the brief in this order:</p>
<ol>
<li><strong>Subject and continuity anchors:</strong> who or what must remain recognizable.</li>
<li><strong>Setting and visual language:</strong> where the scene happens and what visible style decisions matter.</li>
<li><strong>Action chain:</strong> what changes, in cause-and-effect order.</li>
<li><strong>Camera role:</strong> how the viewer observes the action.</li>
<li><strong>Timing:</strong> when the important beats occur within the selected duration.</li>
<li><strong>Audio:</strong> dialogue, ambience, effects, music, or deliberate silence.</li>
<li><strong>End state:</strong> the composition the shot should resolve on.</li>
</ol>
<p>The order is not a special command language. It is a clarity device. If a human reader cannot tell what happens first, the prompt probably asks the generation to solve too many decisions at once.</p>
<h2>Define Subject, Style, and Continuity Anchors</h2>
<p>Start with details that must stay stable. For a recurring anime character, that might be the short copper bob, teal rain jacket, silver camera strap, and cautious body language. Choose a small set of visible anchors; a biography that never affects the frame adds noise.</p>
<p>Describe style through observable properties. "Clean 2D anime linework, hand-painted cloud shapes, bright midday color, restrained bloom, and readable facial shading" gives the shot something visible to preserve. A vague label such as "cinematic masterpiece" does not explain line quality, light, palette, or composition.</p>
<p>If you already have approved references, use them in the project workflow rather than trying to reconstruct every detail in prose. The <a href="https://mkanime.ai/guides/seedance-2-5-anime-test">Seedance 2.5 anime scene tests</a> show why visible anchors and specific style language are more useful than broad quality claims.</p>
<h2>Write Motion as Cause and Effect</h2>
<p>Write the main movement as a chain: trigger, response, secondary motion, and settle. This gives the shot a direction and a natural place to end.</p>
<p>Compare these two instructions:</p>
<blockquote>
<p>The girl moves dramatically while the wind blows.</p>
</blockquote>
<blockquote>
<p>A train enters the platform and pushes a gust through the station. The girl's jacket hem and loose hair lift first; she braces one hand on the railing, turns toward the arriving headlights, then settles into a still profile.</p>
</blockquote>
<p>The second version identifies what causes the motion and which details react. It also separates the primary performance from secondary movement in hair and clothing.</p>
<p>Avoid asking every object to move. One dominant action plus two or three supporting reactions is easier to read than simultaneous running, spinning, flying debris, flashing lights, and a changing background.</p>
<h2>Give the Camera One Clear Job</h2>
<p>The camera should reveal, follow, compare, or hold. Pick one primary job for a short shot.</p>
<ul>
<li><strong>Hold:</strong> locked medium shot while the performance changes inside the frame.</li>
<li><strong>Reveal:</strong> slow push-in or controlled pull-back to expose new information.</li>
<li><strong>Follow:</strong> lateral track that maintains a stable distance from a moving subject.</li>
<li><strong>Reframe:</strong> gentle pan or tilt that transfers attention from one subject to another.</li>
</ul>
<p>Specify the start and finish rather than adding a list of camera verbs. "Begin at a waist-up profile and make one slow push-in to a close-up, stopping when she looks toward the light" is testable. "Pan, zoom, orbit, handheld, dynamic camera" contains competing movement systems.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161610Z-image-02-50f014c0.webp" alt="Matched anime station frames demonstrating hold, reveal, follow, and reframe camera jobs" /></p>
<h2>Plan Timing Across 5, 10, 15, or 30 Seconds</h2>
<p>Match the number of beats to the duration selected in MkAnime. A five-second shot usually needs one readable change. Ten seconds can support setup, action, and settle. Fifteen seconds gives room for a reaction or reveal. Thirty seconds needs a planned progression rather than a short prompt stretched over more time.</p>
<p>Use approximate ranges to organize the story:</p>
<pre><code class="language-text">0-3s: establish the character and the closed station gate
3-7s: the train light appears; wind reaches the platform
7-10s: the character turns and the camera completes one push-in
Final frame: still close-up, eyes reflecting the arriving light
</code></pre>
<p>Treat the ranges as editorial guidance, not frame-accurate guarantees. Review the output by whether each beat has enough screen time to be understood.</p>
<h2>Direct Dialogue, Ambience, and Sound Effects</h2>
<p>Audio direction should identify source, timing, and priority. "City sounds and music" leaves the mix undefined. "Low platform ambience throughout; one distant train horn at the first appearance of light; jacket fabric rustle during the turn; no music" gives each sound a visible or narrative job.</p>
<p>For dialogue, keep the line short enough for the chosen duration and describe delivery. Name the speaker, quote the exact line, and add one performance cue: whispered, breathless, steady, hesitant, or interrupted. If lip timing is essential, leave room before and after the line rather than filling the whole shot with speech.</p>
<p>Use silence intentionally. A quiet beat before an impact, reveal, or reply can make the event readable and reduce competition between ambience, effects, dialogue, and music.</p>
<h2>Combine the Variables in Copy-Ready Prompts</h2>
<p>Use this master structure:</p>
<pre><code class="language-text">[SUBJECT + CONTINUITY]
[SETTING + VISIBLE ANIME STYLE]

[TIMELINE]
0-__s: [starting state]
__-__s: [trigger and primary action]
__-__s: [reaction and settle]

Camera: [one job, start framing, end framing]
Audio: [dialogue, ambience, effects, music/silence with timing]
End frame: [locked final composition]
Constraints: [only the few failures that would make the shot unusable]
</code></pre>
<p>Here is a filled 10-second example:</p>
<pre><code class="language-text">Original anime character with a short copper bob, teal rain jacket, silver camera strap, and cautious body language. Bright contemporary 2D anime film frame, clean linework, luminous overcast daylight, wet platform reflections, readable facial shading.

0-3s: locked waist-up profile as she waits beside a closed station gate.
3-7s: an approaching train light creates a gust; her hair and jacket hem lift, then she steadies the camera against her chest.
7-10s: she turns toward the light and whispers, "You came back."

Camera: one slow push-in from waist-up profile to close-up, stopping as she speaks.
Audio: soft rain and distant rail hum throughout; one train horn at 4s; quiet female whisper at 8s; no music.
End frame: still close-up, eyes catching the train light, face fully readable.
Constraints: no extra characters, no camera orbit, no costume change, no new action after the line.
</code></pre>
<p>You can test this structure in the <a href="https://mkanime.ai/tools/seedance-2-5-video-generator">Seedance 2.5 generator</a> or compare it with playable examples in the <a href="https://mkanime.ai/seedance-2-5-prompts">Seedance 2.5 prompt library</a>. Keep the subject and action original rather than copying a protected character or named artist's style.</p>
<h2>Revise One Variable at a Time</h2>
<p>When a result fails, identify the earliest broken control. If the subject changes before the action begins, revise continuity anchors. If the performance works but the view spins, simplify the camera. If the ending feels unfinished, lock the final composition. If sound arrives late, tie it to a visible event and remove lower-priority audio.</p>
<p>A controlled revision keeps the successful parts unchanged. Save the original prompt, duplicate it, and modify only one category, subject, motion, camera, timing, audio, or end frame. After two or three comparisons, you will know which wording controls the shot instead of merely knowing that one random attempt looked better.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161611Z-image-03-9514aab2.webp" alt="Four matched anime station variations for baseline, camera-only, timing-only, and audio-cue prompt iteration" /></p>
<hr />
<p><em>This post first appeared on the <a href="https://mkanime.ai/guides/seedance-2-5-prompt-guide">MkAnime blog</a>. AI assistance was used to help draft and organize the article; the steps and product behavior described were checked against the live product.</em></p>
]]></content:encoded></item><item><title><![CDATA[AI Anime Video Generator: Seedance 2.5 Workflow]]></title><description><![CDATA[Cross-posted from the MkAnime blog. I build and write for MkAnime; this is one of a series of Seedance 2.5 workflow guides.
An AI anime video generator is most useful when you know what kind of contro]]></description><link>https://hashnode.yihui.dev/ai-anime-video-generator-seedance-2-5-workflow</link><guid isPermaLink="true">https://hashnode.yihui.dev/ai-anime-video-generator-seedance-2-5-workflow</guid><category><![CDATA[AI]]></category><category><![CDATA[AI Video Generation]]></category><category><![CDATA[Anime]]></category><dc:creator><![CDATA[Pat Lee]]></dc:creator><pubDate>Thu, 20 Aug 2026 07:18:49 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6a74646f0785c746efc919b8/b829970a-b4f8-46b8-90f9-f331a22dbae8.webp" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><em>Cross-posted from the <a href="https://mkanime.ai/guides/how-to-use-seedance-2-5-in-mkanime">MkAnime blog</a>. I build and write for MkAnime; this is one of a series of Seedance 2.5 workflow guides.</em></p>
<p>An <strong>AI anime video generator</strong> is most useful when you know what kind of control the shot needs before you generate it. In MkAnime, Seedance 2.5 has two practical entry points: a text-only generator for direct experiments and a project workflow for shots that need visual references or continuity.</p>
<p>This guide helps you choose the right path, set the generation controls, run a clip, and decide what to revise next. It focuses on the current MkAnime workflow rather than repeating the separate scene-quality tests already published on the site.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161606Z-image-01-2ff7dc0b.webp" alt="Seedance 2.5 workflow decision between a prompt-only generator and a reference-aware MkAnime project" /></p>
<h2>Choose the Right Seedance 2.5 Entry Point</h2>
<p>Choose by the inputs you already have, not by which page looks more advanced. If the idea can be communicated as one self-contained shot brief, the standalone generator is the shorter route. If a character, location, pose, opening frame, ending frame, or movement reference must survive the generation, work inside a project.</p>
<table>
<thead>
<tr>
<th>Your starting point</th>
<th>Better entry point</th>
<th>Why</th>
</tr>
</thead>
<tbody><tr>
<td>A written shot idea</td>
<td>Text-only generator</td>
<td>You can test direction without preparing assets</td>
</tr>
<tr>
<td>A tested prompt from the library</td>
<td>Text-only generator</td>
<td>The prompt can be loaded, adjusted, and generated directly</td>
</tr>
<tr>
<td>A specific first or last frame</td>
<td>Project workflow</td>
<td>The frame becomes a visible boundary for the shot</td>
</tr>
<tr>
<td>A recurring character or storyboard</td>
<td>Project workflow</td>
<td>References and scene context stay connected to the shot</td>
</tr>
<tr>
<td>A motion clip you want to use as guidance</td>
<td>Project workflow</td>
<td>The movement reference belongs with the production context</td>
</tr>
</tbody></table>
<p>The important boundary is simple: the public <a href="https://mkanime.ai/tools/seedance-2-5-video-generator">Seedance 2.5 video generator</a> takes text, while a project can carry additional visual and story context. Do not write a reference-heavy prompt and assume it is equivalent to supplying the reference itself.</p>
<h2>What You Can Generate From Text Alone</h2>
<p>The standalone generator is designed for a prompt-first test. You write the shot, choose an aspect ratio and resolution, select 5, 10, 15, or 30 seconds, decide whether generated audio should be on, review the credit quote, and start the job.</p>
<p>That makes it a good fit for three kinds of work:</p>
<ol>
<li><strong>Direction tests:</strong> compare a locked camera with a slow push-in, or restrained acting with a stronger action beat.</li>
<li><strong>Prompt tests:</strong> change one phrase about motion, timing, or sound and inspect what changed in the output.</li>
<li><strong>Early story exploration:</strong> see whether a single continuous idea has enough visual progression to justify a longer scene.</li>
</ol>
<p>Treat the first result as evidence, not as a verdict on the whole idea. Check whether the main action is readable, whether the camera follows the assigned role, and whether the ending lands on a usable composition. Those observations tell you what to change in the next prompt.</p>
<h2>When to Move Into a MkAnime Project</h2>
<p>Move into a project when the cost of losing context is higher than the convenience of another text-only attempt. A recurring lead character, a prop that must stay on the correct side, or a storyboard transition is a continuity problem, not merely a wording problem.</p>
<p>The <a href="https://mkanime.ai/features/seedance-2-5">Seedance 2.5 project workflow</a> can pass starting images, first-and-last-frame decisions, motion references, characters, and storyboard context with the shot. This does not guarantee identical pixels across every frame. It gives the generation a clearer source of truth than prose alone.</p>
<p>Use the smallest reference set that resolves the actual risk. One approved character reference and one clear first frame are often easier to interpret than several images that disagree about hairstyle, clothing, lighting, or camera angle.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161607Z-image-02-6f1f3b1f.webp" alt="Real MkAnime Seedance 2.5 prompt controls beside a real project storyboard shot with scene, character, frame, and video context" /></p>
<h2>Set Ratio, Resolution, Duration, and Audio</h2>
<p>Settings are production decisions, not export cleanup.</p>
<p>Choose the aspect ratio for the destination. A vertical short should begin as a vertical composition so faces, hands, and action are staged for that space. A horizontal scene should use the room for entrances, eyelines, and lateral movement rather than leaving empty edges that will later be cropped away.</p>
<p>Choose duration by the number of visible beats. Five or ten seconds suits one action or reaction. Fifteen seconds can hold a setup and payoff. Thirty seconds needs a deliberate sequence of changes; otherwise the model has time but no direction.</p>
<p>Resolution affects the quoted cost, so confirm the displayed quote before generating. Turn generated audio on only when sound belongs to the experiment.</p>
<h2>Run the First Generation and Check Progress</h2>
<p>Before pressing Generate, read the prompt once as a shot list. You should be able to underline the subject, starting state, action chain, camera role, timing, ending state, and sound direction.</p>
<p>MkAnime requires a signed-in account to start a generation. Once the job begins, the result area reports its state while the page polls for progress. The standalone tool allows one active Seedance 2.5 generation per account, which keeps the quote and current task unambiguous.</p>
<p>Use the waiting time to write a review checklist:</p>
<ul>
<li>Did the same character remain readable throughout the clip?</li>
<li>Did the action follow a cause-and-effect order?</li>
<li>Did the camera perform one understandable movement?</li>
<li>Did the final two seconds resolve rather than introduce a new idea?</li>
<li>If audio was enabled, did the sound occur near the visible event?</li>
</ul>
<h2>Reopen, Compare, and Revise a Saved Clip</h2>
<p>Completed generations remain in the account's private history. Reopen a result to recover its prompt and settings, then compare it with the next attempt using the same criteria.</p>
<p>Change one control at a time. If the character moves correctly but the framing drifts, keep the action language and simplify the camera direction. If the first half works but the ending weakens, preserve the setup and specify the final composition. If a prompt from the <a href="https://mkanime.ai/seedance-2-5-prompts">Seedance 2.5 prompt examples</a> is close to your goal, adapt its structure rather than copying surface details that do not belong to your scene.</p>
<p>A useful comparison records the prompt version, settings, observed failure, and the single change made. Without that record, repeated generation becomes guessing.</p>
<h2>Which Workflow Should You Use Next?</h2>
<p>Stay in the text-only generator when you are still discovering the shot: testing a camera choice, motion phrase, duration, or audio direction. Move into a project when you have approved visual decisions that should survive into later shots.</p>
<p>The handoff is not simple mode versus professional mode. It is exploration versus continuity. Choose the entry point that protects the most important decision in the scene, then review the result against that decision before spending another generation.
<img src="https://static.mkanime.ai/static/demo-images/seo/seedance-2-5-weekly-20260819/20260818T161608Z-image-03-2028b32e.webp" alt="Decision tree for revising a prompt, adding project references, or approving a Seedance 2.5 clip" /></p>
<hr />
<p><em>This post first appeared on the <a href="https://mkanime.ai/guides/how-to-use-seedance-2-5-in-mkanime">MkAnime blog</a>. AI assistance was used to help draft and organize the article; the steps and product behavior described were checked against the live product.</em></p>
]]></content:encoded></item></channel></rss>