I finally got some time to use the new Unleashed N1 in the field. After a day of shooting as I was sorting my pictures I noticed some of them were out of order. Looking at the metadata, some pictures were off by as little as an hour and a half, others by 4 days. In the camera, the UTC time from the GPS is correct; it was the local time that was off. I do not know if this is an issue with the Unleashed, but I have never experienced this before.
—
Nikon D5 C1.21 LD2.017 W3.00
iPhone XS iOS 12.1
Unleashed N1 A1.0 B1.0 C1.1
Timestamp Sometimes Incorrect [solved]
I am traveling, but in the same time zone as home. When reviewing pictures on the camera, the local time is shown at the bottom. Pressing the down arrow to show the latitude and longitude also shows the UTC time. It is the UTC time which is correct, unfortunately Apple Photos apparently only goes by the local time. Today, half my pictures were just under 13 hours off.
Hi
Sorry for the trouble.
until we fix the bug with the wrong GPS time, please make sure that the setting "Use GPS to set camera clock" is off!
The times we have noticed that the timestamp of the Unleashed can be wrong is after it wakes from sleep mode (ie after you haven't been using your camera for a longer time!), and The Unleashed was not connected to the App.
If the above setting was on, the camera clock was set when you turned on the camera, using this wrong timestamp, which might explain your problems.
We hope to able to roll out the firmware update with this (and many other) fix(es) soon!
Sorry for the trouble.
until we fix the bug with the wrong GPS time, please make sure that the setting "Use GPS to set camera clock" is off!
The times we have noticed that the timestamp of the Unleashed can be wrong is after it wakes from sleep mode (ie after you haven't been using your camera for a longer time!), and The Unleashed was not connected to the App.
If the above setting was on, the camera clock was set when you turned on the camera, using this wrong timestamp, which might explain your problems.
We hope to able to roll out the firmware update with this (and many other) fix(es) soon!
Founder & CEO of Foolography, Hardware & Firmware developer.
Having the same issue. Here are the details of how I experienced the issue in case it's helpful to fix:
Using the N2 with my D7200, spent the morning shooting approximately 450 images. The first 24 all had date/time stamps (except GPS Time) with values 22:02 (22 minutes, 2 seconds) in the future (ahead of GPS Time). GPS Time looks correct for those 24 images. Those 24 images were taken over a period of 3:45 (3 minutes, 45 seconds). All images taken for the rest of the day had correct time values.
If I understand, setting the "Set clock from satellite" option to OFF will avoid this issue until a FW update is available?
My FW, A1.0 B1.0 C1.1. Any ETA on a FW update?
Using the N2 with my D7200, spent the morning shooting approximately 450 images. The first 24 all had date/time stamps (except GPS Time) with values 22:02 (22 minutes, 2 seconds) in the future (ahead of GPS Time). GPS Time looks correct for those 24 images. Those 24 images were taken over a period of 3:45 (3 minutes, 45 seconds). All images taken for the rest of the day had correct time values.
If I understand, setting the "Set clock from satellite" option to OFF will avoid this issue until a FW update is available?
My FW, A1.0 B1.0 C1.1. Any ETA on a FW update?
MarkF, Nikon D7200, D90 / N2 A1.0 B1.0 C1.1
I am having a similar problem in that the date seems to be change by a couple of days. It has happened twice, changing it to two days in the future..
Again I hope it will be fixed in the next firmware update (any time estimate?) and will set the appropriate flag in camera to off. (D7200)
Again I hope it will be fixed in the next firmware update (any time estimate?) and will set the appropriate flag in camera to off. (D7200)
-----------------------------
Regards MIke
Regards MIke
I just heard that the update will be pushed back to Monday so that in case that a bug slips through the developers and starts causing crashes, it can be fixed immediately and users don't have to wait all weekend being unable to use the app.
Andy
Firmware developer at Foolography
Firmware developer at Foolography