Make three storyboard panels: enter, speak, leave. They can look perfect on the board and still fall apart as a video. The face may change at the first cut. The door can jump to the other wall. A voice may arrive after the mouth stops moving. Wan 2.7 offers several routes from references to motion, but a route name does not promise continuity. The useful test is one short story with joins you can inspect.
Build the Three-Shot Storyboard in APOB
I would lock the board before generating anything. Put the exact Wan 2.7 route at the top. List the source images, voice, panel files, settings, and a pass line another reviewer can understand. Do not repair the brief after seeing the output. This checklist was refreshed on September 2, 2026 because the topic table’s September 1 review date had passed. Alibaba Cloud’s current Wan 2.7 image-to-video guide and video model overview are the factual references.
Search labels blur important boundaries. “Wan 2.7 image to video,” “Wan 2.7 API,” “Wan 2.7 reference to video,” and “Wan 2.7 video generator” may describe different tasks or interfaces. This article names the route whenever it matters. The continuity method is APOB’s editorial test, not an Alibaba benchmark.
BoardLock Stage I — Freeze the July build before touching a frame
BoardLock 01 — Record the exact snapshot
Start by writing the exact model ID, region, endpoint, console or API route, documentation check date, SDK version, and account. Do not write only “Wan 2.7.” Alibaba Cloud currently lists separate text-to-video, image-to-video, reference-to-video, and video-editing models, including dated variants such as wan2.7-r2v-2026-06-12.
The original topic was framed as a July snapshot. Keep that historical label in the project note, but use the identifier actually returned by the current interface. The documentation was updated after July and now lists Wan 3.0 alongside Wan 2.7; that does not erase the older test, but it makes the as-of date essential.
BoardLock 02 — List every reference asset
Create an asset register before uploading anything. Give each subject image, environment image, prop, storyboard panel, source clip, final-frame image, voice file, and script a stable ID. Record dimensions, duration where relevant, rights owner, consent status, and a file hash.
Alibaba’s current Wan 2.7 image-to-video documentation describes multimodal inputs across text, images, audio, and video. Which inputs are valid depends on the task. A complete folder is not proof that one endpoint accepts every file; map each asset to the selected route.
BoardLock 03 — Name the route that produced the file
Write the generation route in every output filename: reference-to-video, first-frame, first-and-last-frame, or continuation. The Wan 2.7 image-to-video API reference says the new image-to-video protocol supports first-frame, first-and-last-frame, and continuation tasks, while older first-frame APIs cover a narrower path.
For reference-to-video, Alibaba’s reference workflow guide documents single multi-panel storyboard input and image/video reference formats. Record the route rather than merging these capabilities into one vague “storyboard mode.”
BoardLock Stage II — Design a three-shot continuity trap
BoardLock 04 — One subject with explicit consent
Use one consenting adult subject with visible identity anchors: hairstyle, face shape, one distinctive clothing element, and one small prop. Choose clean references from more than one angle, but avoid contradictory wardrobe or lighting. Save the consent record with the inputs.
Do not test a celebrity or scrape a stranger’s face. The aim is to measure continuity, not how well the model can approximate an identity the team has no right to use.
BoardLock 05 — A panel card for every shot
Design three panels with different continuity pressures:
Shot | Action | Continuity risk | Required match |
|---|---|---|---|
1 | Subject enters and raises the prop | Establishing identity and room | Face, wardrobe, prop, screen direction |
2 | Medium view with one spoken line | Cut and lip/audio timing | Identity, eyeline, voice, prop hand |
3 | Subject turns and exits | Motion and final geography | Direction, room layout, wardrobe, sound tail |
Give each card duration, aspect ratio, camera position, lens description, action beats, beginning state, ending state, dialogue, ambient sound, and protected elements. The ending state of one shot becomes the opening contract for the next.
BoardLock 06 — A voice/script pair that can be compared
Use one short sentence with clear consonants and a natural pause. Record or generate one consented reference voice, then keep the text and file unchanged across routes. Mark the intended start word, pause, and final word against the shot timeline.
Alibaba documents audio-driven and audio-synchronized options for parts of the Wan 2.7 family. Treat that as capability availability, not proof of lip-sync quality. The test must inspect mouth movement, word timing, voice identity, room tone, and transitions in the returned file.
BoardLock Stage III — Inspect the joins, not the prettiest frame
BoardLock 07 — Identity across the cut
Compare the last clean frame of Shot 1 with the first clean frame of Shot 2, then repeat for Shots 2 and 3. Check face proportions, hairline, skin marks, age, clothing construction, prop shape, hand assignment, and body scale. Log the first frame where an identity anchor changes.
Score each join pass, repairable, or regenerate. “Repairable” needs a named fix and time budget. If the face changes, do not hide the failure under a fast cut and call it continuity.
BoardLock 08 — Space across the cut
Draw a simple overhead map showing subject, camera, door, key prop, and main light. Confirm that screen direction, eyeline, entry point, background geometry, and light direction agree with the panels. A beautiful room that flips at the cut is still a failed scene.
Use the APOB AI Storyboarder to keep the three panels and camera intent visible before generation. The advantage is a shared visual plan: reviewers can point to the expected geography instead of arguing from memory after the render.
BoardLock 09 — Sound across the cut
Listen without looking. Check whether the voice timbre, loudness, room tone, ambience, and music perspective change without a story reason. Then watch lips at normal speed and inspect only the first and last spoken phonemes frame by frame.
Log audio problems separately from picture problems. A route can preserve identity while failing dialogue timing; combining them into one quality score hides the correction path.
BoardLock Stage IV — Put two generation routes against one board
BoardLock 10 — Reference-led generation
Run the three-panel reference route with one multi-panel input when that option is available in the selected account and region. Preserve the panel file exactly as submitted. Record prompt, model ID, task ID, timestamps, settings, input hash, and output hash.
Judge whether the route reads the panels as one story: correct shot order, subject identity, scene geography, action, and audio. Do not credit a result for visual polish if it ignores the board.
BoardLock 11 — First-frame animation
Export the first frame of each approved panel and run three separate first-frame tasks with the same motion descriptions and duration targets. This route gives each shot a strong opening anchor but may leave the ending state less constrained.
Compare setup time, controllability, join quality, and number of regenerations against the reference-led path. Use current API documentation for accepted file and parameter rules rather than copying limits from an old test.
BoardLock 12 — Shot continuation
Use the approved end of Shot 1 as the starting video for continuation into Shot 2, then repeat into Shot 3 when the selected route supports it. Alibaba’s current guide describes video continuation within the Wan 2.7 image-to-video workflow, with task-specific inputs.
Continuation may preserve recent motion while accumulating drift. Inspect identity, background, framing, audio, and duration after each extension. Keep every intermediate clip; a final composite cannot reveal where the first mismatch entered.
BoardLock Stage V — Decide with a revision ledger
BoardLock 13 — When a mismatch forces another pass
Define the threshold before choosing a favorite. Regenerate when a protected identity anchor changes, shot order breaks, room geography flips, the wrong hand holds the prop, dialogue becomes unintelligible, or audio starts outside the intended beat. Repair only when the correction is local, measurable, and does not alter approved identity or product truth.
For another controlled route, run the same panels through APOB’s Wan 2.7 page or broader AI Video Generator. APOB does not claim to expose every Alibaba API mode. Its practical advantage is keeping a creator-facing generation option beside the storyboard and review record.
BoardLock 14 — Rights and disclosure before approval
Verify consent for the subject and voice, rights for every image, clip, prop design, logo, script, and sound, plus the distribution terms of the chosen account. Add visible disclosure when the synthetic scene or speaker could reasonably mislead viewers, and follow the platform rules for the destination channel.
Review the exported file after any edit or recompression. Watermarks, labels, captions, and metadata can change downstream. Archive the exact disclosure that accompanies the approved version.
BoardLock 15 — Store the evidence, not just the export
The archive should contain the three panel cards, overhead map, asset register, consent and rights records, route and model IDs, prompts, settings, task logs, input and output hashes, approval frames, issue ledger, disclosure, and final decision. Add the documentation check date and next refresh trigger.
Re-run the BoardLock when a model ID, API protocol, region, duration, resolution, reference format, audio behavior, or APOB workflow changes. The winning route is the one that preserves the story with the fewest unresolved joins—not the one that produced the most impressive isolated frame. That is a defensible Wan 2.7 storyboard-to-video decision.
Save one failed join beside the approved sequence. Label the timecode, violated anchor, attempted repair, and reason for rejection. That small negative example is useful training material for the next operator and a stable challenge clip for the next model refresh; deleting it erases the evidence behind the decision.
Sources
Be the first to like this.
No credit card needed
