Erratic behaviour of Manual Lens Correction in Develop Module

64 bit Windows 7
Sometimes - not always - using the manual lens correction, with Constrain Crop activated, leads to the image jumping around very quickly and erractically and it being impossible to achieve fine control using the mouse: tiny movements of the slider by dragging with the mouse result in large jerky movements of the image. I have only used this for correcting converging verticals and cannot comment on the other adjustments.
Moreover, on a subsequent crop when this has happened, it may be impossible to crop as you would like using the crop tool - the top edge of the image jumps above the intended crop outline. The only way to get the crop you want when this happens is to adjust each edge individually, rather than by dragging the corner.
Apologies if I have not explained this well. In short, it seems to be a bug whereby proper mouse control of the lens correction is lost. I often correct converging verticals in buildings and have never seem the same behaviour in version 3. I cannot always replicate it in version 4, but it happens a lot.
Hope this feedback helps. I cannot see that it has been reported elsewhere in this forum.

Hmmm, this is going to be tricky. I just tried to replicate it on two photos on which I know I had the problem, by going back to the original import setting, but both behaved fine this time! Both, as it happens, were portait format, having been rotated 90 degrees counter-clockwise from the original. I cannot recall, I am afraid, whether or not other ones with which I had an issue had been rotated first. I will try to replicate and keep more detailed notes. In at least these two instances, I had not applied a lens correction profile first. The vertical transformation slider would be set to somewhere between -25 to -35.
Having played about with this for a while now without full replication, I have one idea which may or may not be correct. When I reset the Develop settings and started on the Lens Corrections first, absolutely nothing untoward happened. Now I have gone back and done a number of other adjustments first (as I would often do, before correcting the perspective). In this case, the vertical adjustment slider seems more sensitive to small mouse movements - definitely discernible, but not nearly as bad as the examples I have seen previously when I was not looking for them, nor is there yet any sign of the cropping problem. Maybe the effect becomes more pronounced as the number of edits accumulates before applying the manual Lens Corrections. If this is correct, I do not know whther the effect is cumulative across all edits to all images (as if memory is not being released - but that should not be a problem, since I have 12GB of RAM and nothing else running) or whether it is a per image phenomenon, since I have only recently re-opened Lightroom. You will know better than I whether this is a possiblity, but it is just a thought as I play with this without so far being able fully to replicate the issue. I have some work to do on a number of images and if I get time, I will come back to these images to see if the problem manifests itself more clearly after a larger number of edits across multiple images in a single session without closing Lightroom.
I am very sorry this is so vague and quite speculative. I hope I will be able to give you more accurate feedback later.

Similar Messages

Lens correction and Develop defaults

in this video http://tv.adobe.com/watch/the-complete-picture-with-julieanne-kost/enhancing-light/ J. Kost shows how to create default settings in the Develop module so that your photos are always lens corrected (she recommends doing that for every photo). I followed her instructions (they are pretty simple) and i'm getting mixed results. Sometimes when i open my photo in Develop, i see that the lens correction has been applied (good). Other times, there is none applied, and if i enable it, it applies the correction (so i know it can be applied.). All my photos are shot with the same Nikon D300, but some are shot with different lenses, and some are shot in JPEGs. I can't yet determine any pattern to why some have correction applied and others don't. Questions:
-- should this work for all photos shot with the same camera and different lenses?
-- should this work for all photos shot with the same camera but some in JPEG and others in RAW?
-- does this work only when a photo is opened in Develop?
Thanks!

