Unsupported Image Format help! - jpeg

I do not know of any easy fix for this kind of situations. Mac OS X is usually very clever when it comes to moving files around on the same volume, but when you move/copy to other volumes it may become dizzy.

I would restore your latest vault into the library. Make a back up of the original, of course, in case someone comes up with a better idea later on.

OK-- I figured it out. By default I had both SMB and AFP set up on my NAS hard drive (a Thecus N5200). When both are active, SMB is preferentially used by leopard. As such, when I transfered my file from the original hard drive to the NAS drive, it was done VIA SMB. It appears that SMB does NOT support the "/" character in a file name, while the mac and SMB natively DO. Since Aperture's library uses folders inside the project package that look like:

2007-04-20 @ 10/52/23 AM - 39.apimportgroup

Where the number in the middle (in this case 10/52/23) equals the TIME of import, this does not play well with SMB. As such, when the library is transfered over, it CHANGES the "/" characters to a character I have never seen before-- a box with an X inside it. When initially looking at the file, it appears that it just erases the "/" characters, but in fact when you go to change the name of the file, this strange character shows up.

It was a pain, but I went through and manually changed every one of these characters back to a "/" an ever since then, the entire library works perfectly. Very odd, and it was a pain to fix, but better than losing all of my images.

Actualy, I am quite surprised that Apple chose to use these kind of characters in the database in the first place. They could have anticipated that people would be sharing an aperture library over a network, and there isn't any good reason, as far as can tell, why those characters had to be chosen for the database format. Why not use another dash, comma, plus sign, etc... anything but a "/"

And I also find it odd that Leopard mounts disks as SMB when both smb and afp protocols are available. But, who knows, maybe this is just a bug. Had I been diligent, I would have immediately disabled SMB.

Klaus Shuler

Message was edited by: kshuler

Same problem here with Aperture 2.1 after working with images 30-40 minutes.
Images are jpg's from a Canon 40D SLR camera.
Unsupported Image Format on reddish background.
A restart of Aperture solves the problem for another 30-40 minutes before another jpg creates the same problem.
And none of the pics have been edited.
Another problem with Aperture is the big slowdown in speed after 20-30 minutes. I have to restart Aperture 5-10 times a day, and the laptop 2-3 times a day to keep working.
As bad as my Vista days - not impressed at all.

New system, all updated, 4GB Ram. Aperture running alone to give it all of the system resources.
What's wrong here Apple? Memory leak?

I get the same problems after using Aperture 2.1.1 for some time. It happened with earlier versions too and I believe it has to do with the amount of available RAM. If Photoshop CS3 is openend at the same time, I feel, the error occures earlier. I have 9 GB RAM but use TIF 16 bit for editing in Photoshop with 21 Megapixel files for about every second image. The red screen and "Unsupported Image Format" first occurs on these 16 bit TIFS not on the RAW files.

In my opinion Aperture runs out of memory while trying to render the previews of the 16 bit TIFs (or PSDs, there is no difference, it happens with bis PSDs too).

Closing Aperture and Photoshop and reopening again ALWAYS gives me back all images, which went red. But the problem comes again after some time.

Maybe we should start a list like this: Available RAM on the computer / which programs were open / which size do the files have / how often does the problem occur

This may be the beginning of this list:

9 GB / Ap + PS CS3 + Apple Mail / TIF 16 bit 21 Megapixel / after working on about 20 of these images.

It would be great, if anyboday having this problem could post his own data for this list. I am sure this will help to locate the problem.

Thank you

Wolfram

Hi Wolfram.

With your setup there is no excuse what-so-ever for Aperture to run out of available memory, is there? Buggy software comes to mind.

4GB / Aperture / Mail / jpgs only, 3-4MB in size / after 30-50 minutes

16Gig/ Mac Pro Dual Quad/Aperture 2.1.1./Tiff 13800 × 7800 65mg

1st image viewed no problem, second crashes app.

