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.

Similar Messages

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.

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.

LR4 Beta...another problem with using Lens Correction

Not sure if it's me or the beta. I'm trying to do a lens correction on a file that was edited in CS5. The photos were taken in 2009/10. They are importing as Process 2012.
I'm using the Lens Correction in manual. About 15 seconds after I start using the sliders, my LR stops working and I have to close the program (white outs the screen with the note saying the program has to be closed).
I do know there can be problems with a beat so I wanted to post this problem in case it is a bug in the system.

I have the same probem if I try to push the scale slider down below about 87%. It is quite annoying when it keeps happening on the same photo. It's not something I use a lot but it can be necessary with tall buildings when the correction pushes the top out of the frame.
JW

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?

CR 8.2 doesn't come up with lens correction profile on Canon 6d with EF 24-105 L 4.0 IS/USM

Dear community members,
Some weeks ago I bought my new Canon EOS 6D with a EF 24-105 L f/4.0 IS/USM lens an I am absolutely happy with them :-)
The only problem that I run in to is when I process my photographs in Camera Raw. The thing is that CR does not come up with a lens correction profile for de Canon 6D with the lens mentioned above.
I do find a profile of the 1D Mark III, but this one does not work very well on the RAWs from the Canon 6D.
Does any one know if and (when yes) where I can find the right profile for lens correction? At the Adobe site I could not find the profile van this camera in combination with this objective.
Or perhaps there is another way to apply automatic lens corrections on RAW;s from the Canon 6D with a EF 24-105?
Kind regards and many thanks in advance for your answers :-)
-Gozotxu-

Hello,
Thanks for your advice.
I did download the DNG Coverter but it did not help. So I decided to uninstall Photoshop CS6 and reinstall it again on my Mac.
For uninstall I followed the following steps:
-go to finder
-go to the Photoshop CS6 map
-dubbel click on the Adobe-uninstall icon
This worked perfectly well without any errors.
Now I am running into another problem, a problem with reinstalling PS CS6.
I don't have a cd-rom with PS on it, but I have a downloaded a .DMG file which I bought and downloaded from Adobe (I don't have a CD-player in my Mac). This should not be any problem. But what happens is this:
When I dubbel-click the .DMG-file (Photoshop_13_LS16.dmg) the normal installation window appears.
After dubbel-clicking Photshop CS6 icon the following screen appears:
After selecting the Install icon the following screen appears:
The error message is in Dutch and says: 'install' excists on the diskcopy 'Photoshop_13_LS16.dmg'. Safari downloaded this diskcopy on 2 July 2013
The two buttons say: " Cancel" and "Delete diskcopy file"
When I select "Cancel" the application stops and when I select "Delete diskcopy file" it removes the Install-file (from screenshot) and the application stops.
Could you please tell me what I am doing wrong?
Thanks in advance!
Kind regards,
Gozotxu

ACR 6.1 vs DXO Lens Correction?

I have been experimenting with the lens correction module in ACR 6.1, which has profiles for two lenses I own, the Nikkor AF-S 18-70mm f/3.5-4.5 G and the Nikkor AF-S 70-200mm f/2.8 G IF-ED VR, and am quite pleased with the results. The 18-70 lens is a decent consumer grade zoom that has good resolution and little chromatic aberration, but which suffers from distortion at the wide end and vignetting at large apertures. From visual onscreen editing, the vignetting is completely removed from the images and the barrel distortion at wide angle settings is sufficiently well controlled that thus far I have seen no need for manual touching up of the distortion correction.
DxO (an Adobe rival) has criticized the ACR module as offering undercorrection of distortion and vignetting under some conditions, suggesting that the Adobe profiling procedures are not sufficiently rigorous. That may be so, but thus far I have seen no major defects and they gave no examples and I am wondering what the experience of other ACR users might be.
http://www.dpreview.com/news/1005/10052001adobedxoensprofile.asp
The 70-200 zoom was highly regarded for use with APS sized sensors, but full frame users have noted an alarming degree of softenss in the corners of the image. With ACR, one could attempt to provide extra sharpening at the edges of the image with an adjustment brush, but DXO claims to automatically correct for uneven sharpness across the image field. They don't say how this is achieved, but the web site explanation hints at something more sophisticated than a variable unsharp mask (perhaps a variable deconvoluiton algorithm) and I would be interested how this works out in practice.

