RAW Processing Workflow

Just attended a LR seminar where I realized that LR is a "gotta have it."
But there is one aspect that confuses me. I shoot RAW & Jpg on a 30D. I am not sure how to process the Raw files.
I know I have to get them into LR, so I download from Card reader into LR - or do I? It seems that both the RAW & jpg's will not be downloaded. So not sure what to do here.
But more important, I open a pic in LR, apply WB, other manipulations to the RAW file. Then I want to edit in PS CS2. so when I Open, will I go directly into PS or will I go into ACR? Once in ACR (or PS), will the pics look different than what I am seeing in LR after making cahnges in LR? Do I again apply things like WB, Exposure in ACR & then click yet again to open in PS?
So it seems that I am adding an extra step by using LR with RAW files, is that right? Then after I edit in PS, I suppose I save as a Tiff or Psd & then open yet again in LR for Printing?
So I guess in addition to not being clear about the way LR, ACR & PS interact, I am not clear if there is even a need to shoot RAW, or to shoot RAW & JPG?
Can someone help clear up my confusion?
Thanks

Not quite right. If you open a raw file in PS CS2 or CS3 from LR, ACR is always involved. Ensure that you use ACR3.6 or newer if you have CS2.
ACR will understand all adjustments you made within LR. The result is then stored is whatever format you choose.
If you use CS3 you can also set the preferences in CS3 to use ACR for the jpg files. This comes in handy if you have photos which are solely in jpg format and you are forced to use the jpg file as your master photo. Then also the LR adjustments will be seen in CS3.
Allow me a comment to your workflow. After working with LR for a while you may consider to skip creating jpg and raw in the camera. In my experience it is more convenient to just create raw files and import them to LR. The jpg for different purposes will be created with the LR export function and (in my case) stored in folders which are not managed by LR
I have to add that 99% of my photos will only need adjustments within LR and no further postprocessing within Photoshop.
regards
Chris

Similar Messages

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.

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.

Canon 6D RAWs processed awfully bad?!

Hi,
I previously owned a Canon 400D and loved Aperture for the entire workflow, it was just a breeze. Now got a new Canon 6D and also took some test photos with the 5D mk3, and every Raw that I import just looks awfully dark and contrasty.
That is, for a moment they look nice, and then, when they're fully loaded, they turn dark and contrasty.
I thought something would be wrong with the cameras, but opened up some of the pictures in lightroom or in Photoshop, using the adobe raw processor, and there, everything looks nice.
I never knew that the aperture raw processing was so bad, not just with colors, but also with noise reduction for example. Am I doing anything wrong, maybe with some secret color space setting or so (cam is set to sRGB), or are the raw profiles in aperture for these new cameras just not implemented properly yet?
Example Images:
Aperture:
http://chfilm.de/download/foto/IMG_0324A.jpg
Adobe Raw Conversion (nothing done, except hit auto adjust and increased the luma denoise a bit)
http://chfilm.de/download/foto/IMG_0324LR.jpg
what is going on?? I seriously what have never expected such an enormous impact on image quality by the software, especially since I thought Aperture was a Pro-tool. Look at the sharpness of the images!!

I have been fortunate enough to recently upgrade myself to a Canon EOS 6D. After my first shoot, I was heartbroken to see the poor quality of the images--dark, low contrast, etc. This was fixable in Aperture with some effort, but then I started noticing serious blue and orange color artifacts around high-contrast edges, and a near total loss of detail in deeper shadows. I was about to return the 6D as defective but then tried a couple images in Canon's RAW processing software. And I was blown away by the results--gorgeous images, perfect contrast and loads of shadow detail that could be extracted with the right adjustments. I also grabbed a trial of Lightroom, which produced results similart to Canon's software.
So there's nothing wrong with the camera. Apple's RAW converter for the 6D is just flat busted. How could something this bad have actually made it out the door?
I've been a long-term Aperture user--since version 2.0, and have grown to love the interface and the effortless workflow for organizing images. But the issues with the 6D RAW converter have pretty much forced me to abandon Aperture over night. Hello Lightroom.
As with previous comments, I suspect this is really just part of the thin end of the wedge with Aperture and that it may be headed for extinction. Sad.
Here is an example that shows the shadow issues. Both are 100% views of he same RAW file loaded without any additional adjustments--except that I've cranked up the shadow level to illustrate the Aperture RAW converter's failure:

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?

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.

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.

Resolve Process Workflows

Hi All,
I've just implemented an activeSync resolve process that notifies helpdesk staff that there has been an identity collision, and includes some information about the incoming data and the clashing identities. For the time being this is adequate.
Still, Identity Manager has a tonne of power and I know that I'm not using it. What are the things that you all would normally implement to handle identity clashes during activeSync processing? Is there any sample code out there that I can look at for ideas?

Hi.
Well, in fact, the new client is a copy of another and the background data for the workflow process is already copied. I just need to re-start the workflows but I was wondering if I can do anything easier than do it manually and one by one. Maybe a migration tool to copy "in process" workflows.
Another option is to redefine sub-WF and try to put every WF in his former situation, but the logic of the original WF is very complex so this is not an option.
I know that is very difficult to do that but...who knows!
Thanks for your interest.
Ismael

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

Document level scripting from process workflow

Hi all,
is there some way to add a "document level" script from process workflow in Livecycle Workbench?
That is, I have a script i want to add to a pdf in my process workflow. How can I do that? Is there some service/function/script I can use to do that?
I'd really appreciate any help.
Thanks
Alessio

Not that I am aware of, could be wrong though

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.

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.

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

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

Migrating in-process workflows

Hi all,
New to BPM. May be using 10g or 11g (possibly depending on the answer to this question). If I'm migrating workflows from another system, and a document is currently halfway through the workflow, how easy is it to take across that document and put it in a BPM workflow at the equivalent point in the process? Is it even possible?
Thanks in advance for any ideas/suggestions!

Hi.
Well, in fact, the new client is a copy of another and the background data for the workflow process is already copied. I just need to re-start the workflows but I was wondering if I can do anything easier than do it manually and one by one. Maybe a migration tool to copy "in process" workflows.
Another option is to redefine sub-WF and try to put every WF in his former situation, but the logic of the original WF is very complex so this is not an option.
I know that is very difficult to do that but...who knows!
Thanks for your interest.
Ismael

RAW Processing Workflow

Similar Messages

Maybe you are looking for