* tony Hamilton <[email protected]> [07-21-20 22:31]: > I had hoped that the advice given 'below' might have made my use of a > preset's 'auto apply' property deliver predictable results. It does, but > only in the sense that in my DT installation I can predict that for newly > imported folders, never previously imported into DT, the 'auto apply' preset > I have defined for monochrome is NEVER applied, automatically. This is in > conflict with the image flags shown in the Image Information panel - which > says that matching auto apply presets have been applied. I use an exported > file to test this. This action is reproducible. > > Similarly, previously imported images, now removed, with the associated > '.raw.xmp' file deleted and the DT cache cleared do NOT have the preset > applied when re-imported, irrespective of the 'use half size raw' option in > preferences. I use an exported file to test this. This action is > reproducible. > > Previously imported images, now removed, but with the associated '.raw.xmp' > file not deleted but the DT cache cleared sometimes have the preset applied > when re-imported, irrespective of the 'use half size raw' option in > preferences. I use an exported file to test this. This action is > reproducible only in the sense that there are always some images which have > not been converted to monochrome, but not always the same images. > > If, in addition, the option 'only show this preset for matching images' is > enabled in the preset definition, then the preset is never applied > irrespective of the presence or absence of an old 'raw.xmp' file. Further > more the wording of this option is misleading. As stated, because the preset > never appears in the list of presets for the monochrome module when this > option is enabled, it implies that DT is unable to find any image in any > folder I ask it to import that match the following requirements: > > - any model and make of camera, with any lens > - ISO between 0 and 32000 > - shutter speed between 32" and 1/8000 sec > - aperture between f/0 and f/128 > - Focal length between 0 and 1000 mm. > > Do I believe I have no images that fall within these parameters? I do not. I > am supported by LightRoom and iMatch.They tell me I do not have a single > image which falls outside ANY and ALL of these requirements. > > The wording 'only show ...' implies 'don't do anything else, other than > show'; the action of 'only' is applied to 'show'; it should be applied > (only!) to 'matching images'. Thus the wording should be 'show this preset > for matching images only', which implies do other things (like auto apply > it!) as well as show the preset. > > So now I start to ask myself is it that there is some secret incantation, > known only to the DT developers and not revealed in any source document I > have studied over the last 4 days, which will cause this preset to meet the > description of 'auto apply' ? Or is there a function defect here? Or is it > just me - in which case what am I doing wrong? Or should I be feeling more > nervous than I already am, as a result of my inability to understand > 'import', in my use of DT? > > On 21/07/2020 11:27, parafin wrote: > > 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] > > > ____________________________________________________________________________ > darktable user mailing list > to unsubscribe send a mail to [email protected]
I would suggest opening an issue at https://github.com/darktable-org/darktable/issues/ and providiing all the called for information and any concrete steps to observe the problem. This will make the developers aware and provide means to track progress on the issue. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
