"Do not import duplicates" IS importing duplicates
I've upgraded to 3.1.1.
This "pro" app is making managing my photos really a pain in the rear.
What. Is. The. Deal?
MacBook Pro C2D, Mac OS X (10.5.1)
MacBook Pro C2D, Mac OS X (10.5.1)
This duplicate recognition is bothering me too. Therefore I've been doing some testing. Renaming of the files will kill Aperture's ability to recognize duplicates. Identical images with different names are not regarded as duplicates.
What was worrying me, was that if my library already contained an image called XYZ01234.JPG and I tried to import another, different, image of the same name, that the second impart would bypass that image if I had set "Do Not Import Duplicates".
Strangely, this doesn't happen it seems. I have successfully imported two different images which share the same name, so that is a relief.
When all else fails, I sometimes remember to go back and read the manual. RTFM.
This is one of those rare cases where I tried RTFM. Here is what it says:-
"When you import images, Aperture automatically checks to see if any of the images are duplicates of previously imported images. Aperture checks the filename of the master to determine if an image is a duplicate of one in the library. Select the “Do not import duplicates” checkbox to prevent Aperture from importing duplicates."
This is by no means an unambiguous definition of its behavior, but it clearly says that file name is part of the process. Clearly I should have read this some time ago, but better late than never.
My conclusion is that Aperture doesn't work the way I'd like it to, but there must be a possible workaround.
This is not thought through really well yet, but maybe the answer is to eliminate duplicates before importing the images.
At this stage, I can only see one scenario that might work.
Clunky, I know. But what do you people think? Could this be a way to go?
Your opinions will be valued
Maybe or maybe not significant...
When you import RAWs matching already imported JPEGs, you must not change the JPEGs' timestamps, otherwise even identical filenames fail to match. One might infer that when Aperture is sorting out duplicate filenames it also looks at the timestamp.
Good point! The timestamp is probably what is differentiating different images with the same file name, possibly in combination with other metadata.
I'm interested in opinions from Aperture users who regularly rename images on import, since that breaks Aperture's duplicate detection.
The following are not duplicates:
renamed.jpg
img_001.jpg
The following are duplicates:
img_001.jpg
img_001.jpg
I would not expect duplicate detection to 'work' on masters that have been renamed since they are not duplicates of the files being imported.
On the other hand, people whose workflow involves automatic renaming of masters as part of the Aperture Import process would probably expect that Aperture's duplicate detection would work. For such users, the camera-generated file name has no meaning or value.
True, some users may expect that. However, the definition of 'duplicate' does not change based on a users workflow. If "Do not import duplicates" is enabled, I expect it to do just that.
I've just come across this issue, and have found that changing my timezone back to the time zone that I used for importing the files originally makes the "Do not import duplicates" function work as expected.
But quoting from above:
"Aperture checks the filename of the master to determine if an image is a duplicate of one in the library. Select the “Do not import duplicates” checkbox to prevent Aperture from importing duplicates."
That description matches how I want it to behave. i.e. if I've got image XYZ.jpg on my flashcard and you see that I've got XYZ.jpg in my Aperture library - don't re-import this DUPLICATE image.
There is no time zone in the filename of the master, so they've introduced a bug if their duplicate detection depends on tme zone.
"Do not import duplicates" IS importing duplicates