Also applies to ACR 6.7 final, which shows the same artefacts for LR-images edited in Photoshop (rendering using photoshop's ACR).
P.S. May be related to http://feedback.photoshop.com/photosh... but I think they are two different/distinct problems (however, both seem to be introduced with changes in clarity in RC2).
I think you are seeing the difference between PV2010 's Develop settings and PV2012 "automatic" White and Black point settings. PV2012 shows more detail in the shadows and highlights, which is not a defect. It's just accentuating the lens defects.
Try this:
Adjust the image file using only PV2010 Basic controls and everything else turned off (zero'd as you say). Now create a virtual copy, change the copy to PV2012, and adjust the Basic controls so it looks as close as possible to the PV2010 image. When done the two Histograms should look virtually identical
Do you still this "hard edge high contrast artifact" in the PV2012 image with no other adjustments (i.e. No Lens Corrections tools) applied?
I did as you suggested and experimented a bit. There was very little difference with the high contrast edges between PV2010 and PV2012 with or without Lens Corrections using a baseline image. But like LRusser24 I obtained similar results (I'll call it the barber pole effect) when applying Clarity with or without Lens Corrections (distortion and CR) applied.
Attached are two screen captures (100% crop in LR) including the settings panel.
Left is PV2012 w/Lens Correction/Clarity 0.
Right is PV2012 w/Lens Correction/Clarity 50.
Clarity set at 50 exaggerates the artifacts, but I was seeing those effects at Clarity 10.
I can see the same artifacts, but it only appears where there is chromatic aberration and/or fringing present in the image. It looks like Clarity is being applied to the image prior to CA and/or Defringe removal, because you can still see it with these two tools enabled. The high Clarity setting to seems to amplify the CA.
When LR builds the preview or export image it applies the Develop settings using several operations and several bitmaps, which are then merged to create the final processed output. What I think is happening is that the Clarity processing uses a bitmap that does NOT have any CA settings applied to it. This accentuates the CA (i.e. fringing), leaving halo like artifacts even after CA processing is applied.
LR3 'Fill' tool creates similar halo artifacts perhaps for the same reason, but we all assumed this was corrected in LR4.
LR 4.1 final and ACR 7.1 final: The "thick" artefacts when using lens corrections are gone, but the "thin" variant shown in my post above are still there. Note: The artefacts still change shape when changing lens correction parameters, but they always stay "thin".
I am slightly disappointed. However, the "thin" variant is probably visible only in 100% view on monitor. I am not sure whether it is visible in normal cases, e.g. prints.
This is a limitation of the current technology, a tradeoff we had to make to keep performance reasonable (otherwise to use the Highlights, Shadows, or Clarity sliders would be several times slower and use a lot more memory ...)
Can you elaborate a bit, please? Under what circumstances do these limitations arise? Generally, I don't see these artefacts. Is this when Highlights, Shadows, or Clarity are pushed to far, when there's purple fringing on the edge or a combination of both?
Dorin, generally this can happen with strong edges (e.g., dark branches against a bright sky), when used in conjunction with strong settings of Highlights, Shadows, and/or Clarity. The tone mapping methods behind these controls are edge-aware in the sense that they try to minimize halos across strong edges, as you'd expect to see if you were to try doing local dodging/burning with a brush. The underlying masking technology to minimize these halos is very complex and expensive, so we had to make some tradeoffs to get performance to a reasonable level in an on-the-fly, parametric editing system.
The "on the fly" part is why we really need a progressive rendering system, so we don't have to make those sorts of trades if we don't want to. We used to have "pixel doubling" and detail panel settings applied later, but these have been removed. I'd like to see them back with a slider for the user to decide just how "on the fly" the renderings have to be.
Thank you Eric, I understand and appreciate the tradeoff concerning maintaining LR's real-time operating performance (screen image building), but what about output image building?
Would it be possible to incorporate changes for better imaging during Export, Edit In, Print, and other output operations? I think most users wouldn't mind waiting a bit longer for their final output to be processed, especially to achieve the best results. I know this may cause complaints about screen imaging not matching the output, but we're talking very small artifacts. IMHO that is also a justifiable limitation of current technology “tradeoff" that most users would accept.
This is just a suggestion for improving an already outstanding product, my compliments to you and the rest of the LR team.
When activating lens profile correction and when i change my process from 2010 to 2012 and using the shadow recovery slider above +20 :
the black area close to white area are becoming jagged and stripped whithin the black area around the white
eg .A white texte on a black surface
My Camera is Nikon, and this apend for any camera i had
This issue is going to be hard to explain but I will give it a shot. I recently upgraded to Lightroom 4.3. After making adjustments to a photograph in Lightroom, I press CMD+E to open the photo in Photoshop. But when the photo opens, it has weird artifacts along the edges of the subjects within the photo. So, alternatively, I export the photo to my desktop and then open it with Photoshop. When it opens, the artifacts aren't there. The artifacts are only there when I use the 'Photo>Edit In' command within Lightroom. When viewing the photos in Lightroom, the artifacts are not present. I am using Lightroom 4.3, Camera Raw 7.3, and Photoshop CS5.1. The artifacts can be seen on the sleeve in the uploaded photo..
This bug has been introduced in ACR 6.7 and the release candidates of 7.1 and LR 4.1. The bug has been subsequently fixed in 7.1/4.1 final, but will never be solved in 6.7.
So, you only option is to render using Lightroom when prompted. If you don't get this prompt when hitting Ctrl+E, reset your warning suppressions in Prefs->General->Reste all warning dialogs.
The 'render using Lightroom' option worked. Thank you for your help. I just spent a couple weeks cloning that crap out of 200 photos. That was a real pain. Again thanks for taking the time to help me.
40
Replies
AdChoices