Photos not showing up on import

Do you have filter set in Aperture's Import settings?

Check the right pane in the Import panel with the Import settings, i.e. the "File Type" section and the

For me, Image Capture sees everything instantly and I am using it to import to Aperture right now. I am importing from the DMG I made earlier and will test the actual card next, if this works.

Thank you for the tip. I never knew about that way of importing. So far everything is coming into Aperture but no preview images yet but there is a slot for each image.

Tip: For those reading this that have this issue and use this method of import, just make sure you have enough space on your startup drive to import the card. 😉

I don't know that I have the hidden folder from Image Capture issue, but I have had the problem where not all images show up from the SD card reader.

I've used Image Capture, but it tends to import both RAW & JPEG with one or the other as the original. So I will typically sort them by type and import them into separate projects, which doubles the work for deleting clinkers.

I've also found that a better work-around is to quit Aperture and re-launch it. Doing that usually restores its ability to see all the images on the card and load them in the correct order.

That is really bizarre.

does Image Capture see card?

You could also try to use Image Capture to import the images to Aperture.

I have managed to import them in two batches, as usual it seems, with Aperture. The first time I ran Aperture import it showed only 500 and some. It took another quit and restart for it to come up with 968. Additional restarts didn't help the number grow, everything stayed the same.

First Batch - 968

Second Batch - 897

I have concluded that the reason nothing would show up to import for the S120 is the preferences on my drive needed to be set to ignore permissions. So disregard the part about images not showing up at all, that problem has to do with the drive's permissions (or so it seems). But all images on the card not showing up is still very frustrating.

As far as I now, it doesn´t.

I would covert it to Adobe universal DNG file format.

Now that I have done this, the issues with using Image Capture are:

• movies don't properly get put in order. They always end getting stuck at the end of the Library when it is ordered by date and should be beside their corresponding photos.

• Startup drive gets filled up with a duplicate of the camera card that is put in hidden folder under /private/var/etc. The only way to get rid of this is to enable hidden folders and dig down to where Image Capture puts the photos and delete the folder that contains them. Quitting Image Capture doesn't delete that folder. It must be done manually, as far as I know.

I'm not a fan because of the above but it is good to know about it in case all else fails.

Canon 5D Mark IV in both JPEG and RAW and have the issue come up with only a few images available.

Can Aperture import the Canon 5D Mark IV RAW files?

As far as I can see, they are not on the list of supported RAW formats in El Capitan (Digital camera RAW formats supported by OS X El Capitan - Apple Support), and afaik the new RAW Support in macOS 10.13. High Sierra is not working for Aperture. Or has this changed?

They do import fine, you just cannot see them or do anything with them. That is why I import them with the JPEGs from the camera. Then I have them all imported and organized and can use the RAW files later if I need to but in the meantime utilize the JPEGs. That is my current workflow. Aperture is still the best application.

I'm on Sierra and this problem is happening. This only started recently (last 6 months) after I upgraded to Sierra, that is why I was thinking it must be security updates that are causing the issue since no one running Sierra seemed to have this issue on record. But all the info I could find on the web are about 10.12.5 or older (mostly 10.12.4), that is why I was thinking security updates and not the actual OS updates that is causing the issue. I did a fresh install of Sierra 10.12.6 when I upgraded.

I too wish Aperture 4 made it out the door but alas it didn't and we are stuck with what we have to work with. Photos is not very good (tried that) and no other program I have looked at comes close to Aperture, for me.

I am experiencing the same issue. It is completely random and very irritating. I open Aperture up and go to import photos from my Canon 5D Mark IV in both JPEG and RAW and have the issue come up with only a few images available. Quit, run the import window again, get more images or sometimes none at all. Right now I'm in another Aperture library with a Canon S120 with just JPEGs and it doesn't see even one image. So there is nothing to import. Normally I just quit and restart Aperture over and over again until it finally registers the whole card, or just import it in batches if some show up and others don't but do later. But this time there is nothing no matter what I do. More on that later.

Here is the catch for this whole issue: Aperture is seeing it and processing what is on the card fully (the Activity window shows this) but it doesn't show up in the import window when it is processing the card like it normally does. Then after Loading Assets is done, it runs through the faces within a few seconds and goes blank with still nothing to import. The contents of the card has never been imported. This isn't a preference setting or any other setting. Here is a screenshot of my Activity window:

I have tried using Disk Utility to create a read-only disk image of the card and import from there but it is still the same. No photos for my current problem. It is completely random with no rhyme or reason. It doesn't matter the camera or how many photos are on the card, thus far. I normally have larger cards with a large amount of photos and/or videos.

I am running Sierra 10.12.6 and the latest Aperture 3.6. Going to try restarting the whole computer and see if that helps at all.

Everything else with Aperture, that I use anyway, works fine. Just this importing issue!

I'm starting to think it has something to do with the latest security updates over the last few months or something like that. The odd time it works perfectly without an issue but that is rare and was then and this is now. 😉

Under 10.11.6 it never had an issue.