Unsupported Image Format (again)

Hi,
I've read some of the other posts about this subject. I've trashed my .plist, rebooted but still the same problem.
I imported my .NEF's (Nikon D80) directly from the camera. I would say about 50% of them display fine; the rest show the magenta screen.
Everything was fine before yesterday when software update installed Security Update; Java release 5; and the Daylight Savings Time updates.
Any help would be appreciated.
Tony.

Thanks for the tip. I tried that still the same.
Then I had a duh moment, and decided to check on the
validity of the NEF files themselves...I tried to
open one of them in Photoshop. PS complained that it
got an unexpected EOF.
So either my camera didn't write properly to the SD
card, or my SD card is broken.
I am having the same problem. The files seem to be fine, I am loading them in the Nikon Picture Perfect software for now until I can figure out why Aperture will not read the files. Photoshop PS may not have the correct filter for the D80 files either...I've tried re-loading the Aperture Update. Nothing seems to be working to read the files.

Similar Messages

After loading Lion I cannot open some pictures. I get Unsupported Image Format. It tells me picture was taken with Canon EOS Rebel with unknown lens

After loading Lion I cannot open open some pictures in Aperture. I get Unsupported Image Format, all files even the ones I can open are .JPG. Also it tells me picture was made using Canon EOS Rebel with unknown lens.

You mention that 'most' of your files are DNG. Try
running the effected files through Adobe DNG
converter again and then import your reprocessed
files to Aperture and see if the problem persists.
I had a problem with a batch of D2x files converted
to DNG which had been metadata tagged by
PhotoMechanic (the evil app).
B.T.W. You mention that you had been using Bridge.
Are you getting any of the embedded XMP metadata
coming into Aperture during the import process?
Already tried that multiple times...no luck. I'm wondering though if it might be related to metadata as you suggest. I'm still trying different things to see what happens.
I was able to alleviate the problem on one set of images by painstakingly searching my external drive for the oldest backups I could find - CR2 files from before DNG conversion. I then ran those through DNG Converter and tried importing them again (this time, I embedded NO thumbnail, but I'm not sure if that made the difference - I think it was more likely a fluke in the original conversion that caused the problem). This time, it worked.
Now, the big problem is that I still have a couple hundred images for which I can't seem to locate the original CR2 files. I don't typically keep them after conversion, as I don't have the space for both.

HT3946 Unsupported image format

I've been getting a message "This photo was adjusted using an earlier version of APPLE RAW processing" unsupported image format and it's been doing this to photos I took today and my older one's any advice on how to fix this?

What is the make of your camera? This problem has occured recently mostly for Lumix and Nikon cameras:
First try, if reprocessing the images will help:
See this section of the user manual on how to do this for selected images:
Reprocessing Images from Previous Versions of Aperture
If this does not help, you may need to register your camera with the the launch service database again, see this post by Alan Roseman:, Re: Aperture 3 preview of raw file greenish
There is a "typo" in the command given in the link above, so read also the following posts on how to correctly enter the command and how the fix is supposed to work
Regards
Léonie

Strange bug - some images showing up as 'unsupported Image Format'

This could be possibly be the last straw with Aperture for me.
I was 'happily' going through my latest shoot when all of a sudden one of my NEF files opens up and I get a solid dark red screen with the text 'Unsurpported Image Format'.
It's the same RAW format as all the other images and the thumbnail is showing fine. I'm getting the same message with several random images.
Has anyone else experienced this?
I guess I need to restart my mac again! Arrrghhh!

this is a bug, but it seems to happen radomly.
aperture would sometimes complain that some of my NEF, PSD, and TIFF files are unsupported Image Format.
sometimes clicking on another project and then back to where i was corrects the problem, and sometimes it just won't do it. when this happens i restart aperture. i think restarting aperture is the least frustrating work-around.
daniel
dual 2.7 ghz powerpc g5 Mac OS X (10.4.3) 8 gb ram and all other standard parts from apple store. such as the xt800 card.

What's with the occasional "Unsupported image format" errors?

I get this error randomly -- suddenly Aperture can't show me anything but a brief flash of the image, and then I get the maroon screen "Unsupported image format" error. Restarting Aperture returns things to normal. I've seen this in both version 1.5.6 and 2.
I can count on this occurring about every hour or so. This is quite frustrating. I use CR2 files almost exclusively, written from a Canon 5D.
Any ideas or workarounds for this behavior?

I was getting this all the time with 1.5, I have not seen it yet with 2. I think it's a memory thing, it happens more quickly if I am running Safari and other stuff. Sometimes quitting Aperture then starting again does the trick, more often shutting the machine down and rebooting clears it. I also have some very large tiff's in the library, Aperture can't (I've not tried it in 2 yet) cope with them, always the unsupported error message. These files are between 300mb to 1gig, sometimes it justs hangs on to the 300mb but mostly not. By the end of the day it was a real problem, I could only export images 2-3 at a time, if I tried to email 10 low res I would get either an out of memory warning or unsupported etc.
Something holds onto the memory somewhere either in Ap or Safari or all things running.
Kevin.

