On Sun, Aug 16, 2015 at 7:46 AM, Bertwim <b...@xs4all.nl> wrote: > But my point is that, when DT is also "touching" pictures that are not > supposed to be touched (yes, I know, not really touching, but via e.g. > the xmp indicating that some processing has been done) it becomes > cumbersome, if not impossible to tell the difference between images that > have been edited alright and images that were supposed to be unchanged. > There will be xmp file for both.
The fact that a xmp exists only means that the image has been imported, nothing more. The fact that a xmp exists *does not* mean that settings have been changed for the image or that the image has ever been exported. > If, e.g. in an automated workflow, new > jpfs are to be regenerated (renaming to the original names, not with > extension "_01" etc.) then this will also be done for the pristine images. Overwriting out-of-camera .jpg files with raw imports seems like a very bad idea. > This is why I think an option like "don't do anything (anymore)" for an > image would be a very useful feature. Actually, not only for pristine > images, but also for images that are made 'final', i.e. no further > (accidental) edition is possible, such an option would be helpful You seem to want to have an option for "this image can not be exported" because your normal workflow is to take the raw file and overwrite the out of camera jpg. This doesn't make much sense for the darktable workflow. Darktable is non-destructive and you're trying to shoehorn a destructive workflow into it. If you want to keep shooting raw+jpeg just import all of them and have a separate export dir (as is the default) so overwriting is never possible. Then you can always go back to the original jpg if you'd like. The raw+jpeg workflow could probably be much better in darktable but I suspect no one has ever worked extensively on it because anyone that starts working with raws extensively ends up going to just raw as that's the only sane choice. Shooting raw+jpg means that you either ignore the jpg completely (and then why have it?) or sometimes use the jpg and sometimes the raw so your output is inconsistent. There's really no good reason to shoot raw+jpg, if you just want a reference image for processing ideas when developing the raw the embedded thumbnail in modern cameras is large enough. Cheers, Pedro ------------------------------------------------------------------------------ _______________________________________________ Darktable-users mailing list Darktable-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-users
