-
All replies
-
Helpful answers
-
Apr 17, 2012 4:44 AM in response to DanielJoshuaLambertby Kriel21,Hello everyone,
First time poster here so take it easy on me
I've been experiencing similar issues regarding the colour streaks and corruption of images and am surprised no definite solution has been found yet. In my case I've run through all the standard Aperture First Aid procedures, repairing then rebuilding the database. I've generated new previews just to check as well. The strange thing is that not only are my newest RAW files spontaneously corrupting but I'm also loosing images that are in jpg format. The jpgs are from 4 different cameras as well as some scans all from the last 10 years.
Currently I have 1 Aperture library on my 2008 MBP Unibody (2.8 c2duo, 4gb ram) with about 4000 managed images. The library file is only about 80 gb. I also have about 20k images (300gb) on a reference external drive that is esata.
There seems to be no rhyme or reason as to which files go corrupt. Both managed and referenced files are bad and it seems to affect the original file. I try opening it outside of Aperture in Preview and it still shows as corrupt. Haven't yet tried opening in Image Capture or Photoshop.
I'm wondering if anyone has any suggestions.
Thanks
-
Apr 17, 2012 5:01 AM in response to Kriel21by Ernie Stamper,This is s very puzzling issue. Can you find one of the now corrupt masters in the Finder, as you seem to have already done, and with Get Info check the date created and the last date modified. Best if this can be done with one you have not previously accessed via the Finder.
Ernie
-
Apr 17, 2012 1:16 PM in response to Ernie Stamperby Kriel21,I just scanned through my library and found a photo from back in 2009 which I haven't looked at since that year. It has no created date but shows last modified as 2009 which is accurate. The thumbnail in the finder initially didn't show the corruption but the preview in Aperture did. They after i did the "get info" routine the thumbnail was updated and showed the corruption. I'm unable to open the .NEF in photoshop or image capture. Preview shows the corruption as does Aperture in all views.
I tried deleting and creating a new preview. Still corrupt.
Does reprocess master only affect the currently selected image(s) or does it apply to your whole library?
Reprocessing and deleting the cache are about the only 2 things I have yet to try.
Anyone have suggestion? It would be most welcome.
Thanks!
-
May 3, 2012 12:59 PM in response to DanielJoshuaLambertby dustobub,Kriel21,
I believe the issue you are speaking about is more closely related to the unresolved issue noted in:
https://discussions.apple.com/thread/3168022?start=0&tstart=0
If anyone has any solution to this issue, please post it. I'm one more corrupt photo away from rebuilding my library in Lightroom.
Thanks,
Dustin
-
May 20, 2012 6:00 PM in response to DanielJoshuaLambertby flwrpwr,I'm having the same issues. Have been having them, I should say. And I have tried everything suggested to no avail. I'm on OS 10.6.8 The corruption is totally random. Sometimes it's the streaky thing, sometimes the photo is just black and other times there's a triangle with an exclamation mark. It's completely inconsistent. In the past, some images would be 'corrected' by regenerating the preview but that has not worked recently. I'm completely beside myself and don't have time to deal with this constantly. I'm about ready to move to LR too. I have never heard LR users complain about this sort of problem and am alarmed to hear other A3 users complaining of this with no resolution in sight.
I shoot Raw and Jpeg. I use SD and CF cards. I shoot with a Canon 1D MIV, Canon Kiss X3 450D, Canon Powershot A610 and didn't have many serious issues for the first few years of using Aperture. I've been using this app from the start and loved it. Have used referenced and managed files.
I have no idea what to do next. I suppose I ought to take it in to the Apple Store. With no assurance as to whether they can fix it, however, I am loathe to pay a fee. So frustrated.
-
May 20, 2012 6:13 PM in response to DanielJoshuaLambertby dustobub,flwrpwr,
Are the images that appear corrupt images that were at one point okay? Or do you only see the issue on new imports? I am having issues with the former.
Thanks,
Dustin
-
May 22, 2012 7:39 AM in response to DanielJoshuaLambertby scarlett11595,So we are having the same problem at work. Have tried most of all of the above, but after reading this thread, not sure it'll be worth continued troubleshooting. We are thinking of switching to LR too. You are not alone!
-
May 22, 2012 4:15 PM in response to scarlett11595by dustobub,Scarlett11595,
Do you see issues on import or randomly? This thread is a little messy as I think it is about multiple distinct issues.
Thanks,
Dustin
-
May 23, 2012 7:45 AM in response to dustobubby scarlett11595,We see the issues randomly. Importing always goes fine. But you go to look back at images and they can be either partially or fully corrupted. It seems the referenced files get corrupted more easily. And to further complicate things Aperture has decided to sometimes import some images (even from the same day, taken minutes apart) as referenced and some as managed even though the import setting has never been changed from managed by a person. We have an external hard drive that hosts the time machine backups but the masters for those mising referenced files arent there either. We are going to start a new library with a new workflow and new backup scheme and keep our messed up library on a different iMac and hope like **** it works. Our messed up library has about 47k images in it with about 14K of those unavailable. Sometimes you can see the thumbnail for the master offline photos but sometimes you can't see anything or you see the corrupted file. Very frustrating.
This thread is a bit messy, but at least has pertinent info in it!
-
May 23, 2012 8:08 AM in response to scarlett11595by lesyk,I took my iMac in because it crashed again while in
Aperture and this time the Genius Bar replaced it with
A completely new machine. Appears that the old one had
Not only hard drive problems but also RAM issues. Anyway
I rebuilt my Aperture library and was happy the I didn't
Seem to have corruption. However, when I went back
To a bOok I had created the referenced image suddenly
Corrupted after looking perfectly normal and then when I
Proceeded back to the master it too was ok for a few
Seconds before it reflected the same random corruption
As in the referencing preview. Had none of these issues
When I had Leopard as OS. There is something seriously
Strange going on within Aperture 3 running under Lion.
EXTREMELY FRUSTRATING! RANDOM!!!
-
May 31, 2012 8:01 AM in response to DanielJoshuaLambertby DanielJoshuaLambert,Hi guys
Just a little update from my original post.
I'm on iMac #3 (due to some other irritating issues).
I decided to keep everything stock for a month or so, ...no crashes. No corruption. Everything was fine, perfect infact.
I have 16GB ram (crucial) waiting to be put to use, so today I decided to install, as there were no issues. I put the Ram in about 2:30 this afternoon - guess what:
at 3:40 this afternoon, my first image has corrupted.
I understand that some people may not buy extra RAM, but for me, it seems this is the cause.
-
May 31, 2012 8:49 AM in response to DanielJoshuaLambertby shuttersp33d,Well that's interesting... and makes more sense. Glad you figured it out.
-
May 31, 2012 9:38 AM in response to DanielJoshuaLambertby Ernie Stamper,Interesting, but not immediately logical it seems to me! Are you absolutely certain that the RAM you ordered was the RAM you received? Are you absolutely certain you order to correct version of RAM from Crucial? Did you use their app to check for the correct version?
I added Crucial RAM to my Mac Pro, btw, and nothing like this has happened.
Ernie
-
-
May 31, 2012 10:39 AM in response to DanielJoshuaLambertby DanielJoshuaLambert,Hi guys
I was guided to this test by apple - and the file I had to download wouldn't work and no matter what they tried we couldn't run a test.
Also, yes it was ram picked by the selector on crucials site...!
I've got replacements on the way...so will let you know how that turns out.
I'm slightly paranoid - as today I lost two images (vital!) and it happened so soon I didn't have a chance to back up.
Hmmmm