No problem with iphoto, lightroom. Seriously considering moving to Lightroom, as all my current work is for large posters and I like to be able to catalogue all my images.


Apple help !

Wolfram, I have the same problem with the unsupported image message after using Aperture 2.1.2 for some time. These are all raw images, Canon CR2s. After working for a few hours, I will suddenly get the maroon unsupported image screen for an image, and for every other image I have not yet worked on. The only cure is to quit Aperture and relaunch.

I think your memory leak theory deserves some investigation by Apple. Perhaps it also accounts for the general sluggishness I am finding in working with my raw files. I recently moved a 6000 image project from a library that had 17,000 files and put it in its own library. I got a very minor decrease in the duration of the spinning pizzas that occur every time I use the sliders in Aperture. I don't automatically generate previews, so that is not what is causing the sluggishness.

Here is my configuration: MacPro octo (8 core) 3 GHz, 8 GB RAM, Aperture 2.1.2, OSX 10.5.5. I also use PSCS3, but I only launch it when I need it. My CR2s are from 10 megapixel Canon DSLRs, the IDIII, and the 40D. I can usually work for a couple of hours before I get the unsupported image message. I can't help but think that the 8 processors in my computer and the 8GB of installed RAM I have should be more than adequate to keep Aperture humming along without problems.

Shirley

I have the same problem with exactly similar behavior. I use a Canon 40D with CR2 and imbedded JPG. The problem is temporarily solved by restarting Aperture, but recurs again after 30-60 minutes editing photos. I updated to 10.5.6 today and the problem persists. I have a G5 dual 2.5 with ATI Radeon X800 XT graphics card, so it appears that this occurs with different graphic cards and thus is probably unrelated to the graphics card. Incidentally, Aperture 2.1.2 appears to be noticeably faster after the 10.5.6 update. If it is not the graphics card, file type, or camera brand, what is it?

2 GB/ Mac Mail + Safari + iChat + Calendar + PSCS3/ Compressed RAW files from Nikon D3 approx. 9mb / after working on 10-12 photos

Rebooting solves the problem. I typically reboot 15-20x per day (getting a little obnoxious). I wrote a post on this same thread back in March, I believe. At that point I was on a Mac Pro laptop with JPEGs. After I lost an entire event, I scrapped Aperture and went back to an Adobe based workflow. In October I started shooting RAW and with terrible conversions in Adobe, I attempted Aperture again. This time on a quad core Mac Pro. For two and a half months, no problems. Now, it's daily. Memory leak seems like a plausible theory.

I use a Canon 40D and shoot in everything from full RAW, .jpg and sRAW. Just recently, I started to get the "unsupported image format" on just a certain group of images. I took it into the Genius bar and they were stumped. One of the guys in the store tried helping me by showing me the "Consistency Check" and "Rebuild Now" options. I did both, and now some of the images are coming up as just a small grey preview while others are are still coming up with the "Unsupported Image Format." I have tried various restarts of both Aperture and my system. None of them have helped. I think I will try one more restart before I put off the project so I don't want to through my computer through the window. Anyone have any ideas?

this is now happening to me as well, did anyone get an answer for this?¿

Nope, no one helped. I am still hoping for some help.

I neglected to mention that after I did the rebuild and consistency check, it happened with more images. I thought that it was limited to my sRAW files, but my last group of RAW images are not working either.
HELP!

Trying out Aperture for the first time. I only have six images in the library, one of which is "Not supported". It worked fine yesterday. Restarting Aperture does not help. Color me unimpressed. Off to check out Lightroom.

I have a Canon 50D and was having the unsupported image format problem, which took me entirely too long to figure out- but here is what i do know now.

I just did some shots with all of the different settings. So now I know why the images weren't working before.
On the camera there are 3 different RAW settings- RAW, sRAW1, and sRAW2.
The normal RAW- which is the largest one works every time and with JPEGS too.
But both of the sRAW settings (1&2) are always showing as unsupported in Aperture.
I’m glad I understand that now, thought you would like to know.