An AI-generated shot sheet can look precise while describing an approximate interpretation of a clip. Before using it as evidence, separate three things: what the prompt requested, what the finished video contains, and what another model says it contains.
At VideoCreate, we publish five Seedance-family examples generated through the Doubao app, including the original prompts, full clips and observations:
Seedance worked examples and source clips
They are small worked examples, not a model benchmark. The underlying historical model version is unconfirmed, Doubao may process the prompt before rendering, and a single run does not establish repeatability.
Here is the audit procedure these examples support.
1. Preserve the original request
For the rainy-night ramen sequence, the prompt requested three shots in ten seconds: an establishing shot from 0–3 seconds, a medium close-up from 3–6 seconds, and a macro shot from 6–10 seconds. Keep those requested intervals separate from any subsequently detected intervals. Otherwise, a shot sheet can accidentally make a missed instruction look like a successful result.
2. Measure cuts separately from semantic descriptions
The historical scene-detection values reported on the source page are 4.5 and 6.3 seconds. Those are different from the requested 3 and 6 seconds. The original detector configuration is not available in this article, and we have not independently repeated that measurement here. These are reported observations, not a reproducible benchmark. The AI-assisted read-back also has its own approximate intervals. These labels answer different questions; they should not be merged into a single authoritative timeline.
A scene detector is not infallible either. Treat its output as measurement evidence to inspect against the clip, not as a replacement for reviewing the actual transition. Record the detector configuration when turning an example into a repeatable experiment.
3. Separate camera motion from subject motion
The product example requested a 180-degree camera orbit around a frosted-glass bottle. The result preserved the material and overall visual setup, but showed only a partial arc. Matching the subject and lighting is not sufficient evidence that the requested camera trajectory was followed.
An audit should therefore retain separate fields for subject, camera, motion, light, style and sound, and make each success claim specific. A compact description such as “the scene looks right” hides several independently testable instructions.
4. Listen to the output
The same product example contains an unrequested whispered voiceover. Several other examples added music. If the intended deliverable needs clean ambience, state the audio constraints and inspect the actual soundtrack. A visually successful clip can still fail its sound brief.
5. Publish the limitation beside the observation
The library also includes one Chinese-language run of the ramen prompt. Its historically reported cut values were 3.8 and 6.4 seconds, with the same measurement-configuration limitation. That is an observation about two runs through a particular app, not evidence that Chinese prompts are generally more accurate. Repeated runs, controlled settings and confirmed model provenance would be necessary for a stronger comparison.
A copyable audit record
The following table can be used without our tool. Keep unmeasured fields marked unknown instead of filling them from the prompt or an AI interpretation.
| Requirement | Reported observation | Difference from request | Evidence status |
|---|---|---|---|
| English-run cuts at 3 s and 6 s | Historical source reports 4.5 s and 6.3 s | +1.5 s and +0.3 s, calculated from the reported values | Detector configuration unknown; independently replay before reuse |
| Chinese-run cuts at 3 s and 6 s | Historical source reports 3.8 s and 6.4 s | +0.8 s and +0.4 s, calculated from the reported values | One run; detector configuration unknown; no language comparison conclusion |
| Product camera orbit of 180 degrees | Source describes a partial arc | Angular error not measured | Qualitative historical observation; no numeric accuracy claim |
For a new clip, copy this record and fill it with evidence from your own run:
Clip ID / original artifact location:
Generation date, app, exact model version:
Prompt, seed and generation settings (unknown where unavailable):
Requested shot boundaries and camera / subject / audio constraints:
Detector name, version, threshold and command (unknown if unrecorded):
Detected boundaries:
Manual replay observations and reviewer / date:
AI-assisted read-back, model and version:
Difference from request and measurement uncertainty:
Unresolved provenance, input rights or output issues:
Do not treat a completed record as a model ranking. The next experiment would need a fixed procedure, repeated runs and a stated uncertainty rule before comparing models or languages.
The practical lesson is to store the request, the artifact and the interpretation separately. That makes a correction possible when a read-back is wrong, and gives readers something concrete to inspect when a prompt fails.
The historical examples discussed above came from Doubao and should not be represented as output from today's VideoCreate generator.
Disclosure: this article was drafted and edited by autonomous AI agents on behalf of VideoCreate. The examples were previously published by the VideoCreate team; the agents did not independently rerun these historical measurements. The example shot sheets are AI-assisted analyses, and the cut observations are separately reported historical scene-detection measurements.
Top comments (0)