I do indeed open the linked NEF without any problems in Preview and Aperture. Leonie just replied to a similar thread with this suggestion to re-register the CoreTypes Bundle. It's worth a shot, let us know if it helps.
Thanks so much for testing, Aye Es Oh. I already tried Leonie's re-register command. To play it safe, I just executed it again (Aperture and all other apps closed) and restarted the machine. No luck. I'm afraid, something went wrong during one of the last OS X / RAW compatability updates. At least the files themselfes seem to be healthy.
I just downloaded your image file - I have the same Aperture version as you, also the same system version, and Aperture could open and import the image without problems; the raw fine tuning controls work, and also the adjustments. Beautiful picture, btw.
Where are your images located? Is your Aperture library managed or referenced? Does it happen with older imports as well as with new imports?
for some of my managed Nikon D700 NEFs
Is there anything special about that files? Do they have a common property? Import session, size, filename (characters in the file name)?For example, national characters, like "Umlaute" can render files unreadable, if you store them on a file system that is not Mac OS X Extended.
Have you tried the usual trouble shooting drill to get a clue, what might be going on? Importing from a different card or card reader? Importing into a new library? Working from a different user account? Can you import images from other cameras (for example your your phone)?
Thanks Leonie, Thanks Jerry.
I flipped through my library. It seems that the problem started first with pics, I imported March 2011. Prior imports look fine. (Interestingly it started right after an air trip. But if the security scans somehow damaged my cards and subsequently the pics, why would you be able to open them...? )
I can't find anything which could be special about the relevant files: In fact I sometimes shot a series of pics of the same subject in a row. Some work, some are unsupported. The filenames I didn't change (standard out of camera format "_DSC####.NEF", file system is Mac OS X Extended (Journaled) btw.).
I tried all of the 3 troubleshooting steps of Aperture several times. I tried repairing permissions for the whole drive. I also tried importing directly from camera besides using a card reader, both, into existing and new libraries. Importing pics from iPhone and an old Lumix is ok (but these are not raw...).
I will try a different user account and report back.
Many thanks again to all for your help.
I'm assuming these images are referenced images. Is it possible you used Capture NX to edit the files, metadata, rating or anything where you might have done a SAVE from Capture NX, after the Import to Aperture?If so you might want to try copying one of the problem files to NEWNAME and re-importing it with Aperture. One more thing, have you tried to delete one of the problem files from Aperture (don't delete the master) and then re-importing it? (Make sure you have a safe duplicate stored somewhere else, peferably on a separte hard drive or flash drive).
the files are managed. I normally don't use Capture NX. I just downloaded a trial to check if an app with it's own raw processor (so not using Mac OS X's one) is able to read the files, which was positive.
I tried your suggestion to delete and re-import (tried both, to import managed and referenced): Doesn't work.
I'm sorry that was a mistake, my RAW is 4.01 as well.
There is a possibility that some program data on your system has gotten corrupted. That can happen. It's a huge labotomy and not to be done unless all else fails, but it is possible to re-load Aperture. It doesn't erase the file structure or any data. I had to do this once a few years ago. Make sure it's all backed first, if you decide to try this.
Before you try that...
If you haven't done repair permissions or verify/repair disk, it's worth a try. Sometimes data get's scrambeled and it's repairable by Disk Utility. As usual make sure you have a backup first. Those utilities shouldn't cause an problem (I have used them for many years and never had a problem) but it's good practice to Always have a backup. Or Backups.
That is funny -
your signature claims you are having the current raw support installed:
iMac 24", 2.4 GHz Intel Core 2 Duo, 4 GB
OS X 10.8.2 (12C60)
Are these data not correct?
The latest raw support can be downloaded from here:
But your camera raw is not part if this update - I checked; It has been supported for a long time now, and should be supported by Mt. Lion.