Ralf Brown

That would point to Filmic's `legacy_params` function as the culprit.

@giovariot #17245 added a high contrast theme which likely resolves this issue.

The RGB parade is indicating that the embedded corrections are resulting in an over-correction - the corners are now too bright.... Possibly the code is mis-interpreting the correction information; maybe...

Lensfun is very picky about the naming, so it's the whitespace difference between the ExIF field it checks and the entry in its database causing problems, as you've already noticed.

It's quite likely that nearly all of the speedup you saw comes from a single occurrence of an SSE intrinsic - the `mm_stream_ps` in `copy_pixel_nontemporal` in src/develop/imageop.h. It probably makes...

Good to hear. It occurred to me after my previous response that one other function in that file needs to be updated for safety - nontemporal writes can violate the...

Several of the processing modules can take upwards of 200 bytes **per pixel** in the image, depending on settings. The Surface Blur module with (ironically) _small_ values on the sliders...

@gi-man The "scale" parameter in Lens Correction only magnifies/shrinks (in both dimensions) the image within the same pixel dimensions as the module's input. It's meant to avoid a black border...

I just tried a bunch of images in my folder of PlayRaw pics and still get 5001-5003K on nearly all. A couple of sunset pics had 499xK, and a third...

Well, it does change the sliders (and thus colors) for me, but nearly always to a default value that doesn't necessarily have anythiung to do with the image.