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.

Similar Messages

  • 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

  • Occasional Unsupported Image Format during import, why?

    Once in a while when importing from my camera (Sony A99) RAW format, I get the Unsupported Image Format on a few pics of the batch. It's random so I'm not sure when it would happen. The only way I find that will fix those images is launch aperture into repair "repair database". It's not a deal breaker as I don't lose any files but it's bit annoying and not sure why this is the case. Any ideas how to permanatly stop this?

    I see this regularly ( one or two files, every other time I import?) with the built-in SDHC card reader on my rMBP.  What I do is simply note which files are corrupt, immediately re-import those files, and then delete the corrupt ones (sorted by date, they are side-by-side with their non-corrupt twin).  Iirc, only once have I had to re-re-import a file that failed to import properly on the first try.
    I reformat (in camera) each card every time I fill it (and recommend this practice), but IME (casually observed and not tested) the problem originates with the built-in card reader, and not with the card.  How are you importing?
    Perhaps only a coincidence, but I use Sony cameras.  I don't recall this ever happening with a CF card though.  (The rMBP does not have a CF reader.) 

  • 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.

  • When I try to import raw files from my nikon d600 I get the message Unsupported image format, When I try to import raw files from my nikon d600 I get the message Unsupported image format

    When I import raw files from my Nikon D600 into Aperture I get a tryangle sign with "unsupported image format"

    Latest Adobe DNG converter (7.2) DOES indeed convert NEF pictures coming from a D600.
    Head up to Adobe's website and download the app.
    You'll only miss the focus information (focus distance and focus sensors used), but you'll be able to work with raw and not rely on jpg only!

  • D800 Raw files produce occasional 'unsupported image format'

    Is anytone else having problems with some Nikon D800 raw (NEF) files in the latest Aperture version? Most of the files are fine, but some are 'Unsupported Image Format'. Aperture sometime shows them, then they vanish and are replaced with a grey triangle. Then randomly they sometimes come back.
    It seems to just be the Nikon D800 raws casuing this. Any thoughts on a fix?
    Thanks

    It is unlikely to be caused by the recent Aperture update because it started happening to me just a few days ago (Nikon D2x NEF/JPEG pix) and I have been using Aperture version 3.3.2 under OS 10.7.4 for a long time.
    Reconnecting the files in a referenced workflow has been resolving the problem for me.
    -Allen

  • 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

  • What's with the Keynote 6 file format?

    Uploading Keynote 6 files to our box.com storage environment (or to Dropbox for that matter) fails when done through a browser. In fact all browser uploads of Keynote 6 files destroys the file and makes it into a folder.
    I there ANY way around this except zipping all files? Is this "packaged file format" just folders? Seem totally bizar that Apple would choose a file format that no other file system or protocol recognizes as a file.

    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.

  • 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.

  • 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

    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

  • Aperture 3.5 cr2 unsupported image format

    upgraded to aperature 3.5 and os x 10.9 , when download raw files from my canon eos 1000d I can see the thumbnails but cannot edit the raw files , all that happens is that I gar a gray screen with the following unsupported image format - the raw format is an cr2 extension --can anyone help -thanks

    Nik just released an update...hopefully for Mavericks support. It appears to be fixing some of the forum user's issues so far.
    See: https://support.google.com/nikcollection/answer/4400822?hl=en&ref_topic=3001406
    Release Notes
    Updates to the Nik Collection are made on an ongoing basis. These updates may include bug fixes, performance enhancements, new features and additional hardware or software support. All updates will be installed to the computer automatically.
    Version 1.109 - December 11, 2013

  • Unsupported Image Format - Please Help

    Since upgrading Aperture to 1.5 all my RAW images (.CRW & .CR2) from my Canon 300D and 20D, initially show when I click them and then very quickly turn to a maron coloured box with the words 'Unsupported Image Format'. I am really worried about this as it's not just 1 or 2, but all my RAW images which is about 80% of my library. All JPG images are fine.
    I would be very greatful to hear some work arounds to this.
    Thanks

    Hello,
    It's not your RAM. Folks on quite a few forums have been reporting similar problems. As well there have been several threads on this forum of a similar nature.
    I've a similar, but different "Unsupported Image Format" error.
    I shoot Canon's 1Dsmk2 and 5D cameras, both of which put out .CR2 files, and both of which are supported by Aperture.
    So far Aperture has been able to open all of these.
    However, I converted quite a few of them to DNG files with the last version (Adobe DNG converter 3.4 I think - 3.5 is the current version so I'm guessing the last one was 3.4)
    Aperture is unable to open any of these DNG files. I get that same 1/2 second preview flash and then the error.
    All of these DNG files open fine with PS CS2, Bridge, Lightroom. They also appear correctly with other Apple Products - Preview and iPhoto [ 6.0.5 (316) ].
    So the problem seems to be Aperture specific.
    I've done some tests with the latest Adobe DNG converter (version 3.5). There are basically 4 settings that one can alter. Embed original, size of preview, compression, and to store the file as a mosaic or linear. If the "linear" option is selected, alone or in combination with any of the other options, then Aperture cannot open the file.
    If linear (in version 3.5) is not selected then Aperature seems to be able to open the files converted with all of the other options, either selected alone or in combinations.
    None of my DNG's converted with the last converter (3.4) had the "linear" option selected.
    Also, I've tried running a DNG created with v3.4 through the v3.5 converter to see if it would then open in Aperture, but this didn't work.
    I've tried rebuilding the library and the other fixes mentioned by others here - every other program except Aperture seems to be able to open these files.
    So, I'm hoping that there is a v1.5.1 out pretty quickly whicch addresses these image compatibility errors.
    Steve

  • "Unsupported Image Format" all of a sudden, with previously workable files

    Folks,
    I've got an issue that seems very strange indeed.
    Months ago, I bought a Pentax K20D. I also bought a 17" MacBook Pro and Aperture. Camera and Aperture played well together.
    I encountered the known issue with white spots on the image when using the 2-second timer for long exposures. I read about how the Pentax firmware update 1.01 changed the EXIF Make information, causing Aperture to be unable to read the K20D PEF RAWs. So I waited.
    When Aperture 2.1.1 was released (and I think the Apple RAW update), I installed both of those. When I heard through this forum that the updates fixed the problem, I also updated my camera's firmware and confirmed that it worked.
    So smooth sailing for a few months on Aperture 2.1.1, OS 10.5.3 (or .4, I forget), and K20D firmware 1.01.
    Then I bought a Mac Pro 8-Core with 10.5.4 on it. I sold the 17" MacBook Pro. I used the Migration Wizard to move my user account from one machine to the other, but did a fresh install of all applications. (I've been an Apple tech for the past 7 years, and have various certifications. I know the user transfer process isn't perfect, but it should have the following results... read on)
    Now, in Aperture 2.1.1 on 10.5.4 with all updates, PEF RAWs taken with K20D firmware 1.01 that were previously edited, manipulated, etc just fine on my MacBook Pro say "Unsupported Image Format" in a big reddish-black box when I try to view the master. If I switch to Quick Preview, it displays just fine, but is un-adjustable. Additionally, any NEW images I copy from my K20D show in the Import window as being 0x0 pixels (or occasionally 160x120 pixels) and will only show a tiny preview or "Unsupported Image Format." All PEF RAWs taken with K20D firmware 1.0 are just fine.
    So here's what I've done:
    1) Tested a fresh install of 10.5.4 on another HD in the Mac Pro. Installed Aperture 2.1, updated to 2.1.1. This should be perfectly clean. It gives the "Unsupported Image Format" error with any new images from my K20D. Copying the library from my other partition gives the same problems as described earlier.
    2) Tested a fresh install of 10.5.3 on another partition in a Macbook Pro. Installed Aperture 2.1, updated to 2.1.1. Applied the Apple RAW update and iLife enhancements. It gives the same errors as before.
    3) Tested a fresh install of 10.4.11 on another partition in a Macbook Pro. Installed Aperture 2.1, updated to 2.1.1. This worked perfectly for all PEFs and DNGs.
    4) Took a month-old backup (from when everything was working just fine) of my Aperture Library and loaded it into all of the above configurations. Same results!
    So what is the deal here? Aperture all of a sudden can't read images that it itself was able to edit a month ago? How come it works just fine in 10.4.11? This seems really messy. I have essentially lost a lot of the work I've put in.
    I can use DNGs moving forward, but my past work is now messed up, and the DNGs are almost 75% bigger than the PEFs!
    Anyone have any ideas for resolution or should I just call Apple?
    Message was edited by: MonsieurBon

    If it's any consolation, I had the EXACT same problem today; just opened Aperture 2 and my entire library of images shows "unsupported image format' -- the thumbnails are still intact but clicking on any image suddenly shows the red screen.
    Same situation, these images were previously editable and accessible. We had a power outage an hour ago and initially I thought my library had crashed, but I was not actually using Aperture 2 at the time of the outage so I don't think that's the case.
    Given the relatively sparse attention Apple gives to these forums, I don't expect there will be a quick response.
    I have Leopard 10.5.4 installed, I don't have access to another version of the OS to see if I can get it work. If I'm not mistaken, wasn't there a series of Software Updates recently? I click on these without really checking the apps that are affected; could Aperture have been one of the apps 'revised' by the recent update?

  • Why do G3 raw files show as "Unsupported Image Format" in Aperture?

    I am moving towards shooting in raw, and as an experiment I imported some sample raw files from the publicly available text images on the Photography Blog. When I try to look at these images, I get a black screen with a warning triangle and the message "Unsupported Image Format". This happens for all the different raws, including some G3 raw files (.rw2). Oddly, it can read the EXIF metadata and has all the information about shooting settings etc. If I import the same files into iPhoto, it displays the images properly and allows editing, etc.
    I have a workaround, which I've also tried with my Fuji X10 raws (still not supported on MacOSX), of running them through the Adobe DNG converter, and then looking at the dng files which seem to work fine. But it's a pain.
    This has to be one of those simple "D'oh" things, but I can't see what I'm doing wrong!

    Thanks Leonie, the second part revealed that I have been an idiot, although the behaviour is still surprising. The folder has a mix of DMC-G3 raws, Fuji X10 raws, and DNG files produced from both. For the Fuji X10 files, the DNGs produce images and the raws produce the "Unsupported file format" message. The latter is not surprising, the former a little surprising (as I've heard that DNGs only work when the associated raw works). The last two remarks don't directly address my problem (or perceived problem), but they perhaps set the frame for my expectations.
    For the G3 files, when I look at it more closely, the G3 raws DO display correctly, while the G3 DNGs give "Unsupported file format". I had managed to fool myself into thinking it was the other way round (Aperture does rather hide the full file name).
    So I was completely wrong, Aperture does support DMC-G3 raw, it's just it's DNG support that's a bit weird. However, it's on my side if I need to use X10 raws (via the DNG step). In fact so far I've given up the latter, as the noise levels are so much greater than in Fuji's in-camera JPEG conversion.
    So, thanks very much for your help. Now I remember the first rule of system support: never trust what the customer tells you! (I know you're not really customer support, but I guess the same rule applies.) Thanks again

Maybe you are looking for

  • Reg:New GL Concept

    Hi Gurus, What is the Difference Between Leading Ledger and Non-Leading Ledger conecpt in New Gl concept. regards JK

  • WIJ20005 error occurred while editing the WebI document

    Hello Everyone, An error occurred while editing the WebIntelligence document. The error don't occur when you run again. Do you know the cause of this problem? Please give me advice how to investigate. Error message is as follows: The current request

  • Guidance for Database 11g Administrator Certified Associate Exams

    HI: I post this question on Database users group and was advised to post here. I would like to get your guidance how I am going to prepare myself for the two exams 1Z0-051Oracle Database 11g: SQL Fundamentals I and Oracle Database 11g: Administration

  • How to find machine is Big/little endian?

    Hi, Can any one tell me that how to find machine on which we are working i.e. Big/Little Endian in using java? One of my friend told me that in C Programming we can find this by using following code: #include <stdio.h> #include <arpa/inet.h> int main

  • Flex 4 QTP Add In - Nested Flex Component Disabled by Automation Library

    QTP Version 10 QTP Flex 4 AddIn Automation Library: Compiled We have the latest QTP flex add-in installed on both QTP and the application being tested (a flex application). The QTP flex plugin is working fine on pages where the flex code is built as