CR2 as "Unsupported Image Format" on Aperture 2.1.2?

I just installed aperture on OS 10.5.5 and immediately installed the available update via Software Update. Then, I imported a day's worth of shooting from my EOS 1D Mark iii (one of the models listed on Aperture's Supported Raw Formats webpage - http://www.apple.com/aperture/specs/raw.html). The .jpegs display fine but my CR2 images only appear as preview thumbnails - when I click on the preview a red box appears with the text: "Unsupported Image Format." I'm a bit incredulous that Apple would fail to support this enormously popular image format - say it ain't so.

Message was edited by: Alexandra Latta

2 x 3 GHz Quad Mac Pro, Mac OS X (10.5.5), Aperture 2.1.2

Posted on Nov 2, 2008 8:23 PM

Reply
21 replies

Nov 3, 2008 10:04 AM in response to tidysteve

Hi, to all!
...I have the same problem with the NEF files from my Nikon d80.

I tried like suggest to import a pic in iphoto 08 and it doens't work (It import only a black mask), instead with preview it works well...

I think (but not 100% shure) that happens after I installed the last update for the new cameras (like d700 etc)...

The problem happens not with all the files...someone work normally...

Thanks for the care!!

lorenzo

Nov 3, 2008 10:11 AM in response to Alexandra Latta

Alexandra,
Your Camera is supported. I use a Canon 1Ds mk III & 40D. They usually work perfectly.
However, I too have seen the Red Screen with the message "unsupported file format", although rarely.
What is even more confusing is that the only times I get it is in the middle of an edit session. I'll import a shoot (500-1200 files) and begin editing. Everything will work fine for a considerable amount of time. I click through images editing each as I go. Then, quite randomly I'll click on the next image and I get the Bright red screen with the "unsupported file format" message. What is interesting is that I can go back to other images without a problem, but if I go forward to that next image I get the red screen.
My workaround has been to quit Aperture, and relaunch. In every case I am able to pick up where I left off and view and edit the image that (30 seconds ago) had been "Unsupported"
I don't know why it happens, and the problem never persists. It is intermittent, and I have been unable to "cause" it to occur. For me it has just been an annoyance, ---I've lost no work and it has "only" happened perhaps 25 times in a year of nearly daily use.
I do not have a solution,but I have offered my experience in the hope that additional information might lead to some help for both of us.

Nov 3, 2008 6:32 PM in response to tidysteve

I only shoot full size raw files. Approximately 25 mb for the 1Ds Mk III & 12 mb for the 40D.
I did not know that sRaw is not supported. I never really saw the point of sRaw, memory cards are the cheapest part of digital photography. This could change in the future as manufacturers use "pixel binning" to push low noise super high ISO's.
Thanks for the post.

Nov 4, 2008 2:27 PM in response to tidysteve

Excellent information that confirms my experience. It has only happened to me in the midst of an editing session, and has always been corrected by a restart of the application.
I don't know if it answers Alexandra's original question.
I have also found that Aperture has gotten progressively slower over the last few months, perhaps a function of a growing managed library?? It's to the point where if I edit to fast, I'll start getting beachballs, and have even had the app quit -or go to the red screen/unsupported file type message.
I don't have the latest machine, but it is a fast one, (Mac Pro Quad 3.0 Ghz 11 gb ram and the nVidia 8800 GT graphics card driving 2 23" Cinema Displays) My startup drive is a 750GB Seagate Barracuda partitioned 250/500 with everything but the Aperture library on the 250 partition (100 gb free space left) and only the Aperture library on the 500 partition (aprox 200 GB free). (there are also 3 more 750 gb drives in the machine for Time Machine & other stuff.
This machine should be really fast (it once was) so I may be doing something wrong, but can't figure what is wrong.
Is anyone aware of an article on speeding up aperture? My previews are limited to the default (2500 x2500 aprox) yet my activity window always seems to have a backup of previews to be built once I'm going in an edit session.
Any advice would be appreciated.
Thanks

Nov 5, 2008 2:26 PM in response to Alexandra Latta

See my post from yesterday regarding strange image colours after installing the latest aperture update and 10.5.5.

I found this to be a problem with the Camera Raw update (ver 2.2) that also came out with 10.5.5.

I installed ver 2.1 and everything worked OK again.

I just noticed that Apple have released an updated version of Camera Raw today - ver 2.3.

I'll install this and see that the problem has been fixed in this version.

let me know your comments.

Nov 17, 2008 6:11 PM in response to Alexandra Latta

Hello, I have the same unsupported image format, but for all images before the update from Aperture 1.0 to Aperture 2. I'm currently in the latest version 2.1.2. I have tried several things with no good results. That is going with my NEF Files (Nikon D100-D200, but just before the update) as well as some scanned jpegs. Actually it happens to all my pictures before the update. The thing is when I look at the pictures in browser view only, I see the picture just fine. If I try to Edit in Photoshop I get the following message: " Editing Error This image cannot be rendered for editing because Aperture does not support the image format."

Can someone help me with this issue? I can't export the pictures to iPhoto as well

Dec 1, 2008 1:26 PM in response to mjperini

I too have had this appear and just like the rest of everyone, I googled" aperture 2 unsupported image format", and now an reading this page.

I'm shooting RAW with a Nikon D2Xs tethered to Aperture 2 and haven't had any problems until today I the unsupported image format message started to be displayed on images that I know have been viewed just fine last week.

It seems that by restarting aperture that it temporally fixes this bug. I have only had this message reappear after intensive editing of my images in Aperture (by that I mean, cropping every image and adjusting exposure). It seems to be that all the changes are filling the system cache or something of that nature.

I too, like the rest of the Aperture users will sit and wait for an update to fix this issue.


Thanks for all the banter pervious to my comment!

Dec 1, 2008 6:04 PM in response to Alexandra Latta

I'm encountering similar issues as well. The problem files (at least so far) are imported from iPhoto and are some old jpegs. The thumbnail is ok, but the image in the main viewer shows as unsupported image format.

What's interesting is that the photo is visible in the main viewer until about the time it completes loading, at which point I get the red overlay and the message.

Restarting Aperture doesn't seem to make any difference.

Problem with the photo?

Dec 1, 2008 6:42 PM in response to Dale Gardner

Dale,
I'm pretty sure what is happening with your "appears-disappears" problem is that while importing Aperture is using the embedded JPEG in the file while it decodes the underlying file, which it then finds unreadable. I'm assuming that the photos were shot in a raw format. I've seen that happen.
If the originals were JPEGS, I don't know why that would happen.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

CR2 as "Unsupported Image Format" on Aperture 2.1.2?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.