40D raw .CR2 files still causing 'Unsupported Image File' error

I have the most recent version of Leopard 10.5.1 and the newest version of Aperture 1.5.6 (2J2). Often times I open a RAW image shot with a Canon 40D (.cr2 file), I get the red screen "unsupported Image File" error message. Color mode is RGB. These were shot with RAW plus JPEG (not SRAW). It doesn't happen on every image shot at the same time in the same way, just some of the images. Can anyone advise why I would still be having this issue so long after Apple is offering 40D support? I've tried rebuilding my library data base to no success. I've tried reinstalling aperture. What next? Getting very frustrated, thanks!

hi, sazer01
sazer01 wrote:
I have the most recent version of Leopard 10.5.1 and the newest version of Aperture 1.5.6 (2J2). Often times I open a RAW image shot with a Canon 40D (.cr2 file), I get the red screen "unsupported Image File" error message. Color mode is RGB. These were shot with RAW plus JPEG (not SRAW).
I use Nikons and sometimes get a message like that. This might not be Aperture causing this. Blow out the connector holes on your memory cards and pins inside the cameras where the card connects. If the error is on the same frames all the time reformat your card a couple of times before using and make sure the card is seated properly. Don't turn off the camera immediately after taking the shot but let the camera finish the process of writing the photo frame onto the card.
Have you opened the frames in Preview to check if it see it?
victor

