Q: "Do not import duplicates" doesn't work
-
Feb 5, 2014 3:08 AMby p.zac,I'm sure the time zone manipulation can be useful. I wish the duplicate detection rule would be smarter though (and simpler: comparing the original file name and an md5/sha hash of the image data should be enough to uniquely identify a picture). In the last three months I've been traveling and changing time zone pretty much every week, back and forth, so I guess it will impossible to fix my library.
-
May 14, 2014 12:52 AMby stuartmorley,I had the same problem and this is how I got Aperture to see the duplicates.
I was in Bangkok for a few weeks and Aperture recognised the dupes. Came back to the UK and the time was set back to UK time and Aperture doesn't recognise them.
So the partial solution is to set the time back to the time where the photos were taken.
I consider it a bug as the duplicate should be selected on filename and checksum IMHO.
-
May 14, 2014 1:14 AMby léonie,I was in Bangkok for a few weeks and Aperture recognised the dupes. Came back to the UK and the time was set back to UK time and Aperture doesn't recognise them.
That is interesting. Did Aperture not recognize the duplicates, even with correct Time Zone settings in Aperture's Import panel? When I use the Time Zone brick in the Aperture Import panel to set the "Camera Time" and "Actual Time" to the correct time zones, the duplicates were recognized. If you do not set the TimeZones in the Import panel, Aperture will always use the System Time settings for the time zone.
-
May 14, 2014 1:19 AMby stuartmorley,To be honest I didn't try that but I will take a look.
Strangely this only worked on my MacBook Air and not the MacPro which is at home. Both had the same library on them and I changed the time zones but only the MBA saw them as duplicates.
Another strange thing happened, the MacPro did not show preview images just a .JPG image (and nothing for the RAW from memory). Both copies of Aperture are the very same version, build and Raw file version. They are both fully up to date.
I guess the whole thing would be sorted if they just did a filename and checksum comparison.
I will try with
-
May 14, 2014 1:35 AMby léonie,so adjusting the system clock would solve the issue only for those with such timezone and the others wouldn't still be marked as duplicates.
You have to import the photos sorted by time zone.
Select all photos taken in the same time zone, then set the Time Zone correctly in the import panel. Otherwise the time stamps will be interpreted incorrectly by Aperture. They will show with your current system time, see the Time Zone setiings in my post above.
-
May 14, 2014 1:59 AMby léonie,Will Aperture change the time of the photo as I want to keep this?. I want the photo to show 3:00pm local time not the UK time.
When you set the Camera Time and Actual Time zones on Import, then Aperture will use the local time of the TimeZone where the photo has been taken. It will not change the date of the photo, only how the date will be interpreted.
You can see that, when you change your system time formats to show the Time Zone for the Medium time format and reboot the mac. Then Aperture will display the Time Zome for the "Date" metadata tag:
In the example above, you can see that Aperture interprets the time correctly as GMT, even if it does not display the timezone in the "date created" field.
