How I fixed the "unsupported image format" error for RAW files

After deleting the .plist file stopped working, I decided to go ahead & reinstall Aperture and...voila--problem fixed. RAW files are again displaying without any trouble (just like they used to!)
G5 2.3DP Mac OS X (10.4)

Just an update. Restarted computer and attempted rebuilds of iPhoto library a couple more times and finally files and photos mostly recovered, except for those I had tried to open. Aperture seems to have a problem, or a host of them, dealing with RAW files, and there is no update yet for the Sony RX1R for Aperture or iPhoto. Lightroom 5, on the other hand, seems to work great with these files directly, so that will be where all photos go for now. Will iPhoto and Aperture just become old archives? It is so infuriating that Apple does not allow for simple importing and exporting compatibility with such an excellent program as Lightroom 5 just to protect their somewhat poorly supported Aperture. I've been a staunch Apple supporter and user since the 80's, but having more doubts about the direction this company is taking.

Similar Messages

Canon G7x and unsupported image format icon with RAW files.

When RAW files downloaded from Canon G7x get "Unsupported Image Format" message. Using iMac with 10.9.5 and Aperture 3.5.1. This is a new camera and is not on the supported list. Is there a way around this? Now that Aperture is static will new cameras continue to be added to supported list?

The only way 'around' it is to upgrade to the required Aperture and/or OS version. So you will need to wait for that to happen. In the meantime you could shoot Raw+JPG, use the JPGs now and when (and if) the camera is supported (or you move to a different program) you will have the Raw files.
As for camera updates in Aperture, no one here can say what Apple intends, we;re just users here like yourself and even discussing this is technically against the TOU of these forums.
But I think it is safe to assume, as Apple will continue to support Raw processing and that the Raw processing is done at the OS level and they have said they will support Aperture at least through Yosemite's life cycle that any new Raw format added to OS X will reusable by Aperture. But that's only a guess.

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.

Unsupported image format error

Hey folks,
I've read several older threads on this topic and have not seen any new information. I am hoping there is a fix and someone out there knows it.
When I fired up aperture today I discovered that all of my images display with the dreaded unsupported image format error.
Thinking that my 215gb library had gotten too large, I tried to create a new library. Same result. When I import new images from my Canon 40D they show as a tiny preview and then quickly turn to the red message. It appears the raw files are not even imported into the library.... which made me think permissions. I repaired permissions and went so far as to set my ~/Photos/ to 777 ... still no dice.
I tried rebuilding my library - did not help
I have tried restoring from TimeMachine backup - no help
I deleted the plist and ~/Library/Application Support/Apreture - no help
I'm getting really worried that I have lost my library. I understand that the files are still there, but what about my edits and metadata. Seeing that this is a wide-spread issue is not helping my situation.
Any suggestions? Thanks in advance!

