Unsupported image format following update to Aperture 3.4.1

Question

Level 1

0 points

Unsupported image format following update to Aperture 3.4.1

Following the update to Aperture 3.4.1 I can not use the JPEG file as the orignal in a RAW + JPEG file import. When I right click on an RAW + JPEG paired image and ask to use the JPEG as the original from either my Canon 5D Mark II or Canon 7D images the screen goes black and says Unsupported Image Format. I then ask to use the RAW as the original and I can see the RAW image. I've tried out other camera makes of RAW + JPEG images and the JPEG can be seen no problem. I've sent Apple a feedback comment on this.

I'd like to know if anyone with Canon 5D or 7D mixed RAW + JPEG images is having the same problem, or possibly any other Canon camera as I suspect this could be isolated to Canon files.

Posted on Sep 30, 2012 7:16 AM

Reply

Answer 1

Gordon_P Author

Level 1

0 points

Oct 1, 2012 10:27 AM in response to Gordon_P

I found the resolution to my problem, which was to delete the Aperture.plist file and restart Aperture. Since then I'ce had no problems moving and back and forth between RAW as original or the JPEG as original

Reply

Answer 2

léonie

Level 10

200,645 points

Oct 1, 2012 10:48 AM in response to Gordon_P

That is a very surprising solution Gordon. Thank you pointing this out.

Léonie

Reply

Answer 3

Gordon_P Author

Level 1

0 points

Oct 1, 2012 12:47 PM in response to léonie

Sorry back to square one and more confused than before! Everything seemed to work for about 30 mins and then went back over and I can no longer use the Canon Jpegs as the originals. I also have a Nex 5 and the RAW + JPEG swap fine between the RAW as original and the JPEG as original.

Further to this problem I've noted that when i quit Aperture and then re-start it i can change one or two images from the RAW as original to the JPEG and then something happens and the error "Unsupported Image Format" re-appears. I've also now deleted that Aperture.Plist file twice and for a short period of time all seems well but then it reverts back to the error.

Not sure what's going on but given the number of problems other users seem to be having I feel I've made a mistake by updating to 3.4.1

Reply

Answer 4

Oct 2, 2012 6:35 AM in response to Gordon_P

Oh, man! I have this problem with ANY images older than about three years. I've got a database check and repair running right now.

And I don't seem to HAVE an aperture.plist file!

Also had a weird error yesterday, where a shoot I did less than a year ago showed as being shot with an older version of Aperture's processing engine. I updated and it seemed to work, but that's truly weird as I don't think Aperture's undergone a major RAW converter change since version 2, s3veral years ago.

Reply

Answer 5

Gordon_P Author

Level 1

0 points

Oct 2, 2012 9:33 AM in response to Otis Fuentes

Assuming you've placed your aperture library in the default folder that Aperture wants to place it (within your pictures folder) then you should find your Aperture.plist file in this folder (~/Library/Preferences). The file to look for is called com.apple.Aperture.plist, make sure you do not have Aperture running at the time you delete this file.

I can't guarantee this will sort out any of your problems but you never know!

Also I understand this file is a simple file that tells Aperture what all your preferences are in terms of set-up and appearance, so if you've made lots of appearance adjustments from the normal way that Aperture looks on a first installation you may want to make comprehensive notes about how you have it looking etc so you can re-do those preferences.

I simply have left it looking as it did after first installation hence I was not concerned about deleting the file as the very next time you run Aperture it creates the file based on your current preferences.

I'd be very interested to know if anyone is experiencing a similar problem that I am as it's quite weird.

I'm running Mac OS X 10.7.5 on a late 2011 Macbook Pro 2.5 GHz Intel Core i7 with 8Gb 1333 MHz DDR3 and all software including Aperture is fully up to date and I store me images solely in the Aperture library. The problem is only showing up on Canon JPEGs.

Reply

Answer 6

léonie

Level 10

200,645 points

Oct 2, 2012 2:53 PM in response to Gordon_P

Just a wild shot, but with previous system updates it helped for some cameras to register the known raw formats in the "Core types bundle" with the OS has again. You need the Terminal to do this:

Quit Aperture, if it is running.
Launch a Terminal (from the Launchpad, or from the Applications > Utilities folder, or typing "Terminal" into the Spotlight search field)
Then enter:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchSe rvices.framework/Versions/A/Support/lsregister -R /System/Library/CoreServices/CoreTypes.bundle/Contents/Library(All in one line and without spaces - the only spaces go directly before and after "-R" (the server inserts random blanks into long lines when downloading a post - remove them). Hit return.
Then reboot and try again, if Aperture recognizes the raw format now.

Regards

Léonie

Reply

Answer 7

Oct 2, 2012 6:27 PM in response to léonie

Just tried that, got a "no such file exists" error in Terminal.

Have also checked for errors in database (which took four hours) and deleted and regenerated the aperture.plist file. Any other ideas?

Reply

Answer 8

léonie

Level 10

200,645 points

Oct 3, 2012 12:39 AM in response to Otis Fuentes

Try to type the command again (copy and paste from this window and make sure that no spaces are inserted other than directly before and after "-R", all in one line):

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchSe rvices.framework/Versions/A/Support/lsregister -R /System/Library/CoreServices/CoreTypes.bundle/Contents/Library

Quit Aperture before doing this, then restart the system.

Reply

Answer 9

Nov 26, 2012 2:17 PM in response to léonie

Did this work for you Gordon_P?

Reply

Answer 10

Gordon_P Author

Level 1

0 points

Nov 27, 2012 8:45 AM in response to matthew.baltrusitis

No none of the suggestions worked and as you can see even the resolution I thought I had stumbled across did not work in the end.

The good news for me though is since my original post there have been further Aperture upgrades and the problem I was having disappeared with version 3.4.2 and has not happened again even now with version 3.4.3.

Reply

Answer 11

Nov 27, 2012 9:01 AM in response to Gordon_P

FWIW, my problem was resolved when Apple released an update to the RAW processing engine (rather than Aperture per se). Turned out others were having this problem too, and they fixed it, yay! Apple engineering FTW.

Reply

Answer 12

Nov 27, 2012 10:18 AM in response to Otis Fuentes

I have heard that has been the case for a lot of other people as well.

Reply

Answer 13

vinz420

Level 1

13 points

Feb 5, 2013 6:27 PM in response to Gordon_P

I had this problem as well and none of the solutions above worked for me I'm afraid. I seem to have solved the problem by 'Creating a New Project' rather than adding it to an existing one. Very weird but I can see this becoming a major annoyance in the near future when existing clients want some items added to their project.

Reply