Wrong capture time on import rename
When I import my Fuji X-T1 photos with COP7 and autorename them with the option label (Image time (HH mm)
it consequently renames them wrong; with a -8 hours time difference!!! ☹️
The strange thing is that it shows the correct time in the "naming sample", but on actually import it goes wrong.
I use the labels: image year (yyyy) - image month (MM) - Image day of month - Image Time (HH mm) - 3 digit counter
For example when shot at 13.01 on 15 august it renames it to 2014-08-15_05-01-001 and not 2014-08-15_13-01-001
Bug? or something to do with timezones .....
Oh btw this is on a Mac Book
it consequently renames them wrong; with a -8 hours time difference!!! ☹️
The strange thing is that it shows the correct time in the "naming sample", but on actually import it goes wrong.
I use the labels: image year (yyyy) - image month (MM) - Image day of month - Image Time (HH mm) - 3 digit counter
For example when shot at 13.01 on 15 august it renames it to 2014-08-15_05-01-001 and not 2014-08-15_13-01-001
Bug? or something to do with timezones .....
Oh btw this is on a Mac Book
0
-
I believe I have seen an error (bug) on this feature. I suggest you create a support case to have it checked. 0 -
In reply to my own question:
I found that if I batch rename the wrongly named files after the import, using the same labels, the correct capture time is used this time
.... 🙄
Added:
We cross posted Paul.
Will raise a support. Thanks for your reply. Bedankt0 -
[quote="Arjan5" wrote:
In reply to my own question:
I found that if I batch rename the wrongly named files after the import, using the same labels, the correct capture time is used this time
.... 🙄
Interesting. Support case seems to be the best course of action:
http://www.phaseone.com/en/SupportMain.aspx0 -
Can you check that your computer and camera clocks match ? 0 -
We also need to know things like Time Zone, Date Format, Region Setting and Clock format.
There are thousands of combinations so sometimes one lucky user in a remote location or with a abnormal setting (Located in the US but region coded for Albania) wins the lottery in these bugs.0
Post is closed for comments.
Comments
6 comments