eschurr wrote:
that's interesting and curious -- why is that? do you recommend only using manual lens correction?
The underlying "Warping* model required for distortion correction is very processor intensive, but this is not the only factor we need to take into account. The choice of how and when to apply the profile in the workflow should be based on, amongst other things, image content, lens used, cpu and system resources. For example, does every image really need geometric distortion correction? Do some images not actually benefit from some vignetting?
Above examples actually highlight another issue (i.e. both lens distortion and vignette correction are built into a single profile). First, we have the correction of geometric distortion, which is the correction that hurts local adjustment and healing brush performance. Then we have correction of lens vignetting, which tends to brighten up the image as whole, rather than just the corners. Applying the lens profile up front will hurt when you carry out any local adjustments or healing whereas any fine tuning of overall tonal balance on an uncorrected image will be screwed up when vignette correction kicks in. So, which hurts your workflow more slow brush performance or having to re-edit tonal balance?

Manual Lens Correction in Lightroom 4

The Manual Lens Correction sliders in Lightroom 4 seem completely useless. They aren't working the same as they do in Lightroom 3. Instead of being able to fix keystoning of images, now the horizontal and vertical sliders just stretch or distort photos. Is this a bug? If not, is it possible to go back to the functionality from LR3? If this isn't possible, I'm probably going to switch back to Lightroom 3, since this is one of the program's most useful features.

Lee Jay wrote:
... This functionality hasn't changed at all for me - it works exactly as before.
I think so, too.
See my example in the feedback forum demonstrating the different effect of the manual transformation sliders depending on the angle of view: http://feedback.photoshop.com/photoshop_family/topics/i_would_love_automation_in_the_lens_ correction_manual_panel : There is an automatic aspect ratio correction, and for photos taken with a rather small angle of view, this is mostly a stretch/distort. Which is totally correct IMHO (and hasn't changed since LR3).
P.S. I don't know which angle of view LR assumes for photos w/o information about focal length and sensor size (probably 50mm focal length and 35 mm film format ("full format") sensor.

Crashes with Manual Lens Corrections

Last night while trying to adjust vertical or horizontal distortion in the Manual half of Lens Corrections panel, I had 4 unexpected quits for 4 different images. Quirky, in that sometimes I can use those adjustments but last night no. Lightrroom was slow and when trying to navigate module changes, the spinning beachball would come on for 15 seconds. I tried a computer restart and it seemed to correct itself.
Mac OSX 10.6.8, MacBook Pro 2011

Are they photos that had existing settings when you imported them into the beta? We're seeing some crashes relating to lens corrections with PV2010 data, and slow sliders with existing data too.

Lens corrections temporarily disabling other adjustments

I have recently noticed something strange with Lightroom. Normally, I work my way down the Develop module making basic adjustments, using the various tools, and so on; the last thing I do is Upright or Manual lens corrections. However, I apply Lens profiles at the very beginning (because it makes a difference). Recently I noticed that when I apply Upright or Manual Lens corrections, Lightroom seems to temporarily disable any other corrections, apply the lens correction (which always seems to take forever), and reapplies the other corrections. I found this out after noticing minor black and white clipping areas temporarily reappear on a photo I had corrected with an adjustment brush while applying a Manual Lens correction.
I find this behaviour odd and do not know if it has any impact on any other corrections like adjustment brush correction (in this case I started wondering if Lightroom readjusts the adjustment brush area or not).

I have recently noticed something strange with Lightroom. Normally, I work my way down the Develop module making basic adjustments, using the various tools, and so on; the last thing I do is Upright or Manual lens corrections. However, I apply Lens profiles at the very beginning (because it makes a difference). Recently I noticed that when I apply Upright or Manual Lens corrections, Lightroom seems to temporarily disable any other corrections, apply the lens correction (which always seems to take forever), and reapplies the other corrections. I found this out after noticing minor black and white clipping areas temporarily reappear on a photo I had corrected with an adjustment brush while applying a Manual Lens correction.
I find this behaviour odd and do not know if it has any impact on any other corrections like adjustment brush correction (in this case I started wondering if Lightroom readjusts the adjustment brush area or not).

Lens corrections in PSE raw

