I believe this is the right approach: darktable will never change the raw file but you might want to change the date taken exif information. So you might spend huge amount of work with darktable to correct the exif data and expect this to have a permanent effect. Now imagine you open the raw data with another program, then your tuning of date taken exif information does not show up. So it looks like you've lost the work. You will realize that you might have intended to change the exif in the image, not the sidecar information.
Peter Harde <peter.harde.pri...@gmail.com> schrieb am Sa., 13. Nov. 2021, 16:07: > Hi Philippe, > > yes, but I never had problems at import until now. The images of interest > here are reproductions of negatives or slides, reproduced with a Sony DSLR. > Of course they have "DateTimeOriginal" of the reproduction date/time > (2019-2021). Then : > > - batch processing with exiftool, changing "DateTimeOriginal" of all > images originally taken at the same day to YYYY-MM-DD 12:00:00 of this day > - importing images into darktable (all images have "DateTimeOriginal" > smaller linux epoch 0 at import) > - selecting / processing / sorting / geotagging (if possible) > - fine tuning time with geotagging module (if reasonable) > > exiftool handles dates before linux epoch 0 without problems and for the > import module of dt I observe the same. > > Best regards > > Peter > Am 13.11.21 um 12:23 schrieb Philippe Weyland: > > Hi Peter, > Thanks for testing. > In the import process, exif time reading may suffer some limitation due to > epoch 0 as well. Do have your source images such old datetimes ? > Thanks > Philippe > > > ___________________________________________________________________________ > darktable developer mailing list to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
