Hi Patrick, thanks for responding.
Sure, this is what I do: only importing the raw files.
But I don't want .nef.xmp xmp-files for images that I have not
touched. They are redundant, serve no purpose, only wrongly suggesting
that I have edited images.
Regards,
Bertwim
On 2/19/21 10:51 PM, Patrick Shanahan wrote:
* Bertwim <b...@xs4all.nl> [02-19-21 16:48]:
Hi,
My camera creates an image both in raw format (Nikon, nef) and a jpg. When
the camera-produced jpg is good enough, I just want to keep it, leaving it
untouched by DT. No xmp-file needed or even desired. For the others
pictures, I use DT to process the the raw image and export a new jpg,
overwriting the original camera-produced jpg. For those pictures I want the
xmp file.
In other words, I would like to have an xmp file *only* for those images
that I have actually edited. No no xmp-files for images that I have not
touched/edited.
I don''t think DT is currently providing this in a convenient way. It can
write xmp files automatically for *all* images, but that is too much.
It is possible to achieve this selective xmp-export manually by first
selecting in lightroom the 'untouched' images, inverting this selection and
then choose "write sidecar files' in the history stack menu. This however,
is cumbersome, tedious and error prone. I am looking for a more robust and
automated way to achieve the same.
It would make sense I think to write an xmp file together with the export,
So I was thinking if I could add this option to the code.
I would value some comments or feedback if this option would be worthwhile
to pursue.
if you would only import raw images, dt would not create xmp files for the
jpg's. surely when you need to work a file, you work the raw.
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
