Dear Bernhard,
This is just semantics. I'm afraid you don't get what I am after.
It seems hard to convey the message that I need a workflow such that
when DT is not used to do any "edits", I don't want to see any redundant
xmp files. If I know that any existing xmp-file can be used to
regenerate the desired jpg file (or png, tiff, etc...) this is a great
help for automated workflows. It means I can blindly overwrite the jpg.
Conversely, If part of the xmp-files are in fact dummies (because I did
not "edit" the image, never exported a new jpg (or png, tiff etc...)),
the triplet of files (raw+ original jpg+xmp) do not form a consistent
triplet of files. In the latter situation I can *not* just regenerate
and overwrite the jpg file, because it would overwrite the original jpg
file, the one that I considered valuable.
On 2/20/21 12:59 PM, Bernhard wrote:
Bertwim schrieb am 20.02.21 um 12:12:
Looking at export makes more sense. I consider the exported files
(say, the jpgs), as the final product of DT. After all, It is the jpg
that I show, send to others, publish on a webpage etc. Pretty sure
this holds for many people. That is why I want to create the XMP only
when I export an image. These are the images that matter to me.
I think there is some misunderstanding of what "final product" means:
We speak of non-destructive editing.
see this paper at
web.archive.org/web/20140912051214/http://www.adobe.com/digitalimag/pdfs/non_destructive_imaging.pdf
As such the "final product" always is the edited image *within
darktable* - that means the input image (be it RAW, JPG, TIFF,
whatever) accompanied by the corresponding .xmp.
If the input file is .JPG then overwriting this image by an exported
.JPG is plainfully wrong - as the whole purpose of non-destructing
imaging is defeated.
Also the exported image is *always* a temporary product - as this has
to be adjusted to the purpose of the export: print, web, social media,
whatever - at least by size, but most likely also by sharpening and
other parameters.
So I don't see any purpose for what you want to do.
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
