Strange RAW processing problem

I've just jumped into the Mac world recently with a Mac Pro (which I absolutely love). I've been watching Aperture since it was announced. A friend of mine has been using it for a while. He has Cannon cameras and so he is golden. However, I was playing with it the other day to get a feel before I decided to purchase. I loaded up a set of RAW files from my Olympus E-500 and was ready to play. Unfortunately several of my shots ended up looking like this on screen:
http://PhilU.smugmug.com/photos/103737186-M.jpg
Lightroom (Adobe's RAW processing has always been excellent) shows the same problem images just fine:
http://PhilU.smugmug.com/photos/103737163-M.jpg
This is on Aperture 1.5 on 10.4.8.
This seems to be an issue with long exposures that have the "Noise Reduction" (dark fram subtraction) turned on. I had a few long exposures with it turned off that looked fine and also some shorter exposures with it turned on that looked fine. That's just speculation though.
Has anyone else run into this? Is there anything I can do to make it work?

Yea, same for me in all apps using the core RAW functionality (Preview, iPhoto, Aperture, etc.)
I had thought this thread was dead long ago. I did get it submitted as a bug on http://bugreport.apple.com back then - it is still in "Open" status. Hope they get a chance to take a look at it.
The upside is that the workaround I mentioned before is still in effect. I also noticed that the last RAW update included a DNG fix so that files converted with the newer versions of the DNG converter are read properly. Would still be nice to have native ORF working properly (it does work fine most of the time, just not with images of the particular combination listed above).

Similar Messages

  • RAW Processing problems with Canon 5D Mark iii

    I am having problems with the RAW files coming from my new 5D Mark iii in Aperture. I have the latest version of Aperture (and update) installed. Selecting a picture style on the 5D doesn't seem to yield any results because when I import the photo into aperture all the images go very dark. I have to pull the exposure levels up all the way to get a decent exposure. The histogram on my camera looks perfect but when imported into Aperutre the histogram changes. I have my custom picture style set to give me a very flat image (contrast off, sharpening off, saturation -2, color tone 0). The images looks very flat and perfect in my LCD but once imported into aperture the RAW processing makes it very dark. I even tried shooting the exact photo in three completely different picture styles but they all look identical once they are in aperture. What's going on??

    Here is a side by side comparison of a RAW image in the latest versions of Aperture and Lightroom. I have never had these issues with the 5D Mark II only the Mark III. As you can see Lightroom produces a nice flat image while Aperture is under-exposing the image. Any thoughts? I really want to continue to use Aperture but with my recent camera upgrade to the Mark III I don't see how this is possible. Anyones help would be much appreciated.

  • My student has been using Lightroom 4 with Photoshop CS5 on her Mac for well over a year. Because of the difference between the Camera raw version available to her in Photoshop CS5 and the raw process in Lightroom 4, she has been exporting her raw images

    Any ideas?

    My student has been using Lightroom 4 with Photoshop CS5 on her Mac for well over a year. Because of the difference between the Camera raw version available to her in Photoshop CS5 and the raw process in Lightroom 4, she has been exporting her raw images from Lightroom and choosing the "Render using Lightroom option when it popped up in the dialogue box. She has been doing this for over a year and a half without any problem. Today when she hit Command E no dialogue box appeared and the image just opened in Photoshop. I'm concerned that all of her Lightroom edits are not being rendered to Photoshop. Anyone have an idea as to how we can get the "Render using Lightroom" dialogue back?

  • Why my raw looks different in lightroom and camera's raw processing software

    Hi, I am using a Sony A-100 and just start using Lightroom to process my raw file. I quite like lightroom's interface and its workflow, however, a a problem disturbing me is the image look quite different in sony's raw processing software and in lightroom (just import without any editing). In sony's software, the WB and exposure is correct and I don't need to adjust so much. But in lightroom, the color always looks warm and image is underexposure.
    Is it a common problem or it is just a special case as to sony's dslr camera.

    The main reason is that each different software is interpreting image and color data in its own way due, I guess, to different processing methods.
    In that way, digital is not different than film : no film render colors and contrast the same way.
    You have to choose what fits the best for you.
    As an example, I think ACR / LR handle Canon files pretty well ( quite close to Canon's propietary raw converter - neutral settings - ). On the other hand, Nikon owners have more troubles and seem to prefer Capture 4 or NX renderings.
    Gilles.

  • This photo was adjusted using an earlier version of Apple's RAW processing

    It is May 16 2012. A couple of days ago there was an update to OSX. I am now at 10.7.4. My Aperture version is 3.2.3. Digital Camera Raw 3.12.0 build 615 and a bunch of zeros.
    Last night when I imported a slew of photos, everything seemed to go well, but when all processing was complete all of the photos changed to a deep green hue. I finally found the message in the title line: "This photo was adjusted using an earlier version of Apple's RAW processing" and somewhat resolved the problem by individually reprocessing each master.
    Does anyone know what has caused Aperture to act this way and how the problem can be fixed? From a timing perspective, I feel that it was the OSX update, but I cannot be sure.
    Thanks in advance for any assistance.

    I am on a MacBook Air (mid 2011) running Lion 10.7.4 and Aperture 3.2.3 with Digital Camera Raw 3.12.0.  I have the exact same green photo import problem described above.  I have a Panasonic Lumix DMC-GF3 and I shoot RAW.  Sometimes (I can't seem to determine what triggers this), when I click on the photo and Aperture brings it up in the Split View, Aperture briefly re-processes the photo and displays it without the green tint, but now the photo is over exposed.  If I right click->remove all adjustments, then the photo finally displays correctly.
    Sometimes, Aperture tells me "This photo was adjusted using an earlier version of Apple's RAW processing".
    The fix suggested by Snoop Dogg at https://discussions.apple.com/thread/3942768?start=30&tstart=0 took away the green tint.  But now the recently imported photo is still over exposed.  By default, I turn on "Auto Enhance" on on my imports into Aperture.  I still have to right click->remove all adjustments, then the reapply the "Auto Enhance" quick fix before my photo finally displays correctly.
    Any thoughts on this would be appreciated.  Thanks.

  • ACR vs Aperture for Raw Processing

    I have been using Lightroom for over a year (including beta versions on my old PC), but have grown tired of it's lack of worthwhile output options. I have a trial version of Aperture and think that it is a far superior product on the management and output side of things, but I am having problems getting my raw files to look good to me.
    I could process all the files in Bridge first, then create tiffs or PSDs to import into Aperture, but that would negate have the purpose of Aperture. I need help with an Aperture workflow and probably with raw processing controls in Aperture.
    Specs: 17" MBP with 10.5.1, Aperture 1.5.6
    Camera: Pentax K10D ver 1.3
    I typically convert my PEF files to DNG due to better compression in DNG, but have tried using the original PEF with identical results. Any help is appreciated.

    I too came back to Aperture after a year of Lightroom's "workflow". It really is possible to match or surpass LR's output. There's a good guide to the adjustment tools here:
    http://www.insideaperture.com/Site/AdjustmentToolGuide.html
    Also lots of tips about workflow, etc. here:
    http://www.bagelturf.com/
    You probably won't want to spend too much money if you're just using the trial, but Ben Long's book
    Aperture Pro training Series: Aperture 1.5 is very good.

  • Leica D-LUX 4 (LX3) RAW Processing

    Hi all,
    Just wanted to report some interesting behavior regarding the long-awaited RAW processing ability for the D-LUX 4 and Panasonic LX3. I did not see this happen on the first library I coverted, because I let Aperture do the image processing, so the files were already converted when the Library upgrade process finihed.
    Anyway, this time I did not process images when doing the upgrade of my personal library, because I wanted it to finish the task quickly. It did about 3 hours for some 40K photos.
    I had been shooting RAW + jpg since I got my Leica D-LUX 4 in the hopes that Aperture would support it some day...and that day came!
    Anyway, the .RWL RAW files show up in the browser view as black boxes with the warning triangle. They convert when you select them individually, and that was pretty much as expected.
    What was cool though, was when I had opened an .RWL image into Split View, and then arrow key selected the next unprocessed image. Aperture displayed "Unsupported Picture Format" on top of a low res image that had really severe lens distortion for an instant in what appeared to be a 16:9 or longer aspect ratio image, then displayed the properly converted 4:3 RAW file.
    This is obviously the lens correction processing that is part of the way the camera operates, and that A2 was incapable of converting correctly. I thought it worth mentioning that you can sort of see it at work in A3.
    It is so great to have A3 do such a good job on these files, and be so responsive. Really enjoying getting to work with my Leica RAW files finally.
    THANKS APERTURE TEAM!
    Sincerely,
    K.J. Doyle

    Tonys264 wrote:
    I have been waiting for over a year for RAW support for the Leica D-Lux 4 using Aperture 2. It seems that this support is only going to be offered for Aperture 3 users. I have asked at my local Apple Store for an explanation without any success. Is it really just a marketing ploy for A3, or was there a technical reason why A2 could not have support for this camera??
    Hi Tony,
    Now I am not sure if this conversion works on a machine without Aperture 3 on it, because all of the machines here have A3 on them...
    BUT...
    I just dragged a .RWL file into iPhoto and it opened, no problem.
    I have no control over the conversion, of course, and the better control system for RAW is what you are paying for in A3.
    I shot over 30K images with my DL4, storing RAW + JPG hoping for this, and seeing them come up in A3, and be so workable (better that Phase one) was a very happy day for me.
    Sincerely,
    K.J. Doyle

  • This photo was adjusted sung an earlier version of apple's RAW processing

    Using Aperture 3 I recieved this message when opening a new set of photos.  The reprocessing button does not work and all adjustments are not functioning.  What do I need to do be able to process these photos?

    I am on a MacBook Air (mid 2011) running Lion 10.7.4 and Aperture 3.2.3 with Digital Camera Raw 3.12.0.  I have the exact same green photo import problem described above.  I have a Panasonic Lumix DMC-GF3 and I shoot RAW.  Sometimes (I can't seem to determine what triggers this), when I click on the photo and Aperture brings it up in the Split View, Aperture briefly re-processes the photo and displays it without the green tint, but now the photo is over exposed.  If I right click->remove all adjustments, then the photo finally displays correctly.
    Sometimes, Aperture tells me "This photo was adjusted using an earlier version of Apple's RAW processing".
    The fix suggested by Snoop Dogg at https://discussions.apple.com/thread/3942768?start=30&tstart=0 took away the green tint.  But now the recently imported photo is still over exposed.  By default, I turn on "Auto Enhance" on on my imports into Aperture.  I still have to right click->remove all adjustments, then the reapply the "Auto Enhance" quick fix before my photo finally displays correctly.
    Any thoughts on this would be appreciated.  Thanks.

  • How to combine Camera-Raw processed files to be viewed within Windows Explorer as processed

          The problem I have with  camera processed files is that when viewed within Explorer what you did on the file, the crop, and other effects are not visible within Windows Explorer. What is visible there is the original file--this seems to be true of the original nef file in my case.  The change does appear if you save it as a .tif, .dng or .psd but not the NEF. But if you were to open again the NEF file and the RAW Window opens you can see your changes immediately.
            I know it is because  with an original raw file nothing has been done to the image except give it instructions so to speak but Bridge does see it as such so why not let Explorer (Or other viewers, for ex. XnView) view it as such as well? Perhaps this is more a Microsoft Windows issue or what-have-you but I thought I would start to present it here first.
    Where's the question? The question is not actually for someone to explain why this is so, I think I may understand this a little but rather the question is, would it be possible to let other software such as Explorer see the raw processed file--to let it see it as Bridge sees it? Yeah I guess this may be a Windows issue but.....
       Why does this bother me? Since I don't use Photoshop or Bridge professionally I view images more often in Explorer then I do in Bridge or PS (The former is instantaneously viewable while the latter take way to long to open--and Bridge vs. XnView needs an extra step.)
            Side note: Sometimes I feel I am wasting my time and yours in writing such silly questions nevertheless they present themselves in my brain and in the process I hope to learn something from it regardless of its silliness/stupidity. It is such questions which at times creates something original, therefore creativity, after all, does it not? (Or so I tell myself in order to justify it all :-)

    You can't...
    Camera Raw plug-in | Supported cameras
    Camera Raw-compatible Adobe applications

  • Older Verions of Apple's RAW Processing?

    I cannot edit files in one of my projects. All of the Adjustment options are dimmed and in place of the histogram it says either "Image Offline" or "Image Not Found." I tried updating with the master but it couldn't find the master. It also says, in dimmed text,"This photo was adjusted using an earlier version of Apple's RAW processing." All (at least I think I checked all) other projects taken before and after (the photos in this project were taken 10/29/10 to 11/1/10) show the histogram and I think the adjustment options are usable. This file contains a couple of images I really like but I want to make adjustments. What did I do wrong? Can I update this project with Time Machine? If so, how? "About Aperture" says I have Version 3.1 followed by 1290000.2 and "Digital Camera RAW 3.4.1 - Build 5460000.1
    I know I updated Aperture recently but I don't recall when. Is this something I need to worry about happening to other projects? Thanks for any insights.

    I am on a MacBook Air (mid 2011) running Lion 10.7.4 and Aperture 3.2.3 with Digital Camera Raw 3.12.0.  I have the exact same green photo import problem described above.  I have a Panasonic Lumix DMC-GF3 and I shoot RAW.  Sometimes (I can't seem to determine what triggers this), when I click on the photo and Aperture brings it up in the Split View, Aperture briefly re-processes the photo and displays it without the green tint, but now the photo is over exposed.  If I right click->remove all adjustments, then the photo finally displays correctly.
    Sometimes, Aperture tells me "This photo was adjusted using an earlier version of Apple's RAW processing".
    The fix suggested by Snoop Dogg at https://discussions.apple.com/thread/3942768?start=30&tstart=0 took away the green tint.  But now the recently imported photo is still over exposed.  By default, I turn on "Auto Enhance" on on my imports into Aperture.  I still have to right click->remove all adjustments, then the reapply the "Auto Enhance" quick fix before my photo finally displays correctly.
    Any thoughts on this would be appreciated.  Thanks.

  • PSE9 Organizer Preview not matching Raw Processing preview

    I noticed the preview in Organizer does not match the preview when I open it in the Raw processing window of Elements. The Organizer preview is much more saturated and when I process the file in the Raw processor the preview updates with the added adjustments making it look like its over processed.
    Does anyone know what is causing this problem.
    I am working on a Mac 10.5.8 and I have the regular Creative Suite 5 installed on the computer.

    The ACR version used are different in PSE and PS CS5. That can be cause of change in preview. Can you open same image in PSE and PS and then compare if they are different.
    make sure you have set ACR dialog box settings to default and not custom or nay otehr saved settings.
    -Garry

  • Canon sx40 RAW processing

    I shoot RAW with Canon SX40 HS using CHDK. Aperture reportedly has a profile for Canon SX50 (not 40) RAW. Does anyone know how Aperture might interpret a RAW image that's associated with the SX40? And is there a way to change the camera model to "fool" or force Aperture into using it's SX50 profile for RAW processing? I don't see any controls for telling Aperture to use a particular camera profile. (Of course, all this may be for naught since Aperture is being discontinued...)
    thx
    mike

    I am having the same exact problem with my 60D. All of my photos process with a dark magenta hue in the blacks. Upping the exposure or brightness on any of my RAW photos causes the pinks to come out of the blacks and the photo looks even more overly saturated with pink. If I shoot in both JPEG and RAW simultaneously, the JPEG looks as it should be. But once the RAW version reaches Aperture, or OS X in general, the pink hue is very apparent and has ruined all of the photos I've shot since I first got the camera.
    It should also be noted that processing the RAW files with the factory software supplied by Canon with the camera processes the photo as expected without the dark magenta hues. Could there be an issue with the RAW compatibility that Apple delivered in the OS X 10.6.5 update? I doubt this is a problem with the camera as the RAW file looks fine when processed with any software that isn't Apple related such as Aperture, iPhoto, or Preview.
    Attached is a screenshot of a normally processed RAW file (top) and an Apple/OS X processed RAW file (bottom), same exact photo:
    http://imgur.com/K9jQs.jpg

  • How do I update a folder of DNGs to the new 2010 (Current) Raw Process?

    Is there an efficient method to update an entire folder of DNG images to the newer RAW process in Camera Raw 6.1 - to "2010 (Current)"?
    And as an added bonus, it would also be great to simultaneously update the Camera Profile - to "Adobe Standard".
    I have lots of folders of DNGs that were processed in ACR 5.7 or Lightroom 2.7, and so they were processed in the older, 2003, process version.
    I see that when I update a single DNG in Lightroom 3's Develop Module that I am asked if I want to update all of the photos shown in the Filmstrip at the bottom of the window.  This is very convenient!
    My father does not yet have Lightroom 3, but does have Photoshop CS5 and ACR 6.1 installed and he wants an efficient method to do the same using those tools. We found that if we open the folder in Bridge, select all the DNG images, open the multiple images in Camera Raw, click on the "Select All" button in the upper left corner of the window, that we can then go to the Camera Calibration panel and make these two changes to all of the images simultaneously.
    It seems like there should be some method of doing this from within Bridge. When we go to Edit -> Develop Settings -> Copy Camera Raw Settings and then select all of the other DNGs in the folder and go to Edit -> Develop Settings -> Paste Camera Raw Settings.... and choose only the Camera Calibration checkbox, that only one of the two settings actually gets changed; the Camera Profile setting does - the Process version does not.

    austinmirage wrote:
    Is there an efficient method to update an entire folder of DNG images to the newer RAW process in Camera Raw 6.1 - to "2010 (Current)"?
    And as an added bonus, it would also be great to simultaneously update the Camera Profile - to "Adobe Standard".
    You CAN easily make a Camera Raw preset or use Copy/Paste develop settings to change a folder's worth of files to "Adobe Standard"...that's simple. However, currently the Process version is not captured in a preset not copy/paste settings...the only current method is to actually open images inside of Camera Raw, select all and change the Process version to what you want...note, even Sync won't sync the Process version...only select all and then change the setting.
    It's hoped in the future this will be somehow addressed...it will require that the subsetting for Process version be a separate item in the Camera Calibration settings.

  • RAW Processing Change?

    Today, I believe after installing the version 5.01 Digital RAW Compatibility Update, all of the pictures in my library produced by my Nikon D2x and D3 cameras are listed as being adjusted using an "earlier version of Apple's RAW processing." And clicking on the button to reprocess the RAW images does result in very minor changes.
    These cameras are pretty old models. Did Apple really sneak in some changes to RAW processing engine for older models along with the added models listed in the RAW Compatibility update? Nothing was said about this in the update page, and this happened before only with a major Aperture version introduction. Did this happen for anyone else?

    I'm seeing changes for many, perhaps all, my Sony camera bodies.  But first, note that the Images aren't -- iirc -- marked as "needing" to be re-converted -- they are simply marked as having been converted by a superannuated version of Digital Camera RAW.  I create my own RAW tuning settings, and save them as the default.  With DCRAW 5.x, I had to create new ones and save them again as the default.  But I didn't have to change any Images that had been converted with any of the older DCRAW versions.
    I think the notice I got was very similar to the one that shows up when you use the old "Highlights & Shadows (sic)" adjustment brick.

  • Raw processing - camera compatibility

    I own a Panasonic DMC-FZ18 camera, and was about to buy the newer FZ45. However, I note that Aperture only appears to support RAW processing with the FZ100 in that range.
    Does this mean I will not be able to process RAW images with either the FZ18 or FZ45? If so, is their any likelihood that these older models will to be added to the supported list?

    Correct. Also we have no way of knowing if any particular camera will be added.
    Regards
    TD

Maybe you are looking for

  • File to Trash Problem

    I have Snow Leopard on a Mac Pro with two hard disks. I have files on the secondary disk that will not delete. It gives an error code of 1407. When I check file information, the file is locked. I unlock it but it does not stay unlocked. Any suggestio

  • How to get the correct value from check box

    hi guys, here is a program to read data from IKPF. with the user tick on the check box, the program will retrive corresponding records based on the inventory counted (zstat) status. however i don't get the correct output with the following selection.

  • Best approach deploying BPM processes

    Hello, What is the best approach deploying a process through different organization units, as far as I understand when a process is deployed it is associated with an OU (for example a child OU_1) and then it is deployed to a soa_domain_1 so if I want

  • Javascript not working in any browser except Opera! Please help!

    I don't know for what particular reason, javascript has stoppped working in all the browsers I have, (Safari, Firefox, Camino, OmniWeb,)except on Opera. Can anyone direct me in the right direction to solve this issue?

  • How can I integrate CommPort into the JBuilder??

    I just downloaded this package and I can�t integrate it into my JBuilder 6 personal API. I copied every file the readme says to both lib and bin directories but nothing. I cant import it from javax!! I really need some fast help on this please. Thank