Hello IMatch,
i just noticed that the Renamer adds 2 hours to the timestamp. I never had that problem before.
I thought maybe it had something to do with winter and summer time, but i don't see the relation.
See print screen in attachment. Picture was taken at 15h, the renamer puts 17h. Why ? What can i do to avoid this ?
Thanks
Peter
What is your local time-zone?
Brussel UTC + 1h, see print screen in attachment.
So you are at +1 + summer time? and the file claims to be at UTC, so +2 hours?
I'm not a specialist, i looked it up in Wikipedia :
Brussel = UTC +60 minutes during Winter Time and UTC +120 minutes during Summer Time.
But that's not the issue. I took the picture at 15h. The properties recorded 15h. So timerecording is OK.
The issue is why the renamer puts 17h.
Thanks,
Peter
I have no idea.
Upload the sample image you have used and the precise renamer steps and sequence you have used.
Keep in mind that date and time attributes and variables are always emitted in your local time-zone.
The image is 6 MByte, i cannot send it, and zipped, it remains as large.
In attachment the result of the Metadata Analyst app. I had to zip it, because json files are not allowed as attachment.
I don't know how to send the renamer sequence, so i took a print screen. also in attachment.
Thanks for helping me out.
Peter
is there news ?
Thanks,
Peter
I cannot reproduce this.
I tried with the same prefs in the renamer with a new file from the cam.
I have not idea. It seems, that the renamer adds simply 2 hours, from where they are, I have no idea.
I also can not reproduce this. Renamer works correctly for me. In case that it helps: These are my time-zone related Metadata 2 settings. They should be the Default settings - I do not remember changing them.
Please send a sample image which exhibits this behavior to support email address (https://www.photools.com/support/)
Please include a link back to this thread (I get many emails per day).
Also include a screen shot of the Metadata and Metadata 2 settings on your system.
Quote from: thrinn on June 23, 2021, 09:23:05 AM
I also can not reproduce this. Renamer works correctly for me. In case that it helps: These are my time-zone related Metadata 2 settings. They should be the Default settings - I do not remember changing them.
thrinn,
that is a good idea, I have not thought to look there. 8)
Hello,
i have sent a e-mail with title "Tools / Renamer" to 'EMAIL REMOVED BY ADMIN'.
It contains the picture and the print screens as requested.
Thanks for helping me.
Regards,
Peter
ADMIN: NEVER POST EMAIL ADDRESSES IN THIS COMMUNITY. Google and SPAM-Bots are constantly scanning it to harvest email addresses.
I especially thank you for not posting my support email address. I get hundreds of SPAM emails per day already :D
Hi,
Today I had a free slot and looked at the file you have sent.
The file shows the following timestamps in the Metadata Panel:
Create Date 2021:06:21 15:17:38.00
Date Subject Created 2021:06:21 15:17:38.00
When I recreate your rename steps (the section I can see, something is missing from the screen shot), I get this result, which is correct:
(https://www.photools.com/community/index.php?action=dlattach;topic=11453.0;attach=27356;image)
Do you use any other steps in the Renamer? File already exists? Anything you did differently than I did?
Hello Mario,
first of all, sorry for mentioning the e-mail address.
I have attached the full list of steps to this post, see timestamp v03 in attachment.
I noticed something in the metadata analysis : "IMatch File DateTime: 2021-06-21T17:17:38" Why 17:17 ??? It should be 15:17, no ??? See extract below and attachment.
Finally, i still have the same behaviour with all pictures that i take : plus 2 hours.
See printscreen timestamp v06 : picture is taken today at 14h, IMatch File DateTime states 16h.
I simplified the renamer sequence to 1 step : the hour. It is 16h. See print screen timestamp v07.
I understand that you cannot help as long as you cannot reproduce the error. The IMatch File DateTime is maybe the cause ?
{
"type": "i",
"text": "XMP Date Subject Created: 2021:06:21 15:17:38.00+00:00",
"helpId": null
},
{
"type": "i",
"text": "IMatch File DateTime: 2021-06-21T17:17:38",
"helpId": null
},
The file you have provided has two usable timestamps, and IMatch uses them either "as-is" (optionally applying the EXIF time-zone offset if it exists) or it uses the local time-zone on your machine.
Check your settings for Edit > Preferences > Metadata 2: Apply time-zone. This is off by default, but when you enable it and you live in GMT+02:00, the EXIF timestamp will me shifted to match your local time-zone.
This is how IMatch produces the global File.DateTime used everywhere. It has no time-zone and is always considered to be in local time-zone.
See: How IMatch uses Date and Time Information (https://www.photools.com/help/imatch/#tech_exifdate.htm) for details.
I saw in a screen shot that you have hard-coded the EXIF and IPTc timezone to be +00:00 (default is empty). So maybe you also have enabled the option to apply the local time-zone?
If you change this setting, you need to select and Shift+Ctrl+F5 > Reload Metadata affected files to update the database with timestamps formed using the new settings.
Mario,
hoera, it seems you solved the problem.
When i change the EXIF and IPTc timezone from +00:00 to empty, and i apply Shift+Ctrl+F5 > Reload Metadata, both the "IMatch File DateTime" in the Metadata Analyst app and the Tools / Renamer work correctly.
i can even simply reproduce the error : when i switch back to +00:00, the error is again there (twice).
So OK, problem solved. Maybe mention somewhere that +00:00 does not behave like empty ?
Thanks,
Peter