Start fresh: * remove images from the library * enable "don't use embedded JPEG preview" preference * remove darktable cache while it's not running: rm -Rf ~/.cache/darktable * remove XMP files for images you want presets to be auto-applied on (we assume they weren't developed so far) * re-import the images
Right now you have a mix of different options applied at different time, that's why it's inconsistent. On Tue, 21 Jul 2020 11:11:49 +0100 tony Hamilton <[email protected]> wrote: > Without wishing to be thought ungrateful for the time you have given me, > I do feel compelled to comment (having read the documentation exhaustively): > > 'Ask for update image by open in darkroom': this does not update the > image in my installation of DT unless and until I turn on the monochrome > module. This does not fit the description 'auto apply' does it? In fact > I get exactly the same result if the preset is not set to 'auto apply'. > That means to me that 'auto apply' does not function. > > 'Ask for update image by export': well, this seems like DT asking me to > do 'useless processing' as you describe it - I don't want an exported > file on my hard-disk merely for the purposes of checking the > appropriateness of my editing. I don't have to do this to view the > effects of my changes to exposure settings for example. Coming from a > LR/ACR background I had expected the results to be shown to me in > real-time, to allow immediate feedback to any changes I had made. If DT > has a design point of not doing this, it would be helpful to say so > early on in the documentation. > > 'Ask for update image by telling darkroom not to use JPEG preview': yes, > I have tried this; the results are unpredictable. It seems to work on > some newly imported folders, but not all; it seems to work on no > existing folders. > > " > > Select one image that has the module in its history stack, Ctrl+C, > select the others you want to copy the effect to, press Ctrl+Shift+V, > from the pop-up, select to paste the monochrome module only. > " > > That hardly seems like 'auto-apply', does it? > > " > https://darktable.gitlab.io/doc/en/module_presets.html#module_presets_new > 'you can define a filter used to decide if the preset should be > automatically applied" > > But surely I have already set a sort of filter by electing to enable or > disable the preset to be automatically applied? Why is an additional filter > required? By logical extension, do I not also need a subequent filter which > determines whether or not the initial filter should be applied - and so on ad > infinitum ? > > On 20/07/2020 21:32, KOVÁCS István wrote: > > On Mon, 20 Jul 2020 at 20:29, tony Hamilton <[email protected]> > > wrote: > >> Are you saying that ALL images in a folder are processed > >> according to the preset, but I just can't see the results - until I > >> enter the darkroom? > > I'm saying you should read the manual section I sought out for you. > > Darktable tries to avoid useless processing. Therefore, it will not > > generate the updated image, unless you ask for it. Ways to ask for it: > > - open in darkroom > > - export > > - tell darktable, via the settings, not to use the JPG preview > > embedded in the raw file (which is the normal, cheap behaviour), but > > do the processing straight ahead, on a half-size preview rendering of > > the raw file. > > > >> This makes me feel quite uncomfortable because I > >> start to ask 'are all other preset effects not visible here on the light > >> table for this reason, or are they not visible because they haven't been > >> applied, for some reason? > > Once you check it and accept it, you won't worry about that. > > > >> For existing images, one has to enter the darkroom and turn on > >> the monochrome module for every image, individually. > > Select one image that has the module in its history stack, Ctrl+C, > > select the others you want to copy the effect to, press Ctrl+Shift+V, > > from the pop-up, select to paste the monochrome module only. > > > >> To my mind that seems like a manual operation , not an example of 'auto > >> apply'. Or am I > >> still failing to understand when presets - like my monochrome one - are > >> applied? Where is that 'timing' defined? > > https://darktable.gitlab.io/doc/en/module_presets.html#module_presets_new > > 'you can define a filter used to decide if the preset should be > > automatically applied > >>>>>>> when opening other similar images in darkroom for the first time > >>>>>>> <<<<<' > > This is what I actually see. > > 1. I opened a Nikon NEF file > > 2. In exposure, I applied a large positive exposure adjustment. The > > image turned white. > > 3. Saved that as a preset, to auto-apply to all raw files. > > 4. Opened another unprocessed NEF. It turned white. Thus, the preset > > is applied to any unprocessed file, as stated by the manual. It won't > > be applied for images that I opened in the darkroom previously. > > > > This behaviour is the same as what the docs describe. > > > > Turning on the half-size raw and importing images also auto-applies > > this preset, and all my thumbnails turned white on import. > > > > Please read the manual, and experiment a bit before asking. > > > > Kofa > > ____________________________________________________________________________ > > darktable user mailing list > > to unsubscribe send a mail to [email protected] > > > ____________________________________________________________________________ > darktable user mailing list > to unsubscribe send a mail to [email protected] > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
