Darktable speed

[houz]

@ggbutcher

don’t transform the floating point native image for display, wait until it’s been converted to the 8-bit/channel wxImage. Further, if it has to be cropped for a high display magnification, wait for that operation and transform the smaller image.

For the thumbnails we are talking about, that’s what is already done in darktable.

@ggbutcher

I also put in a property called display.cms.transform if =set do the display transform when the display image is set by the processing pipeline, if =render do the display transform at each display change, e.g. pan or zoom. Jury is still out on the usefulness of this setting.

Those thumbnails are coming from an image cache and are not fetched from the processing pipeline directly. They might also come from the disk cache. So in order to show the right colors even when changing monitors we keep the thumbnails in either sRGB or AdobeRGB and transform them whenever they are shown. Of course, we could transform them to the display profile when loading the file, but then we would have to invalidate the whole cache whenever the display profile changes.

@ggbutcher

Finally, in my colorspace tool instead of cmsTransform-ing the whole image I let the OpenMP break it into chunks and send them to the cores.

darktable already does that.