* Bengt <[email protected]> [03-04-21 13:02]: > > The xmp file contains Epoch time information. E. g: > darktable:import_timestamp="1614867405" > darktable:change_timestamp="-1" > darktable:export_timestamp=""1614868405 > darktable:print_timestamp="-1" > > The time information is altered whenever a picture is exported. I. e. not > modified, only exported to jpg file for presentation. > > In case of backing up files into archives, this results in different xml > file contents whenever a picture has been exported and in errors when > archive versions are compared/checked (md5sum-ing). > > Questions: > 1: Is there any way in darktable to avoid timestamp registration when only > exporting or printing? > 2: Is it "dangerous" to force export_- and print_timestamps to "-1" by > writing an external script that modifies all xml files before archiving (and > export/print time information is unimportant for the user)? > 3: Any other suggestions?
the <file>.xmp is a duplicate of what the library.db contains and, if modified externally (not by dt), affected images need to be re-imported or their xmp files re-read to update library.db. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
