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

Similar Messages

  • 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

  • My RAW files suddenly says "Unsupported Image Format" and can't import new pics

    Hi all,
    A week ago I imported the latest bunch of RAW-images from my Canon EOS 30D (.CR2-files) and all was working great. I did take some of the pics and exported them to an e-mail and sent them off to a friend. Then after rearranging my home office I was trying to import some pics from my iPhone 4 - won't work!
    And the RAW-images are not supported any longer!...??
    Facts:
    - iMac 2,66MHz Core 2 Duo/4GB/OS 10.8.1
    - Aperture 3.3.2
    - Aperture Library located on a Netgear ReadyNAS NV+
    Have searched for a solution without finding anything that works...
    Have tried to:
    - repair permissions
    - examine database
    - tossed com.apple.Aperture.plist to the trash
    - am right now trying to rebuilding database as a last resort
    Anyone have a good idea as I'm very reluctant to belive that rebuildning will work?
    BR,
    Pete

    Thanks for your reply!
    I've looked into it a bit.
    The ReadyNAS uses Linux Ext3/Ext4 file system.
    Found that my rights to Aperture Library has been downgraded to "Read only" even though I'm the admin...
    Won't take changes either... Get a message stating that I don't have the privilage to change file rights...!!
    I've just started a copy session of the 125 GB large Library to the internal HDD... It seems like a good idea to have it there - even though it's eating massive amounts of disk surface! Almost 20%...
    I'm calling Netgear tomorrow - how the heck can may rights be changed, just like that???
    Funny thing it's been working fine for a pretty long time, it's after Mointain Lion it has started to acting up.
    I did have similar problems the day after upgrading to ML but after a firmware upgrade of the ReadyNAS it worked like a charm again - until yesterday...
    Hope that I'm allowed to change the rights when it's been copied to the internal disk... Been typing and researching file system type etc for at least 15 mins now and it's still "preparing to copy"
    Here's what I found in Console, the line called "2012-09-13 01:13:16,238" gave it away for sure (while trying to import new pictures).
    2012-09-13 01:06:28,704 WindowServer[91]: CGXDisableUpdate: UI updates were forcibly disabled by application "Aperture" for over 1.00 seconds. Server has re-enabled them.
    2012-09-13 01:06:33,213 WindowServer[91]: reenable_update_for_connection: UI updates were finally reenabled by application "Aperture" after 5.51 seconds (server forcibly re-enabled them after 1.00 seconds)
    2012-09-13 01:07:50,105 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:07:50,383 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:07:50,956 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:07:53,224 WindowServer[91]: CGXDisableUpdate: UI updates were forcibly disabled by application "Aperture" for over 1.00 seconds. Server has re-enabled them.
    2012-09-13 01:07:56,045 WindowServer[91]: reenable_update_for_connection: UI updates were finally reenabled by application "Aperture" after 3.83 seconds (server forcibly re-enabled them after 1.00 seconds)
    2012-09-13 01:08:04,033 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:08:04,166 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:08:04,337 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:08:05,588 Aperture[4027]: The function `CGCMSUtilsGetICCProfileData' is obsolete and will be removed in an upcoming update. Unfortunately, this application, or a library it uses, is using this obsolete function, and is thereby contributing to an overall degradation of system performance. Please use `CGColorSpaceCopyICCProfile' instead.
    2012-09-13 01:08:06,937 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:08:07,037 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:08:07,257 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:08:09,069 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:08:09,137 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:08:09,700 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:08:09,726 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:08:10,330 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:08:11,463 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:08:14,680 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:08:45,151 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:08:50,593 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:08:50,646 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:08:50,753 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:08:52,368 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:08:54,564 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:08:57,876 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:07,732 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:07,785 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:08,613 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:09,289 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:11,050 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:30,529 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:32,090 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:32,114 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:35,890 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:36,622 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:41,105 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:42,018 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:42,064 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:43,558 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:47,057 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:47,372 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:49,190 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:50,757 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:50,771 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:50,786 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:52,494 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:09:53,835 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:00,281 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:00,299 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:00,314 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:01,799 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:03,490 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:03,528 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:04,393 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:04,410 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:04,434 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:10,510 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:11,671 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:11,724 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:12,487 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:15,266 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:20,511 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:20,559 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:24,635 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:26,227 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:32,667 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:32,729 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:32,767 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:41,388 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:41,410 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:43,233 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:43,277 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:10:45,381 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:13:16,238 Aperture[4027]: Document destination folder is not writable
    2012-09-13 01:15:01,576 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
    2012-09-13 01:15:02,317 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer

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

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

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

  • Nikon D800 raw files "unsupported image format".

    I've a problem with Nikon D800 raw files "unsupported image format".
    I've just upgrade to mountain lion with no success.
    also aperture seems the last version
    only Nikon software seems to work
    thank you
    Andrea

    Hey Andrea
    sorry for the late reply. Have been on some working holidays
    My setting is : typ>>>>  no
                           bit>>>>   14
    The only information, which is not transmitted is the adjustment level of the AF-finetuning
    Good luck and hope it works meanwhile also with your camera
    :-)) FJ

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

  • 10.5.2; Canon 1DsM3 Raw Files = "Unsupported Image Format" in Aperture

    Just did the update and pointed Aperture to a folder of Canon 1Ds Mark III raw files (standard raw files, no sRaw or anything like that). Thumbnail previews are grey and Viewer says, "Unsupported Image Format".
    Tried rebooting and verifying/fixing permissions. No help. No thumbnails, no images in Aperture.
    Canon 1Ds Mark III raw files do show fine in the finder and in Quick Look.
    Message was edited by: Jon Roemer

    I have the same exact issue.
    I do get the same error with 1Ds MIII raws.
    Also the G9 raws are not working.
    Finally after 3 months it's still not working
    I could imagine that there is the need to edit some property file (like I have read before in the forum somewere) to add the new cameras to the list of supported cameras.
    Are the D3, D300 raws working?

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

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

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

  • 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

Maybe you are looking for