I cannot determine whether lens corrections work in ACR 6.4 using Elements 9. I know the lens correction tab is not available - but does that mean no lens corrections are applied at all - or does it simply mean I cannot manipulate the correction beyond the default provided in ACR?

ACR will use whatever the ACR default is for the specific camera the raw file is from. I say this because with ACR 7, at least, you can enable Auto-CA (a manual lens correction) as the default for a particular camera when using ACR with PSE10, by editing the ACR camera-defaults file with a text editor.
Here is what I did on Windows 7 to enable Auto-CA for my brother who does not use LR nor PS, only PSE:
1) Open a new RAW image for the camera you are wanting to affect the settings of in PSE/ACR that has never had any edits done.
2) Go to the Camera Calibration tab in ACR (a black camera icon) and change the Process Version to 2012—this will update the camera-defaults file to have PV2012 values which include the Auto-CA. You can skip this step if you are using an older version of PSE.
3) Click the 3-dots-three-lines icon at the right of where it says Camera Calibration, and choose Save New Camera Raw Defaults from the bottom of the menu that pops up. This step will create a or update the camera-specific ACR-defaults file for your computer user.
4) Exit ACR with Cancel, and Exit PSE.
5) Using Windows Explorer, browse to the following folder under your user folder: c:\Users\yourusername\AppData\Roaming\Adobe\CameraRaw\Defaults\
The AppData folder is hidden so you may need to type this part into Explorer’s address bar.
6) In the Defaults sub-folder there should be one or more files named: Default_somehexdigits.XMP.
7) Open each of these XMP files and find the one that matches the camera the raw file was from. The value of the crs:KeyString attribute is the camera name.
8) Further down in this XMP file, look for several lens-correction-specific attributes and change them to be the following:
       crs:LensProfileEnable=”1”
       crs:AutoLateralCA=”1”
       crs:LensProfileSetup=”LensDefaults”
The other parameters for Vignetting and Perspective are for manual adjustments and you don’t want to set these other than “0” for your defaults although you can set them for an individual image by editing its XMP file.
9) Save the XMP file.
10) Start up PSE and open a new RAW file and see that the lens-distortion and Lateral-CA has been corrected as much as the auto-correction can do.

LR 3.2 Develop module not fluent but CPU not fully taxed

Hello,
on my AMD Phenom II X6 2.8GHz (Windows 7 Home Premium 64Bit, 4GB RAM) I experience LR3.2(64Bit)'s Develop module not to be really fluent. Esp. manual lens correction is sluggish. I expected the CPU to be fully taxed but I only see all 6 cores at 55-70% load. I tried overclocking the CPU to 3.2GHz but it doesn't really help. The CPU load decreases to 45-60% but there is not so much of a performance difference. I don't see a difference when I switch off writing metadata to files either. I also tried to exclude JPG, CR2 and lrcat files from the virus scanner's plan. LR uses around 950MB of ram. The catalog is around 15000 files large and I work on Canon 15MP CR2 raws (around 20MB/file).
Any idea what I could do?
best regards,
Fabian

