Le mardi 26 mai 2015 à 18:29 +0200, Bertwim a écrit : > Don't you think it would make sense to (automatically) couple the > writing of the xmp-file to the *export* of an image?
No, because in this case you do not have the safety of the .xmp in case your DB is corrupt. The DB is fine for fast access but if it got corrupt you *loose* all your edit for *all* your pictures. That's just not an option to me. > 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. As already stated you have tag for this. > The fact that, when xmp files are present, darktable can just recover > from losing the database is a great, great, great feature. Right :) -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ------------------------------------------------------------------------------ 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
