Hi,
while looking through my vacation images I noted the next Unleashed bug (again Nikon D750, latest app and firmware versions).
I had two cameras during vacation, whose times I synchronized manually at home. I changed "Uhr per Satelliten stellen" (modify time by satellite date) explicitly to "off", so the Unleashed won't change anything. Now I noted that the Unleashed still changed the camera time - no idea why.
Expected behaviour: The Unleashed should respect the camera setting.
Now I am in the totally weird situation that I have no idea how to synchronize those camera images, as the vacation spanned multiple time zones. Could you please fix this?
Matthias
Unleashed updates the camera time even if the respective setting is set to off [probably camera bug]
Hi,
I'm sorry for your trouble, and totally understand your dilemma...
however, that's actually not possible. The Unleashed CANNOT set the camera clock. The Unleashed only provides the Camera with GPS data including a (UTC) timestamp.
If the setting "Uhr per Satelliten stellen" or "Use GPS to set camera clock" is on, then it will use whatever data is being sent to the camera the first time after turning it on.
The Unleashed keeps incrementing the time and date even if it hasn't received "fresh" GPS data in a while, so even with a long GPS Interval, the timestamp we send to the camera should be very precise at all times.
So if the set camera clock setting is turned on, the Unleashed would only ever provide a correct timestamp.
If that setting is off, the camera clock should not change.
Now I'm not saying there is absolutely no chance for a wrong time to ever be sent to the camera - we have had to fix a bug (a long time ago) where exactly that happened. We can only work with the data being sent from the phone. So if you manage to set the phone's clock wrong, that's the best chance to get the wrong time to the Unleashed (and in turn to the camera).
But again, the camera only sets it's own clock and uses that data, the Unleashed does not do that.
What did the time get set to, if I may ask? Off by minutes, hours, days, years?
I'm sorry for your trouble, and totally understand your dilemma...
however, that's actually not possible. The Unleashed CANNOT set the camera clock. The Unleashed only provides the Camera with GPS data including a (UTC) timestamp.
If the setting "Uhr per Satelliten stellen" or "Use GPS to set camera clock" is on, then it will use whatever data is being sent to the camera the first time after turning it on.
The Unleashed keeps incrementing the time and date even if it hasn't received "fresh" GPS data in a while, so even with a long GPS Interval, the timestamp we send to the camera should be very precise at all times.
So if the set camera clock setting is turned on, the Unleashed would only ever provide a correct timestamp.
If that setting is off, the camera clock should not change.
Now I'm not saying there is absolutely no chance for a wrong time to ever be sent to the camera - we have had to fix a bug (a long time ago) where exactly that happened. We can only work with the data being sent from the phone. So if you manage to set the phone's clock wrong, that's the best chance to get the wrong time to the Unleashed (and in turn to the camera).
But again, the camera only sets it's own clock and uses that data, the Unleashed does not do that.
What did the time get set to, if I may ask? Off by minutes, hours, days, years?
Founder & CEO of Foolography, Hardware & Firmware developer.
Hi Oliver,
I just tried it here with different timezone settings and times on a Android 9 phone - I couldn't reproduce it. Still, I can see this behaviour on my vacation pictures - and the only instance that could change the time on the camera is the Unleashed.
Maybe it only happens when changing timezones in real? I don't know. I can just see that the camera changed it's time (correctly) according to the phones (or GPS?) value, even if this setting was set.
To answer your question: the offset is exactly the timezone I was in. Interesting enough it really had exactly the time of the timezone I was in.
Maybe this was also related due to the two phones that were paired in that time frame? I mean I had to swap the phones to reproduce the other error...
Matthias
I just tried it here with different timezone settings and times on a Android 9 phone - I couldn't reproduce it. Still, I can see this behaviour on my vacation pictures - and the only instance that could change the time on the camera is the Unleashed.
Maybe it only happens when changing timezones in real? I don't know. I can just see that the camera changed it's time (correctly) according to the phones (or GPS?) value, even if this setting was set.
To answer your question: the offset is exactly the timezone I was in. Interesting enough it really had exactly the time of the timezone I was in.
Maybe this was also related due to the two phones that were paired in that time frame? I mean I had to swap the phones to reproduce the other error...
Matthias
Hi,
Interesting.
The UTC timestamp (saved in the GPS metadata) does not have a timezone. it's the UTC time (well, GPS time to be exact - 18 seconds different from UTC).
We'll have another look at how we get the UTC time from the phone. But I guess it's possible to set the time manually (eg ignoring timezone, and changing the "UTC" time on the phone), which could cause these kind of issues. There might be an option to use the actual GPS time rather than the phone's system time. We'll look into it.
But as I said, if the setting on the camera was off (to set the Clock from GPS), then the normal timestamp of the photos (not the one in the GPS metadata) should not have changed. Could you verify this?
ie is the UTC timestamp in the GPS metadata off,
or is the file date (or date digitized in the metadata) off,
or both?
Interesting.
The UTC timestamp (saved in the GPS metadata) does not have a timezone. it's the UTC time (well, GPS time to be exact - 18 seconds different from UTC).
We'll have another look at how we get the UTC time from the phone. But I guess it's possible to set the time manually (eg ignoring timezone, and changing the "UTC" time on the phone), which could cause these kind of issues. There might be an option to use the actual GPS time rather than the phone's system time. We'll look into it.
But as I said, if the setting on the camera was off (to set the Clock from GPS), then the normal timestamp of the photos (not the one in the GPS metadata) should not have changed. Could you verify this?
ie is the UTC timestamp in the GPS metadata off,
or is the file date (or date digitized in the metadata) off,
or both?
Founder & CEO of Foolography, Hardware & Firmware developer.
Well - in short: I don't know.
To give you an impression: the firs image in US still had a German timestamp [1]. The second image is just maybe an hour later, where I connected the Unleashed (which is why you'll also see GPS coordinates in there (by then the Unleashed still worked)). However the date jumped by hours in between (2019:09:17 03:57:21 vs. 2019:09:16 20:17:16, whereas the second image was taken later than the first).
[1]
[2]
To give you an impression: the firs image in US still had a German timestamp [1]. The second image is just maybe an hour later, where I connected the Unleashed (which is why you'll also see GPS coordinates in there (by then the Unleashed still worked)). However the date jumped by hours in between (2019:09:17 03:57:21 vs. 2019:09:16 20:17:16, whereas the second image was taken later than the first).
[1]
Code: Select all
ExifTool Version Number : 11.16
File Name : 2019_09_17__03_57_21.NEF
Directory : .
File Size : 29 MB
File Modification Date/Time : 2019:10:02 14:04:41+02:00
File Access Date/Time : 2019:10:04 14:37:04+02:00
File Inode Change Date/Time : 2019:10:02 17:49:51+02:00
File Permissions : rwxr-xr-x
File Type : NEF
File Type Extension : nef
MIME Type : image/x-nikon-nef
Exif Byte Order : Little-endian (Intel, II)
Make : NIKON CORPORATION
Camera Model Name : NIKON D750
Orientation : Horizontal (normal)
Software : Ver.1.15
Modify Date : 2019:09:17 03:57:21
Artist :
Jpg From Raw Start : 1172992
Jpg From Raw Length : 1445245
Y Cb Cr Positioning : Co-sited
Image Width : 6032
Image Height : 4032
Bits Per Sample : 14
Compression : Nikon NEF Compressed
Photometric Interpretation : Color Filter Array
Strip Offsets : 2618368
Samples Per Pixel : 1
Rows Per Strip : 4032
Strip Byte Counts : 28048388
X Resolution : 300
Y Resolution : 300
Planar Configuration : Chunky
Resolution Unit : inches
CFA Repeat Pattern Dim : 2 2
CFA Pattern 2 : 0 1 1 2
Subfile Type : Reduced-resolution image
Other Image Start : 251392
Other Image Length : 921496
Reference Black White : 0 255 0 255 0 255
Creator Tool : NIKON D750 Ver.1.15
Copyright :
Exposure Time : 1/100
F Number : 5.0
Exposure Program : Aperture-priority AE
ISO : 1600
Sensitivity Type : Recommended Exposure Index
Create Date : 2019:09:17 03:57:21
Exposure Compensation : 0
Max Aperture Value : 4.4
Metering Mode : Multi-segment
Light Source : Unknown
Flash : Off, Did not fire
Focal Length : 85.0 mm
Maker Note Version : 2.11
Quality : RAW
White Balance : Auto1
Focus Mode : AF-S
Flash Setting :
Flash Type :
White Balance Fine Tune : 0 0
WB RB Levels : 2.078125 1.14453125 1 1
Program Shift : 0
Exposure Difference : 0
Preview Image Start : 45060
Preview Image Length : 148040
Flash Exposure Compensation : 0
External Flash Exposure Comp : 0
Flash Exposure Bracket Value : 0.0
Exposure Bracket Value : 0
Crop Hi Speed : FX Uncropped (6032x4032 cropped to 6032x4032 at pixel 0,0)
Exposure Tuning : 0
Serial Number : 2107035
Color Space : sRGB
VR Info Version : 0100
Vibration Reduction : On
VR Mode : Normal
Active D-Lighting : Auto
Picture Control Version : 0200
Picture Control Name : Standard
Picture Control Base : Standard
Picture Control Adjust : Default Settings
Picture Control Quick Adjust : Normal
Clarity : 1.00
Brightness : Normal
Hue : None
Filter Effect : n/a
Toning Effect : n/a
Toning Saturation : n/a
Time Zone : +01:00
Daylight Savings : Yes
Date Display Format : D/M/Y
ISO Expansion : Off
ISO2 : 1600
ISO Expansion 2 : Off
Vignette Control : Normal
Auto Distortion Control : Off
Black Level : 600 600 600 600
Lens Type : G VR
Lens : 24-85mm f/3.5-4.5
Flash Mode : Did Not Fire
Shooting Mode : Single-Frame
Contrast Curve : (Binary data 578 bytes, use -b option to extract)
Shot Info Version : 0234
Firmware Version : 1.15a
NEF Compression : Lossless
Noise Reduction : Off
NEF Linearization Table : (Binary data 46 bytes, use -b option to extract)
Color Balance Version : 0223
Lens Data Version : 0204
Exit Pupil Position : 93.1 mm
AF Aperture : 4.6
Focus Position : 0x05
Focus Distance : 11.89 m
Lens ID Number : 180
Lens F Stops : 5.33
Min Focal Length : 24.5 mm
Max Focal Length : 84.8 mm
Max Aperture At Min Focal : 3.6
Max Aperture At Max Focal : 4.5
MCU Version : 182
Effective Max Aperture : 4.5
Raw Image Center : 3016 2016
Retouch History : None
Shutter Count : 7410
Flash Info Version : 0107
Flash Source : None
External Flash Firmware : n/a
External Flash Zoom Override : No
External Flash Status : Flash Not Attached
External Flash Ready State : n/a
Flash Compensation : 0
Flash GN Distance : 0
Flash Group A Control Mode : Off
Flash Group B Control Mode : Off
Flash Group C Control Mode : Off
Flash Group A Compensation : 0
Flash Group B Compensation : 0
Flash Group C Compensation : 0
Vari Program :
Multi Exposure Version : 0100
Multi Exposure Mode : Off
Multi Exposure Shots : 0
Multi Exposure Auto Gain : Off
High ISO Noise Reduction : Normal
Power Up Time : 2019:08:26 15:42:20
AF Info 2 Version : 0100
Contrast Detect AF : Off
AF Area Mode : Single Area
Phase Detect AF : On (51-point)
Primary AF Point : D6
AF Points Used : D6
Contrast Detect AF In Focus : No
File Info Version : 0100
Memory Card Number : 0
Directory Number : 101
File Number : 5735
AF Fine Tune : Off
AF Fine Tune Index : n/a
AF Fine Tune Adj : 0
Retouch Info Version : 0200
Retouch NEF Processing : Off
User Comment :
Sub Sec Time : 95
Sub Sec Time Original : 95
Sub Sec Time Digitized : 95
Sensing Method : One-chip color area
File Source : Digital Camera
Scene Type : Directly photographed
Custom Rendered : Normal
Exposure Mode : Auto
Digital Zoom Ratio : 1
Focal Length In 35mm Format : 85 mm
Scene Capture Type : Standard
Gain Control : High gain up
Contrast : Normal
Saturation : Normal
Sharpness : Normal
Subject Distance Range : Unknown
GPS Version ID : 2.3.0.0
Date/Time Original : 2019:09:17 03:57:21
TIFF-EP Standard ID : 1 0 0 0
Aperture : 5.0
Auto Focus : On
Blue Balance : 1.144531
CFA Pattern : [Red,Green][Green,Blue]
Image Size : 6032x4032
Jpg From Raw : (Binary data 1445245 bytes, use -b option to extract)
Lens ID : AF-S Zoom-Nikkor 24-85mm f/3.5-4.5G IF-ED VR
Lens Spec : 24-85mm f/3.5-4.5 G VR
Megapixels : 24.3
Other Image : (Binary data 921496 bytes, use -b option to extract)
Preview Image : (Binary data 148040 bytes, use -b option to extract)
Red Balance : 2.078125
Scale Factor To 35 mm Equivalent: 1.0
Shutter Speed : 1/100
Create Date : 2019:09:17 03:57:21.95
Date/Time Original : 2019:09:17 03:57:21.95
Modify Date : 2019:09:17 03:57:21.95
Thumbnail TIFF : (Binary data 57816 bytes, use -b option to extract)
Circle Of Confusion : 0.030 mm
Depth Of Field : 6.21 m (9.54 - 15.75 m)
Field Of View : 23.7 deg (5.00 m)
Focal Length : 85.0 mm (35 mm equivalent: 85.0 mm)
Hyperfocal Distance : 48.09 m
Light Value : 7.3
Code: Select all
ExifTool Version Number : 11.16
File Name : 2019_09_16__20_17_16.NEF
Directory : .
File Size : 28 MB
File Modification Date/Time : 2019:10:02 14:05:07+02:00
File Access Date/Time : 2019:10:02 17:55:18+02:00
File Inode Change Date/Time : 2019:10:03 11:09:58+02:00
File Permissions : rwxr-xr-x
File Type : NEF
File Type Extension : nef
MIME Type : image/x-nikon-nef
Exif Byte Order : Little-endian (Intel, II)
Make : NIKON CORPORATION
Camera Model Name : NIKON D750
Orientation : Horizontal (normal)
Software : Ver.1.15
Modify Date : 2019:09:16 20:17:16
Artist :
Jpg From Raw Start : 1340416
Jpg From Raw Length : 1761019
Y Cb Cr Positioning : Co-sited
Image Width : 6032
Image Height : 4032
Bits Per Sample : 14
Compression : Nikon NEF Compressed
Photometric Interpretation : Color Filter Array
Strip Offsets : 3101696
Samples Per Pixel : 1
Rows Per Strip : 4032
Strip Byte Counts : 25747886
X Resolution : 300
Y Resolution : 300
Planar Configuration : Chunky
Resolution Unit : inches
CFA Repeat Pattern Dim : 2 2
CFA Pattern 2 : 0 1 1 2
Subfile Type : Reduced-resolution image
Other Image Start : 276992
Other Image Length : 1063059
Reference Black White : 0 255 0 255 0 255
Creator Tool : NIKON D750 Ver.1.15
Copyright :
Exposure Time : 3
F Number : 6.3
Exposure Program : Aperture-priority AE
Sensitivity Type : Recommended Exposure Index
Create Date : 2019:09:16 20:17:16
Exposure Compensation : 0
Max Aperture Value : 4.8
Metering Mode : Multi-segment
Light Source : Unknown
Flash : Off, Did not fire
Focal Length : 145.0 mm
Maker Note Version : 2.11
Quality : RAW
White Balance : Auto1
Focus Mode : AF-S
Flash Setting :
Flash Type :
White Balance Fine Tune : 0 0
WB RB Levels : 1.44140625 1.9296875 1 1
Program Shift : 0
Exposure Difference : 0
Preview Image Start : 44888
Preview Image Length : 173775
Flash Exposure Compensation : 0
External Flash Exposure Comp : 0
Flash Exposure Bracket Value : 0.0
Exposure Bracket Value : 0
Crop Hi Speed : FX Uncropped (6032x4032 cropped to 6032x4032 at pixel 0,0)
Exposure Tuning : 0
Serial Number : 2107035
Color Space : sRGB
VR Info Version : 0100
Vibration Reduction : Off
VR Mode : Normal
Active D-Lighting : Auto
Picture Control Version : 0200
Picture Control Name : Standard
Picture Control Base : Standard
Picture Control Adjust : Default Settings
Picture Control Quick Adjust : Normal
Clarity : 1.00
Brightness : Normal
Hue : None
Filter Effect : n/a
Toning Effect : n/a
Toning Saturation : n/a
Time Zone : +01:00
Daylight Savings : Yes
Date Display Format : D/M/Y
ISO : 50
ISO Expansion : Lo 1.0
ISO2 : 50
ISO Expansion 2 : Lo 1.0
Vignette Control : Normal
Auto Distortion Control : Off
Black Level : 600 600 600 600
Lens Type : G VR
Lens : 70-300mm f/4.5-5.6
Flash Mode : Did Not Fire
Shooting Mode : Single-Frame
Contrast Curve : (Binary data 578 bytes, use -b option to extract)
Shot Info Version : 0234
Firmware Version : 1.15a
NEF Compression : Lossless
Noise Reduction : Off
NEF Linearization Table : (Binary data 46 bytes, use -b option to extract)
Color Balance Version : 0223
Lens Data Version : 0204
Exit Pupil Position : 97.5 mm
AF Aperture : 4.9
Focus Position : 0x01
Focus Distance : 21.13 m
Lens ID Number : 141
Lens F Stops : 5.67
Min Focal Length : 71.3 mm
Max Focal Length : 302.0 mm
Max Aperture At Min Focal : 4.5
Max Aperture At Max Focal : 5.7
MCU Version : 143
Effective Max Aperture : 4.9
Raw Image Center : 3016 2016
Retouch History : None
Shutter Count : 7458
Flash Info Version : 0107
Flash Source : None
External Flash Firmware : n/a
External Flash Zoom Override : No
External Flash Status : Flash Not Attached
External Flash Ready State : n/a
Flash Compensation : 0
Flash GN Distance : 0
Flash Group A Control Mode : Off
Flash Group B Control Mode : Off
Flash Group C Control Mode : Off
Flash Group A Compensation : 0
Flash Group B Compensation : 0
Flash Group C Compensation : 0
Vari Program :
Multi Exposure Version : 0100
Multi Exposure Mode : Off
Multi Exposure Shots : 0
Multi Exposure Auto Gain : Off
High ISO Noise Reduction : Normal
Power Up Time : 2019:08:26 15:42:20
AF Info 2 Version : 0100
Contrast Detect AF : On
AF Area Mode : Contrast-detect (wide area)
Phase Detect AF : Off
Primary AF Point : (none)
AF Points Used : (none)
AF Image Width : 6016
AF Image Height : 4016
AF Area X Position : 3008
AF Area Y Position : 2712
AF Area Width : 648
AF Area Height : 540
Contrast Detect AF In Focus : Yes
File Info Version : 0100
Memory Card Number : 0
Directory Number : 101
File Number : 5757
AF Fine Tune : Off
AF Fine Tune Index : n/a
AF Fine Tune Adj : 0
Retouch Info Version : 0200
Retouch NEF Processing : Off
User Comment :
Sub Sec Time : 13
Sub Sec Time Original : 13
Sub Sec Time Digitized : 13
Sensing Method : One-chip color area
File Source : Digital Camera
Scene Type : Directly photographed
Custom Rendered : Normal
Exposure Mode : Auto
Digital Zoom Ratio : 1
Focal Length In 35mm Format : 145 mm
Scene Capture Type : Standard
Gain Control : None
Contrast : Normal
Saturation : Normal
Sharpness : Normal
Subject Distance Range : Unknown
GPS Version ID : 2.3.0.0
GPS Latitude Ref : North
GPS Longitude Ref : West
GPS Altitude Ref : Above Sea Level
GPS Time Stamp : 03:17:16.03
GPS Satellites : 04
GPS Map Datum :
GPS Date Stamp : 2019:09:16
Date/Time Original : 2019:09:16 20:17:16
TIFF-EP Standard ID : 1 0 0 0
Aperture : 6.3
Auto Focus : On
Blue Balance : 1.929688
CFA Pattern : [Red,Green][Green,Blue]
GPS Altitude : 595 m Above Sea Level
GPS Date/Time : 2019:09:16 03:17:16.03Z
GPS Latitude : 36 deg 7' 24.88" N
GPS Longitude : 115 deg 9' 13.34" W
GPS Position : 36 deg 7' 24.88" N, 115 deg 9' 13.34" W
Image Size : 6032x4032
Jpg From Raw : (Binary data 1761019 bytes, use -b option to extract)
Lens ID : AF-S VR Zoom-Nikkor 70-300mm f/4.5-5.6G IF-ED
Lens Spec : 70-300mm f/4.5-5.6 G VR
Megapixels : 24.3
Other Image : (Binary data 1063059 bytes, use -b option to extract)
Preview Image : (Binary data 173775 bytes, use -b option to extract)
Red Balance : 1.441406
Scale Factor To 35 mm Equivalent: 1.0
Shutter Speed : 3
Create Date : 2019:09:16 20:17:16.13
Date/Time Original : 2019:09:16 20:17:16.13
Modify Date : 2019:09:16 20:17:16.13
Thumbnail TIFF : (Binary data 57816 bytes, use -b option to extract)
Circle Of Confusion : 0.030 mm
Depth Of Field : 8.28 m (17.78 - 26.06 m)
Field Of View : 14.1 deg (5.21 m)
Focal Length : 145.0 mm (35 mm equivalent: 145.0 mm)
Hyperfocal Distance : 111.07 m
Light Value : 4.7Sorry, I don't mean to ignore you.
We've just released a new Android app - hopefully this fixes your connectivity issues.
Now, about that date time issue:
Here are the relevant parts from your data:
So yes, you're right, the later image did get an earlier date.
- Now as to which date is correct, I really can't tell you - you'll know better. It might simply have been a mistake when manually setting the date in the camera, or when starting the android phone again after the trip, before you had internet and the time was able to adjust automatically...
- as for the difference between GPS Date/Time and Date/Time Original - that's due to the Timezone setting in your camera.
(I don't know if the camera also uses the GPS data to set its timezone, or if you set it manually)
- however, the mystery remains why the camera clock was set to the GPS time, which it obviously was: the difference is only 100 milliseconds.
As I've said before, the Unleashed doesn't actually set the clock, the camera sets its own clock, and just uses the GPS time the Unleashed provides. The Unleashed can only provide the time it gets from the phone, so if that gives it a wrong time, the Unleashed has no control over that. We will check if we can find a more reliable time source on the phone than what the user sets it to (maybe the GPS of the phone can provide a more reliable time)
If you're 100% sure the "Set Camera clock from GPS" Setting was OFF, then there is a bug in the camera firmware. I'm really sorry - but that's something we have no control over... We only provide the GPS data, and have to include a timestamp. As I said, we'll try add more checks to make sure that's correct.
We've just released a new Android app - hopefully this fixes your connectivity issues.
Now, about that date time issue:
Here are the relevant parts from your data:
Code: Select all
Serial Number : 2107035
Shutter Count : 7410
Create Date : 2019:09:17 03:57:21.95
Date/Time Original : 2019:09:17 03:57:21.95
Modify Date : 2019:09:17 03:57:21.95
Code: Select all
Serial Number : 2107035
Shutter Count : 7458
Create Date : 2019:09:16 20:17:16.13
Date/Time Original : 2019:09:16 20:17:16.13
Modify Date : 2019:09:16 20:17:16.13
GPS Date/Time : 2019:09:16 03:17:16.03Z
- Now as to which date is correct, I really can't tell you - you'll know better. It might simply have been a mistake when manually setting the date in the camera, or when starting the android phone again after the trip, before you had internet and the time was able to adjust automatically...
- as for the difference between GPS Date/Time and Date/Time Original - that's due to the Timezone setting in your camera.
(I don't know if the camera also uses the GPS data to set its timezone, or if you set it manually)
- however, the mystery remains why the camera clock was set to the GPS time, which it obviously was: the difference is only 100 milliseconds.
As I've said before, the Unleashed doesn't actually set the clock, the camera sets its own clock, and just uses the GPS time the Unleashed provides. The Unleashed can only provide the time it gets from the phone, so if that gives it a wrong time, the Unleashed has no control over that. We will check if we can find a more reliable time source on the phone than what the user sets it to (maybe the GPS of the phone can provide a more reliable time)
If you're 100% sure the "Set Camera clock from GPS" Setting was OFF, then there is a bug in the camera firmware. I'm really sorry - but that's something we have no control over... We only provide the GPS data, and have to include a timestamp. As I said, we'll try add more checks to make sure that's correct.
Founder & CEO of Foolography, Hardware & Firmware developer.
Hi Oliver,
not sure whether I described the situation correctly, so I'll try again. Maybe the whole thing is just a misunderstanding on my side:
* We had two camera on the vacation. One with an Unleashed, one without. I deliberately disabled the camera setting to set the GPS time on the one with the Unleashed, in order to keep the two cameras always synchronized from a date / time perspective.
* When switching the camera with the Unleashed on in US, the camera always overtook the time from the smartphone. What I'd wanted: Not changing the time at all - not the GPS time and not the time from the smartphone, just the time that was set in the camera.
* This changing of the date and time happened all the time on vacation, as we crossed timezoned quite often. Every time the smartphone got a different time, the camera afterwards also had the changed time. I did not touch the time setting during that time.
To sum it up - this is not really about setting the GPS time - it is about the Unleashed changing the camera time all the time according to the phone's time settings.
Now the big question is - does the Unleashed to this intentionally?
Matthias
not sure whether I described the situation correctly, so I'll try again. Maybe the whole thing is just a misunderstanding on my side:
* We had two camera on the vacation. One with an Unleashed, one without. I deliberately disabled the camera setting to set the GPS time on the one with the Unleashed, in order to keep the two cameras always synchronized from a date / time perspective.
* When switching the camera with the Unleashed on in US, the camera always overtook the time from the smartphone. What I'd wanted: Not changing the time at all - not the GPS time and not the time from the smartphone, just the time that was set in the camera.
* This changing of the date and time happened all the time on vacation, as we crossed timezoned quite often. Every time the smartphone got a different time, the camera afterwards also had the changed time. I did not touch the time setting during that time.
To sum it up - this is not really about setting the GPS time - it is about the Unleashed changing the camera time all the time according to the phone's time settings.
Now the big question is - does the Unleashed to this intentionally?
Matthias
I do think I understand your situation.
But as I said, the Unleashed has absolutely no control over the camera clock. We only provide GPS data, which must include GPS/UTC Time. (if we wouldn't provide time, then Nikon would not save any GPS data into any photos). We only provide this because you want to save GPS data to the photos, as would any other GPS device for Nikon.
The camera decides whether to use the GPS time to set the camera clock. And it SHOULD respect the setting whether you want this at all, but it seems yours doesn't, so it sounds like there is a bug in the camera firmware.
When you power on the camera, it takes one of the first sets of GPS data it gets, extracts the time from that, and sets its clock.
So we don't provide a time specifically for the camera to set to, nor do we (or can we) tell the camera to set the clock to that time.
We only provide sets of GPS positions and time as required by Nikon to be stored in photos...
So to answer your big question: NO. Not intentionally, and No, not even unintentionally.
But as I said, the Unleashed has absolutely no control over the camera clock. We only provide GPS data, which must include GPS/UTC Time. (if we wouldn't provide time, then Nikon would not save any GPS data into any photos). We only provide this because you want to save GPS data to the photos, as would any other GPS device for Nikon.
The camera decides whether to use the GPS time to set the camera clock. And it SHOULD respect the setting whether you want this at all, but it seems yours doesn't, so it sounds like there is a bug in the camera firmware.
When you power on the camera, it takes one of the first sets of GPS data it gets, extracts the time from that, and sets its clock.
So we don't provide a time specifically for the camera to set to, nor do we (or can we) tell the camera to set the clock to that time.
We only provide sets of GPS positions and time as required by Nikon to be stored in photos...
So to answer your big question: NO. Not intentionally, and No, not even unintentionally.
Founder & CEO of Foolography, Hardware & Firmware developer.