Reliable on-set VFX data capture gives tracking, Houdini, lighting, and compositing teams enough evidence to reconstruct the photographed shot without relying on avoidable assumptions. The priority is not to collect every possible reference image. It is to preserve the camera, lens, timing, scale, lighting, color, and environmental information that the specific shot will require.
This guide provides a practical capture and validation checklist for intermediate artists and on-set teams. It covers pre-production planning, camera and lens metadata, set measurements, HDRI and sphere reference, clean plates, lens distortion, file organization, color management, and the final Houdini handoff. Use it as a framework rather than a rigid template: a locked-off product shot, a moving-camera destruction setup, and a digital environment replacement do not need identical capture packages.
Define the Shot Requirements Before the Shoot
Start with the problem that post-production must solve. A generic reference checklist can create a large volume of attractive but irrelevant material while missing the focal length, scale measurement, frame relationship, or lighting state that determines whether the shot can be reconstructed.
Divide the plan into three categories:
- Essential technical data: Information required to interpret, track, scale, or reproduce the shot.
- Supporting reference: Material that improves artistic and technical judgment but may not be necessary for the initial solve.
- Shot-specific capture: Additional evidence required by a particular effect, interaction, camera move, or environment.
| Shot requirement | Typical essential capture | Downstream use |
|---|---|---|
| Camera tracking and layout | Camera and lens identification, sensor or gate, focal length, focus, frame rate, shutter, frame range, movement notes, distortion information, and measured set features | Reproduces the plate’s projection, timing, and spatial relationships. |
| CG asset integration | Object scale, contact points, eyelines, clean plates, material reference, and lighting reference | Supports placement, look development, contact, shadows, reflections, and occlusion. |
| Digital environment or set extension | Camera height, lens height, horizon, set survey, panoramic reference, background plates, and coordinate conventions | Supports perspective matching, environment reconstruction, projections, and lighting. |
| FX interaction | Collision geometry, surface measurements, practical motion, event timing, camera data, and witness views | Provides physical scale and timing for destruction, particles, fluids, cloth, or debris. |
A locked-off plate with a small CG addition may only require a clean plate, reliable lens data, a few scale measurements, and lighting reference. A moving-camera destruction shot may also need surveyed collision surfaces, witness cameras, impact timing, moving-object reference, synchronized timecode, and a defined world coordinate system.
Build the brief around the final Houdini task
Describe requirements in terms of downstream operations. For example, a procedural set extension needs a camera and lens record, surveyed geometry, horizon information, a coordinate convention, and environment reference. A destruction setup may additionally need wall thicknesses, construction details, breakable boundaries, impact positions, practical debris motion, and surfaces that receive dust or contact shadows.
Assign ownership before photography begins:
- The VFX supervisor defines shot requirements, priorities, and acceptable fallbacks.
- The cinematographer and camera team confirm the camera, lens, exposure, focus, filters, and movement.
- The data wrangler or capture team records slates, measurements, reference media, witness-camera details, and setup changes.
- The DIT preserves source media, timecode, camera metadata, color information, and verified backups.
- The matchmove, Houdini, lighting, and compositing teams identify special requirements early enough to capture them rather than infer them later.
For a wider view of these responsibilities, see Artivoxa’s guide to on-set VFX supervision.
Agree on the delivery specification before the shoot. Confirm resolution, aspect ratio, frame rate, frame numbering, expected handles, timecode standard, color pipeline, plate format, camera-media relationship, and naming conventions. The source files should remain distinct from debayered, resized, cropped, stabilized, color-transformed, or undistorted derivatives.
Most importantly, record the photographed setup rather than only the planned setup. If the lens changes, the camera moves, focus differs between takes, a practical is dimmed, set dressing shifts, or an HDRI is captured after the light changes, update the notes immediately.
Capture Camera, Lens, and Motion Data
Camera tracking data establishes how the two-dimensional plate maps to a three-dimensional Houdini scene. Some missing values can be estimated during matchmove, but each estimate introduces ambiguity. An approximate focal length combined with an uncertain sensor crop and unknown distortion can produce a plausible solve that still has the wrong perspective or scale.
Camera and lens records
Record values for each take, not merely the equipment package available on set:
- Camera manufacturer, model, body ID, and recording mode.
- Sensor area or gate in use, recorded resolution, aspect ratio, crop, extraction, and overscan.
- Frame rate, shutter angle or shutter time, ISO or gain, aperture, white balance, and filters.
- Lens manufacturer, model or serial ID, focal length, zoom position, and focus distance when available.
- Focus pulls, exposure changes, lens swaps, stabilization status, and in-camera lens correction.
- Existing lens grids, distortion maps, calibration data, or lens-encoder metadata.
Lens metadata must describe the actual take. A zoom lens labeled only by its full range does not reveal the focal length used. Focus changes can also alter distortion, breathing, field of view, and sharpness. Optical or electronic stabilization should be documented because the resulting image motion may not correspond directly to the movement of the camera body.
Cross-check handwritten records against embedded metadata where possible. Neither should be assumed infallible: manual reports may contain transcription errors, while metadata can be omitted, rounded, overwritten, or lost during transcoding.
Movement, timing, and frame interpretation
Identify the support and describe the move: tripod, dolly, crane, handheld rig, gimbal, vehicle mount, motion-control system, or another configuration. Record whether the shot contains translation, rotation, zoom, a focus pull, stabilization, or a combination of these. Include start and end positions or repeatable marks when they are available.
Preserve the timing relationship between all recordings:
- Source clip or reel, slate, shot, take, frame range, and timecode.
- Capture and playback frame rates, including intentional off-speed photography.
- Shutter timing and any speed ramps, retimes, repeated frames, or dropped frames.
- Synchronization method for witness cameras, sound, motion control, practical events, and reference recordings.
- Handles and the intended mapping between source frames and the working plate.
A common failure is interpreting a sequence at the wrong frame rate rather than changing its actual frames. A 24 fps source treated as 25 fps changes duration and synchronization even though every image remains present. Likewise, a one-frame witness-camera offset can undermine motion analysis in a fast interaction.
Witness cameras are especially useful for occluded motion, articulated props, fast events, and camera moves that cannot be understood from the hero view alone. Record each witness camera’s position, orientation, lens, frame rate, resolution, start point, and synchronization method. Unsynchronized footage can still provide visual context, but it should not be treated as frame-accurate motion evidence.
Lens distortion and image processing
Document whether the delivered plate is distorted, undistorted, cropped, stabilized, sharpened, denoised, or otherwise processed. Matchmove may use an undistorted working plate, while compositing often needs a defined method for restoring the original distortion. The distortion model, image bounds, overscan, pixel aspect ratio, and any crop introduced by processing should travel with the shot.
If a dedicated lens grid cannot be captured, preserve architectural lines, tracking-marker coverage, and reference across the frame. These are not equivalent to a controlled calibration grid, but they may help diagnose distortion. Focus pulls and zooms may require more than one calibration state.
Record Set Scale and Spatial Relationships
A plate is a view into a physical volume, not just an image sequence. Set measurements allow matchmove, layout, procedural modeling, simulation, lighting, and compositing to work in a consistent space.
Measure features that constrain the camera or affect the CG result:
- Camera position and the optical center or lens height above the floor.
- Camera distance and orientation relative to stable set features.
- Floor, wall, ceiling, doorway, window, stair, platform, and major set-piece dimensions.
- Hero props, practical fixtures, tracking markers, contact points, and actor eyelines.
- Surfaces that receive shadows, reflections, destruction, particles, fluids, or other interaction.
- Distances between important objects rather than isolated dimensions alone.
Measurements need context. A note reading wall height: 2.4 is ambiguous unless it identifies the wall, unit, endpoints, and relevant take. Photograph measured features and associate them with survey IDs or annotated diagrams. Wider photographs should show how each feature relates to the rest of the set.
Separate permanent geometry from temporary conditions. Furniture, cables, scaffolding, removable flats, tracking markers, and practical props may move between takes. Note whether an element is fixed, movable, deforming, replaced, or intended for removal. Do not allow one static survey to silently represent multiple configurations.
Coordinate-system conventions
The survey handoff should state:
- The unit system and any conversion required for Houdini.
- The origin and the stable physical feature to which it is attached.
- The up axis, forward direction, and axis labels.
- Whether the coordinate system is right-handed or left-handed.
- Whether a camera measurement refers to the body, sensor plane, optical center, entrance pupil, or another survey point.
- The transform between survey, stage, matchmove, and Houdini coordinates when they differ.
Houdini can accommodate different scene-unit conventions, but all departments must interpret the numbers consistently. A set that appears visually correct after an arbitrary scale adjustment may still produce incorrect simulation behavior, light placement, depth of field, or camera clipping if other data remains in the original scale.
Include stable survey points with IDs, coordinates, measurements, and reference photographs. These provide an independent way to validate the imported camera and geometry. If a projected point misses the plate, the team can investigate the camera solve, axis conversion, origin, or measurement instead of adjusting geometry blindly.
Capture Lighting, Color, and Environment Reference
Lighting reference should describe diffuse illumination, specular response, shadow direction, source size, color, exposure, and the surrounding environment. A useful image is not automatically reliable lighting data; its capture position, settings, orientation, and color interpretation must also be known.
HDRI and panoramic capture
Capture an HDR environment when the shot needs image-based lighting, accurate reflections, environment reconstruction, or a record of the surrounding sources. Place the capture position as close as practical to the subject or tracked camera position relevant to the intended use. In a small interior, even a modest offset can change nearby parallax and reflection placement.
Record:
- Capture position, camera height, orientation, date or setup, and the direction corresponding to plate forward.
- Camera, lens or panoramic rig, aperture, shutter, ISO, white balance, and bracket sequence.
- Whether the camera moved, panned, tilted, or was repositioned after the plate.
- Changes to windows, practicals, flags, diffusion, screens, reflectors, weather, or daylight.
- Moving crew, vehicles, foliage, clouds, flickering sources, or other causes of ghosting.
Preserve the bracketed source exposures as well as the merged HDRI. Inspect the result for clipped highlights, missing brackets, stitching seams, ghosting, and incomplete zenith or nadir coverage. A panorama with clipped windows or practicals may still help with background context, but it may be unsuitable as an authoritative illumination or reflection source.
Do not force every environment image into the same role. Depending on its quality and position, a capture may serve as a light source, reflection source, projected background, orientation reference, or simply a guide for manually reconstructed lights. For further scene-building context, compare the roles of Houdini and Gaffer in lighting.
Gray ball, chrome ball, and color-chart reference
Place gray and chrome spheres near the subject or at a representative lighting position. Capture them from the relevant camera view without changing the shot lighting.
- The gray sphere shows diffuse balance, gradients, and shadow direction.
- The chrome sphere records reflection placement, source direction, and apparent source size.
- A color chart supports color-response evaluation when its exposure, illumination, source file, and transform are documented.
Keep the reference objects still and record their positions. Check that the gray sphere retains readable highlight and shadow information, the chrome sphere is clean and unobstructed, and the chart receives the intended illumination. A chart held under a separate work light does not describe the shot lighting.
Preserve the original files and state whether each image is camera raw, log-encoded, scene-linear, display-referred, or shown through a production look. A display preview with an unknown transform should not become the authoritative color reference.
Photograph the broader lighting setup as well. Include fixtures, windows, bounce surfaces, flags, diffusion, practicals, interactive sources, and objects that create important spill or shadows. Record dimmer values, gels, fixture changes, and adjustments between takes where production permits.
Collect Plates, Material, Object, and Actor Reference
Reference photography supplies evidence for asset construction, look development, occlusion, contact, and compositing. Prioritize coverage that explains form and function over a large collection of nearly identical images.
Assets, materials, and interactions
For hero assets and environment areas, capture:
- Overall proportions from several useful angles.
- Undersides, rear surfaces, seams, fasteners, labels, construction thickness, and damage.
- Material transitions, roughness cues, weathering, wetness, and surface variation.
- Ground contact, support points, pivots, and relationships to measured set features.
- A known scale reference and, where relevant, camera distance or field of view.
- The asset’s identity, orientation, shot position, and any movement or redressing.
Texture photographs without lighting context can be misleading, especially for glossy, metallic, translucent, wet, or strongly directional materials. Capture wider views that reveal source direction and reflections, and distinguish appearance reference from photographs intended for texture extraction.
Actor and prop reference may also be necessary when body position, wardrobe, hair, contact, shadowing, or interaction affects the CG. Views of areas hidden in the hero plate can help artists build holdout geometry and understand where an effect passes behind or touches a live-action element.
Clean plates and background plates
A clean plate should match the hero setup’s camera position, lens, framing, focus, exposure, shutter, and lighting while omitting the actor, prop, marker, rig, or practical effect that may need removal. Even a small camera move can introduce parallax that makes the plate unsuitable for a straightforward patch.
A background plate is not necessarily a clean plate. It may be a separately timed or photographed environment element intended for compositing, projection, or replacement. Label its purpose, setup, and timing rather than treating the terms as interchangeable.
Check clean and background plates for moving foliage, smoke, crowds, reflections, changing daylight, practical-light variation, and cast shadows. If an exact clean plate is impossible, capture the closest useful alternatives and document the mismatch. Foreground-only, background-only, prop-only, or empty-set passes can still reduce uncertainty when their setup is clear.
Organize the Handoff as Production Data
Reference becomes difficult to use when artists cannot connect it to the correct shot, take, lens, frame range, or lighting state. Preserve source media, separate it from derivatives, and use stable identifiers across filenames, slates, reports, and production tracking.
A practical filename can include project, sequence, shot, camera, take, capture type, position or setup, version, and date:
PRJ_SEQ010_SH020_CAMA_TK03_HDRI_POS_A_v001_YYYYMMDD
Do not overwrite original camera files. If pipeline requirements demand renamed files, retain a manifest that maps working names to source names.
A shot-level folder structure might use:
SEQ010/SH020/CAMERA/originalandworkingSEQ010/SH020/LENSandSURVEYSEQ010/SH020/PLATES/hero,clean, andbackgroundSEQ010/SH020/LIGHTING/HDRI,SPHERES, andCHARTSSEQ010/SH020/WITNESS_CAM,OBJECT_REF, andACTOR_REFSEQ010/SH020/DOCSfor reports, slates, color notes, manifests, and change logsSEQ010/SH020/DELIVERY/v001for the reviewed handoff
Use position or state identifiers such as POS_A, LIGHTING_B, or SETUP_NIGHT when several captures belong to one shot. Filenames should not carry the entire metadata burden; maintain a shot report or machine-readable sidecar where appropriate.
Preserve processing and color-management history
Every derivative should state what changed. Record debayering, resizing, cropping, stabilization, denoising, sharpening, frame-rate conversion, distortion or undistortion, and color transforms. Preserve original frame boundaries and document any overscan added to working plates.
For color, identify whether plates, HDRIs, charts, and stills are camera-original, log-encoded, scene-linear, display-referred, or converted to the production working space. Record the input transform, display transform or show LUT, exposure adjustments, and any exceptions. Lighting and compositing cannot compare images reliably if one reference contains an undocumented display look.
The compositing handoff should retain the same shot, camera, frame, distortion, and color conventions. Artivoxa’s overview of CGI compositing steps provides additional context for how those decisions affect the finished image.
Validate the Capture Before Work Begins
Validation should test relationships, not merely confirm that files exist. Compare the plate metadata, camera report, lens notes, survey, witness footage, color records, and delivery manifest. Resolve discrepancies while the setup is still accessible whenever possible.
Common failure modes
- Missing lens data: The report lists the lens package but not the lens, focal length, focus state, or sensor area used for the take.
- Incorrect frame interpretation: A sequence is assigned the wrong frame rate, frame range, timecode offset, or source-to-working-frame mapping.
- Inconsistent scale: Measurements omit units, use different origins, or are converted independently in matchmove and Houdini.
- Ambiguous camera height: The record does not state whether height refers to the body, sensor, lens center, or another point.
- Unsynchronized witness cameras: Footage lacks timecode, a sync event, frame-rate information, or a documented offset.
- Moving reference objects: Spheres, charts, tracking markers, props, or measuring references shift between the hero take and reference pass.
- Clipped HDRIs: Brackets fail to retain bright windows, skies, or practicals, limiting lighting and reflection use.
- Contaminated clean plates: Camera movement, changing light, shadows, reflections, smoke, or moving scenery prevents a clean match.
- Undocumented set changes: Camera, lighting, focus, practicals, or dressing changes without an updated report.
- Lost metadata: Renaming, transcoding, exporting, or messaging reference files strips their source identity or color information.
- Duplicate or overwritten files: Repeated filenames silently replace earlier captures or obscure version history.
Use verified-copy procedures or checksums for source media and inspect representative files after transfer. A successful copy operation does not guarantee that every expected bracket, frame, report, or witness clip was included.
Final VFX shot handoff checklist
- Shot identity: Shot, take, slate, camera, source clip, frame range, handles, and timecode agree across the package.
- Camera and lens: Body, sensor or gate, resolution, aspect ratio, frame rate, shutter, lens, focal length, focus, exposure, filters, stabilization, and distortion state are documented.
- Movement and timing: Camera support, move description, retimes, off-speed capture, witness-camera synchronization, and practical-event timing are clear.
- Scale and coordinates: Units, origin, axes, handedness, camera or lens height, horizon, survey points, and required transforms are defined.
- Lighting and color: HDRI brackets, panorama orientation, gray and chrome spheres, charts, exposure notes, practical-light changes, and color transforms are present and usable.
- Plates and reference: Hero, clean, and background plates are correctly labeled; material, object, actor, texture, and interaction reference maps to the photographed setup.
- Media integrity: Source files are readable, verified, protected from overwriting, and separated from documented derivatives.
- Change history: Lens swaps, camera moves, focus changes, lighting adjustments, set changes, repeated captures, and known limitations are recorded.
Before approving delivery, run a small technical test in the intended Houdini workflow. Import the camera or survey, set the units and axes, inspect the full frame range, and project stable survey points or proxy geometry over the plate. Check the horizon, scale, camera timing, and distortion assumptions. Then verify that representative plates, HDRIs, charts, and renders display through the expected color pipeline.
The handoff is ready when another artist can identify what was captured, where it belongs, how it was interpreted, and what changed—without depending on undocumented assumptions before tracking, layout, simulation, lighting, or compositing begins.