Unsupported Image Format - One culprit

I would receive this message for any RAW formatted file within Aperture. ...even the provided example files. Through trial and error, I found that Unsanity's Fruitmenu was the culprit. Luckily this 'hackie' has the ability to exclude applications.
Problem solved!!

I just attempted to import NEF files into aperture. All show up in import window but upon importation I get 'unsupported image format' indication.
What am I to do?

Similar Messages

  • Unsupported image format after moving from one project to another

    I scanned several thousands of images to my Aperture library. Went thru all of them providing adjustments to many of them, keywords to all of them and adjust date/time to all of them. All of the pics were visible, format is jpeg.
    This is a managed library (all pics within Aperture db).
    This morning started to restructure the project files (had three of them). After moving couple of hundred images to newly created project file I started seeing "unsupported image format" red screen after clicking the jpeg. 20-30% of the pictures clicked showed on viewer "unsupported image format".
    Tried regenerating the previews. Tried command-option start with first fix the preferences option. Then with rebuild option.
    Tried moving the pictures back to their original project file.
    No joy... Still 20-30% of the pictures show the "unsupported image format".
    Aperture 2.1.
    Amy other tricks I could try?
    Reported this to Apple aperture feedback of course.
    --h

    Link the two Macs together: there are several ways to do this: Wireless Network, Firewire Target Disk Mode, Ethernet, or even just copy the Library to an external HD and then on to the new machine...
    But however you do choose to link the two machines...
    Simply copy the iPhoto Library from the Pictures Folder on the old Machine to the Pictures Folder on the new Machine.
    Then launch iPhoto. That's it.
    This moves photos, events, albums, books, keywords, slideshows and everything else.
    +Note: there is no importing involved+
    The thumbs appear, but the images are added 2 or 3 times each and the events are all messed up.
    This happens when you import one Library to another, which you've done by drag and drop:
    Creating a black library and over writing the new with the old.
    Your problem is arising because of the Network Share. iPhoto needs to have the Library sitting on disk formatted Mac OS Extended (Journaled). Users with the Library sitting on disks otherwise formatted regularly report issues including, but not limited to, importing, saving edits and sharing the photos.
    Regards
    TD

  • Unsupported Image Format - but only on one machine ....

    Hi,
    I imported some images into my Aperture library last night. The library is located on a Time Capsule which has over 300Gb of free space. Overnight, I left it processing thumbnails and in the morning I woke to a message reporting I was running critically low on disk space. Which I wasn't, still over 300Gb. How odd. Anyhow, since then, I've not been able to open ANY of the images within the library. All, going back to 2006 which have been working fine until now, come up with the "Unsupported Image format" message.
    I have rebooted my Mac, rebooted my Time Capsule, copied the library to the desktop of my Mac, deleted my preferences file, but nothing works. I tried to create a new project and that was fine. I imported one of the images from my camera and that worked fine in the new project. I tried copying the project file from my existing library to the new one - and I get unsupported image format.
    So, I started to panic - you're not telling me I've lost ALL my photos since 2006?! But then I tried looking at the library on the Time Capsule from my Macbook Pro. It worked fine.
    So it seems that the problem isn't so much with the library as with something in the Aperture install on my iMac which has become corrupted.
    Any ideas on how to give it a kick up the bum (I'd prefer not to have to reinstall).
    Also, this has kinda scared me. If the library fails, I'll lose all my photos? That's pretty cruddy. Can I make Aperture store my photos as individual files rather than one big library, so I can recover them if the library becomes corrupted?
    Thanks for your help!

    Thanks for your help.
    I'm using Aperture 2.1.4, sorry I should have mentioned that in my original post.
    I've installed the RAW Compatibility Update nonetheless, but no joy.
    I did a consistency check on the database and nothing came up. Then I did a rebuild and it almost worked. Luckily, I did this on a copy of the library. It removed most of my images from my library, but those that remained (which were a seemingly random subset of my whole library) were fine.
    I'm now making another copy of the library from the Time Capsule
    It's strange that it would be a problem with the database if it works fine on my MBP, don't you think?
    I'm out of ideas!

  • Unsupported image format from iPhoto

    I just installed Aperture and excitedly moved an album of jpeg pics over from iPhoto to play with and do some corrections on. To my dismay, quite a few of them show the "unsupported image format" screen though they will be identical in format to the ones next to them. I reverted them all to original before I moved them and they are all jpeg. Any help with this would be appreciated. Thanks.

    i can't make it out from your screenshot. are your pictures managed or referenced? it's very easy to determine if the problem is with a picture or with aperture. if it's referenced, just look it up with the finder and see if the system can read it. that way you know aperture's the culprit, otherwise you have some kind of disk corruption. if it's managed, you'll have to dig inside the library to look up the picture and do the same thing.
    if your library is corrupt, the easiest way to fix it is to hold command and alt during aperture launch and select rebuild library. depending on the size of it, this may take a while. this should normally fix things, but as i said, it's important to check whether the problem lies withing aperture, or on disk.
    j

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

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

  • HT3946 Unsupported image format

    I've been getting a message "This photo was adjusted using an earlier version of APPLE RAW processing" unsupported image format and it's been doing this to photos I took today and my older one's any advice on how to fix this?

    What is the make of your camera? This problem has occured recently mostly for Lumix and Nikon cameras:
    First try, if reprocessing the images will help:
    See this section of the user manual on how to do this for selected images:
    Reprocessing Images from Previous Versions of Aperture
    If this does not help, you may need to register your camera with the the launch service database again, see this post by Alan Roseman:, Re: Aperture 3 preview of raw file greenish
    There is a "typo" in the command given in the link above, so read also the following posts on how to correctly enter the command and how the fix is supposed to work
    Regards
    Léonie

  • Strange bug - some images showing up as 'unsupported Image Format'

    This could be possibly be the last straw with Aperture for me.
    I was 'happily' going through my latest shoot when all of a sudden one of my NEF files opens up and I get a solid dark red screen with the text 'Unsurpported Image Format'.
    It's the same RAW format as all the other images and the thumbnail is showing fine. I'm getting the same message with several random images.
    Has anyone else experienced this?
    I guess I need to restart my mac again! Arrrghhh!

    this is a bug, but it seems to happen radomly.
    aperture would sometimes complain that some of my NEF, PSD, and TIFF files are unsupported Image Format.
    sometimes clicking on another project and then back to where i was corrects the problem, and sometimes it just won't do it. when this happens i restart aperture. i think restarting aperture is the least frustrating work-around.
    daniel
    dual 2.7 ghz powerpc g5   Mac OS X (10.4.3)   8 gb ram and all other standard parts from apple store. such as the xt800 card.

  • 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

  • Unsupported Image Format After External Editor

    I have Aperture set up with Photoshop Elements 6 for MAC as the external editor. I have PSD(16bit) 300 dpi. I have used this external editor several times in the last two days. The most recent time I had a problem. It started PSE 6 as requested and displayed the picture with a *.pdf filename. I used the filter option I wanted and was satisfied with the result in PSE 6. I saved the file and quit PSE. It came back to Aperture and displayed two images: the original on the left and the edited on the right. After one or two seconds the image on the right (the result of the edit) was replaced by a dark red background with the black text Unsupported Image Format displayed. If I click on the right image, the edited image appears briefly and then reverts back to the error display.
    As I said, I used this only the night before several times with no problems and I have not changed my Aperture preferences since then. The master file is a Canon cr2 file and I did some Aperture corrections before I decided I needed to run a filter in PSE 6.
    Thanks,
    Bruce

    I'm having a similar problem with unsupported images. The problem has occurred when I use an external program to create an image. I've tried creating them as TIFF and JPEG. If I use the Sony Image Data Converter (v2 or v3) I get the unsupported image format.
    Last night I was scanning film with Silverfast, creating TIFF files and using them in Aperture 2 as referenced files. Everything was fine. This morning I did the same thing and got the red Unsupported Image Format screen from the same original image.
    I have found if I import the unsupported image into the Aperture library instead of using it as a referenced file it usually works. I don't like this solution because it messes with my work flow and I'm trying to keep the size of my Aperture Library under control.

  • 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

  • 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

  • Canon 7D, .CR2 and the miserable RED "Unsupported Image Format" screen

    I have seen a lot of posts on this:
    First, yes, all of my software is up to date ~ running Mac OS X SL 10.6.2 and Aperture 2.1.4
    I just got the 7D ~ my system is set up to automatically open Aperture when card reader and/or camera is plugged in.
    I have been shooting in Camera Raw, not sCR2, not mCR2, just .CR2 and large JPG simultaneously.
    Obviously, the JPG imports fine, but that dastardly "Unsupported Image Format" red screen pops up.
    I can't seem to find the file to open and see if it works in iPhoto ~ even when I am in iPhoto and try to show my Aperture library, it is not there.
    So, the big question is this: how do I download .CR2, find them to then convert them (and what am I converting them to?) and import those converted files into Aperture?
    I know, I know a lot of questions...but am appreciative of any help someone is willing to throw my way.
    Thanks

    Lv4Tunes wrote:when you plug your card into your card reader and then into your computer, what opens? Canon Image Browser? Digital Photo Professional? What do you do from there? How do you bring your stuff into Aperture from there?
    I mount the drive to see it in the finder only.
    I shoot both RAW & Jpeg the same time.
    I explore the Jpeg thumbnails, skipping over the raw files which takes a little longer to load.
    One main advantage doing both/
    Now anyone can load the Jpegs to view, otherwise they may not have viewer or software to see RAW files.
    For safety, I load the whole card file to the desktop.
    From here, I pre-sort the images to a folder within.
    Otherwise it's back & forth reloading the whole card file into Aperture picking out a few, and doing the process 10 - 20 more times for other images not related.
    Or making mistakes along the way. A simple slip of the wrist, or happy mouse.
    Now any software you chose, It can load from saved file on desktop.
    **The card anytime it's put back in camera gets reformatted.
    Or set aside for safe keeping until the process is complete in case of power failure and or crash.
    Reformatting the card is a must in the camera vs just deleted at computer.
    This might be the X crisis you see of old data mixed in.
    Other Issues/
    By default for years, compact flash cards & reader.
    On the Canon 1DsMkII, it has two slots, CF & SD.
    Along comes SDHC, and off to do wedding, get back to computer to load from reader and the computer says, we have no clue.
    Card readers are specific to SDHC.
    I had a thumb drive reader for SDHC but never gave it a thought there was any difference.
    Prior/
    The camera smarter, picked the SD slot to record to if pulling & replacing CF.
    So I was shocked not finding the images on CF at first.

Maybe you are looking for

  • Configuration solaris 10.5 on vmware 8 fror oracle

    I want to configure a Solaris 10.5 on vmware 8 ( my host system is windows 7 ).. mainly network part how to entry host name and DNS entry .. and i want to this configuration access on putty on windows 7 ... .. problem is that at installation time i a

  • Mapping and designing COA

    Hi friends, Can anyone please tell me what does someone mean when he say designing COA. Please share some knowledge on difining ,developing ,mapping COA interfaces with legacy systems. Thanks

  • InvocationTargetException acting odd

    If I invoke a java.lang.reflect.Method and that method throws InvocationTargetException then surely the first stack frame of ite.getCause() should be the method that I invoked, except that's not happening! In fact the frames returned seem to be nothi

  • What the heck is going on with my CODE?

    Ok.. so the program encrypts and decrypts text files.. you input the paths for which file to read and where to export it to.. the encrypt code and decrypt code is EXACTLY the same only like ONE line of code is different.. the difference was one had "

  • Compare previous value and new value on Campaign Save

    Hi All, I create a campaign. I need some exit ( badi etc.) which is called before saving the campaign and after saving the campaign. My main intention is to compare the previous value and the new value. Thanks in advance, Raviraj