Sielk
Level 1 (0 points)

Q: Aperture corrupting images during editing

Hello,

 

Starting a few days ago, aperture started corrupting images during editing.  This was normally at the time of my fist cut, going through doing simple straighten and croping.  Sometimes it would happen when doing a small lighten or darken of the exposure.  I purchased a new MacBook Pro about a month ago but this only started happening this week.  No OS or Aperture upgrades this week.  I did have a crash earlier this week and after the crash my Spotlight re-indexed my computer.  I updated QuickSilver this week and Awaken.  I tried quiting both QS and Awaken but problem still happens.  The real scary thing is I usally have to go back and re-import the raw CR2 image to fix the problem, doing an update from master or resetting all adjustments does not fix the problem.  Below is an example of an image with the problem.  This is a Version Export of a corrupted image, as you can see the cor  Can I get any help?

 

rll_20110606_1116.jpg

MacBook Pro, Mac OS X (10.6.8)

Posted on Jul 9, 2011 9:08 AM

Close
Sielk

Q: Aperture corrupting images during editing

  • All replies
  • Helpful answers

first Previous Page 4 of 4

  • by teamDWP,

    teamDWP teamDWP Jul 11, 2013 1:53 PM in response to Sielk
    Level 1 (0 points)
    Jul 11, 2013 1:53 PM in response to Sielk

    I'm so glad I found this discussion. We are wedding photography studio that has been using aperture since day 1. Recently, we changed our workflow as three of us need to access projects in the same library. We have been exporting libraries and then exporting originals so we can edit the images. We have started to run into all of kinds of problems within this process, the biggest one being that when we export originals, it somehow corrupts our referenced master files. This problem has happened consistently in projects which have been exported then merged. We have three backups of everything, and have been able to restore these corrupted files, but figuring the problem out has been a huge headache. It most definitely is a bug within aperture that occurs when you export the originals.

     

    We have adjusted our workflow so that we do not have to export projects and masters anymore. If you have backups of the originals, all should be well!

     

    -Nancy

  • by DG1234567,

    DG1234567 DG1234567 Jul 11, 2013 2:13 PM in response to DG1234567
    Level 1 (0 points)
    Jul 11, 2013 2:13 PM in response to DG1234567

    After a fresh replacement dimm from OWC, Mac is running full speed ahead with 16 GB again, no ITUNES issues and no Aperture image corruption issues since removing the offending DIMM.

     

    MEMTESTX spotted memory errors and pull and retest found the dimm with the errors.

     

    Looking good....

  • by dustobub,

    dustobub dustobub Jul 11, 2013 2:16 PM in response to DG1234567
    Level 1 (0 points)
    Jul 11, 2013 2:16 PM in response to DG1234567

    I can also confirm that my issue seems to have been resolved after replacing a DIMM that reported errors.

  • by imgmkr,

    imgmkr imgmkr Apr 4, 2014 12:17 AM in response to Sielk
    Level 1 (39 points)
    Apr 4, 2014 12:17 AM in response to Sielk

    Screen Shot 2014-04-04 at 15.40.34.png

    I used to get this kind of corrupred preview iamges of raw files once in a while but they are appearing  increasingly.

    It seems like the first image of imported from a memory card gets corrupted often time. The image appears normal first then after processing the raw image to generate a preview, it garbles up like the attached screen capture...

    It is **** annoying, Apple! I don't even store my originals in the Library, reference them on my local drive, albeit the Library files containing preview is about 35GB size managing photos for 6 years. Should I migrate to LightRoom now???

  • by DG1234567,

    DG1234567 DG1234567 Apr 4, 2014 4:44 AM in response to imgmkr
    Level 1 (0 points)
    Apr 4, 2014 4:44 AM in response to imgmkr

    Yep, had exactly the same problem, found 1 dimm was bad, replaced the dimm and no problems at all since, and I have a 400 plus GB managed library.

     

    Get yourself a copy of MEMTESTX and run it, it should find out if a dimm is bad.

first Previous Page 4 of 4