ANDRO Save EXR

ANDRO Save EXR is where the float32 decode in this pack actually lands. It writes an IMAGE batch as a real float32 EXR sequence, values untouched - including everything outside [0,1] - and it's the only sane target for keep_out_of_range decodes that are headed into a grade. Wire ANDRO VAE Decode in, save, and out come frame.00001.exr files that carry the headroom a colourist actually spends. The pack's own arithmetic: 121 frames of 1280×704 float32 EXR is about 1.2 GB, so give it a folder of its own.

It uses the OpenEXR module, not cv2, and verifies the file landed rather than trusting the writer - both deliberate. OpenCV compiles the EXR codec in but leaves it disabled unless OPENCV_IO_ENABLE_OPENEXR=1 is set before cv2 imports, which no ComfyUI launcher does. Any node writing EXR through cv2.imwrite silently produces nothing; this one sidesteps the whole class of bug. No EXR backend available? It falls back to a 32-bit float TIFF carrying the same values under a different extension (needs pip install OpenEXR to avoid the fallback).

The part no other save node does

The header records how its own pixels were made. With write_metadata on, each file carries andro/* attributes - measured range, how much sat outside [0,1], bit depth, frame count - and wiring ANDRO VAE Decode's range_report into the decode_report input stores the decode's own account verbatim, dtypes included. Six months later the file still answers "was this the float32 pass?" on its own. That's the workflow-in-the-file philosophy ComfyUI PNGs made famous, transplanted to a format that can hold out-of-range values.

• colorspace (default srgb_display) labels what the numbers are: a decoded SDR frame is display-referred sRGB/Rec.709 gamma, not linear, which is what most compositors would wrongly assume about an untagged EXR. Two exceptions to remember: LTX-2.5 HDR decodes are ACEScct, and the LTX-2.3 HDR IC-LoRA is LogC3. This is a label, not a conversion - not one pixel is touched. Nuke or Resolve still has to be told the same colourspace on input.
• clipped_layer adds a second EXR layer holding exactly what the stock clamp would have deleted, zero everywhere it would have kept the value. The loss then travels inside the file instead of in a screenshot you have to show someone.
• start_frame/padding - defaults 1 and 5 give the historic stem.00001.exr; VFX pipelines set 1001 with padding 4 and land on frame.1001.exr, the convention Nuke and Resolve expect. Numbers too big for the padding are written in full, never truncated (truncation would collide two frames onto one filename).
• embed_workflow (on by default) stores the whole workflow and prompt in the header plus a summary of every checkpoint, VAE, seed and prompt - turn it off for confidential graphs; the summary fields still get written. A <stem>.manifest.json sidecar carries the same facts for scripts without an EXR library.
• output_folder - absolute path to drop the sequence straight into a project folder; empty means the ComfyUI output directory.

half_float (16f) halves file size at roughly 11 bits of mantissa - far above bf16, so a 16f EXR of a float32 decode keeps most of what the decode won. Use 32f when frames will be stretched hard under a grade.

Install

ANDRO Save EXR ships in the comfyui-vae-float32 pack. ComfyUI-Manager → search comfyui-vae-float32 → install → restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/AndreiOrehov/comfyui-vae-float32
pip install OpenEXR

Restart and find it under ANDRO. One operational gotcha shared across the pack: a measuring/saving node that "never runs" usually means you hit the selection strip's ▶ button, which executes only the selected output node and drops everything else while still reporting success. Hit a plain Run. The author's full pipeline example, LTX2.5_float32_EXR.json, shows the intended whole - float32 decode, EXR sequence, video, and the decode's range report all from one image.