Which TVC shots should use real evidence instead of generated atmosphere?

Mark the job of every shot

A fictional insulated flask campaign includes a tabletop reveal, lid detail, pouring action and a temperature-retention scene. The first two can present visible form. The last one implies measured thermal performance, which an attractive generated scene cannot establish. Mark each shot as presentation, visible-feature explanation or evidence-dependent demonstration before finalizing the script.

This classification helps direct production effort. It does not imply that generated presentation scenes are automatically accurate. Even a harmless tabletop view must preserve the lid, label and sold configuration.

A pouring scene can imply operation even without a measurement caption. Verify that the real flask opens, pours and seals in the way shown; do not dismiss invented mechanics as atmosphere. Count and classify every actual shot in the selected plan, whether it contains 9, 16 or 25 scenes.

Choose the source for the claim

The examples are editorial distinctions, not product test results. If a necessary evidence shot is unavailable, remove the claim, change the scene or capture the missing material. Do not let AI fill a factual gap with an invented demonstration.

These are hypothetical evidence requirements, not completed tests. Real footage of one fit does not establish universal compatibility, and a genuine measurement does not validate a different size or product revision. If the evidence scope is unknown, hold the claim rather than broaden it.

Brief a mixed-source edit clearly

Give an external editor the approved generated atmosphere and separately verified demonstration. Label which source supports each statement. Avoid cutting from a real test into a generated result in a way that suggests both are the same recorded event. Review transitions and captions for that implication.

Current CartVisual TVC generation creates its supported source clips; arbitrary real-footage insertion is an external editing decision. A planning table does not add an upload-and-splice feature to the website.

Keep each supplied demonstration’s filename, source, product revision and supported statement beside the generated atmosphere file. The current assembler uses its supported generated source sequence; this manual map does not create an arbitrary upload-and-splice control. Preserve both sources and require a fresh check of the external editor’s final file.

Review the full claim after editing

Watch the advertisement as a buyer and write down every performance or compatibility inference. Compare those inferences with the evidence record. Remove unsupported conclusions even when no single caption states them explicitly. The goal is a useful product story whose persuasive force comes from truthful features, rather than effects that resemble proof.

Use a comprehension review to learn what a viewer actually inferred, then compare that inference with the evidence scope. For audio and captions, give the finishing editor the same approved claim record. Clear storytelling does not substitute for support.