On Thu, Aug 13, 2015 at 11:38 PM, Jan Kundrát <j...@kde.org> wrote: > On Sunday, 2 August 2015 07:13:37 CEST, junkyardspar...@yepmail.net wrote: >> Did you try just using the time offset feature in the geotagging module? > > Thanks, that did the 99% of the job done -- my SQL DB now contains > timestamps adjusted towards reality. Here's how I did it: > > 1) calculate the offsets, > 2) select all images from camera A, > 3) enter the determined offset into the geotagging module and press the > "apply time offset" button (shown with a tick mark in the GUI) > 4) repeat for other cameras > > This is with the git version and with the map mode compiled in (in case > that matters). > > However, these offsets aren't exported to the .XMP files, so if I lose my > SQL DB for some reason, I cannot just recover from the standalone XMP files > (and a backup of presets, and...). I think that storing the date also to > the XMP sidecar (and loading these during import) makes sense, doesn't it? http://redmine.darktable.org/issues/10569#note-5
> With kind regards, > Jan Roman. > > -- > Trojitá, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/ > > ------------------------------------------------------------------------------ > _______________________________________________ > Darktable-users mailing list > Darktable-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/darktable-users ------------------------------------------------------------------------------ _______________________________________________ Darktable-users mailing list Darktable-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-users
