Q: "Do not import duplicates" IS importing duplicates

blewis_13 wrote:
Why does "do not import duplicates" no longer work in Aperture 3?

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?

A bit more information sure would be helpful in trying to help you fix your problem.

By the way you do realize that Aperture 3 requires 10.5.8 or 10.6.2 or higher?

"do not import duplicates" isn't working for me now either. I don't know when it started because I usually reformat my cards as soon as they are backed up, but I noticed it on my last import session that involved multiple cards. I just confirmed that it's still not working, but I haven't found a cause yet.

DLS

This is not working for me either. I'm running OS X 10.6.5 and have Aperture upgraded to 3.1.1. I found this support item http://support.apple.com/kb/TS3087 but it still does not work for me.

I have the same problem. which is very basic. i have a two 2tb disks, i am a working photographer in
england, portrait weddings portfolio and commercial. this year i took 70,000 photos. 1000 for your average wedding 3000 for a big wedding with two or three photographers,
DO NOT IMPORT DUPLICATES is a major problem. i have now started putting start file and end file as a voice memo on the card after each shoot, the fact that this basic problem (as well as others) is not been solved makes me think of what other solutions are available, i have found that as more has been bolted on to aperture (slideshows, facebook and faces) the less its a program works for photographers.

You're not renaming the master files on import (or after import) are you? Aperture pretty much goes by master file name to decide if an image is a duplicate.

just off the card, no rename. i use nikon & fuji cameras mainly in raw. i import into the project named after the job like "smith wedding" . i keep the files name as given by the camera.

mike

ilovebillgates wrote:
just off the card, no rename. i use nikon & fuji cameras mainly in raw. i import into the project named after the job like "smith wedding" . i keep the files name as given by the camera.

mike

With my Cannon 40D, as long as I don't mess with the master file name after I've imported the image *Do not import duplicates* works for me. The images on the card that were imported previously do not appear in the import viewer.

Here is an interesting test for you to try. Take a card, format it so it is empty and then take one shot with it. Import that one shot. Now disconnect the camera, turn it off or whatever then reconnect, turn on *Do not import duplicates* in Aperture and see if the image appears in the viewer. If it does, import it and compare the images side by side to see what if anything is different about them. Might give you some hint as to what is going on. I'd be interested in seeing what happens.

good luck.

"Do not import duplicates" seems to only deal with the project listed in the import dialog. Thus if you are importing into an empty project, it will import (and display) photos that you have already imported. I am uncertain whether this is a bug or a feature. If the photos already exist in the project, then they are not displayed. I do not find this feature or the checkbox feature to be particularly useful for the input workflow.

Do not import duplicates does not work for me no matter the source and no matter the destination project, and I do not rename files on import.

Those who know me here, know that I do not use the "B" word very often, but I believe that this is a bug in either 3.1 or 3.1.1.

However, although many are reporting it, many others are not so I'm going to do a rebuild to see if that solves it.

DLS

This is one of those bizarre things. With my Cannon 40D as long as I don't rename the actual file name (not the version but the actual master file name) *Do not import duplicates* works like you would expect. The project I import into has nothing to do with it. It can be the same project or a different project, works in both cases.

Now one thing I did notice with my camera. It has different numbering modes you can set. One of them, manual reset, creates a numbering system that emulates a directory structure. That is each time you reset the file numbers it changes a prefix on the file name. If I select this mode somewhere in the import stream the file name is getting changed. So in this case it appears as if Aperture is importing dups but in fact the file names are different from import to import.

I urge you to try a quick experiment if you haven't already done so. Format your card, create a new empty Aperture library, take 3 or 4 pics and import them. The as soon as processing finishes reimport with *Do not import duplicates* checked. If Aperture imports the images again compare the actual master file names.

As I type this another thought comes to mind. I have all managed images, it is possible that it may not work with referenced images. Those who report this as not working do you have managed or referenced images?

Ok this is bizarre: I repaired permissions and my data base with no change in behavior.

I then tried your experiment with a new library. To my great surprise, do not import duplicates worked as it always has. So I went back to my main library with the same card, and do not import duplicates didn't work- even though I had reset the defaults in the import dialog.

I don't believe this is related to projects nor do I believe it's related to file names (I think Aperture uses more than the file name to identify dupes.)

I'm go to try a database rebuild and see how it acts in the morning as I'm leaving for the day anyway.

DLS

BTW: I have a mixed managed/referenced library, but the images in question are managed. Everything starts out managed and later gets relocated.

I just confirmed that it does not change the name or recognize an image as the same file when I go ahead and import a few dupes. The exact same version name and exact same file name are side by side in the same project.

DLD

DLScreative wrote:
I'm going to try a database rebuild and see how it acts in the morning as I'm leaving for the day anyway.

No change

Well I guess I got the working copy

Seriously this is really strange. There has to be some difference between the image imported already and the image still in the camera. and some difference between our installs.

Figures it would work for me, I never, well very very rarely have the need for it.