Re: [darktable-dev] Upgrade from 3.0.2 to 3.2.1 destroys order of modules

2020-08-12 Thread Philippe Weyland
Hi Andreas, If I can give my cent... 1. keep your 3.0.2 database backup safe 2. do not use „load sidecar file …“ which is buggy 3. ... try the different configuration options after replaying the migration ... but here I cannot help much. Using "legacy module order" you should be able to keep

Re: [darktable-dev] Upgrade from 3.0.2 to 3.2.1 destroys order of modules

2020-08-12 Thread Pascal Obry
Le jeudi 13 août 2020 à 00:21 +0200, Andreas Herold a écrit : > Screenshot 3.0.2: > https://www.dropbox.com/sh/orbifgwd23sgzw8/AAC3SjlwjRe-LvLhX7U5UZBaa?dl=0=Bildschirmfoto+2020-08-12+um+23.02.54+Kopie.jpg > Screenshot 3.2.1 custom: >

Re: [darktable-dev] Upgrade from 3.0.2 to 3.2.1 destroys order of modules

2020-08-12 Thread Pascal Obry
Le mercredi 12 août 2020 à 22:03 +0200, Andreas Herold a écrit : > Thank you. I didn't notice that before. Currently it's showing > "custom" (which is the wrong order) and I can change it to "legacy", > which results in another wrong order. "custom" is not the wrong order (expect if there is a

Re: [darktable-dev] Upgrade from 3.0.2 to 3.2.1 destroys order of modules

2020-08-12 Thread Pascal Obry
Le mercredi 12 août 2020 à 21:32 +0200, KOVÁCS István a écrit : > I thought that setting changes which modules get auto-applied (base > curve or filmic+exposure or none). There's a 'module order' setting > in > the darkroom (below the modules, above 'more modules') that allows > you > to switch

Re: [darktable-dev] Upgrade from 3.0.2 to 3.2.1 destroys order of modules

2020-08-12 Thread Andreas Herold
Hi, here is what I did in the meantime: * 3.2.1.: Changed Preferences/processing/auto apply pixel workflow to none (without success) * switched back to 3.0.2. Did not found any option to configure processing order of modules * 3.0.2: created screenshot * 3.2.1: upgraded DB * 3.2.1: checked

Re: [darktable-dev] Upgrade from 3.0.2 to 3.2.1 destroys order of modules

2020-08-12 Thread Andreas Herold
> Am 12.08.2020 um 21:09 schrieb Mica Semrick : > > Hi, > > You can still use the old, ordered processing pipeline with base curve and > all that. You just need to select it from the modules menu. Thank you. I didn't notice that before. Currently it's showing "custom" (which is the wrong

Re: [darktable-dev] Upgrade from 3.0.2 to 3.2.1 destroys order of modules

2020-08-12 Thread Andreas Herold
> Am 12.08.2020 um 21:32 schrieb KOVÁCS István : > > On Wed, 12 Aug 2020 at 21:09, Richard Hobday wrote: >> You might benefit from changing the settings in: >> Preferences/processing/auto apply pixel workflow defaults >> this should allow you to the revert to the legacy pipe order. > > I

Re: [darktable-dev] Upgrade from 3.0.2 to 3.2.1 destroys order of modules

2020-08-12 Thread Andreas Herold
Hi Richard, thank you. I tried It, but applied afterwards the order has not changed back. I have enabled writing of xmp files and I’m seeing that the timestamps of xmp files of images I had not opened yet, are still before the upgrade to 3.2.1. Most xmp files should still contain the right

Re: [darktable-dev] Upgrade from 3.0.2 to 3.2.1 destroys order of modules

2020-08-12 Thread KOVÁCS István
On Wed, 12 Aug 2020 at 21:09, Richard Hobday wrote: > You might benefit from changing the settings in: > Preferences/processing/auto apply pixel workflow defaults > this should allow you to the revert to the legacy pipe order. I thought that setting changes which modules get auto-applied (base

Re: [darktable-dev] Upgrade from 3.0.2 to 3.2.1 destroys order of modules

2020-08-12 Thread Mica Semrick
Hi, You can still use the old, ordered processing pipeline with base curve and all that. You just need to select it from the modules menu. Your workflow sounds very nonstandard though, I'd think most start with global adjustments and work toward local adjustments at the end of the edit. - m

Re: [darktable-dev] Upgrade from 3.0.2 to 3.2.1 destroys order of modules

2020-08-12 Thread Richard Hobday
You might benefit from changing the settings in: Preferences/processing/auto apply pixel workflow defaults this should allow you to the revert to the legacy pipe order. R. On 12/08/2020 19:15, Andreas Herold wrote: Hi, some feedback from a User who made currently the upgrade from 3.0.2 to

[darktable-dev] Upgrade from 3.0.2 to 3.2.1 destroys order of modules

2020-08-12 Thread Andreas Herold
Hi, some feedback from a User who made currently the upgrade from 3.0.2 to 3.2.1. In my workflow I’m using very often modules, which are using parametric masks. I’m applying moduIes with parametric masks very early in processing. I do this, to have stable masks, that are not depend on other

[darktable-dev] darktable 3.2.1. crop function update. THANK YOU

2020-08-12 Thread Vincent Agudelo
Hello Developers, I hope this gets through. but THANK YOU for the update on the crop module. now I can freely move the crop area without having the application process all modules. i know it's a small thing but sometimes the crop box hangs because of all the modules being read. thank you very

Re: [darktable-dev] Taking reference photos for adding lens correction profiles

2020-08-12 Thread Andreas Schneider
On Tuesday, 11 August 2020 20:16:26 CEST Germano Massullo wrote: > I have a question concerning shooting reference photos in order to add > lens correction profiles for various lenses. > > I would like to use these buildings > https://goo.gl/maps/fX6om53ENGSnN9Fw8 as reference. > > When you