Export module scaling options and full-size caching
When using image scaling in export module, it could allow one to choose the method for scaling. So instead of the current method, applying filters to scaled images, which is fast but unreliable, one could have a choice to pick processing at full size and scale down after processing using a selectable method (e.g. Sinc/Cubic/Linear algorithms).
This would also help to work around problems like described in #8547 .
A checkbutton for "use full-size cache", causing the export module to cache the results in a lossless format, allowing the export module to run several times without re-processing the whole image, could speed up such operations. E.g. exporting at full size and after that creating a web gallery from the same images would receive a huge performance boost.
Therefor the cache manager needs to reliably lookup cached full-size images, thus it would be reasonable to incorporate cryptographic hashes of both the sidecar file and source image file.
Also means for configuration are required. At least the cache path should be configurable (e.g. to use cheap storage or special location) and a configurable rule how long cached images may live in the cache. Also a "clear cache now" button whould be nice, as well as a "force re-processing" checkbox in the export module.
#1 Updated by Tobias Ellinghaus about 6 years ago
- % Done changed from 0 to 20
- Target version changed from --- to Future
- Status changed from New to Triaged
- Category set to General
Normally we don't like tickets with several issues, but since most of this is already fixed and only the caching of exported images to speed up future exports is left I'm leaving this open.
Instead of caching the real output it might be possible to use the new mipmap cache for this. At least thumbnails for web galleries and similar things could be taken from the cache instead of running the whole pipe again.