Samoreen wrote:
Hi,
bob frost wrote:
IME a lot of this slow response to sliders etc is due to graphics card and driver problems.
Sorry Bob but I fully disagree with this. Most people having these problems with LR3 have up-to-date drivers and powerful systems. Moreover, what if Photoshop CS5, DxO Optics Pro, Bibble 5, LightZone,... work normally without any performance issue on a given system and LightRoom drives you nuts because it sometimes becomes so slow on the very same system? How could one explain that on the same system where the same display drivers are installed, LR 2 works with acceptable performances while LR 3, which is supposed to enhance these performances, brings the system down to its knee under some circumstances?
Finally, these performance problems are almost always appearing when using local adjustements on the Mac and on the PC. And this should be caused by a display driver that is not up-to-date?
I regret that Adobe have been totally quiet about these problems since they appeared and especially since the release of LR 3.2. It's obviously a bug (or a series of bugs) and they could at least advertise that they are working on a fix.
You can have the most up-to-date graphics drivers and the most powerful systems, but still suffer from bugs in the graphics drivers. Just have a look at the release notes for the latest nVidia graphics http://http://uk.download.nvidia.com/Windows/260.89/260.89_Win7_WinVista_Desktop_Release_N otes.pdf
This very lengthy document lists all the problems that have been solved and those that are still unsolved, and you will see that the driver has problems with some programs (games mainly) and not others, runs faster with some games and not others, has problems with some graphics cards and not others, etc. It is an absolute minefield of bugs/problems.
I'm not saying that Adobe can't get round some of these problems themselves, as they have done in the past, and they have co-operated with nVidia in the past to solve some of the problems. They are probably still doing so.
Local adjustments have always been the achilles heel of LR; when you read how they are done, it is not surprising that anyone expecting to do loads of local adjustments runs into problems eventually. Personally, if an image needs a lot of local adjustment, I take it into Photoshop, which is better able to do this sort of work because of the fundamental difference in the way the program works. Horses for courses!
If you have a nVidia card, and go to the nVidia Control Panel, under 3D settings you will see a long list of variables that can be altered, and the panel has preselected sets for different programs and games. A long time ago, people showed that some of these settings had a big effect on LightRoom performance.
I'm sure Adobe is working on all the problems that they know about, and that the next version of LR will have fixes for some of the problems. But they won't cure all of them any more than nVidia, which still has loads of problems in driver version 260! LR is only in version 3 (Photoshop is in version 11).
Bob Frost

Noise reduction won't display properly in LR 3.4.1 Develop Module

