
Pixel pitch is a specification, not a verdict
Moiré is seen by a particular camera, lens, focus choice, sensor sampling path, distance, wall pattern, exposure, and movement. A panel specification can be relevant to a conversation, but it cannot certify a shot that has not been photographed. The useful question is not “what pitch is safe?” It is “under the intended capture conditions, what artifact appears, where, and does it survive the shot?”
Netflix’s OpenVPCal guide gives a narrow but practical calibration instruction: defocus the camera just enough to prevent moiré during calibration capture, with the defocus toward the camera, and warns that too much can confuse analysis. This is not a general instruction to soften every production image. It is evidence that focus and camera-to-wall conditions matter to the observed result.
Build the matrix around the shot
Choose the actual bodies, sensor modes, lens candidates, focus distances, stops, shutter settings, camera-to-wall distances, and wall content classes. Include an unhelpful-looking test image: fine horizontal detail, fine vertical detail, diagonal texture, moving content, gradients, and the intended background. Add a small physical foreground such as fabric, hair, or a reflective edge when the show needs it. A flat gray chart alone cannot reveal every interaction.
| Variable | Test values | Record |
|---|---|---|
| Lens and distance | Widest/longest planned positions | Frame grab, focus distance, wall distance |
| Focus and stop | Planned sharpness extremes | Artifact location and accept/reject note |
| Wall content | Fine detail, movement, intended plate/render | Whether artifact changes with content |
| Motion | Static, pan, dolly, rack focus | Recorded clip, not only stills |
Keep calibration capture separate from the creative test
OpenVPCal also describes camera and LED warm-up, multiple frames per patch, and checking the camera output when using its verification patterns. Those are source-backed calibration practices for that tool. Atlas proposed process is to schedule a separate creative camera matrix after the technical image-chain check. A calibration capture can be correctly defocused for its analysis while the production shot has a different focus requirement. Do not turn one purpose into evidence for the other.
Illustrative decision record
Illustrative: the intended 85 mm close shot is clean at its normal actor focus distance, while a 32 mm move that starts close to the wall produces moving interference in a fine brick texture. The record says exactly that, includes the settings and clip, and gives three options: revise the texture, alter the move or subject-to-wall distance, or move the shot to a different capture method. It does not claim that a panel has “failed” or that moiré has been permanently solved.
Epic’s stage-testing guidance reinforces the operational point: test on the hardware and configuration that will carry the work, and document the results. The matrix is the document.
- Test intended lenses, distances, stops, focus behavior, and movement.
- Include real candidate content, not only synthetic charts.
- Save clips and settings together so a result can be repeated.
- Write the shot-level decision and its fallback; do not promise a universal pitch threshold.
Sources & evidence
Primary documentation establishes tool behavior or a reported production. Checklists and illustrative examples are Atlas editorial guidance, not results of independent testing. Match documentation to your installed version.
Its user guide describes controlled defocus to prevent moiré during calibration capture, warm-up, patch capture, and camera-output verification.
Source published: Not established · Retrieved 19 September 2026
Recommends regular, documented tests using stage-equivalent or on-stage configurations.
Source published: Not established · Retrieved 19 September 2026