Sudden "unsupported image format" after using Dodge & Burn Plugin

After using Dodge & Burn plugin for first time (seems great) one of the images suddenly turned into "unsupported image format" in Aperture. Just happened to one but its a critical one so I need to figure it out. Any thoughts?
Thanks - Robert robert (at) robertholland (dot) com
<Edited by Host>

scott nichol wrote:
if you keep the console open when you're editing these photos and the "unsupported image format" message comes up, you'll notice that Aperture is throwing malloc errors on the console. this means that while its trying to load the image, it is running out of RAM. the core problem here is that Aperture can't address more than 2GB of RAM and i think the only way that Apple can address this problem is by moving to a 64-bit version of Aperture. it would be really nice if this issue was addressed in a 2.2 release sometime soon as this happens to me all the time now after round-tripping an image to Photoshop.
i would not expect to have to quit and restart a professional photography application every time i finish editing an image.
Good to know. But I don't expect a .2 upgrade to be 64bits, a next major version of Aperture is more likely to be 64bits (Aperture 3), considering AP 2 is at the end of its development cycle and a new major release is due before summer.

Similar Messages

Unsupported image format after using external editor

A new twist (for me) on the familiar unsupported image format problem: On my MacBook Pro (running Aperture 2.1.4) I export an image to PS as a 16 bit TIFF 300 dpi to work on it; when I'm done it comes back as a TIFF. But Aperture won't open the edited image; it gives me the maroon screen. The edited image shows up fine as a thumbnail, though. This is a new problem, one of a great many issues with Aperture. On my MacPro, running the same OS and Aperture version, I don't get this problem. Many of my problems with Aperture's defects simply go away after a couple of restarts; this one is persistent.
I notice one other weird thing with exporting to PS as a TIFF; when I hit command/save I often get a screen asking for instructions on saving the TIFF, i.e., compression and so on. According to an Apple tech I spoke to, this screen shouldn't appear when saving back to Aperture. It appears inconsistently, most of the time but not all the time. Any thoughts?

ericnepean wrote:
Adobe - it just works!
Uh Yeah: http://forums.adobe.com/community/lightroom
photobydc,
Everyone understands your frustration, but we get frustrated when someone throws up their hands and blames the program for a problem that's unique to them.
When you had a problem in the darkroom, did you blame it on Omega or Bessler or Agfa or Kodak? That refrain just makes the contributors reluctant to spend time typing in an effort to help. If your problem were common, this board would be lit up with complaints about it.
BTW: have you even tried it as a PSD? Have you tried on another user? Have you repaired permissions? Have you rebuilt the Database? Have you done a consistency check? Have you removed the preferences? What possible causes did you eliminate before concluding that the problem was with the program?
It's just not realistic to think that the Software Engineers at Apple can address each individual problem that a unique user might have.
DLS

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

Unsupported image format after merging aperture libraries

I've experienced a large number of files with 'unsupported image format' after merging aperture libraries from separate external hard drives. I did not have this problem in either library prior to merging them. Can anyone advise how to rectify this issue? Thanks

Try running library repair on the merged library and see if that helps.
To run the repair open Aperture while holding the option and command keys down. Select Repair from the menu.
Post back if you still have the problem.

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 after recent Digital Raw Update..?

I think there is a serious bug in the most recent digital camera raw update.. Though I am not sure if it's a 10.5.6 update issue or the recent camera raw update (v2.4)... The problem is didn't launch aperture between these so I don't know..
I have a Leica V-Lux 1 camera. The RAW format for this camera has been supported since leopard came out. However, in a effort to save space I always convert my leica raw files to DNG. This hasn't been a problem for me and things have worked fine... However, after this update I am receiving the dreaded unsupported image format.. What is interesting however, is that this is only for my DNG converted RAW files in aperture.. Those files which I didn't convert to DNG and remain in raw (i have a few) don't have this message. This is serious, I have lost access to my entire collection of pictures as a result..

