Re: [darktable-user] Can timestamp information in xmp files be altered with external script?
Test message. Please ignore. On 05/03/2021 13:09, Remco Viëtor wrote: On vendredi 5 mars 2021 10:30:11 CET Jean-Pierre Verrue wrote: Hi, The timestamps were created precisely to record all darktable's input/output operations. It is therefore normal that the export timestamp is updated with each export. Resetting it to -1 would cause you to irretrievably lose the information. Moreover, as Patrick says in his previous answer, this modification of the xmp file should be saved in the DB, otherwise it will be overwritten during a later export operation. The fact that a checksum calculation is different after an export is quite normal since it reflects the fact that "something happened" to this file. The content of this file is entirely governed by darktable and other photo software. It is therefore unwise to rely on it for other uses. Also, if you use a checksum on the whole file for version control, you indicate that you want to see all changes to the file. If you only want to follow part of the information, you'd have to limit your checksum for version control to that part of the info... Remco darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Can timestamp information in xmp files be altered with external script?
Hi, The timestamps were created precisely to record all darktable's input/output operations. It is therefore normal that the export timestamp is updated with each export. Resetting it to -1 would cause you to irretrievably lose the information. Moreover, as Patrick says in his previous answer, this modification of the xmp file should be saved in the DB, otherwise it will be overwritten during a later export operation. The fact that a checksum calculation is different after an export is quite normal since it reflects the fact that "something happened" to this file. The content of this file is entirely governed by darktable and other photo software. It is therefore unwise to rely on it for other uses. JPV Le 04/03/2021 à 20:29, Patrick Shanahan a écrit : * Bengt [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 .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. darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Can timestamp information in xmp files be altered with external script?
On vendredi 5 mars 2021 10:30:11 CET Jean-Pierre Verrue wrote: > Hi, > > The timestamps were created precisely to record all darktable's input/output > operations. It is therefore normal that the export timestamp is updated > with each export. > > Resetting it to -1 would cause you to irretrievably lose the information. > Moreover, as Patrick says in his previous answer, this modification of the > xmp file should be saved in the DB, otherwise it will be overwritten during > a later export operation. > > The fact that a checksum calculation is different after an export is quite > normal since it reflects the fact that "something happened" to this file. > The content of this file is entirely governed by darktable and other photo > software. It is therefore unwise to rely on it for other uses. Also, if you use a checksum on the whole file for version control, you indicate that you want to see all changes to the file. If you only want to follow part of the information, you'd have to limit your checksum for version control to that part of the info... Remco darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Can timestamp information in xmp files be altered with external script?
* Bengt [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 .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.orgopenSUSE Community Memberfacebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
[darktable-user] Can timestamp information in xmp files be altered with external script?
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? darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
