Currently Being ModeratedOct 10, 2012 6:45 PM (in response to Louis C. Oberländer)
That looks pretty weird: It's not just darker there's an entire color shift. You don't have soft proofing turned on somehow do you?
Currently Being ModeratedOct 10, 2012 7:01 PM (in response to Louis C. Oberländer)
I have the same problem after being prompted to reprocess my library after the recent upgrade. All my NEF files from a D700 have a dark green cast. Totally unusable.
I assume the files aren't corrupted and I can just move my entire library to Lightroom if necessary?
Currently Being ModeratedOct 10, 2012 7:08 PM (in response to S. Yokel)
I would like to switch to lightroom after this, but I thought that switching to lightroom, you can't keep the adjustments you've made to photos in Aperture.
Currently Being ModeratedOct 10, 2012 7:17 PM (in response to quemas)
That is correct. Adjustments in Aperture and Lightroom both are database parameters and thus not transferable between programs. You can export/transfer keywords and other metadata (like star ratings) if you do it right - Google would help with this.
That said, it makes more sense to find out what's going wrong here.
Currently Being ModeratedOct 10, 2012 7:52 PM (in response to William Lloyd)
I will try to use time machine to restore a pre-upgraded version of my aperture library. I notice a number of my NEF files also have an "i" inside a triangle (corrupted?).
I'll report back tomorrow, 30K file library.
Currently Being ModeratedOct 10, 2012 8:04 PM (in response to William Lloyd)
I know, that's what is so confusing. It is literally a different type of processing, as if some parameters have been swapped within Aperture. I am not aware of "soft proofing" I will try to look it up and find out. If you have any pointers, that would be great!
Currently Being ModeratedOct 24, 2012 5:46 PM (in response to William Lloyd)
So I double-checked, no, no Soft-proofing (even if it where, soft proofing changes are mostly very subtle, what happens over here is RADICAL)
I've been contacted by Apple in regards to this issue and they have confirmed the issue.
It's been a HORROFYING 4 weeks and I still don't know how to handle 1000s of pictures that have been screwed up... There is kind of a workaround, but it's too tedious because its not batch applicable!
Sorry to say but his puts Aperture into into the amateur category as great as this software is otherwise. Any software that deals with data on a professional has to make sure that the data integrity of finished versions is being protected.
I'm so upset, it's maddening. I lost 5 clients already because of this issue!!
Currently Being ModeratedOct 24, 2012 6:22 PM (in response to Louis C. Oberländer)
Did you try again with today's RAW camera update 4.0.1? Curious if you select the problem photos and reprocess originals whether it's any better.
Currently Being ModeratedOct 24, 2012 8:33 PM (in response to S. Yokel)
I used Time Machine to grab an older version of my Aperture Library. When I opened it up, Aperture prompted me to correct some inconsistencies in the library. I remember doing this to my old Library and I think this is what caused my problems. I have been running my restored library for about a week now and everything seems stable and all files are correct. The prompts to "repair inconsistencies" seemed to go away after I rebooted several times and repaired permissions. DO NOT FOLLOW THE PROMPT TO REPAIR LIBRARY INCONCISTENICES. I believe it is a bug in the new version of Aperture.
Currently Being ModeratedOct 25, 2012 12:45 PM (in response to William Lloyd)
I just updated to RAW 4.0.1 and its still doing it for me. I'm curious through.. I'm still using Lion. Is is possible that upgrading to Mountain would solve this? When I look at the specs for the new RAW update, my camera (Canon 7D) is listed in the cameras supported by mountain lion. I don't know enough about what is actually happening to know.
I'm hesitant to switch to Mountain lion because I have other software that isn't compatable.
Currently Being ModeratedMar 18, 2013 10:58 PM (in response to Louis C. Oberländer)
Did you ever find a solution to this problem? I still have not, but I kind of gave up for a while. Its very frustrating.