The solution to fix this was to restore the 2.3 camera update (RawCamera.bundle) file using time machine. I will have to report this to apple bug reporter as this is a clear problem with 2.4 update and easily reproducible.

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' after migrating project

I finally when to an Apple store and purchased version 2.
But I have a major issue with one project I just migrated to RAW 2.0.
Lots of the images are now saying 'Unsupported Image Format', these images are from the same Nikon D80 camera using the same RAW settings that I have used for sometime. I have also successfully migrated other projects already with no problems.
This is very strange as Aperture reprocessed all the thumbnail images just fine.

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

Unsupported image format after upgrade to 3.4.5

I have just upgraded to Aperture 3.4.5 and have connected the previous library which had been comiled in version 2.
I am now seeing loads of Unsupported Image Formats appear in the random sample of files I have checked.
I use two cameras mainly, a Nikon D2x and a Canon Powershot G15 and shoot a lot on raw with the Nikon but mainly high res jpegs on the Canon. Images from both are subject to this occurrence.
Initially the preview and the image will appear in the main panel but when I attempt to do anything in the adjustments panel then I get the Unsupported Image format appear.
Any inputs would be most appreciated.

Also the Aperture Trial library that appears at the top of the side bar.
Aperture shows the name of the Aperture library at the top of the Library Inspector panel. If you bought Aperture originally by downloading a trial version and then unlocking the trial with a serial number your library may still be called "Aperture Trial". You can rename the Aperture Library in the Finder. Select the package "Aperture Trial.aplibrary" in thePictures folder,or wherever you keep the libraries and rename the package to Aperture Library.aplibrary" or similar.
I have gone through a few folders and reconnected them and this is working so far. Is there a way to connect the who;le library without having to go through every folder as there are many of them.
You can select several projects at once to reconnect the originals. If Aperture can guess the location of the originals from the ones it just reconnected it should work to select all images at once, then pair the first image with the original, and then to select "reconnect all".
The easiest way to select all images at once is the Photos tab.

Unsupported image format after Photoshop

I recently upgraded to 3.4.5, and now after taking images to Photoshop for editing they come back into Aperture with an "unsupported image format" exclamation mark screen. I need to be able to open images in PS5 and close them without this glitch...I have tried all the typical fixes, so please don't suggest that I rebuild my library, etc. Please help! I have clients who need me to edit their images this week...
Many thanks!

Hi Léonie,
Thanks for your quick response!
Here are some answers...
I am on CS5, I have been on iOS 10.7.5 for some time now, and Aperture 3.4.5. I upgraded Aperture from the most recent - I always keep up-to-date on the periodic updates...so I guess that was 3.4.? - I have not skipped any upgrades.
I am exporting into photoshop as a 16bit PSD. My originals are managed. Not sure what you mean by file export settings in PS...I have chosen maximize PSD and PSB file compatibility as "Always".
I have tried repairing permissions, repairing the database and rebuilding the database. I have also temporarily trashed my prefs file to see if that would make a difference. None of the above have made any difference. I may try TimeMachine next to go back to the previous version of Aperture...
When I import a PSD file from my desktop, it brings it into Aperture, and shows a preview properly, but when I then try to open that PSD file from Aperture into Photoshop, it flattens it and none of my layers have been preserved.
Thanks very much!
Lori

"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

Unsupported Image Format after update

I support a fair number of Macs, and if someone tells me that one day the computer did something and then the next day would not and they didn't change a thing I would know they were wrong. Something changed but they don't know what changed.
I use Aperture 1.5.2. I installed the RAW updae for PPC. Great. Aperture opened the NEF files.
Next day it would not opwn NEF files, showing 'unsupported file format'. I swear So I reinstalled and the installer said it wasn't necessary.
I don't know where to even begin looking to resolve this. Any ideas?
Michael
too many to mention, really Mac OS X (10.4.8)