Aperture 2.1.4 - 'unsupported image format'

Aperture has suddenly gone haywire. All photos apparently lost as they all disappeared and 'unsupported image format' appeared for each one instead - but at the same time they are all showing in the thumbnails at the foot of the screen. They are all JPEGs. So I reinstalled the program, etc and now all photos reinstated except for all scanned images (from various Albums) and a few ordinary photos from one Album. Those exceptions are all JPEGs. I have tried the possible solutions on Apple's 'Aperture 2: Troubleshooting Basics' page but they do not help. Some, but not all, of the missing photos will also not appear when I go into iPhoto and go to File - Show Aperture Library. But some do. Does anyone have any ideas? Thank you.

Thanks. The short answer is No. The best situation is from the most recently reinstalled version of Aperture where the result is as described in my previous post. Older versions all seem to be corrupted in the way I described.
A longer answer involves another problem I had. I add geo metadata (probably the wrong term!) to my photos so that, when imported to a mapping program, they show where they were taken. Then, when I put those photos on my iPhone, the mapping feature (Places) also showed where the photos were taken. But then, without warning, all this data was lost from the phone and the mapping feature no longer worked, although it continued to work on the computer. I asked the Genius people at an Apple store about this, but they had no idea and could not help. Now, in respect of the photos restored in Aperture where the 'Unsupported Image Format' message no longer appears, the feature has started working again on my phone.

Error message "unsupported image format" over red screen

Working my way through a project making corrections to a series of jpegs, when the image preview disappears and turns red with the error message "unsupported image format" in small print over the top, the thumbnail is fine and I know the image to be fine. Move on to the next 2-3 images all with the same message and then the App hangs.
Force quit and relaunch Aperture and the images are ok again.
I am assuming that the previews are corrupting and causing this. Oh the app has been hanging intermittently throughout he day, I have trashed both the pref's and the App support folder, but still I get the spinning beach ball.
Any thoughts?
Tony

I just noticed a similar problem. But for me it seems to be only for images referenced from my iPhoto library. I have not seen it yet on images imported directly into Aperture. If I click on a folder of images they appear fine at first, but if I just leave it displaying the first image after a few seconds the image disappears and displays the "unsupported image format" message over a red screen. Or it may display a random icon from somewhere in the application. And then the preview images start changing. Sometimes they change to what looks like system or application icons (arrow, the ratings "star", a printer icon, etc.)
Peter

Camera RAW support 2.2 update and Nikon .NEF unsupported image format

Hi,
I Use a Nikon D2x and only take raw images (.NEF file)
After I update from RAW support 2.1.1 update to RAW support 2.2 update, all my raw image file (.NEF file) taken before 13th September 2006 ! would not display - In the Aperture program, if i navigate to a project / folder and clicked on a thumb nail in the browser, I get a magenta / cyan screen showing in the main viewer panel with unsupported image format. ?
This is my worst-case scenario ! - I have entrusted Aperture with all my digital images (all raw .NEF) images taken before 13th September 2006 are un accessible with camera RAW support 2.2 update installed !
I have deleted (the 2.2 update) “from” System/Library/CoreServices/RawCamera.bundle and reinstall the RAW support 2.1.1 update.
* NOW I can now see all my raw Nikon .NEF images and they are now all fully functional again *.
Their is a problem with the Apple digital camera RAW support 2.2 update, it rendered the Aperture program useless to me for my older .NEF image/files (as above).
This requires a fix ASAP
Martin

