Am 17.03.2013 22:37, schrieb Tobias Ellinghaus: > > darktable stores all the changes to an image in XMP sidecar files. When > exporting an image this very XMP data is also embedded into the exported image > (provided the file format supports it). So every exported image already > contains the settings used to get that image (styles applied during export > might be missing, not sure, never tried that). > > Another feature of darktable is the ability to load random XMP files from > other > images and apply the settings to the selected image. This is done in the > "history stack" module in lighttable using the "load sidecar file" button. > > Since loading of XMP files is done using libexiv2 which can also load XMP data > from images you can "abuse" this button to load the settings used for an > exported image and apply them again. > > TL;DR: > Just load the exported image as a sidecar file in the "history stack" module > and you get the old settings back. >
Good point that can really serve as a disaster recovery. We should have that documented! Ulrich ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