Good questions and thinking! I was vague about the chronology.
I first noticed the issue when I intended to import some images on my iMac which is home to my main 200+gb library. I never even got to the importing stage b/c I saw red, literally, when I launched the app.
I then created a new library and tried to import.
My final stage was to import onto the MBP, different machine, different library.
As for updates, I had applied the Dec. updates to the iMac but not the MBP.
While I know this will destroy my crediability as a troubleshooter (if you saw my images you'd know I have none as a photog ) I have realized that my Canon 40D somehow got switched into a custom mode during a few of the shots causing it to go into Canon's sRAW. I think that accounts for the behavior of the imported images on the MBP. It does not, however, account for my entire library turning red on the iMac.

"Unsupported Image Format" error ONLY on exposures longer than 4 minutes

When importing my photos to Aperture, I get an "Unsupported Image Format" error, but ONLY on images where my shutter was open for longer than 3 minutes or so. I'm looking at Aperture right now, and I've got one shot that was 184 seconds long - no problem. Next shot, 240 seconds - ERROR. I shoot everything in RAW and have no trouble with any of my "normal" exposure shots - thousands of them. Error shows up only with the shots where I've locked the shutter open for more than 4 minutes.
What the heck is up? I'm *assuming* it's a problem with Digital Camera RAW in OSX, as Preview.app is also unable to display the image. Photoshop CS6 and Lightroom 4 have no trouble with these images. Even in Aperture, I see a low-res preview of these "error" images for about two seconds before the error message replaces it.
Aperture 3.4.5
Digital Camera RAW 4.07
Nikon D600 (latest firmware) shooting .NEF RAW files, all images imported directly into Aperture from SD card in computer's slot
OSX 10.8.4

This problem, unsupported image format for long exposures, has been reported on and off for some time now.
Its not an easy search to phrase but for example I found this Aperture 3 will not recognize RAW files obtained from long ... at dpreview from a while back.
Sorry to say there are no resolutions that I can find. You might want to try and get in touch with Apple. They don;t make it easy to get software support even on there 'pro apps' but if you start with the normal Mac support number you might get to someone who can help.
Additionally you can leave feedback by going to Aperture->Provide Aperture Feedback. There is a setting to report bugs.
Sorry I don;t have anything better to report.
good luck, post back if you find out anything
regards

Raw Files Appear Deleted or Corrupted Suddenly in Aperture with Unsupported Image Format Error

I have been using Aperture 3, latest update, for the past year. Today, I tried to import new raw files from my new Sony RX1r and, as far as I can see, all raw files in Aperture give the "Unsupported Image Format" and alert symbol in the library where not only new files should be, but also ALL PREVIOUS RAW FILES. These files do no even show up as existing in the iPhoto Library.
This is, needless to say, distressing, as hundreds and hundreds of photos seem lost. Also, the files show a reduced pixel size and file sizes all go to .5 Mb. Some of the photos seemed to show up initially and look fine until I tried to open them, then they all either disappear or show the Unsupported Image Format instead of the opened file. I have tried rebuilding the iPhoto library, but no help.
I have looked in these discussions and see similar problems with Aperture. Perhaps, Apple has not made an update for the RX1r from the RX1 for raw files, but why should all older raw files now be corrupted, especially those recently made with my Olympus OM-D? Had no problem with Aperture until this disaster.
Please help.
William

Just an update. Restarted computer and attempted rebuilds of iPhoto library a couple more times and finally files and photos mostly recovered, except for those I had tried to open. Aperture seems to have a problem, or a host of them, dealing with RAW files, and there is no update yet for the Sony RX1R for Aperture or iPhoto. Lightroom 5, on the other hand, seems to work great with these files directly, so that will be where all photos go for now. Will iPhoto and Aperture just become old archives? It is so infuriating that Apple does not allow for simple importing and exporting compatibility with such an excellent program as Lightroom 5 just to protect their somewhat poorly supported Aperture. I've been a staunch Apple supporter and user since the 80's, but having more doubts about the direction this company is taking.

Unsupported Image Format after opening a file in Photoshop.

As from today,I am getting an unsupported Image Format after opening a file in Photoshop. I have made nothing more than as crop on the image. Why?

Ernie, I misread your post indeed. I never saw a option to send RAW files to an external editor. All I can see is the option to chose what editor and then specify if PSD or TIFF is used. I always use PSD, usually 16bit and in one other installation in 8bit (due to RAM restrictions there).
So Aperture creates the PSD version and PS edits that very version and saves it back into aperture. This is where I sometimes () get that "unsupported image" problem.
I think this also is what Mike does: select a RAW master, use an external editor -> Aperture creates a PSD or TIFF. I haven't tried the TIFF option , though.
My main point was: it all worked for a very long time and with the latest updates it is broken.
have a good day.
Roland

Unsupported Image Format Error- Damaged files???

I have been working a series of pictures (all .jpg) and doing some editing. Pictures were fine.
I went back in today and a fair number of pictures are now indicating unsupported image format and just show red. I can see the image in the thumbnail and briefly if I press "M" or click on the red background. The image will flash and then go back to the red-background with "unsupported image format" message.
What happened?
Can I get back to the Master somehow and save the image?
Are there certain edits you shouldn't try in a .jpg (vs. RAW) file??
I am afraid to do more work on the pictures for fear of damaging more files.
Thanks.

Hi Pittsburgh,
I don't have a quick fix except to go and find the master file. If you're using a referenced file, this should be easy enough; just navigate to the place you're storing all the masters. If you're storing all your master files in your Aperture library, this can be opened by right-clicking the library icon, and selecting "Show package contents". You might need to do this 3 or 4 times to navigate through the library, folders, projects and import groups etc, but it is possible to dig right down to the originals.
Once you've found the original file, how does it look? Can you open it with other apps? (Be careful not to save any changes to this file). Is the file there?
If you can answer this question, you'll give us more info to work with and a better chance at resolving your problem.
Of course you could look up this problem in your manual, or Time Machine back a while and restore either file or the project. But these are last ditch efforts (the manual especially
Andrew

How to fix the ''500 internal privoxy error''?

My brother had this error message today and can't use the internet, this error pops up every time he goes to any website. Anyone know how to fix this problem?

You would have to reset the Firefox connection settings.
*Tools > Options > Advanced > Network : Connection > Settings
You can select "Use the system proxy settings" or "No Proxy" in case the former doesn't work properly.
See "Firefox connection settings":
*https://support.mozilla.org/kb/Firefox+cannot+load+websites+but+other+programs+can

Anyone know how i fix the fm2011 xml parsing error? Urgently need to find a fix before holidays

Anyone out there know how i can fix the xml parsing error on football manager 2011? It's wrecking my excellent 4th season and even a delete and reinstall with new game hasn't worked

Have you tried Windows Update in the Control Panel?
Many times it will find the newest supported drivers for Hardware.
Just be sure to install everything not just the Important ones.
Let us know if this helps.

How I fixed the 'network host busy" error

I've been down for a day solving the "network host busy' error.
First, I had fits trying to hook up this HP to my system. Here's the thread on that:
http://forums.techguy.org/networking/858081-laserjet-4500-mac-osx-10-a.html
Once all that was done, it was working.
The system was off and sometimes unplugged over the course of the evening.
I could not get it to work again.
It turned out that somehow during the course of events, the ip number of the printer had changed. I printed out the configuration page directly from the printer's configuration menu, and reset the ip address to match the new one.
Protocol in this case was HP Jet Direct socket.
Hope that helps someone out there. It looks like there are a lot of people tearing their hair out over this message and that there is no one solution.

I just found a solution to this problem and thought I would post it here, too.
I'm using a HP Photosmart C7280 with 10.6.1
Ever since updating to Snow Leopard, I kept receiving the "Network host busy" message. Today, I thought I would try running the network wizard feature on the printer itself, and after the printer connected to my router and I entered the password, the problem fixed itself. No more error message.
I'm not sure if this will work for everyone, but it did for me. Such an easy solution for such a headache-inducing problem.
Message was edited by: TNTWhite

Random unsupported image format problems with .psd files

this is driving me nuts...just finished retouching 6 files....same as always...color, tones, basic stuff in aperture, images-edit with- CS4....work in PS CS4...come back in aperture...3 of the 6 files show the maroon screen...all files have several layers, all files are about the same size (500+mb)....this just does not make any sense at all....it also did not happen with 10.5/aperture 2.1.1 (or whatever the last 10.5 version was)....
bad enough that raw files aren't supported but are .psd files now also considered not professional enough for a DAM?
any input welcome.....

The only way 'around' it is to upgrade to the required Aperture and/or OS version. So you will need to wait for that to happen. In the meantime you could shoot Raw+JPG, use the JPGs now and when (and if) the camera is supported (or you move to a different program) you will have the Raw files.
As for camera updates in Aperture, no one here can say what Apple intends, we;re just users here like yourself and even discussing this is technically against the TOU of these forums.
But I think it is safe to assume, as Apple will continue to support Raw processing and that the Raw processing is done at the OS level and they have said they will support Aperture at least through Yosemite's life cycle that any new Raw format added to OS X will reusable by Aperture. But that's only a guess.

How to define the Structure and FCC parameters for EDI file format.

Hi All,
I have a EDI file(FTP)-->XI-->IDOC
the source file content is as follows
PR H01PHUPS
FH   SHP 0.0.5
H1   S0022323
W6   7752508853                     D
PT   1Z58R7070341111111
PT   1Z58R7070342222222
PT   1Z58R7070353333333
N1ST ZZ 142222
N3ST 8827 D OLD
N4ST MARCY
N1WH ZZ 2070
N3WH 401 QUALITY
N4WH HARRIS
DTENT20111206
DTSHP201112061754
N9LL BN20700033333333
N9NT
CD   CP      UPS
IT026
P1GD    VN A1111
PD   Product ID 1
QTORD000000000000010CA
QTSHP000000000000010CA
AM U 000000000000000000M
AM X 000000000000000000
LTLT 1112811111
AM G 000000000000000000
AM N 000000000000000000
AM TAX000000000000000000
AM SVC000000000000000000
AM COD000000000000000000
ST   00000000100000000010000000000000000000000000008500LB
Can any body share me how to declare the structure in DataType.
The first two characters in each record is constant , so this would be the keyfields right?
ex:- PR,FH,H1,W6,PT,AM,N1,N3,N4......
In Comm channel the FCC parameters
i need to go for fieldFixedLengths?
Thanks&Regards
Sai_SHA

Hi.
if you need to convert an EDI to XML you need to use an Adapter specific (e.g Seeburger) because PI doesn't support EDI files.
Also if you use a FCC , this configuration is for two level Header and Detail.
Check this.
http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/frameset.htm
Regards
Luis Ortiz

File format error for xml file

Hi!
We are trying to upgrade our SAP 4.6C to EHP4.
While "configuration roadmapstep", system asks us the XML file we have
produced via solman. When we enter the path of the file system gives theerror below:
The selected configuration file
("E:\downloadupg\SMSDXML_FKQ_20100917142727.656.xml") is not useable.
Reason: "File format error"
We have tried the txt file instead of xml file. The result was same.
You can find the details of our system.
4.6D EX2 32 bit kernel
windows 2003 64 bit OS
sql 2005 64 bit database software
We have to upgrade our system until that monday.
Please help us as soon as possible.
Best regards
Noyan Durna

Hello Noyan,
first, the official information: please refer to note #1022704 - for source release 4.6, the TXT file has to be used instead of the XML file. Otherwise, 'File format error' will occur as in your case.
But since you tried this option, you should turn your attention to the XML itself, which must contains entries that are not handled by function module OCS_GET_UPG_STACK_INFO in the 4.XX source systems. The function module only expects the entries [SPAM_CVERS], [PRDVERS] and [SWFEATURE]. Any other entries present on the file can cause an error.
Please check your file for other entries like [APP_SYSTEM], [SWFEATUREINC], [TECHUSAGES], [INITIAL_CVERS], [EXPORT_CVERS], and [DVD_SET]; this might be the cause of the error.
In order to workaround this, you can either edit the file and remove the invalid entries or recreate it (w/o this entries also).
Best regards,
Tomas Black

How to fix the Blue Screen of Death for iPhone 5S?

I have an iPhone 5S and I never got water on it, dropped it, or inflicted any kind of damage upon it. But one day when I turned it on it kept getting this blue screen and then restarting CONSTANTLY. This is referred to as the Blue Screen of Death (BSOD). Does anyone know how to actually fix this problem besides just restoring the phone (I already tried that.)

Hi ..
If you restored the iPhone to factory settings and it still won't startup correctly, make a reservation at a Genius Bar.

How I fixed the "unsupported image format" error for RAW files

Similar Messages

Maybe you are looking for