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

Similar Messages

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

  • 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" after import from Canon PoweShot A2000IS

    Every time i import pictures from my Canon PowerShot A2000 IS Aperture presents the message
    "Unsuppported image format" in the viewer window.
    I can preview the images using coverflow or preview.
    Is there a way to handle this?
    Help would be appreciated.

    I don't know what happened, but suddenly it works just fine.
    I reconnected my "old" Powershot A70, imported some Photos, same problem.
    I deleted all importtes photos, restated Aperture, connected old camera, all works fine.
    Connected new camera... all works fine.
    "There are more things in heaven and earth, Horatio,
    Than are dreamt of in your philosophy."
    Hamlet - Shakespeare

  • 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

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

  • XMLFormService Error importing image. Unsupported image format.

    Hello,
    I'm getting the following error when trying to import an image into a form:
    2010-10-04 08:56:35,717 WARN  [com.adobe.document.XMLFormService] ALC-XTG-017-936: [8392] Error importing image. Unsupported image format.
    2010-10-04 08:56:35,717 WARN  [com.adobe.document.XMLFormService] ALC-XTG-029-461: [8392] XFAImageService: Image cannot be resolved for node: ImageField1.
    The strange thing is that it works fine on our production server, yet it fails in development.  I've restarted jboss, flushed tmp, work, and data, replaced the images, but still nothing.  The image that won't load is a 1 pixel by 1 pixel JPG image, so it's not like it could be too large or anything. 
    Please help if you have any insight into this problem.
    Thanks!

    So when I went to get the image, it wouldn't load in the Web browser, and it looks like that was the problem.  I mentioned that I had tried changing the image.  I was actually changing a field in the database that says which image to retrieve.  I'm wondering if maybe I was changing the wrong record or maybe my query browser wasn't updating the DB correctly.  I can't find the record I was using last week when I reported the issue, but either way, I'm glad it's working now. 
    Thanks for the help. 

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

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

  • Aperture 3 and DNGs from LX5 raw files: unsupported image format

    My LX5 arrived, and I tried converting a raw file to DNG with Adobe DNG Converter 6.2.0.21 beta and importing it into Aperture. No luck: Aperture says it's an unsupported image format. I tried setting the compatibility as far back as possible in the preferences, and still no luck. Any idea why this doesn't work? I used Adobe DNG Converter multiple times to work with raw files from unsupported cameras, so it's a real surprise to get the unsupported image file message.
    —Andreas

    Unfortunately, this is more about Apple dragging its feet than a cutting edge issue. I got an LX3 and upgraded to Aperture 3 in February of this year. RW2s straight out of the camera always imported just fine. However, I've never been able to get a DNG generated from an RW2 with Adobe DNG converter to work. Interestingly, DNGs from another file format I use (PEF) work fine in Aperture.
    I submitted a issue report to Apple about the RW2 to DNG problem back in March, and like so many other suggestions to them, it seems to have vanished into the ether.

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

  • Unsupported Image Format for DNG from GF1?

    I am in the process of trying to switch from Lightroom 3 to Aperture 3 (in case you are wondering why the main reason is increasing integration between iOS and Aperture).
    Most of the images in my Lightroom catalog are from Nikon DSLRs which when I import as DNGs from Lightroom into Aperture show up just fine. However, all of the old DNGs I try to import from Lightroom as DNGs that were shot with my Panasonic GF1 don't render in Aperture and just show up as "Unsupported Image Format."
    Please note that new GF1 images I import from the SD card of my GF1 import just fine. The problem seems limited to GF1 images saved in Lightroom as DNGs that I am importing into Aperture.
    Does anyone have any suggestions as to how to correct this issue?
    Thank you.

    Solved it. Had nothing to do with Photoshop PS4 install, it had to do with moving my home space to a larger external drive. One of the "import" setting changed (I don't remember changing it) such that the images weren't getting imported into Aperture. (Re-?)checked that, and all is well. Will go for the PS4-reinstall tomorrow.

  • 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 when inporting from my new Canon 400D (KISS X) CAM

    Could someone please tell me why Apeture is giving me the Unsupported Image Format notice when trying to view and import Raw images from my new Canon 400D camera? I can view the photos on my Canon software. Is it possible that just becase the file is 10.1 MP on my new cam instead of the 8mp that my rebel XT (350D) was that Apeture can not use the format? If in fact this is the case, what can i do to get the 300 plus photos that I just shot at a paid photo shoot into Apertue and still be able to work with them raw?
    I would be grateful for any help I can get.
    Thank you.
    Stan

    Two problems with this workflow:
    1) A 16 bit TIFF file is 52 megabytes. Ouch. Reading them bogs down my little MacBook like you wouldn't believe. I may have to work with JPEG or, god forbid, use Photoshop until Apple's devs can get support for the XTi
    2) Aperture seems unable to figure out the colour balance of the TIFF files. I added a bit of saturation and colour correction (working in the Adobe RGB space) in Canon DPP, but Aperture seems to totally screw up on these files. http://images.dasmegabyte.org/wine_tour/large-37.html almost no detail at all in those bins (plenty in the RAW) and I had to boost the gamma on the web gallery by 1.2x so they didn't look fire engine red.
    MacBook Pro   Mac OS X (10.4.8)  

  • Unsupported Image Format?  CR2 from Canon 20d

    ok, so my jpg's import fine. my problem is with my CR2 Raw pictures from my Canon 20d. I tried to import some. They import, all the metadata info is there, but there is no thumbnail in aperture and in the top viewer it says unsupported image format. Has anyone had this problem? After import why are the CR2 thumbnails missing and why do the viewers say Unsupported Image Format? Any help or thoughts would be appreciated.

    Since I can't open the problem RAW files in Preview or import them into iPhoto, but can open them in ACR/Bridge or DPP, I'm fairly certain this has something to do with the underlying RAW support at the OS-level in Tiger -- and not just an Aperture issue.
    I have had no problem with some older RAW files captured using my 20D. I think I may have upgraded the 20D's firmware since those images were shot -- could it be an incompatibility brought on by that?!?!

Maybe you are looking for