Thankfully, I wasn't affected by the issue given I'm currently with Canon. There have been Canon woes in the past though.
On a side note, I never update anything until it has been out for a few weeks just to be sure. Because Aperture is such an integral component of my studio and business, I make sure everything always works before making any updates or changes - including upgrading cameras.
I'm sure the next update will fix the magenta issues.
Best,
CD

Aperture 2, OS 10.6.4, and Pentax K-x, creates unsupported image format

Upgraded from 10.6.3 to 10.6.4, and started getting the "Unsupported Image Format" problem in Aperture again for my RAW DNG files from a Pentax K-x.
The previous fix was to remove the Raw Compatibility Upgrade, and reinstall the 3.0 version. (3.03 was the installed version after 10.6.4).
Doing this, I was able to view my images, but they show up as only 250 x 170 pixel images in Aperture metadata!
File size is what it should be (~10MB), but they are dinky little images. What the heck?!!!
Any ideas what's going on here?
I would upgrade to Ap 3, but still see tons of people reporting problems with it supporting Pentax, especially color shifting of RAW images after upgrading.
Suggestions appreciated!
db

Hi David-- thanks for your advice. I have been looking into it further and it just gets more confusing. I am able to open all of these DNG files in Photoshop so the problem seems to be with some combination of the K-X, OS 10.6.4 and Aperture 2. I have gone so far as to purchase Aperture 3 but haven't opened the package yet. After hearing about your experience (not to mention the thousands of other complaints about Ap 3 performance I've seen) I think I'll take it back and make the switch to Lightroom 3. Lightroom's features may not be quite as good, but at least it seems to be stable and I imagine it will be able to read the DNGs since Photoshop does. I just don't have the energy to be constantly patrolling the state of my photo management program!
I'll keep you posted on my experiments with Lightroom.
Thanks again.
-Baz

"Unsupported Image Format" malloc error BUG

