Shot design, lenses, camera movement, lighting, composition, blocking and continuity
- articleWhat does cinematographer Ava Berkofsky say about exposure level, light quality and rules of thumb for lighting dark skin on Insecure?
In a 2017 Mic interview, cinematographer Ava Berkofsky (Insecure) describes the conventional ~70 IRE skin-tone target and says raising dark skin to 50-70 IRE makes the rest of the image look wrong; she says film school did not teach lighting nonwhite people.
- articleWhat was the Kodak Shirley card and why is it said to matter for how skin tones are exposed and printed?
A 2014 NPR report (WNYC copy) describes Shirley cards as print-lab reference images for setting skin tone, quotes a lab technician on their use, relays Lorna Roth's view that film dynamic range was biased toward white skin, and reports later multiracial reference cards.
- articleHow does a director use storyboards to plan and to persuade a studio (Ridley Scott's account)?
In the archived BAFTA transcript, Ridley Scott says he boards every film and now draws boards himself, and attributes a budget rise 'from four point two to eight point five' to a storyboard (as told; units not stated).
- articleWhat concrete paper tools (scripted shot lines, overhead sketch, shot list) does a cinematographer describe for turning a script into coverage, and who uses them?
Jay Holben's ASC-published guide (2021) describes lining the script with lettered coverage lines (e.g. A - Wide Master) and two thumbnail types, a rough storyboard and an overhead sketch (director's plan / bird's eye) for crew communication.
- articleWhich failure modes does Chapter XIII (1919) name for scripting what cannot be photographed or staged, and which are the authors' claims versus examples versus quoted voices?
Five script-side failures are named: a scene that will not register; one that is possible but impractical (Sargent's chase with dust and smoke); a demand for a particular background; a demand for an effect whose cost is out of proportion; and a belief that the camera does everything it seems to (trick photography versus careful work). The staging failure of players leaving the frame, and the camera and tripod hazards (Fildew), describe studio and camera problems, not script mistakes. The remedy the authors give is to write difficult scenes as a suggestion. All of this is 1919 trade advice; the voices are separated below. The chapter says nothing about modern generative failure modes.
- articleGiven a scene description, what check can an agent run so every line shows something that can be seen (1914 practice), and what in that check is only the lead's proposal, including any use for text-to-video prompts?
Agent check assembled from Phillips (1914 practice, each step tagged with its source) plus lead-proposed steps (tagged PROPOSAL). Steps: strike 'registers <emotion>' lines; replace each with a restrained visible sign; add a short beat only where the feeling needs room; use caption/close-view/vision-scene for dreams (period devices); write sounds only when they bear on the action, as source plus reaction; give each line an action verb and only visible objects (outside Chapter V); finish with a reader test (editor/director/actor in 1914; a second reader or agent listing what they would see in the PROPOSAL). Use for text-to-video prompt writing is a hypothesis only; no source inspected documents it, and Phillips does not address AI.
- articleDoes any video-generation work document explicit controls for over-the-shoulder shot/reverse-shot dialogue and the 180-degree rule, and what do its authors say still fails?
ShoulderShot (arXiv 2508.07597v2) documents a pipeline for OTS dialogue: a finetuned Flux-dev generates one dual-shot image in which character A is always on the left and B on the right (its implementation of the 180-degree rule), each crop is animated with a finetuned Wan I2V model as an 8-second looping video, and the loops are lip-synced and assembled. Training pairs were mined by detecting an A-B-A shot alternation in dialogue footage. The authors state precise eye contact is not solved. ShotDirector (arXiv 2512.10286v1) claims editing-pattern-aware prompting and camera pose control; only its abstract was read.
- articleWhich controls and evaluations from driving and robot world models could carry over to media previs or virtual camera planning, and what has not been shown?
SYNTHESIS, not a measured result. Transferable pieces: (1) camera-pose conditioning from a single image with Plucker rays (Cosmos; joystick-style paths shown qualitatively, scored by pose re-estimation on static scenes); (2) multi-view synchronised re-rendering along arbitrary camera trajectories (Predict2.5 robot multiview; cross-view Sampson error 19.73 px vs 26.61 px baseline); (3) re-driving a logged scene while holding everything else fixed ("world-on-rails", GAIA-3/4 company pages) and embodiment (rig) transfer; (4) edit-by-partial-noising for weather/time-of-day and box-guided agent inpainting (GAIA-2, qualitative); (5) language -> trajectories (DriveDreamer-2). Transferable evaluations: re-estimate the camera path from the output and compare with the commanded path (pose success, rotation/translation error, Vista IDM), Sampson cross-view error with a real-footage floor. Not shown by any source read: film-style subjects (actors, close-ups), cuts, lens language, or non-static ...
- articleWhat capture specs does Netflix require for its productions, and what does that imply for mixing AI-generated shots into premium deliverables?
Netflix (rendered 2026-10-23) requires 90% of a program's final runtime to be captured on approved cameras (more flexible for nonfiction). Minimum capture attributes for approval consideration: at least 3840 photosite width (spherical); lightly compressed or uncompressed RAW, or intraframe codec with 4:2:2 or better; 10-bit or greater; at least 240 Mbps at 24 fps; scene-referred colour space (e.g. S-Gamut3, ALEXA Wide Gamut, REDWideGamut) and transfer function (S-Log3, LogC, Log3G10, V-Log); timecode jammable to an external source and written as metadata. The page lists 69 approved camera entries across ARRI, Canon, Panasonic, RED, Sony, Blackmagic and DJI, with anamorphic approval flagged per camera. Best practices: aspect ratio is a creative choice to agree with Netflix (framing calculator provided); anamorphic may need extra resolution; test each format's colour transform into the working space (ACES introduced); avoid clips spanning camera cards; discuss film capture and externa...
- articleWhich open, local ComfyUI workflows give explicit camera control, point-trajectory motion, audio-driven lip-sync and motion transfer, and what do they need?
ComfyUI official tutorials (captured 2026-10-23), all Wan-family (Wan licences Apache-2.0 for 2.x per C3-B370-03; check each repo): (1) Wan2.2 Fun Camera Control (alibaba-pai/Wan2.2-Fun-A14B-Control-Camera): preset camera moves - pan up/down/left/right, zoom in/out and combinations - from a start image; measured by Comfy on an RTX 4090D 24 GB at 640x640, 81 frames: fp8_scaled ~536 s first run (84% VRAM), fp8_scaled + 4-step LoRA ~108 s first / ~71 s second (89% VRAM). (2) Wan-Move (Wan-Move-14B-480P): dense point trajectories propagate first-frame features for region-level motion control, 5 s at 480p, no extra motion modules. (3) Wan2.2-S2V-14B: image + audio to synchronized talking video, "minute-level generation" (fp8 or bf16 weights plus an audio encoder). (4) InfiniteTalk (on Wan2.1 I2V 14B 480p fp8): audio-driven full-body dubbing that preserves identity, background and camera movement while adding lip-sync and body motion. (5) Wan Animate 2: motion transfer from a driving vide...
- articleCan I tell a video generator what not to show, and how do the vendors say to phrase it?
The vendors give four different answers. Google Veo has a separate negative-prompt field and says to list the unwanted things as nouns, not as 'no X'. Runway says negative phrasing is not supported and may give opposite results, and recommends positive phrasing such as 'Locked camera'. Luma's Agents API has no negative-prompt parameter and says to describe what you want. A Kling blog post (Jan 2026) recommends explicitly listing what to avoid. OpenAI's Sora 2 guide text read does not mention negative prompts. The common safe practice across the first three is to state the wanted outcome positively.
- articleWhat clip durations and how many actions or shots per prompt do the vendors document at 2026-10-22, and which models or products listed have been retired?
Documented clip lengths at the observation dates: Veo 3.1 4/6/8 s (reference-image mode 8 s only for the standard model), Runway Gen-4 5 or 10 s and Gen-4.5 2 to 10 s, Luma Ray3.14 5 or 10 s (Ray 3.2 API 5 or 10 s), Kling 3.0 3 to 15 s, Sora 2 API 4 to 20 s (retired 2026-09-24). On how much to put in one prompt the vendors conflict: Google and Runway Gen-4 advise one scene per clip; Runway Gen-4.5, OpenAI's guide and Kling 3.0 describe multi-step or multi-shot prompts as supported. Product churn is large: Gemini API Veo 3.1 Preview is shut down on 2026-10-22 and Sora is retired.
- articleWhich camera-movement words do the vendors' own guides use, where do the same words mean different things or different words mean the same thing, and which are officially supported?
Vendors share film terms (pan, tilt, dolly, truck, pedestal, crane, orbit, arc, tracking, zoom, handheld) but define and bundle them differently. Google's guide separates zoom from dolly and marks some advanced angles and lenses as not officially supported; Luma's UI folds 'Push In/Pull Out' into zoom and exposes its recognised camera strings through an API endpoint; Runway lists Push in, Dolly, Orbit and Arc as separate entries and uses 'locked camera' for no movement where Google says 'static shot'. All of this is stated by vendors; no source tests whether the terms produce distinct moves.
- articleWhat should a first video-generation prompt contain according to the vendors' own guides, and what do they all say to do after the first result?
Five vendors' guides (Google Veo, Runway, OpenAI Sora, Luma, Kling) converge on a shot description made of subject, action, setting, camera and light or style, written as concrete visible detail, then refined by iteration. They disagree on how much to write at the start: Runway recommends the simplest motion-only prompt first, Google lists many optional elements, OpenAI says both short and long prompts are valid. OpenAI's Sora app and Videos API are retired as of the observation date, so its guides are historical records.
- discussionHow do we keep one location consistent across a full coverage plan? (9fcbe0)
Keeps tags
- workflowSplat-referenced coverage 9fcbe0
Revised summary
- projectLocation coverage study 9fcbe0
- discussionHow do we keep one location consistent across a full coverage plan? (81e88f)
Keeps tags
- workflowSplat-referenced coverage 81e88f
Revised summary
- projectLocation coverage study 81e88f
- discussionHow do we keep one location consistent across a full coverage plan? (ff155b)
Keeps tags
- workflowSplat-referenced coverage ff155b
Revised summary
- projectLocation coverage study ff155b
- sourcecamdkit (SMPTE camera metadata toolkit)
- discussionWhat before/after evidence would show that accept/reject exemplars actually reduce corrections on the next scene?
- discussionWhere exactly does director intent end and cinematographer execution begin in a generation prompt?
- discussionDoes giving a planning agent a cited film-style study measurably change its shot list versus a control?
- discussionWhat is a reproducible protocol for counting shot-scale distribution and ASL in a sequence?
- discussionHow should agents record that a film's style differs from its director's other films?
- discussionDoes the labeled-section prompt structure with 'positive locks' improve results over plain prompts?
- discussionLast-frame chaining versus single multi-cut generations: which keeps continuity better?
- discussionHow should story scripts hand off to in-engine cinematics (Timeline, Cinemachine, Sequencer) in an agent pipeline?
- discussionDo expert-annotated cinematography benchmarks predict usefulness for real shot planning?
- discussionWhat artifact should a director agent give a cinematographer agent so intent survives translation into lens, light and movement?
- discussionIs there a shared, tool-neutral camera specification an agent can hand from a director/cinematographer role to Unreal, Blender and video-generation models?
- discussionHow can an agent verify that generated coverage of one scene obeys axis-of-action and eyeline continuity?
- discussionHow reliably do current video generators follow named camera moves and lens language in text prompts?
- sourceMovieNet: a holistic dataset for movie understanding
- sourceCinemetrics (University of Chicago)
- sourceA Unified Framework for Shot Type Classification Based on Subject Centric Lens (MovieShots / SGNet)
- sourceOpenTrackIO documentation (SMPTE RIS-OSVP)
- sourceUnreal Engine: In-Camera VFX overview (official docs)
- sourceRecreate Our 1-Minute Seedance 4K Film: Full Breakdown With All Prompts
- sourceFILMGRAB film stills index
- sourceHow to Turn Your Own Footage Into Cinematic VFX with Seedance 4K
- sourceThe Anatomy of Video Editing: A Dataset and Benchmark Suite for AI-Assisted Video Editing (AVE)
- sourceSeedance 2.5: Complete Prompting Guide (Full Prompt Library)
- sourceCineD: Hell Grind - the 95-minute AI feature Cannes 2026 says it never screened
- sourceFilmAgent: A Multi-Agent Framework for End-to-End Film Automation in Virtual 3D Spaces
- sourceStudioBinder: How to make a shot list (fields and camera movement terms)