Thanks, that clarifies the scene-linear behavior. It looks like your previous reply with the more detailed description of how isHighlightRecoveryEnabled affects the boost curve, GainTableMap, and gamut mapping has disappeared. Could you re-post that description? How should I accurately describe this setting to my users?

Thanks, that clarifies the tradeoff. When you say Core Image keeps the intermediate tiles around for later, is that reuse expected across subsequent renders of an equivalent rebuilt CIImage graph using the same CIContext, or only while rendering/reusing the same retained CIImage graph object?

Thanks, that clarifies the intended use. So for non-RAW images where I want to use expandToHDR, should I default to loading through CIImage?

Thanks, that clarifies it. For minimally processed scene-referred linear output, should despeckleAmount generally be left at its default sensor-cleanup value, or set to zero?

Thanks, that clarifies the RAW 9 behavior. Could you also clarify the intended API path for non-RAW images? Should non-RAW images generally be loaded through CIImage rather than CIRAWFilter? If so, is there an equivalent to isDraftModeEnabled for CIImage initialization? If CIRAWFilter is also acceptable for non-RAW images, is there a way to get the expandToHDR behavior available through CIImage options?

Unfortunately there is no other workaround that I am aware of. I created a ticket in Feedback Assistant 6 months ago that is still open (FB9561877). Also talked to Apple and they are aware of this issue but haven't solved it yet. Hopefully they will address this issue at some point as I want to be able to support intel machines for a long time!