I've been having this issue for weeks now; not sure what triggered it, but lately, it happens after editing somewhere between 20 - 50 photos. It happens with files from my Nikon D1, Nikon D70, and Nikon D300. It happens to both RAW files and JPEGS.
The issue is, while going through a project, performing edits to the photos and then moving to the next one, after doing a set of photos, eventually, Aperture will give me the dreaded burgondy "Unsupported Image Format" in the main viewing window. That error will pop up for every photo, until I fix it, by quitting Aperture and restarting it; once I do that, the problem goes away, until it pops up again in another 20 - 50 photo edits.
When the error does occur, something similar to what is below gets written to /var/log/system.log. This is most definately a bug in Aperture. Obviously not everyone is running into it, but Google tells me that enough people are hitting it, so there is obviously some combination of software and hardware configurations that causes this bug to trigger. There is a memory allocation bug in Aperture. The below messages make that statement indisputable. Apple, please fix this!
May 17 09:49:01 sklarbook Aperture[17310]: Aperture(17310,0xb0cda000) malloc: * mmap(size=48848896) failed (error code=12)\n* error: can't allocate region\n* set a breakpoint in mallocerrorbreak to debu
g
May 17 09:49:03: --- last message repeated 1 time ---
May 17 09:49:01 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: Aperture(17310,0xb0cda000) malloc: * mmap(size=48848896) failed (error code=12)
May 17 09:49:01 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: * error: can't allocate region
May 17 09:49:01 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: * set a breakpoint in mallocerrorbreak to debug
May 17 09:49:01 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: Aperture(17310,0xb0cda000) malloc: * mmap(size=48848896) failed (error code=12)
May 17 09:49:01 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: * error: can't allocate region
May 17 09:49:01 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: * set a breakpoint in mallocerrorbreak to debug
May 17 09:51:27 sklarbook Aperture[17310]: Aperture(17310,0xb0cda000) malloc: * mmap(size=48848896) failed (error code=12)\n* error: can't allocate region\n* set a breakpoint in mallocerrorbreak to debu
g
May 17 09:51:33: --- last message repeated 1 time ---
May 17 09:51:27 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: Aperture(17310,0xb0cda000) malloc: * mmap(size=48848896) failed (error code=12)
May 17 09:51:27 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: * error: can't allocate region
May 17 09:51:27 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: * set a breakpoint in mallocerrorbreak to debug
May 17 09:51:27 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: Aperture(17310,0xb0cda000) malloc: * mmap(size=48848896) failed (error code=12)
May 17 09:51:27 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: * error: can't allocate region
May 17 09:51:27 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: * set a breakpoint in mallocerrorbreak to debug
May 17 09:51:46 sklarbook Aperture[17310]: Aperture(17310,0xb0637000) malloc: * mmap(size=35876864) failed (error code=12)\n* error: can't allocate region\n* set a breakpoint in mallocerrorbreak to debu
g
May 17 09:51:52: --- last message repeated 1 time ---
May 17 09:51:52 sklarbook Aperture[17310]: Aperture(17310,0xb0cda000) malloc: * mmap(size=48848896) failed (error code=12)\n* error: can't allocate region\n* set a breakpoint in mallocerrorbreak to debu
g
May 17 09:52:03: --- last message repeated 1 time ---
May 17 09:51:46 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: Aperture(17310,0xb0637000) malloc: * mmap(size=35876864) failed (error code=12)
May 17 09:51:46 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: * error: can't allocate region
May 17 09:51:46 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: * set a breakpoint in mallocerrorbreak to debug
May 17 09:51:46 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: Aperture(17310,0xb0637000) malloc: * mmap(size=35876864) failed (error code=12)
May 17 09:51:46 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: * error: can't allocate region
May 17 09:51:46 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: * set a breakpoint in mallocerrorbreak to debug
May 17 09:51:52 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: Aperture(17310,0xb0cda000) malloc: * mmap(size=48848896) failed (error code=12)
May 17 09:51:52 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: * error: can't allocate region
May 17 09:51:52 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: * set a breakpoint in mallocerrorbreak to debug
May 17 09:51:52 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: Aperture(17310,0xb0cda000) malloc: * mmap(size=48848896) failed (error code=12)
May 17 09:51:52 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: * error: can't allocate region
May 17 09:51:52 sklarbook [0x0-0x279279].com.apple.Aperture[17310]: * set a breakpoint in mallocerrorbreak to debug

Make sure you use Aperture's "send feedback" to report this bug. Apple doesn't necessarily read these forums on a regular basis (see the TOS); they are user-to-user forums.

Aperture 2+D5100+.NEF(RAW)/JPG=Unsupported Image Format

First off, I am new to all this...
But anyway....Last night, for the first time, I imported images directly from my Nikon D5100 memory card onto Aperture 2. (Yes, I know there is an Aperture 3. I am just trying this one until it is something I decide I want to put the money in to...then I will get Aperture 3.) It appeared as though everything was going well because I could see the thumbnails/ previews along the bottom in my browser. So, I went ahead and deleted the images from my memory card. Then, when I clicked on an image to edit it in the viewer, I got a red screen with white writing that says "Unsupported Image Format." Boo! Is there ANYTHING I can do to recover my images? And secondly, is there anything I can do to prevent this from happening again?
A few suggestions from looking around online that I have tried:
***Opening Aperture while holding down Opt+Command and then selecting: "Rebuild Now" and also the "Consistency Check" buttons.
***Opening: Finder- Library- Preferences- and then deleting com.apple.aperture.plist
The only change from doing all that is now my thumbnails don't appear- instead it just appears as though they are loading...
Again, working with Aperture 2, camera is a Nikon D5100, image format is both RAW (.NEF) /JPEG, (only the RAW file is showing up) and "Unsupported Image Format" message appears when I click on image and try to edit in the viewer.
Thanks for any help or suggestions!
Egrubbs

The D5100 requires Aperture 3 see http://www.apple.com/aperture/specs/raw.html

Aperture gets "Unsupported Image Format" on some JPG images