I hardly know where to start!
Anyway, looking at the list of available lenses, the list for Photoshop Nikon optics is extensive, and also has at least one error. The list for ACR is far less, and my principal lens isn't present. The problem with that item is that, if you choose Custom and your lens isn't on the list, it reverts to the first lens on the list and corrects the image for that. In Auto, it tells you it isn't on the list, so I would urge the use of Auto at all times when operating with commercially available lenses.
In PSCS5, my basic lens also is not present; (18 to 105 mm), but there is a lens, 18 to 125 which is not in the Nikon line. This appears to be an error. Is this the 18 to 105?
I have serious reservations with the idea of "Photographer Empowerment" with respect to lens corrections. I hope that if you publish this data it is in it's own category to which I can ignore. Lens measurement, data collection and conclusions is an intense activity and is best left to the professionals as is photo editing software. DXO knows what they are doing. The concept of "Photographer Empowerment" indicates to me Adobe does not know what it is doing. This makes me very nervous, to say the least.
Let me give you an example. I ran an image from my 70 to 300mm lens, which is on the charts, through both DXO and ACR 6.1, then set one over the other in Layers. Switching back and forth showe a vast difference in the correction for barrel/pincushion and vignetting. Which is right?
FYI, I always have two sets of raw data when anticipating running the DXO corrections so that there is no preconditioning by either party when running such tests. Also, I use DXO only for lens correction activities. Their RAW converter, imo, cannot compare to even CS3, for reasons I won't go into here. There are cheaper programs for doing barrel, vignette and such, but DXO also provides corrections for other lens errors, which makes it well worth while.
To answer my own question is that, in architectural photos, DXO is on the money. The only way to tell for sure is an optical setup that is precise and repeatable.
Finally, here is a site that uses the DXO software to provide lens tests that are extensive and comprehensive, all for the practicing photographer. Using their data for inclusion in the ACR correction would be a good start, not Photographer Empowerment.
http://www.slrgear.com/reviews/index.php
I use them once I have narrowed down the field to a few lenses and haven't been disappointed.

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.

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?

Lens Correction Question

Well, I am happy to report that I completed an "optimize catalogue" and my Lightroom 3 appears to be working faster. Fantastic.
What I don't get now has something to do with the Lens Correction module.
Here's my example. When I select "Enable Profile Correction" the software correcntly picks out the make and model of my Nikon lens. Great.
However, previously, I was noticing that under "profile" it used to give me the Nikon D3X ... lens ... etc etc info.
I no longer get that. All my photos are profiled using the "Adobe (lens Nikon etc etc)" profiles. When I click on that box, there is no option to use the Nikon profiles.
Question: Is this an issue I should be worried about? I have noticed on various tutorials that the Nikon and Adobe profiles differ ever so slightly.
I am concerned about not being able to get accurate profiles.
I have fiddled with going between "default" and "auto" in the "setup" drop down, but I am only able to load the Adobe profiles for the make and model of my lens. (I only shoot Nikon by the way).
Perhaps I am overanalyzing this but I would like my software to have the most accurate profiles and I believe the Nikon profiles are slightly more accurate than the Adobe ones.
Can someone shed some light on this for me?
Thanks in advance to all that take the time to reply.
Fulvio

"There are two seperate "profile" areas now. You need to scroll down to the 'Camera Calibration' panel, where you will find your "camera" profiles.
Your camera lens will be automatically detected in the Lens Correction panel, that is if it is a lens model in the database. Otherwise no lens model will show up and you will have to select 'Manual' to make your own profile. This is the case for my Sigma F2.8 Macro lens – It is NOT listed."
Thanks for the reply however, Under the Camera Calibration module there are no camera's listed. All I see listed under the profile tab in the Camera Calibration module is:
ACR 4.4
ACR 4.3
Adobe Standard
Camera D2X Modes 1 through 3
Camera Landscape, neutral, portrait, standard and vivid
My question is focussed on the lens correction. The correct lens is listed in that module but the Nikon profiles that were present before optimization are no longer there instead replaced by Adobe's profile for the selected Nikon lens.

