I can duplicate the overly light result with a 100 Clarity, but I get normal results from letting LR render...so it may be an "issue" with ACR 6.7 RC1...thanks for pointing it out.
I can duplicate this, also:
Either by using Open Anyway from LR4 to CS5 via ACR 6.7 RC, or
Opening a virgin image in ACR 6.7 RC and converting to PV2012 using the Camera Calibration tab Process dropdown and then adjusting the new Clarity2012 slider in ACR to +100.
The short answer is that ACR 6.7 RC’s Clarity2012 adjustment is stronger than LR4-Release’s Clarity2012 adjustment. It is not clear whether the LR4 Release Clarity2012 is too weak or the ACR 6.7 RC Clarity2012 is too strong. But they are different.
If I had to guess and remembering right, the Clarity2012 in the LR4 Beta was more intense than the Clarity2012 in LR4 Release and somehow ACR 6.7 RC is using LR4 Beta treatment instead of LR4 Release’s treatment. Maybe the same thing is occurring for the Adjustment Brushes in certain scenarios—ACR 6.7 RC is using an older code-branch of PV2012 process than LR4 Release has.
I posted this on the Feedback site, too:
It's not only the clarity. I can reproduce the problem also using an extreme "HDR" setting, i.e. lights and white -100, darks and black +100 (adobe defaults otherwise, clarity is zero).
Render with LR4.0:
Render with PS-ACR 6.7 (slightly, but noticeably brighter in certain areas, difficult to see directly here in the forum, download and use a picture viewer):
So it must be something with PV 2012 of ACR 6.7 in general, not only the clarity.
I am able to reproduce this problem, and have entered the issue in our bug database.
I too have noticed differences - here was my tests, results... and observations?
I opened the same raw file 5 ways:
>From Lightroom to Photoshop:
1. "Open Anyway" (Default... although I don't know why)
2. "Render Using Lightroom"
3. "Open as Smart Object"
>Directly thru PS CS5 (w/ACR 6.7 plug-in)
4. Open as "Smart Object "
5. Open as "Image"
- #2 & #3 are slightly darker than #1 "Open Anyway" and appear to look most like the LR4 rendition
- #4 & #5 looked similar to each other and similar to LR's #1 "Open Anyway"... all were slightly lighter than LR #2 & #3 (most faithful)
- It appears that opening thru LR takes advantage of its ACR 7.0 with PS's ACR 6.7 having the capability to maintain LR's ACR 7.0 adjustments.
- Opening in PS uses the ACR 6.7 plug-in and does not have all the capability of ACR 7.0 in LR
...maybe this it what the LR message "Open Anyway" means - it defers to the PS ACR Plug-in (this is just a guess)
I am hoping these issues are because 6.7 is a "Release Candidate" and would expect that in the final ACR plug-in 7.0, opening any way will look the same.
Yeah that's pretty much what it means when Ben says "I am able to reproduce this problem, and have entered the issue in our bug database."
It'll get fixed...count on it...
Saw no mention of "Smart Object" and thought it might have added something to the discussion, sorry
Well, I think the info about the smart object is interesting
Didn't expect that opening as a smart object from LR4 would render the image correctly (did not try it out myself, though). This could be an important info for the ACR developers - perhaps there is nothing wrong with ACR's PV2012 "machine" itself, but only in the way that the parameter values are transferred from LR to ACR when "edit in..." ist used. This could also mean that the problem is not on the ACR side, but on the LR side.
maybe this it what the LR message "Open Anyway" means - it defers to the PS ACR Plug-in (this is just a guess)
Yes, this is exactly what "open anyway" means: "As customary, I (LR) wanted to delegate the rendering to Photoshop's ACR, but noticed that its version does not match my version, so: Open anyway?"
Yes, I was surprised/pleased that "Render using LR" and "Open as Smart Object" were similar and consistent with the LR adjustments. "Open Anyway" and opening thru PS/ACR 6.7 we similar but lighter than when using LR's ACR 7.0 engine. This leads me to think that opening through ACR 6.7 (whether thru LR 4's "Open Anyway" or thru PS/ACR), the culprit is the RC 6.7 which probably will never see the light of day but just show-up as ACR 7.0.
One interesting noet about opening as a Smart object thru LR - the files are uneditable in ACR 6.7 and must be converted to PV2010 to be processed. Again, leading me to believe tha ACR 6.7 RC is just a stop-gap to opening your LR4 adjustments.
Adobe supports is LR and PS integration and LR4 was released when CS5/ACR6.x was the current version of Photoshop, so ACR 6.7 should see the light of day because it is what allows the current version of LR to operate with the current version of PS; however, ACR 7 is the only version of ACR that has a compatible UI to LR4.
My testing of Smart Objects from LR4 to CS5 via ACR 6.7 RC shows the expected erroneous brightening with Clarity of +100, which should occur because ACR is rendering for PS, not LR. You don’t need LR to have a SO in PS.
I am testing with a Canon CR2 file. If you are seeing no extra brightening, then are you using a DNG? Perhaps PS uses the embedded preview in the DNG as a shortcut for the initial SO view; however, if you go into PS and do an Edit Contents of the SO, which brings up the ACR 6.7 RC interface, then I’d expect you’d see the erroneous extra brightening.
I am testing with a Canon CR2 file.
Same here. Confirmed that with a CR2 file, too (EOS 40D). The smart object variant is too bright, too. And the same happens when not using LR at all (open the raw in PS-ACR, set to PV2012, set clarity to 100). So it is not LR that is to blame, but ACR 6.7 RC itself
Clarity2012=+100 in ACR 6.7 RC is much brighter (stronger) than in LR4. It is unclear where the error is.
It’s possible that LR4 was released with a Clarity2012 that was tamped down too much, and I actually prefer the super-Clarity adjustment in ACR 6.7 RC because it lets me achieve a creative pseudo-HDR or Grunge look using one slider instead of minning and maxxing out several of the other toning sliders. Of course, because LR4 has already been released, its PV2012 treatment is official and would supersede any beta treatment even if the beta treatment was what was intended and LR 4 actually has the error, unless Adobe pushes a LR 4.0.1 out the door within the next week or so, like they did with 1.4.1 when 1.4 was corrupting files.
There is a "work-around" to this ACR 6.7RC issue !
It is PS CS6 beta! The free beta (now available) ships with the ACR 7.0 plug-in...
- now more queries: "Open Anyway" / "Render using LR"
- the raterized "Background" layer and opening as a "Smart Object" have no brightness shift and produce the same results consistent with the LR4 processing.
The options using PS CS5 are"
- "Render Using LR" and wait for the ARC RC 6.7 to be fixed.
This is now fixed in ACR 6.7/Lightroom 4.1.