Similar Messages

  • When I submitted my iPhoto book to Apple, an error caused the  image file to be unreadable or unprintable,why can anyone help me please

    when I submitted my iPhoto book to Apple, an error caused the  image file to be unreadable or unprintable,why can anyone help me please:)
    what I did with my system was following:
    1. Update your software.
    2. Restart your computer.
    3. Make sure all applications are closed.
    4. Open iPhoto or Aperture.
    5. While all other applications are closed, preview your print product as a
    PDF.
    6. Resubmit your order. 
    and still my PDF ibook file looked like my photos were scratched across the photos. Please help:)
    Thank you
    CJ

    Yes me too!!
    I thought that I had done someting wrong.  The first time it was my first attempt so I did not preview the photobok (did not know this trick).  When I did the cover photos were completely ruined with lines and code.
    The second time I changed everything and even made a different sized book - thinking my photo files were too big.  I dutifully previewed before buying the book and everything was fine.  Then a few days later got the usual e-mail message from Apple. When I previewed the project again ALL of the photos were corrupted.
    What to do - I need to get the photobook to friends to celebrate their engagement!
    If I saved the pdf then submitted this would that work??
    Any thoughts - I am working on a large project and do not want to go any further if all the work will be ruined on buying the book.

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

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

  • 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

  • Nikon D70 RAW files now get "Unsupported Image Format"

    Prior to March 12th, everything was working fine with my D70 Raw files. I now get the maroon "Unsupported Image Format" (USF) when I select the images that were previously fine. They show up for a fraction of a second before I get the error. I tried rebuilding the database to no avail. I can export the RAW files and open them in Photoshop so they are OK. Also now when I import from my D70 I get the gray box instead of the image and a letterbox maroon USF message, the EXIF data still imports and is associated with the image. Help. I did upgrade to 1.1.1
    Dual 1.8Ghz Powermac G5 2GB RAM Radeon X800 XT   Mac OS X (10.4.6)  

    Well, I can't really put my finger on it. I know for sure it happened post 1.1 upgrade, but it happened with 1.0 as well (I didn't do any troubleshooting when it first happened, just re-imported and it was fine.) The last time it happened it was the last 20 images on the original CF card, mostly in succession, but there were a few images that were still able to be read okay inside of that 20 image string. I reimported from the original card (thank God I had not erased yet!) and it was fine.
    At least I know to keep my originals outside of aperture, what a space wasting bummer! I don't think I have any bad RAM because I've been running for 2 years without any real problems... The minor problems have happened, I believe with very tough weather conditions (humidity) and I experienced problems on all my Macs and even at work on windows. Maybe it was sun flares or static electricity, I don't know. The other issue is that my a/c power dips to low voltage often and my UPS switched to battery. I have a better UPS which always outputs 120v even when things sag or jump.
    The only other thing I can possibly think of is that I have my Aperture library on a new Seagate 300GB drive that has only been used for images and sits dormant in my system except for scratch disk and Aperture. Actually, I did use it for about a month or two mirroring my boot drive with no errors, so I think the drive is good. Grr!
    Troubleshooting rare occurances without have access to trace level data *****! (At work we can take a trace dump from our equipment and the guys can see pretty quickly what happened, and if it is hardware or software issue.)
    To clarify, which Dual 1.8 do you have? The June 2004 one with only 4 RAM slots, or the 2003 one that was added to the original lineup with 8 RAM slots?
    Aaron

  • 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

  • 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 file" when importing RAW images from Olympus E-PL1

    When I try to import images save in RAW format on the camera, the images import but they can't be displayed (all I get is a warning triangle with the words "unsupported image format" below it, though in the import preview the images are displayed properly.
    EDIT: just noticed that the E-PL1 isn't listed as being supported, just the E-P1 & 2
    Message was edited by: drathquark

    Apple have just included RAW support for the Olympus E-PL1 with the Digital Camera Raw Compatibility Update 3.3 - iPhoto can now import RAW files from the E-PL1.

  • Canon 40D RAW (CR2) Files import

    I've Photoshop and Aperture. Cannot install Elements which would be my preference - so help needed here.
    Also - I use iPhoto mostly in the latest Apple OS, yet I cannot import Canon 40D RAW files. I get an error message saying they could not be imported - import failed.
    Help please.
    Freshacre

    Freshacre:
    Welcome to the Apple Discussions. What version of PS Elements are you trying to install? I've installed the PSE 6 demo without any problem.
    What type of files are you trying to import and from where?
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier) database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
    I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 6 and 7 libraries and Tiger and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

  • 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

  • DNG files labeled as Unsupported Image Format

    I have used the Adobe DNG Converter and LIghtroom 3 to convert some raw image files from a Fujifilm S100fs camera, and then tried to import them into Aperture 3.  In all cases, DNG files from this particular camera are labeled Unsupported Image Format, while DNG files converted from other unsupported cameras have been imported successfully into Aperture.
    I think this is clearly a defect in Aperture that should be fixed, and I would like to know how a user is informed by Apple that a behavior has been identified as a defect and put on a list of problems to be fixed.

    I can now add more details to my problem with Apple's treatment of DNG files originating from .RAF files created by the Fujifilm S100fs camera.
    I took this issue to the Adobe DNG Converter forum, to investigate whether the DNG Converter was creating a Linear DNG file from these originals.  I had read on Apple forums that the MAC OS would reject DNG files that were linear, and that this sometimes happens when the Adobe Converter encounters raw file parameters that it cannot handle, such as barrel distortion correction figures.
    I have established that these DNG files from my S100fs camera RAWs are NOT linear DNG's.  I found a helpful reader on the Adobe forum who had the tools and knowledge to look inside my DNG files, and ascertain that they were not Linear DNGs.
    So I have exhausted the possibilities that the MAC OS is rejecting my DNG files for a recognized valid reason, and I return to my opinion that this is an Apple bug and needs to be fixed.

  • Exist an easy way to convert base64 code in XML files into the original image file on forms

    I've made a form in lifecycle that will be distributed by email as a pdf, and submitted back to me as an XML file and then that data imported into the pdf form template to view the data. Issue is I have an "attach image" field on the form and in XML it gets written to a base64 encoded format. Is there convenient way to extract this code from the XML file so that I would have a workable jpeg image file that I can save and open in other apps? Thank you in advance!  -Robert Tampa

    I tried to make John Brinkman's sample working in reverse.
    This script will grab an image field's value and produce an attachment (png-file), which then can be saved to the hard drive.
    //Get Base64 data of the image field
    var b64Data = ImageField1.value.image.value;
    //Convert to a read stream
    var ReadStream = util.streamFromString(b64Data);
    //Decode from Base64
    var DecodedStream = Net.streamDecode(ReadStream, "base64");
    //Attach an empty image file
    event.target.createDataObject("MyExportImage.png", "", "image/png");
    //Update attached image file with stream data
    event.target.setDataObjectContents("MyExportImage.png", DecodedStream);
    //Show attachment pane
    event.target.viewState = {overViewMode:7};
    This works so far, but the produced images are always cutted off.
    No idea what's the reason for this behavior.

  • File size with JPEG Image files

    I recently had to re-load all of my photos from an external hard drive due to the fact that my hard drive crashed. When I did, I noticed that the files are JPEG Image files. As a result, the file size is considerably smaller than the original file and the quality is much less.
    Any suggestions on how to restore the file to the original format and quality?

    Connie:
    Yes, it seems you backup the Data folder instead of the Originals folder. Unfortunately, there's nothing you can do at this time.
    In the future, I suggest you copy the entire iPhoto Library folder to the external and then keep it updated with a backup application like Digital Backup, Snyk, etc. They compare B (the backup copy) with A (the working copy) and copy new or changed files from A to B to keep them identical. After the initial copy process, the subsequent backups are rather quick, about a minute or less.
    Do you Twango?
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
    I've written an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

Maybe you are looking for

  • Using IN keyword in an sql query in a view criteria

    Hi, I am using jdev 11.1.1.1.0 and defined an lov query/viewobject as select a, b, c from myTable I now need to predefine filtering for lov search functionality and need something like the following select a, B, c from myTable where B in ('X','Y') I

  • Video in button Selected state?

    I'm rusty in DVDSP - been a couple of years since my last DVD menu project, but I have one now and the client has provided the menu art and description of what they want - but there are 2 items I'm not sure if I can include the way they want, and bef

  • Itunes wont start (nothings pup op, not even error message)

    Hi, I got the problem the day i installed Win Xp instead of my Vista.. I cant turn on Itunes, it dosent come up with any message or error. When i want to shut down, it comes up with a box says "itnues wouldnt answer" And then its have a "bar" there g

  • EDI trading partner setup

    I have my organization is set as Party under parties. say MyOrg I created another party say Party1 then create agreement between  Party1 and MyOrg . Good working fine. Now I have Party2 and trying to create agreement  between Party2 and MyOrg . In bo

  • Oracle 10g express editon for windows 7  x64

    I cant find a free download for oracle 10g express editon or oracle 10g personal editon for windows 7 x64. Any Help?