Hello Johannes,
Thanks for your response.
Don't you think it would make sense to (automatically) couple the
writing of the xmp-file to the *export* of an image?
Or at least have this option? It would be a great help in the simple
workflow where the original images (raw,jpg,both) are loaded into darktable,
some of them are "edited" with darktable, after which new copies of
these "modified" images are exported.
This option sounds much more useful to me than having xmp-files being
generated (on import) for *all* images.
It would help preventing mistakes I made, where I lost original jpgs
because I recreated a jpg just because there was
an associated <raw>.xmp file. The original jpg file (created in the
camera, next to the raw) was of better quality that the one recreated
via the minimal xmp that was generated by default! True, my mistake, but
it would have been prevented if there were no redundant xmp-files
littering around.
The fact that, when xmp files are present, darktable can just recover
from losing the database is a great, great, great feature.
I "loose" the database quite frequently, on purpose. I like the
lightweight, non-intrusive character of darktable very much.
Kind regards,
Bertwim
On 25/05/15 20:45, johannes hanika wrote:
maybe we should remove this option to not write sidecars, it's really
just there so you can shoot yourself in the foot. it was introduced
for read-only (cdrom) file systems.
if you develop your images in dt with a specific version, the sidecar
file should contain all the current defaults, such that a newer
version of dt will make it look the same. there is no such thing as an
unedited raw. you need to apply some processing to get a jpg out of it.
that said, the xmp is just used as a backup, all processing is stored
in db and replicated in xmp so you can move it, share it, and to some
limited extend import to other applications (and get your work back if
you lose the db).
-jo
On Tue, May 26, 2015 at 6:13 AM, Bertwim <b...@xs4all.nl
<mailto:b...@xs4all.nl>> wrote:
Hello,
In the darktable preferences->core options menu, there is the option
"write sidecar files for each image".
When this option is switched on, darktable writes indeed a sidecar
file
*on import* for each image"
I wonder what the use of this option is. It means that sidecar
files are
being generated also for files that have not been edited, and perhaps
never will be edited.
What is worse, if I later decide to run darktable (e.g. in
batchmode) to
generate (=export) new jpgs for the files I have edited,
I have no way to figure out which image actually has been edited.
The workflow I now follow, is the manually press the "write sidecar
files" button for the files I have modified, and export new jpg's.
This,
however, is cumbersome and error prone as well.
To me, the said option seems redundant and even an invitation to make
errors. Wouldn't it be better to change this option to:
"write sidecar files for each image that has been edited".
Looking forward for opinions on this,
Kind Regards,
Bertwim
------------------------------------------------------------------------------
One dashboard for servers and applications across
Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable
Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Darktable-users mailing list
Darktable-users@lists.sourceforge.net
<mailto:Darktable-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/darktable-users
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Darktable-users mailing list
Darktable-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-users