I'm using Aperture 1.5.2 "trial" on PB 15" with OSX 10.4.9. I am getting "Unsupported Image Format" on about half of the 15,000 JPG images that I have on my HDD. But not all of them - even though all images come originally from my D100 camera and are JPEG images. These are all JPEG images with extensions JPG, jpg and jpeg. No RAW or TIFF.
My images are currently catalogued in iVew MediaPro [IVMP] and I'm interested in switching to Aperture. So I've gotta find a way to import those photos.
Here's a clue: When I put the CF card from my camera into the computer yesterday and tried to add the images to Aperture it reported that all the images on the CF chip were "Unsupported Image Format." I was not copying the images - just leaving them im place. As a test, I then used IVMP to import from the CF card onto the HDD, into a directory. Afterward, I fired up Aperture and it could properly index and display the files. I noticed that the pre-existing images that are viewable in Aperture all have previews when viewed in the Finder. Also, they've all been imported from CF to HDD using IVMP, so there may be some processing going on there. I also tried reading files into Photoshop and rewriting them with previews, which I verified in the Finder, and those files also can not be viewed in Aperture. So it is not just a question of having a preview - it's something else about the files.
Another clue - when I shoot more than one CF of photos in a day, I use IVMP to import the first CF batch, and those are always visible in Aperture - but IVMP doesn't let you import two batches on the same date (pretty goofy huh?) - so to import an additional batch I have to (Finder drag-drop) copy from the CF to the HDD into a directory - and those files have no previews, have not been imported thru IVMP, and interestingly are not viewable in Aperture.
So I'd have to conclude that iView MediaPro is doing something to "tame" the files' format that makes them acceptable to Aperture. But I want to dump IVMP, so there has to be some other way to make these D100 files acceptable to Aperture.
I either need to "fool" Aperture into reading the files or find a way to tweak 'em and make 'em acceptable to Aperture. Any ideas from other iView/Aperture users out there?
PB 15" Mac OS X (10.4.9)

Good idea, but I checked it... I mentioned reading right from the card in order to illustrate that the JPG files are "unsupported image format" even *right from the camera*. *In fact* the CF is not the differentiating factor between renderable and non-renderable. The real factor is whether the files went thru iView Media Pro or not. Files that were drag-dropped from the CF into a folder are not renderable by Aperture and files that were imported first (from the CF or from another folder) thru IVMP into a folder are renderable.
Yesterday I confirmed again that GraphicConverterX does not fix the files if I import and then rewrite with additional options turned on. It also sees the same IPTC data and EXIF on both a "good" file and a "bad" file. Identical. I also fixed the OS9 creator and filetypes so they're <none> and that didn't fix anything - some good files and some bad files have this configuration.
Ah another COOL THING - I just loaded a CF card into the computer and brought up Aperture - it immediately recognized the card and showed me two previews - one for a NEF (Nikon RAW) and one for a JPG. The previews looked fine. I clicked to have it import the photos. Once imported, the NEF looked OK, but the JPG had a grey preview and then "Unsupported Image Format" on the large version. I think this confirms the file format is a problem, but then why was Aperture able to gen a preview when the file was on the CF chip but not after it was copied to the HDD?
I double-checked this by copying in Finder drag-drop from the CF card to the HDD and then importing the same two photos (NEF and JPG) from the HDD, and indeed the NEF was renderable and the JPG was not. For me this confirms that there's something about the file format that Aperture can't deal with.
I then imported the same two files using IVMP (Media Pro) and as expected, both files could then be "imported" and rendered by Aperture. So IVMP is doing something that makes Aperture really happy.
In case someone can actually compare the two files - I have put up a "bad" and a "good" JPG - it's the same image from a Nikon D100, but one of them (bad) is right from the camera and the other (good) was imported by IVMP and somehow is acceptable to Aperture. Any intelligence that anyone can add based on these files would be useful.
http://fire.red7.com/aperture-tests/DSC_0070-good.JPG
http://fire.red7.com/aperture-tests/DSC_0070-bad.JPG
PB G4 15" Mac OS X (10.4.9)

Aperture 2.1.4 shows landscape JPEGs as "Unsupported Image Format"

