So, I was realy shure I double checked the problem, but it is as Tobias said, darktable handles it as it is. I don't know what lead me to the sugestion it was not.
So sorry for the noise, all is fine so far. Timestamps from exif in darktable matches the one from the camera. Martin Am 15.09.2017 um 11:09 schrieb Tobias Ellinghaus: > Am Mittwoch, 13. September 2017, 21:33:12 CEST schrieb Martin (Lists): >> Hallo > > Hi. > >> I recently stumbled over a minor problem: exif timestamp handling in >> darktable. I usually set my camera to record tiemstamps in local time >> zone including DST. This is to get an idea at which local time the photo >> was shot. UTC is only an option if I can set the timezone as well (which >> I can not or at least I don't know how). > > Yes, it's a pity that EXIF is quite bad in that regard. > >> Darktable seems to use the time set in camera as UTC time and adds two >> hours for central europe in summer. So I am two hours ahead of real >> time. If I shot photos in London (and set camera time) I am one hour >> off. To get the real local time I always have to recalc the displayed time. >> >> If I shot a photo in New York at 8am I want to see a timestamp of 8am >> not a corrected one for germany of 2pm or even worse corrected via UTC >> with additional two hours. >> >> May be an option will be great to use exif timestamp as it is, or as UTC? > > Timestamps should already be displayed as-is. > What operating system are you on? What version of darktable are you using? > And > could you please share a sample file, together with what time you'd expect to > see for it? I think I saw issues like that in the past but can't remember > details. > >> Regards >> Martin > > Tobias > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
