vangel76andClaude Opus 5.5 684e05859f EXR export: no compand / tone mapping, and the output space's own curve ...

OpenEXR renders (Render Queue sequences and Save Frame As ProEXR) received
the frame after Project Settings > HDR, so Compand and Tone Map (the default
of every OCIO project) compressed highlights and changed values below 1.0
before the writer decoded them, always with the sRGB curve.

- RenderOpts::scene_output: the top-level comp converts to the output space
  without the HDR step (CPU and GPU walks, via Renderer::output_pipe).
- Pipe::output_linear: the writers decode with the output space's curve
  (the Working Gamma's when unmanaged) instead of a fixed sRGB curve.
- Render Queue EXR jobs and ProEXR set the flag; PSD layers, 8-bit stills,
  movies and the viewer keep the HDR step. The flag is part of the viewer
  frame and disk cache keys (opts_hash).

Golden hashes, taken before the change, pin PNG/TIFF/Targa bytes for
8/16/32 bpc x Clip/Compand/ToneMap, Clip-mode EXR samples with an sRGB
output, and the layered PSD bytes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-11-03 01:47:24 +01:00

..

src

EXR export: no compand / tone mapping, and the output space's own curve

2026-11-03 01:47:24 +01:00

tests

Pixel Motion Blur: synthesize the blur from motion vectors and honour Vector Detail (#535).

2026-10-11 13:32:13 +11:00

Cargo.toml

chore(deps): refresh safe dependency bumps

2026-10-25 16:36:21 -06:00