If you are using DxO (either PhotoLab or PureRAW) to pre-process your raw files into linear DNGs before editing them, you have to throw a massive wrench into the standard ETTR advice.
DxO's demosaicing algorithms and DeepPRIME denoising engines are phenomenal, but they handle the bleeding edge of raw data completely differently than Adobe Lightroom or Capture One.
Preprocessing with DxO completely changes how hard you can push your Z8 and Z50 II sensors.
1. The Ceiling Drops: DxO Discards the Absolute Edge
When you pull an aggressive ETTR file into Adobe Camera Raw or Lightroom, Adobe’s engine uses hidden metadata thresholds to actively compute and guess the values of raw channels that are practically touching saturation.
DxO handles raw data with mathematical rigidity. To guarantee pure color accuracy, DxO's pipeline establishes a strict "white level" safety ceiling. If a raw channel (usually that dominant Green channel we discussed) gets too close to the sensor's physical clipping limit,
DxO will frequently discard or hard-clip that data early in its internal math.
- The Trap: If you push a file to your absolute +2.7 EV limit, and then pass it through DxO to generate a linear DNG, DxO will bake its strict clipping boundary into that DNG.
- The Consequence: When you open that DxO-generated DNG in Lightroom and try to pull the Highlight slider down, you will often find the highlights have abruptly clipped into a nasty magenta or purple color cast. The safety margin Adobe usually uses to reconstruct the channel is gone because DxO flattened it.