Then you may file a feature request at https://github.com/darktable-org/darktable/issues/new?assignees=&labels=&template=feature_request.md&title= and be patient until someone implements it ...
> Am 20.02.2021 um 09:23 schrieb Bertwim <b...@xs4all.nl>: > > Hi Martin, > > Sure, but that is not what I am looking for. I don't want unnecessary being > being generated. > > Kind Regards, > Bertwim > > On 2/20/21 7:31 AM, Martin Straeten wrote: >> You can use the collection filters just to display edited images using >> darktable related tagging >> >> ___________________________________________________________________________ >> darktable developer mailing list >> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org >> >> >> >> Then ctrl+a and save xmp file >> >>> Am 19.02.2021 um 22:46 schrieb Bertwim <b...@xs4all.nl>: >>> >>> 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. >>> >>> Kind Regards, >>> Bertwim >>> >>> >>> >>> ___________________________________________________________________________ >>> darktable developer mailing list >>> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org >>> > > > ___________________________________________________________________________ > darktable developer mailing list to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
