Some presets are incorrect migrated from 2.4 to 2.6
- I created presets for highpass and lowpass filter, that include blending (uniform; overlay and darken respectively). Up to 2.4.4 if I chose the preset for one of these modules, the blend mode was applied. However in 2.6 and 2.6.1 the preset is applied without the blend.
- the "export selected" module in Lighttable sometimes changes the profile assigned to the exported image. I had ProPhoto (so the conversion to the paper/printer profile is handled by the Turboprint driver) but in 2.6 it was changed to "image settings". On the other hand my preset for jpg export, which specified sRgb profile, worked correctly.
- Another user reported "After installing 2.6.1 today and seeing that the collection module presets were still not working..."
Workaround: recreate or update (for the export preset) the preset with proper values, and afterwards it is applied correctly.
Filing a bug report because this is a real problem (esp if printing on expensive paper); I think this should be tested in the next major upgrade and then corrected, or the users warned.
This is Darktable 2.6.1 from Archlinux 5.0.0-arch1-1-ARCH #1 SMP PREEMPT Mon Mar 4 14:11:43 UTC 2019 x86_64 GNU/Linux.
#1 Updated by Bojidar Bojkov 12 days ago
I can confirm that presets for collection module did not migrate properly 2.4.x to 2.6.x. The presets are visible (but they do not collect the images they are supposed to). Creating a brand new preset works as expected. The old (corrupted) preset and the new (properly working) preset can co exist. It is possible to switch back and forth. The UI displays no changes between the 2 except the name of the preset but the actually collected images are completely different from one another.
DT 2.6.x is installed from third party packages and PPAs OBS - the stable release
#3 Updated by Bojidar Bojkov 11 days ago
Pascal Obry wrote:
I can confirm that presets for collection module did not migrate properly 2.4.x to 2.6.x. The presets are visible (but they do not collect the images they are supposed to).
This is a completely different issue that is fixed in 2.6.1.
My experience is different. I am on 2.6.1 and I still keep the preset from 2.4.x that misbehaves. It used to work well on 2.4.x