Atlas Register Plate (Float-Safe) 🎞

AtlasRegisterPlate looks like a no-op - image in, image out, and the output image is pixel-identical to the input. The actual work happens in the second output, a plate_ref that doesn't touch the pixels at all. It's the node that tells the rest of the pack what this image is: its path, its colourspace, its bit depth, and its role in the shot. Everything downstream that needs to hand a plate to Nuke or Maya or Resolve reads that metadata instead of guessing.

This is the colour-management discipline the whole pack is built around. The README is explicit about it: plates are tracked by reference in their working colourspace (ACEScg) and bit depth (EXR 16/32-bit float), and the projection path stays floating-point all the way down. In practice that means the 8-bit preview you're looking at in ComfyUI and the 32-bit float file your comp actually uses are the same plate, described correctly. That's the difference between "it looked fine in the graph" and "it's fine in Nuke."

The inputs that matter

• image - the plate, however it got there.
• plate_path - the original/final plate file, ideally an EXR at 16f or 32f. Blank marks it proxy-only, which is fine for testing but not for a real handoff.
• colorspace - defaults to ACEScg, which is what you want for a VFX handoff. Change it only if your source really is something else.
• bit_depth - auto, or descriptive values like 16f, 32f, 10-bit, 8-bit. This is metadata, not a converter - the node won't re-encode anything, it just tells exporters what they're dealing with.
• role - one of source, patch, clean_plate, matte, proxy. Pick honestly; a clean plate tagged as source will confuse the export later.
• lut_path - attach a Resolve/Iridas .cube to the plate reference so the LUT travels with it instead of living in some disconnected grade node.

Outputs

The image (passthrough) and the plate_ref - an ATLAS_PLATE_REF handle that your exporters consume for the EXR/float-safe handoff. The node is deliberately boring: it's how the pack keeps a scene-referred, correctly-coloured pipeline without you having to remember which node did what to which plate.

Install

Core tier, nothing to install beyond the pack:

cd <ComfyUI>/custom_nodes
git clone https://github.com/mikejamesvfx/atlas-camera.git

Restart, or use ComfyUI Manager and search "atlas-camera". It lives in Atlas/01 · Input & Camera, right where you'd expect the "make my plate official" node to be.

Where people get tripped up

The most common mistake is skipping it and wiring the raw LoadImage straight into exporters. Those will run, and the result will be an 8-bit sRGB plate described as if it were a proper scene-referred EXR - wrong colours on the other side of the handoff. The second gotcha: colorspace is metadata, so setting it to ACEScg does not convert an sRGB JPEG into ACEScg. Convert the source properly (Atlas's colour path handles that elsewhere), then register the result. Register what you actually have, not what you wish it were.