2 questions: 1 - (as far as I understand “No correction” was the one selected in the starting window (so called “Select a preset”)) so my question is if this folder was opened with PL before?
2 - are your RGB images outputs from PL?
P.S. Could you, please, double check if it’s really No correction applied (not paying attention to what is written in History)?
I’m not understanding this assumption, Svetlana; I did not manually apply a preset - I am depending on my Preferences setting to apply “JCM_RGBpreset” to new RGB images.
Yes - it’s my WIP/“Work-in-Progress” folder - in which I do all my PL processing (a batch of images at a time). Reminder: I’m using sidecar/.dop files and I delete the database each time before I invoke PL.
Yes - - And I think you’re on to something here - as I tested with a JPG image from a different source and it does apply “JCM_RGBpreset” to such images. Aha !! … Is it that PL is smart enough to know that it should not apply corrections to images that it has already processed ?
Yes, it’s definitely “No Correction” that has been applied … Not “JCM_RGBpreset”.
Exactly, PL treats these images differently from the original RGBs and always apply ‘No correction’ to them (no matter what is selected in Preferences) . So the problem is solved ?
On investigation, to avoid this behaviour, I found I could remove the ‘exif:software’ and ‘xmp:creatortool’ tags from the EXIF of the file, since they both, currently, contain “DxO PhotoLab 4.1.3”, which is presumably how PL distinguishes such files.
Nor me (obviously) - but, there’s a minor downside: my “JCM_RGBpreset" sets-up the Crop tool such that it’s all-set-to-go, but the “No Correction” preset does not … and there’s no way to override it.
I have no problem with any of that, Joanna: I do “enhancements” like this for a number of the DxO-provided presets … but, for the Win version (perhaps it’s different for Mac ?) the “5 - No correction” preset does not exist in the Presets folder … That’s what I meant by “there’s no way to override it”.