
Inspect an EXR layer in each Natron view before assuming that a listed layer exists in both eyes. Natron's Read interface can list the union of layers found across views. A depth layer shown in the menu may belong to only one view; the menu entry alone does not prove a complete stereo pass.
Key Takeaways
- A layer list can combine the layers of several views.
- Confirm the intended layer/view combination in the actual image.
- Missing source data should be resolved or explicitly scoped before delivery.
Separate the layer choice from the view choice
The Natron 2.5 stereoscopic-compositing guide explains that the Read node displays all layers available across the file's views, even when some are absent from individual views. It also describes a multiview indicator and a Viewer view selector.
Select the layer required for your operation, then inspect each intended view. Use a visible image feature or a deliberately understood diagnostic pass to confirm what is being displayed. Do not treat a dark image as conclusive proof of absence: a valid data pass can also look uninformative under an unsuitable display interpretation.
Make a layer-by-view manifest
For a proposed delivery with left and right views, write a small inspection sheet:
| Required component | Left view checked | Right view checked | Action if uncertain |
|---|---|---|---|
| Main image | Record visible identity | Record visible identity | Inspect source view mapping |
| Depth pass | Confirm the required data | Confirm the required data | Ask the renderer for the missing pass |
| Additional named pass | Check the exact layer name | Check the exact layer name | Clarify whether both eyes are required |
This sheet is a proposed review method, not an assertion that every renderer uses those names. Copy the actual layer names from the source and preserve their meaning.
Proposed example: one-eye depth delivery
Suppose the beauty images exist for both eyes but only the left view has a depth pass. A depth-based operation may work for the left image and fail to produce a comparable right image. Reconnecting the same menu entry cannot create the missing right-eye data.
Confirm the requirement with the person supplying the EXR. They may provide the missing view/pass, or the project may intentionally use a mono-only depth workflow. Document that limitation. Do not silently relabel the left pass as right-eye evidence.
Check the output after fixing the source
When revised source data arrives, reopen or refresh it through the normal Read workflow and inspect the combinations again. Review the affected composite frames in both views, not only the pass browser.
Accept a stereo-pass handoff only when every required layer/view pair has been identified and the output format preserves the intended views. The Read guide covers the broader import context, but does not turn a visible layer name into proof of data availability. Keep the inspection record with the source manifest.
Related tasks
- Why Did My Layered PSD Arrive Flattened in Final Cut Pro?
- Should a Krita Filter Mask Go on a Group or an Individual Layer?
- Why Does My Image Sequence Skip Frames or Play at the Wrong Speed?
Sources and scope
- Natron2.5 official documentation: Read lists the union of EXR layers across views; layers need not exist in every view.
- Natron2.5 Read guide: Broader image import interpretation.
Documentation-based guidance for Natron 2.5 manual and named built-in node; later2.6 not assumed. Examples are proposed checks, not reported tests. Official source bodies were read on2026-10-23; user-discussion evidence is not search-volume or AI-citation-frequency data.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Paparazzi Ratzfatzzi / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.