I have just imported a few JPEGs from a Boots scan of some 35mm film I had processed there. All 7 portrait aspect photos are fine, but all 8 landscape format images come up as "Unsupported Image Format" on the maroon screen of death. The original scans from the lab are all landscape, and I viewed them all in Preview and rotated and saved the portrait images therein. I then imported them into aperture and adjusted the date and time metadata (as they show the scan date).
Now, the landscape pictures come up as thumbnails in browser, and show fine for a second whilst "loading" in viewer, then disappear leaving the maroon screen. I can view the pictures fine in iPhoto 09 through "show aperture library", and the exported original through iPhoto shows up just fine everywhere. I cannot export versions from aperture, and "export master" exports something to the desktop that I cannot open in preview. The metadata for the landscape and the portrait pictures are identical (740 KB, camera comes up as "SP-2000") except the pixel size dimensions (1840 × 1232) are naturally inverted.
Any ideas anyone?

Thanks. The short answer is No. The best situation is from the most recently reinstalled version of Aperture where the result is as described in my previous post. Older versions all seem to be corrupted in the way I described.
A longer answer involves another problem I had. I add geo metadata (probably the wrong term!) to my photos so that, when imported to a mapping program, they show where they were taken. Then, when I put those photos on my iPhone, the mapping feature (Places) also showed where the photos were taken. But then, without warning, all this data was lost from the phone and the mapping feature no longer worked, although it continued to work on the computer. I asked the Genius people at an Apple store about this, but they had no idea and could not help. Now, in respect of the photos restored in Aperture where the 'Unsupported Image Format' message no longer appears, the feature has started working again on my phone.

Aperture - Unsupported Image Format

All of a sudden when trying to open images I have previously been able to open, I get a black box with a grey triange, exclaimation point in the middle od the triange and the message "Unsupported Image Format". This is happening on my 27" iMac and my MacBook Air, all updates are current for both OS and software. Has anyone else been getting this? Any solutions?

If it's just a single image, it could be a corrupt file. Unfortunately SD cards do occaisionally have issues. The image you are seeing at first is the embedded JPEG which it shows until it finishes processing the raw (or building it's own preview). So even if the raw is corrupt (and this is only possibility - it might be fine) you will be able to at least extract the JPEG using sometiming like the free IJFR app - instant jpeg from raw.
You can try 'Reprocess Original' and/or 'Update from original', it occasionally helps (I had 4 ORF files in a batch show as unsupported which were then fine after 'Reprocess Original'.
Also you cn try relocating the original, say to your desktop (which makes it a referenced file), then delete in Aperture and empty the Aperture trash but without deleting the referenced file (the one on your desktop). Then you can try importing it again from your desktop.
Andy

Twist on Unsupported Image Format message

I have Aperture on my G5 tower as well as my Macbook Pro. A year ago I copied a project from the G5 to my Macbook Pro. The project was fine on both computers. Two days ago I was in Aperture on my G5 and I noticed that not all but some of the pictures in that project threw up the magenta screen with the Unsupported Image Format message. Interestingly, those very same pictures on the Macbook Pro also come up with that message.
Now, understand that these files have been separated for a year. Both Aperture programs are up to date, both computers are up to date. Both have Adobe CS3 products installed, all up to date.
To me this has nothing to do with file corruption or anything to do with editing time or memory as suggested in a number of places in various posts. An update from Apple has caused this. No way two computers could corrupt the same files at the very same time.
If anyone has any advice or insight beyond restarting Aperture or the computer I would be quite happy to hear it. So far my searches have revealed nothing.

I also had the Unsupported image format with the maroon background today. I have a Nikon D80 but all of my images are .jpg and I don't use raw .nef format. Working on a project all afternoon an early evening and SUDDENLY started getting 'unsupported image format' messages on the red background. I know the files are not corrupted because I had been in and out o many of them all day long. Had a similar problem with 1.5 and phoned Apple support and was told to restart Aperture holding down the Option - Command keys. A message appears to rebuild the library. Took about an hr for 40,000 images (24"3.0 iMac with 4 GB) and all is fine again.
If I remember correctly, Aperture keeps track of everything in a database of some sort and sometimes it gets corrupted. The uif messages start to appear and quickly get more frequent. Rebuilding the database resolves the problem.
Worked for me today, hope it works for others.
Cheers,
Dave
PS. How come someone from the Aperture support team doesn't post this???
Also, searching for "unsupported image format" in the help menu or the aperture support page doesn't immediately display this solution. Instead you have to hunt through the forums?

Unsupported Image Format (again)

Similar Messages

Maybe you are looking for