Live action shot with people or a camera: none (0%)
Auto-detection (live_action_check.py) flagged 11 segments (13–17s, 20–24s, 174–176s, 210–232s, 306–311s, 311–315s, 317–329s, 348–350s, 352–354s, 356–359s, 360–362s) as “live-action video”, but a check of all 25 contact sheets at 0.5s intervals showed every one was a 3D render or game screen recording. The whole frame keeps moving, so it was detected like camera noise. Live-action photo candidates: 0.
“Source videos” that play the live-action role Click to see that scene's prompt
Usage rules (measured)
| Item | Value |
|---|---|
| Share | Source video 62.7% Source image 21.1% Code only 16.2% |
| Placement | The first 23.5s and the last 81s are all result video. The middle alternates with diagrams and images |
| Length | Each video shot runs 6.1–14.8s with no edits inside the shot (exception: five 0.4s cuts in the first 2s of S30) |
| Transitions | Hard cuts in and out |
| Framing | Eye-level push-in, aerial push-in, turntable on a solid backdrop, slow close-up move, third-person gameplay |
| Overlays | 1 title tag + one subtitle line (+ 3 numbered cards or a before/after wipe line) |
This video has no live-action footage, so you don't need to decide “what to do about live-action scenes” before writing the script. For source video, prepare your own screen recordings or renders.
This example screen only draws the 01+ Live action tab as it really looks. This tab just lists what will go here.