Lens correction won't automatically detect lens and correct

I'm having a fun time with the lens correction feature in LR 3.2, but it will not auto detect the lens. I have all profiles loaded, I checked. I convert all photos to .dng from the .nef format. (Nikon shooter) When I enable the profile corrections button the setup changes to custom and the lens profile "maker" drop down says none??? and on the bottom it reads "Unable to locate a matching profile automatically." If I change the Make to Tamron by manually selecting it, for example, it finds the profile and all is well. How in the heck do I set it up so the profile connection is enabled automatically and the right lens pops up without intervention?? Hope someone can help with this...I'm working through 500 down selects and this would be nice to fix this issue.
I can see all the lens info in the metadata on the normal library screen????.
Thanks so much for your help in advance!

So you have Tamron lenses...
Here's a quote from a post by Eric Chan (one of LR/ACR developers):
Re: the Sigma 10-20 question. Regrettably, we cannot always automatically determine with 100% certainty the identity of the lens used to shoot the image. We try to be conservative. So if in doubt, we don't choose one automatically. For some third party lenses, this can happen. Choosing Sigma from the Make popup is the right thing to do in this case.
Still, you can try the following trick:
Choose an image shot with a Tamron lens.
Go to lens correction. (The Lens profile auto-detection is supposed to be failed at the moment.)
Choose Tamron and the desired profile from the lists.
Drop down the Setup list and choose "Save New Lens Profile Defaults".
This should rememeber the lens setup (i.e. slider values and lens profile) for the given camera/lens combination.
You can also use a develop preset to apply a lens correction quickly.

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).

My Lightroom lens corrections need correcting. Is this normal?

I have bought myself my 1st DSLR camera (Nikon D3100) as i now want to shoot Raw instead of Jpeg. I've always shot Jpegs in the past with my old cameras. The in-camera Jpegs from my new Nikon don't show any lens distortion. However, when i open the Raw (NEF) files in Lightroom and tick 'enable profile correction' in the Lens corrections section, the distortion correction seems too much and i have to manually adjust it every time.
The lens profile comes from Lightroom itself (not from other users), & so this doesn't seem quite right to me that the correction is somewhat wrong each time.
I'm wondering if i'm doing something wrong or that maybe its even normal to have to adjust the correction further yourself each time (and perhaps most users have to do that too)?
I've included 3 Jpegs of the same image to demonstrate the problem (detailed below):
1) The export from Lightroom with the lens distortion corrected by Lightroom (note the straight red line).
2) An exported Jpeg version of the uncorrected Nef from Lightroom (to show the full original lens distortion)
3) The original in-camera Jpeg (obviously the distortion corrected by the camera)
I've drawn straight red lines on to the images to demonstrate the differences.
Any ideas?
^ above image is a Lightroom exported Jpeg (from NEF) with lens correction ON (note the red line along the top of the roof)
^ above image is a Lightroom exported Jpeg (from NEF) with NO lens correction yet, thus showing original distortion.
^ above image is the ORIGINAL in-camera JPEG showing no distortion at all (note the red line along the top of the roof).
P.s i've taken different shots too and the problem is the same for them all (at least at 18mm anyway).
Additional information:
The Nikon D3100 has an APS-C sensor (I'm not sure if that's significant or not). Also the lens described in the profile correction matches the one from my camera.

