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

Similar Messages

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

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

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

Is there a way of running cd's"windows" formatted with inf and swf files?

Is there a way of opening and running CD's 'window' formatted with .inf and .swf files on a mac??

In your operating system, move the photos to wherever you want them to be (keeping the folder tree structure the same), and then in Lightroom re-link via http://www.computer-darkroom.com/lr2_find_folder/find-folder.htm

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.

"unsupported image file" when importing RAW images from Olympus E-PL1

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

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

"unsupported image file" message

hi there, this is the message that appears with some tiff files saved by Photoshop CS2: unsupported file image.....
But if I export the master of the file and open back in photoshop, the file is OK
Does anybody can solve this problem?
I've tried rebuilding all the projects but still happens the same and sometimes the "corrupted" files work fine after but other that were OK, give the error message.... !?!?!?!?
It's frustrating for my job, wasting a lot of time to export, save, then import again without solution
THANKS FOR YOUR HELP
PowerMac G5 Quad Mac OS X (10.4.8) 4Gb Ram, 3x1Tb HD ext drives

How big are the TIF's?
Are you reading them across from an external HDD?
Is the external on FW400, FW800 or eSATA?
I used to have problems with 200+Mb TIF's from scans, but this got corrected by the development team. Recent posts say that there is still a problem with very big TIF's.
Other possibility is the graphics card. If you have the 6600, then it's slow speed may be causing Aperture to "time out" waiting for the TIF to render. This will be exacerbated by a slow external disk sub-system. Again, this should be associated with big TIF files of >200Mb.
G.

Unsupported Image File????? iphone videos???? Aperture????

Hello,
I have only ever imported video files to aperture from my iphone 4.
So I havent changed the video format on the phone, it should just be a straight forward import and as apple have made the hardware & the software????
If you cant view the videos in aperture, whats the point of being able to import them to aperture in the first place??????
Is there anyway around this stupid error ???
Any ideas would be wonderful
Lisa. xx

Not sure if you are still suffering from this problem, but I had a similar issue, and tracked it down to the files being imported from a shared folder. If the shared folder has any Access control list set up, or the permissions aren't quite right (including some that you can only change yourself in Terminal like permission to Execute), then the video will import but appears to be unsupported.
An easy work around is to move the file to one of your personal directories into a library also in your private directory. If you are actually looking to share your library, then I had to set up a new partition and set it to 'Ignore permissions'. It then worked absolutely fine - also resolved some corruption issues I sometimes got with the shared library.
Hope this helps, and let me know if you need more details. Note that other posts fixed this by removing 3ivx libraries from Quicktime : https://discussions.apple.com/message/15714152#15714152.

Using another db with previous db all files

dear members
i am using db 10 g release 2 on my system.
due to improper shutdown, i am getting messages like
ORA-00607
ORA-00600
ORA-24324
ORA-01090
ORA-01041
by connecting with sys as sysdba;
shutdown immediate;
command does not complete. and leads me to the above messages.
analytical backup file *.dmp does not exits.
ALL information in file oradata\orcl\
control files
redo files
data files
temp files
users data files
undo files.
from these files can i recover the schema into a new database.
if possible,.......
mustafa ghulam
lahore,pakistan

dear member
my os is windows server 2003 enterprise edition.
moreover dont focus on the error messages.
i have taken a physical backup of the the files.
now on fresh os after installing a new db, can i be able to retrieve my schema,
by replacing old files with new files.
files meaning control, data, redo ,etc. mentioned before.
thanks for concern.
teefu
lahore,pakistan

Crossgrade Upgrade Not working with previous LiveType Media files

I have recently received the crossgrade discs and was able to successfully upgrade FCP, Motion, DVDSP...however, when it came to LiveType...and requested the previous LiveType Media discs, the installer didn't seem to recognize the first disc, and spit it out, thus stalling the rest of the install...anyone else experienced this issue, or have any suggestions?

None of what I posted you should need the device for. Now if you did not delete any folders then it should snap back to where the file was stored in the first place. If you still have issues it is possible for you to search for the files though windows. This maybe a little work around that you may need.
If Garmin did not change any of the files types then this maybe the trick. Using the search function look for .dat or .bak you may find some under the palm/[Hotsync Username].
Next thing would be to see if Garmin could help you. From what it sounds you just need to know where the file location is and an old forum board or KB just might help you.
Post relates to: Treo 800w (Sprint)

Suddenly getting "unsupported image fomat" on RAW files that have been working perfectly. How do I fix it and can I get those images back?

I am suddenly getting "unsupported image file" for RAW images that have been working just fine. How do I fix this and how do I get those images back? Version 3.4.5, Canon 7D, everything up to date and no updates since files were loaded into Aperture.

Would it help to buy a separate external hard drive for Aperture?
That would be by far the best solution. And it would make the backup easier. You could include the "Aperture" drive in your Time Machine backup. With the original files stored on your Time Machine volume there is no way that Time Machine could back them up.
Use Disk Utility to format the new drive "MacOS X Extended (Journaled)".
Set the "Ignore Ownership on this Volume" flag. (select the drive in the Finder, use "File > Get Info ⌘I)
In the "Get Info" panel your drive should look like this:

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.

Unsupported image format for nikon D7000????

I bought the latest Macbook air 13 inches and the Nikon D7000.
I tried to import the raw files (NEF) from the Nikon d7000, but it show can't read the files type, or
unsupported image file. It works fine with my nikon D5000, why?
anyone can help?

It's the price we "early adopters" pay. It usually takes a few weeks to even months before Apple and Adobe add support for the latest RAW camera profiles. There is no standard RAW format, even within a brand. It's maddening, but that is the nature of the format.
For now all we can do is either shoot JPEG and grin and bear it or shoot JPEG + RAW, and when RAW support is available trash the JPEGs and upload the RAWs. Or in your case use the 5000 when you absolutely need RAW.

Previously good songs became corrupted when I upgraded to Itunes V7.

I have the problem with previously good songs becoming corrupted when I upgraded to Itunes V7. I have the same songs on 3 computers and all were corrupted when I updated the software. This is clearly an Itunes bug and not a driver issue as the same exact songs were effected on three very different machines once each was updated.

I have the problem with previously good songs becoming corrupted when I upgraded to Itunes V7. I have the same songs on 3 computers and all were corrupted when I updated the software. This is clearly an Itunes bug and not a driver issue as the same exact songs were effected on three very different machines once each was updated.

Data format problem with Write to Spreedsheet File

I have a problem with the data format with Write to spredsheet file.
I have an N*3 array, where the 3 elements in each row should has different length. When I used Write to spreedsheet file,
it can only save the three data in one format. How can I save them in the format of "%0.8f %0.3f %0.2f"?
Thanks for your help.

Hi powerplay,
another solution may be to convert column-wise using "number to fractional string", then interleaving resulting arrays and again using "array to spreadsheet string" (with "space" as separator).
Many ways lead to Rome
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

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

Suddenly "Unsupported Image Format" with previously good image files

Similar Messages

Maybe you are looking for