I'd try and split the problem in half.
Will Preview.app open the NEF file in question? It uses the same RAW image support (as delivered in the update you applied) as Aperture.
If it won't, then there's something about the RAW update for PPC that has got broken/modified/disturbed.
If it will, then it's Aperture that is being awkward (is it the same NEF file? It has been said that sometimes an image needs to be reimported if support for it wasn't present at the time when it was previously added to Aperture's library.)
just a couple of ideas.

Suddenly "Unsupported Image Format" with previously good image files

Aperture 3.3.2 under OS 10.7.4 on a 2011 MBP with 8 GB RAM and no overfilled drives.
Nikon D2x NEF + JPEG files, RAW as Master. Has been working fine for weeks, no change in setup of any kind. No crashes until hours after this problem presented today. As recently as yesterday I was round-tripping to Photoshop and exporting from Aperture smooth as silk.
Suddenly today most images will not open in Photoshop via Aperture but they open fine in PS from the referenced originals. Aperture will not export NEf files or most PSD files. JPEGs as Masters work normally.
Aperture apparently sees the referenced files fine, including displaying and zooming. Most of the time. This is not an issue of unconnected originals.
I have tried rebuilding the database, repairing permissions, deleting plist, etc. About half the time Aperture ends up stuck and reqs a force quit. Tested with multiple Libraries. New image files imported tday for testing work normally with any Library.
I tried Terminal mode and Léonie's string
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchSe rvices.framework/Versions/A/Support/Isregister -R /System/Library/CoreServices/CoreTypes.bundle/Contents/Library
multiple tries always came back with "no such file or directory."
This was a very stable setup so I am very _not_ desirous of starting to upgrade things just because. I have an upgrade plan for 10.8 but for good reasons do not want to do it just yet. Also I do not want to back up or upgrade from anything broken. 100% of originals are readily available, but there are many tens of thousands...
Any ideas would be appreciated.
TIA
-Allen

Allen,
there have been several threads with similar problems of broken references to raw images; in some cases even with managed raw images, that cannot be reconnected, for example:
Raw images all blank
One more reason to avoid managed libraries.
The "lsregister" command must exist on your machine. It may move around a bit, because there are many links in the path to current versions.
After the last update I found this direct path (MacOS X 10.8.2):
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchSe rvices.framework/Support/lsregister -R /System/Library/CoreServices/CoreTypes.bundle/Contents/Library
To search the "lsregister" command in your system, try to open the "/System/Library/Frameworks/CoreServices.framework" in the Finder and to navigate from there:
Typing "open /System/Library/Frameworks/CoreServices.framework" into the Terminal will open a Finder window in the directory (as you probably will know )
Added: If newly imported raws are recognized without problems it is unlikely to be a problem of missing raw conversion registration. I am just concerned about the error message you get.
Regards
Léonie

"Unsupported image format" after exporting original RAW file

My library has been working fine (albeit slow - it is very large). Today I exported a photo that I have edited and played around with many times in the past. I inadvertantly exported the Original, and I got an error message (which I don't recall what it said) but then immediately afterward, I could not view the image. I can't remember if I chose a duplicate version or the edited master to export (not sure why it would make a difference). Either way the photo did not export and it is now completely unviewable. I am trying to repair my library to see if that will help. If not I will try to reprocess my originals (I can't seem to find a way to just reprocess the one image so will have to run it for my entire library). Any help would be greatly appreciated!

What is your Aperture 3 version?
The symptoms you are describing suggest, that Aperture has lost the connection between the edited version of the image and the original image file. This will typically result in being unable to export the originals or to edit.
As a test - what happens when you select the image in question and press the "M" key to toggle between original version and current version?
I see this, when the original file is missing:
Is your library referenced or managed?
Regards
Léonie

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

Sudden "unsupported image format" after using Dodge & Burn Plugin

Similar Messages

Maybe you are looking for