Rob Cole wrote:
Hi Paul,
I'm really not sure exactly what DxO outputs when you choose DNG:
It's not raw data, yet preserves some ability to do raw things in Lightroom, like white balance and camera profiles.
I dunno about pulling from highlight/shadow "reserves", but note: it's different than a DNG-wrapped tif or jpeg, it may be able to pull from the highlight/shadow reserves as can be done via the DNG used for smart previews - I just don't know.
trshaner: do you know for sure that a DxO DNG hard-clips shadows/highlights, or are you just "extrapolating/assuming/educatedly-guessing"?
Regardless, DxO has some auto shadow/highlight recovery (for those extreme black/white tones) that is quite good - don't sell it short.
Google 'dxo linear dng highlights.' Here's one that supports what I said:
http://forums.adobe.com/thread/663428
I've tried using Canon's DPP for the same purpose with TIFF output AND with DPP's highlight recovery. I can't get the same highlight recovery with the TIFF as compared to the raw inside LR with PV2012.
Rob Cole wrote:
I still think about it when Lr's lens corrections are wonky. But my problem with Lr's lens corrections have more to do with vignetting than distortion (because I mostly shoot nature, not buildings...), and I can add manual correction and/or a dab of paint to the automatic corrections, which saves me the complication of front-ending via DxO. If distortion is your primary concern, consider balancing auto with manual distortion corrections (I've not done much of that, so no guarantee...). Also, there's the upright feature in Lr5...
What's wrong with simply changing the Lens Profile 'Amount' settings from 100 if a specific lens profiles is "over-correcting" or "under-correcting? Don't forget most zoom lenses have a "complex" moustache shaped distortion, which is NOT easily corrected with LR's Manual Distortion control. You can certainly try both, but there's no way to save the Manual Distortion "correction" setting to a specific lens profile's defaults.
Rob Cole wrote:
PPS - DxO's purple fringe tool will get the fringe out without the artifacts of Lr's global defringer, however it may also take away real image color sometimes, and can't be done locally, so one may ultimately get better results in Lr if willing to spend a while painting local defringing.
I've never seen any artifacts caused by the LR Defringe tools (see image posted of Canon 8-15mm Fisheye lens CA), but you do need to be very careful concerning the actually settings used. After using the eyedropper tool to sample a fringe area I fine tune the settings to eliminate desaturation of areas that have similar color as the fringe area. Once you have the correct settings save it to a Develop preset for manual application. For example with my Canon 8-15mm F4L Fisheye zoom I have two (2) Develop presets of 8-12mm (Purple 2, 30/55) and 13-15mm (Purple 4, 30/55). There is no need to use Local controls with Defringe if you follow my suggestions for manually tuning the settings to prevent desaturation in like colored areas. IMHO the LR CA and Defringe tools are darn near perfect when you use them correctly!

Why is my new imac i7 (os 10.6.4)crash every time I am in CS5 using filter tool-lens correction?

In the middle of using lens correction tool or noise reduction filter, my new imac crashs, I have lightroom sometimes on, and Firefox brawser with music streming, any ideas why?

Maybe updating might help as you seem to be behind with the OS and don’t even mention Photoshop’s exact version.

Lightroom 3.4.1 Lens Corrections – Manual Tab Defaults

I'm running LR 3.4.1 on Windows 64bit OS. I just discovered some pictures shot recently with my 5D MKII have the Lens Corrections Manual tab Chromatic Aberration settings applied Red/Cyan = -17 and Blue/Yellow = +5. I hadn't applied these settings so went back and checked my Lens Profile defaults only to find this is the default for those settings. What I mean is when you double-click on the Manual tab slider titles 'Red/Cyan' and ‘Blue/Yellow,' or on the heading title 'Chromatic Aberration, these are the settings applied as "defaults." I would have expected the default to be '0' for both, and there does not appear to be anyway to reset them to '0' other than manually correcting each. I tried 'Reset Lens Profile Defaults,' but that only resets the settings in the 'Profile' tab.
It appears to have only affected one group of pictures and import of new pictures applies the Lens Profile correctly with Manual tab settings at '0.' But it still defaults to the non-zero settings for Manual CA when double-clicking as described above, which is probably how I screwed up on that one group of pictures.
Anyone have ideas in what is going on...or am I simply overlooking something obvious?

Thanks Lee Jay. I must have inadvertently set those when updating the camera profile. ALT key, 'Set Default' and selected 'Update to current settings' with them set back to '0' did the trick.

Crashes with Manual Lens Corrections

Similar Messages

Maybe you are looking for