I've fought with aperture for years and had multiple corrupted libraries. The only program that I have found that was able to find corrupted pictures is an old program called MacScan. It pulled out the corrupted files as Trojan horse programs. You can then identify those pictures and either delete them, or isolate them in a smaller library. In your case, pulling them into a new Aperture library may help contain the damaged files. There are to many variables to managed files. It takes only a couple of bad pictures to corrupt an entire library. Also Raw convertion of files isn't an Aperture problem, that's in the operating system independent of Aperture. For the time being, you will probably need to use the softwear provided by canon to take your 60D raw images and convert them into a tiff format and manage with Aperture. Make sure to keep the original raw picture out of the camera managed by Canon. Canon softwear is terrible at raw conversion.
@Jared O\'Connor, thanks for the suggestion! I do have MacScan installed but I don't see any options for sanning an image ibrary for damaged files. It only scans for viruses, tracking cookies etc. Am I missing something?
I ran a scan of my entire hard drive by MacScan, and it pulled out the corrupted files. The program believed that they were Trojan horses. I was able to delete the files. In other corrupted library episodes, I was able to localize the corrupted picture to a set of pictures by a process of elimination (ie I accessed each set of pictures until the program crashed). I then started up aperture in a safe mode (unfortunately I don't remember how to start up in safe mode anymore), and exported the corrupt library or the pictures out. Followed by erasier of the bad pictures from the library. This salvaged multiple libraries.
I'm concerned you may have a less contained problem. In my case, the corrupt files were contained within aperture. Your files are being managed by aperture, so the problem could be more difficult to find. The problem could be in the external pictures, the interface between aperture and storage area, or internal to aperture.
I assume that with the 60D being a new camera, you had a previous camera. One thing you could do as a trouble shooting step is to create a new library and directly import the pictures from your previous camera(card reader). See what happens. This step would conceivably eliminate your 60D as part of the problem. I assume this problem started prior to the new camera?
With Aperture 2, I would have to erase the aperture program and reinstall from disk every 6 months. I think over time, little strings get broken between aperture and the operating system. I think the operating system keeps redirecting the broken strings until it becomes overwhelmed.
Jared, thanks for trying to help. I know I didn't have the latest version of Camera Raw as I couldn't work on my photos in Photoshop straight out of the camera, but I could, after importing them into Aperture. I was finally able to upgrade my Camera Raw and can now open photos in both Photoshop and Lightroom. No issues. I can successfully work on photos that caused my Aperture to crash. It hasn't helped Aperture at all though.
As for Macscan, I have it running every night, but it never catches anything.
I have tried editing photos taken with my old camera. The flickering still persists.
So at this point, it seems like the issue is Aperture itself. It doesn't seem like a clean install can fix it as I've already done it.
I think I should just move to Lightroom by now... Unless somebody else has any ideas??
Thanks to everyone for the help!
The Macscan only worked for one of my bad aperture libraries. It didn't work for any of the others. If it didn't catch the problem on the first time, it won't help. With the previous pictures (previous software) not being supported by aperture, I think you want to remove your previous pictures from your hard drive. The raw conversion is actually handled by the operating system. I think your operating system is being dragged down by the incompatible pictures. I would move them to an external hard drive and use the provided camera software for editing purposes. When you erase the pictures from your hard drive, I would use a secure erasier to make sure they completely disappear (trash settings). When Aperture gets a picture that it can't handle, it keeps working on it. It just keep spinning/working on it. The operating system is probably set up with a similar format, so as long as you have a corrupt picture (incompatible format) on your drive it just keeps working on it.
I think that if Aperture can't process my RAW images and my JPEG's, it's not the images that are at fault. Is that a fair assumption?
There is not a simple A-B, yes/no answer.
Note that there are a zillion reasons a particular work flow fails, and corrupted images can come from multiple sources, multiple reasons. Such as bad card, bad connection, flaky drive(s), bad copying, flaky Aperture conversion (not so likely with JPEG), etc.
Allen, I understand there may be multiple reasons. I am just trying to whittle it down to those that I can address. I think by now I've done pretty much everything I could and I'm seeing no improvement.
- I understand the bad card issue - I've tried 2 cards. Old JPEGs vs. new RAW images came from cards of different format. Logically thinking, card issue is ruled out as cards vary but the issue persists.
- Corrupted image - I'm successfully editing these images in other applications: Photoshop, Lightroom. - Thinking it's probably not the cause either.
- Corrupted library - I've created a copy of my library, a brand new library with brand new images, a very small library - same issues, probably not the library issue
- Issues with the user account. Again, I created a brand new user account, tried all these libraries, created a new library - same issues, probably not the user account issue
- Bad drive - this is a brand new laptop and I've run a disk utility to check the hard drive - no errors reported. I have had the same issue on my old laptop, where the hard drive didn't have any issues either. - probably not the reason
- Flaky Aperture conversion - could see that being the reason, but doesn't explain the issue with JPEG's, like you mentioned - probably not the reason....
At this point, I am blaming it on Aperture, but at the same time I understand if that was the issue, there should, in theory, be people with similar issues, seaking help. I am seeing a lot of complaints about aperture under Lion, my issues started under Snow Leopard. There are plenty complaints there too, but I haven't found any that would match my profile.
So that makes me think that it's a user issue, but I think I've ruled out most if not all possible issues. What else am I missing?
I just can't get it to work. I mean, isn't SW supposed to work, right out of the box, with a clean instal on a brand new user account, with a brand new set of images? I've eliminated so many things it can be unhappy about, how come it's not working? I understand I'm digging myself a hole here and already foresee possible comments about me being computer illiterate, but I have already exausted all of my computer smarts and now am just at the poit where, as a consumer, I want the product to work for me as it does for other people. I don't know how I'm different.
Don't feel bad. I have been using Aperture for 3 years. I was excited when Aperture 3 was released, not happy when I started to use it. Since this upgrade, I have spent more time being kicked out of the program, reporting why I was kicked out, watching the rainbow circle spin out of control.....
For some, this is a weekend hobby. But, this is what I do for a living. I don't have time to sit around waiting for the next upgrade or to change my workflow around their issues. If this was a 1.99 application I may not have such heartburn about the issue. It wasn't. Sure I can turn to Photoshop and Lightroom, yet I don't feel that I should have to seek other options when I was perfectly happy with the one I had.
I have 3 IMac's, each of them have the same issues. In turn, I have a Nikon D3s. I highly doubt that all of a sudden that my highly priced camera has the issue.
The error that my "console" shows is: unhandled sortkey path. I have 4,000 (yes I did put the correct amount of zero's) from 5/14-5/16 on my log.
Unless you installed all three of your operating systems from the same disk, I'd be suspicious that you got a bad copy of Aperture or a bad uptdate. Have you wiped everything (aperture + Operating System+ cards) at the some time? Are you running the most current softwear on your camera? If all else fails, maybe you will have to buy a Canon .
I got the Snow Leopard from a CD, Lion came pre-installed on the new laptop.
Aperture was originally installed on my old computer from a trial, got carried over. I thought it was a bad install/copy so I followed the instructions on here (http://support.apple.com/kb/HT3805) and re-downloaded and reinstalled it completely.
I have a habit of formatting my cards after I copy the photos onto my HD, so they get wiped regularly.
My Canon SW is up to date.
Are you saying I need to buy a new 5D MK3???
That reminds me. I had a lot of problems with my original transformation from a trial version to my purchased copy. It wasn't until I erased my downloaded version of aperture and reinstalled from disk that things somewhat stabilized. I'm getting rather sick of having to install version two and then installing version three and then having to update online with the software update program. On the next version, I'll probably buy a non-upgrade version.