Currently Being ModeratedNov 24, 2012 8:42 AM (in response to FrankieGans)
I'm sorry I can only imagine how frustrating this is. This might be a computer problem.
As I mentioned earlier, it's possible for a segiment of a hard drive to go bad and corrupt data. If that happened and the data was in the sectioin that stored the program for interperting the RAW, you might experience behaivor like your seeing. There is a report on Aperture Expert where images on a remote drive became "unsupported format" after being moved to a remote drive. The problem turned out to be a bad firewire cable.
Once more just to be sure my system info:
Currently Being ModeratedNov 28, 2012 12:20 AM (in response to Jerry Dalton1)
Thanks Jerry. I'm hoping now for the next OS X update. Maybe this will fix things (and if only by re-writing the raw engine files....).
Currently Being ModeratedNov 30, 2012 10:03 AM (in response to FrankieGans)
Hi again, great news: The latest Digital Camera RAW Update 4.02 and reprocessing the affected masters resolved the issue.
At this point I have to compliment Apple on its assistance. The support team was extremly responsive.
Again, many thanks also to Leonie, Jerry and Aye Es Oh.
Currently Being ModeratedNov 30, 2012 10:05 AM (in response to FrankieGans)
Great that your NEFs are recognized again!
Currently Being ModeratedNov 30, 2012 4:24 PM (in response to FrankieGans)
That is good news! I'm glad the issue is resolved.