I encountered this issue first time last night - noise reduction will not show in "Fit" view of the Develop module for pictures that have a graduated filter applied as well. Having said this,
- The pictures display correctly in Library Loupe view (Fit and 100%)
- The pictures display correctly in Develop module when zooming in to 100%
- The pictures display correctly in Develop module when clicking in history on Luminance smoothing (first picture). Selecting the next step in the history, Add Graduated Filter, displays the picture without noise reduction (second picture - I tried on a virtual copy the other way round - first have a graduated filter and then apply noise reduction, but doesn't work either. Noise reduction just won't display in Develop module / Fit View once a graduated filter is applied as well.
Has anyone else seen this behaviour or, even better, found a solution? I already tried purging the raw cache, no success. Working on Windows 7 / 64bit.
Thanks,
Andreas

Jeff, I had difficulty understanding this same issue as presented at the link I posted above. With my low-noise Canon DSLR RAW images I simply couldn't see the onscreen rendering issues they were talking about. It even appeared this might be unique to Mac platforms and Windows 32 bit OS, since my Windows 7 64bit system didn't appear to have this issue.
Following suggestions to shoot a picture at -4 F stops and then increase exposure by +4 F stops in LR helped me get a better understanding:
http://forums.adobe.com/message/3857767#3857767
Granted this is an extreme shooting situation, but it helps demonstrate what happens when using exposure, fill and HSL sliders to increase exposure significantly (+2 to +4 EV) in specific areas of the image. Now you have noise that will be visible in smaller exported scaled images, perhaps even those sized for posting to the web.
The issue is at lower ISO settings (camera specific), view sizes less than 1:1 have no noise reduction applied (Mac & Windows) or sharpening applied (Mac & Windows 32). There appear to be platform differences in the way sharpening is applied, because on my Windows 7 64bit system sharpening is applied at all ISO and all view sizes including "fit" view, but noise reduction is only applied at higher ISO settings – the same as all others have described. I wanted to point this out since it is one of the reason I had difficulty duplicating what the OP was seeing.
We know sharpness and noise reduction settings interact with each other, so it is important to have both applied in the onscreen image to determine their affect. Using images with additive Exposure, Fill and HSL slider settings approaching +2 to +4 EV, there is simply no way to see accurate rendering without both noise reduction and sharpness applied at all view sizes, including “fit” view. This can occur with low ISO images, not just at some predetermined camera specific high ISO where noise becomes predominant.

Lens Correction Manual Slider Bug!

Hello,
I've been having a problem with the Lens correction Manual Sliders. Constrain Crop selected.
The vertical and horizontal sliders are behaving more like the distortion slider.
When sliding left or right they are pulling from the center, rather than the right or left end.
Also, with the scale slider....If I scale down it shifts to the right. when I reset all the sliders to zero.
The image doe not reset to its original position.
Is this something that the Lightroom 4 team is aware of?
One all the bugs are fixed I look forward to its release! Your hard work on this software is appreciated!
Best, Pam

The vertical and horizontal sliders are behaving more like the distortion slider.
When sliding left or right they are pulling from the center, rather than the right or left end.
Well, they *are* distortion sliders (sort of), leaving the very center of the photo unchanged. This has not changed from LR3. I can see no bug there. Also keep in mind that the visual effect is very different from wide angle photos to tele photos. Photos made with a tele lens are more or less just changed in the aspect ratio, and not so much distorted like wide angle photos.
Also, with the scale slider....If I scale down it shifts to the right.
This can happen if you used the horizontal slider before, combined with "Constrain Crop" - because the usable part of the photo shifts to one side or another. In the same way, scaling will shift up/down if one used the vertical slider before. This is perfectly normal. Hint: Try the vertical and horizontal sliders independently, with scaling set to 50 (minimum) and "Constrain Crop" *OFF* to see what they do with the photo - that made it a lot clearer to me how they work.
when I reset all the sliders to zero. The image doe not reset to its original position.
Also normal, because if you reset the manual corrections after working with "Constrain Crop" enabled, only the manual corrections themselves are reset, leaving the crop&straighten tool at some "funny" settings. Go to crop&straighten and reset it, too.
In conclusion, I see no bugs here. I also fiddled with the various manual sliders, and could not see any behaviour that was different to LR3, which has no bugs in this respect as far as I know...
P.S. I am not sure if I quoted the last question correctly or not. I assume these two sentences belong together?

Lens Correction Profiles: Pasting develop settings in bridge yields inconsistent crop

Hello Everyone,
I recently discovered lens correction profiles which have been a real benefit to me in my most recent batch of images shot at 16mm on a Canon 5d MII. The lens distortion isn't always spot on, but it is a huge headstart most of the time.
I bracket photos for HDR and will apply all my crop settings to one image in the bracketed series and afterwards psate the settings onto all the others in the series. This works great.
However, once I started using Lens Correction Profiles, when I paste the crop setting onto the subsequent images, the crop is in a different position. I was completely baffled. But after some fiddling around, I noticed that if I manually open each of the subsequent images, remove the crop, uncheck and recheck the Lens Correction Profile, and reapply the crop, it is consistent with the first. This leads me to believe that somewhere in the Paste Setting sequence, it is doing the crop out of order. (As if it is cropping the image and THEN applying the lens correction--which yeild different results.)
(As a item of note, when I mean cropping, I use the automatic crop obtained by highlighting the entire area of the image after applying lens corrections so as to only crop out the grey areas acquired by shifting the image around while still maintaining aspect ratio.)
Is there any way we can get the pasting to paste so as to make these subsequent images identical to the original image? Or am I missing something?
Relevant Specs:
OS: Windows 7 Professional 64-bit
Bridge 4.0.4.2
Adobe Camera Raw 6.4.0.139
Photoshop 12.0.3 x64
Thanks,
Dave

Normally, when you apply a lens correction profile, there shouldn't be any visible gray areas around the border of the image.
Are you saying this is not the case?
Are you making additional distortion or keystoning adjustments (e.g., in the manual tab)?

How can I activate the option "lens corrections" in the Develop-mode?

Hello
How can I activate the option "lens corrections" in the Develop-mode? I have lightroom 5.5.
In the Develop Mode I have every option exept "lens corrections" - where is it hidden? (see picture - sorry it's in German)
Thanks!

Perfekt!
Vielen Dank!
Christian Gazzarin-Junginger
Rietstrasse 17
CH-9016 St. Gallen
Tel. 071 280 00 38
[email protected]
www.scouwon.ch
Am 07.07.2014 um 12:29 schrieb mangray <[email protected]>:
How can I activate the option "lens corrections" in the Develop-mode?
created by mangray in Photoshop Lightroom - View the full discussion
Gehe mit der rechten Maustaste in irgend ein Feld und ein häckchen bei Objektivkorrektur!
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at https://forums.adobe.com/message/6527965#6527965
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page:
To unsubscribe from this thread, please visit the message page at . In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Photoshop Lightroom by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

When I attempt to apply a lens profile in the Develop module the only choices are for the Fujifilm X100/S/T even though in the Library module the EXIF data correctly shows the camera as the X-T1 and the precise lens used to take the picture. How do I get

When I attempt to apply a lens profile in the Develop module the only choices are for the Fujifilm X100/S/T even though in the Library module the EXIF data correctly shows the camera as the X-T1 and the precise lens used to take the picture. How do I get the right profile available?

First, the required profile needs to be present. LR 5.4 supports the X-T1 in terms of understanding its Raw format, but will not come with a profile for every lens which can be mounted onto that.
A profile is made for each specific lens, as mounted on a certain camera. It can also be used with pictures taken on a different (reasonably similar) camera body than the one originally used during profiling. This is subject to the sensor format: you can employ a given lens profile made for full frame, on an image from a crop sensor behind the same lens - but not vice versa.
Next, the image type needs to correspond to the image type which has been built into the profile: Raw, or non-Raw.
Lightroom offers only profiles of the right type for the image(s) concerned. There are many more provided for correcting camera Raw, than for correcting camera JPG. That is also the case with additional profiles, e.g. those accessed via the Adobe lens profile downloader utility.
Finally, in the event that there simply is no profile out there for a given lens, it is not particularly difficult (though a little tedious) for the end user to generate one, using a further Adobe utility which is downloadable as a package, including a range of checkerboard calibration targets, each of which needs to be printed at a stated physical size.

Hello I have the Latest version of Adobe Lightroom 5 to date (8/26/14) however just recently when I open the develop tab I'm missing two options on the right side column "Lens correction" and "Effects" I do not know I've hit some setting to remove those

Hello I have the Latest version of Adobe Lightroom 5 to date (8/26/14) however just recently when I open the develop tab I'm missing two options on the right side column "Lens correction" and "Effects" I do not know I've hit some setting to remove those options or if this latest version deleted those options? Any help would be greatly appreciated and please excuse my ignorance :/

Right click next to one of the other headers and you will get a pop-up to enable the missing ones.

Lens correction 6.3 -- automatic vs manual

Installed 6.3 RC -- yay! worked like a charm, automatic lens correction identified my kit lens for D5000 and made the changes. Love it.
Refresh my memory: for images where I had made manual adjustments (chromatic aberration etc) but now there is a lens profile, I should undo the manual adjustments and just let the automatic correction do its thing?

I should undo the manual adjustments and just let the automatic correction do its thing?
Yes. Otherwise you will double correct.

Lens correction feature completely missing from Develop Module

The lens correction feature has gone missing from the Development Module. It was missing before I upgraded to 5.6 and is still missing. Previously, it was present, so I am wondering if I did anything to hide or remove it?

Right-click on one of the other section headings, such as Tone Curve, Basic, etc. Make sure there is a checkmark in lens corrections. This is how you control which develop features you want displayed on your system. Sometimes features disappear mysteriously.

Erratic behaviour of Manual Lens Correction in Develop Module

Similar Messages

Maybe you are looking for