Sign in to follow this  
Followers 0
AndreiV

Very strange issue with timestamps

5 posts in this topic

I have a script that basically reads the EXIF date taken from some jpg files and uses it to set the date created and date modified to that date. (I read the exif using exiftool.exe)

Everything works just fine, except for one very strange thing: the hour from the timestamp is always one hour behind. For example, if the EXIF date taken is 2014:06:17 12:00:00, after writing this to date created using FileSetTime() (of course, first a adjusted the string to be as requested by the function) it works fine, the date created is adjusted but, when I look at the file properties in windows explorer, the EXIF tag is 2014:06:17 12:00:00, while the date created is 2014:06:17 11:00:00.

Where is this one hour difference coming from?

Share this post


Link to post
Share on other sites



I did a little more experimenting. After setting the date with FileSetTime() a read back the time with FileGetTime() and wrote the output to a text file. From the script, the date and time are ok:

Processing file P0100013.jpg

Exiftool returned: 20010113120000
New file Created Time : 20010113120000
New file Modified Time: 20010113120000
But in windows explorer this same file has the time modified one hour behind.

Share this post


Link to post
Share on other sites

Found the problem. The files that I was modifying are on a Diskstation NAS. It looks like the NAS doesn't have DST settings. I just changed the time zone on the NAS to GMT +3 and not it is ok.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0