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?

Similar Messages

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 and chromatic fringe - broken in CS5 ?

Hello, chromatic aberration correction has changed since CS3.
It's limited to ONE pixel correction, or what ? It seems i cant get strong cyan/red bands anymore, i used it as an artistic effect and i need it back. Any way to have it behave like before? I'm not interested in manual workflow (moving manually RGB channels), thanks.
Paolo

It definitely seems different between cs3 and cs5.
I don't believe there is a way to get the same effect in cs5's Filter>Lens Correction and it's
not broken just improved i guess.
You might try a pixel bender filter called Convergence (ships with pixel bender plugin) or Color Separation Effect
http://www.adobe.com/cfusion/exchange/index.cfm?event=extensionDetail&loc=en_us&extid=2422 029
You would need to install the pixel bender plugin into photoshop cs5 from the bottom left of this page to use the above filters:
(Archived downloads)
http://www.adobe.com/devnet/pixelbender.html

Lens corrections and adjustment brush bug

First of all, congratulations for a spectacular implementation of these seemingly "conflicting" (at least in a non-destructive workflow) features.
Here, I got a fish-eye image where I want to paint the sky (say I want to make it darker). For the beginning, I just define the borderline between the earth and the sky.
Apply a lens correction and you get this:
Fantastic! The brush stroke got distorted almost perfectly. "Almost", because if you make a single brush click, painting a circle, it doesn't get distorted with lens corrections, turning into an ellipse (though the spot removal circles do). Instead all brush path point coordinates get recalculated along with the radius of the brush at each particular location. This works very well in real world even for extreme examples like de-fisheyeing. For rectilinear lenses, the difference is imperceptible.
And now, some bugs/limitations.
If you use a large brush, say I want to fill the whole sky in this example, things get a little more complicated.
Turn on lens corrections and...
The thick stroke gets distorted in a way that fill almost the entire image. This happens on extreme debarreling only. For normal lenses, it's a non-issue.
Also, sometimes I get a strange artifact in preview only. The exported image doesn't have this solid rectangle:
And a final, smaller, issue: for strong corrections like de-fisheye-ing, the brush pin easily gets lost outside the image area after you apply lens corrections.

While we do the best we can mapping the local corrections, it is not perfect if you adjust the lens corrections after applying them, as you can see in some of your extreme examples.
In the future, when processing new images, if you apply the lens corrections first, and then the local corrections, you completely avoid these remapping issues.

Lens Correction and JPEGs

Hi,
I'm new to LR. I've spent the last two months watching every tutorial, practicing with a portfolio/video instructional off the Adode site and reorganizing my own photos and folders on my computer.
I finally took the "bold" step to put a few of my photos into LR. All my photos are from either a Nikon 3000 or 3100 with the same lens AF-S DX Nikkor 18-135mm f/3.5-5.6G ED.
Also, all my photos are JPEGs.
1) In Lens Correction > Profile > Enable Profile Correction there are 3 options
Default (no make/model options)
Auto (no make/model options)
Custom > when I click this I get the model and Adobe profile for the Nikon AF-S Nikkor 14-24mm f/2.8G ED
Is the Adobe profile the same for both lenses? The 14-24 and the lens on my camera - the 18-135?
Default and Auto look the exact same. If I click Custom, the image becomes a little more exposed. To my eye, Default/Auto look better.
2) Also, should I "check" chromatic aberration for all my photos? I'm not sure how this feature works in LR with JPEGs.
3) Considering where I am and my skills at this point, what is the best recommendation going forward, for learning LR and working with my JPEGs.
Since I'm going to be essentially working only with JPEGS for a while, what lens correction should I use with these photos? Default/Auto/Custom?
4) Are there any other settings that I need to pay attention to with the camera/lens/file type that I am using while trying to learn LR?
I'm starting to realize from my readings, that JPEGS will have a more limited range of development in LR and "LR will display only the profiles available for the file type of the selected image." Lens profile support | Lightroom 5, 4, 3 | Photoshop CS6, CS5 | Camera Raw 8, 7, 6
I want to become a more serious amateur and enthusiastic photographer, but I also don't want to spend 15 minutes editing/developing every semi-decent photo I take.
As an aside, my 3100 has a shutter problem, so I will be upgrading at some point (probably Micro 4/3) and I plan to explore shooting RAW or a combination of RAW/JPEG somewhere down the road.
Thanks
Andrew

As I understand lens correction profiles, most are written for RAW photos only, and there are only a few profiles written for JPGs. That would explain why you don't see your specific lens under Custom.
2) Also, should I "check" chromatic aberration for all my photos? I'm not sure how this feature works in LR with JPEGs.
I'm certainly not the biggest expert on chromatic aberration, but it seems to me that the chromatic aberration algorithms are looking for certain types of coloration at "edges", and I don't see why that would be different for JPGs compared to RAWs.
But I'm confused by the actual question ... checking the box and seeing if it makes the photo better seems so simple that I don't really understand why you had to ask the question.
3) Considering where I am and my skills at this point, what is the best recommendation going forward, for learning LR and working with my JPEGs.
Since I'm going to be essentially working only with JPEGS for a while, what lens correction should I use with these photos? Default/Auto/Custom?
Again, the learning process in Lightroom is ... just do it. You can't harm your photos, you can always undo whatever you did that you didn't like. The lens correction you choose is the one that makes the photo's appearance look best to you.
4) Are there any other settings that I need to pay attention to with the camera/lens/file type that I am using while trying to learn LR?
Any setting and any slider and any tool might be the right one for your photo. There is no general setting that EVERYONE uses, as the reason software provides options is that some people want it one way, and other people want it a different way.
I want to become a more serious amateur and enthusiastic photographer, but I also don't want to spend 15 minutes editing/developing every semi-decent photo I take.
The learning curve can be difficult, but as I said, editing your photos will never harm your originals, and you can always undo whatever you did. So ... just do it.
I am concerned that even as a beginner, you think it might take you 15 minutes to edit a single photo. Unless you are doing a HUMONGUS amount of brushing, this should never take 15 minutes, even for a beginner. Yes, of course if you want everything to be absolutely PERFECT, then it will take longer, but there really is no such thing as a PERFECT photo. Your goal ought to be (in my opinion) making the photos look GOOD, and learning what the sliders and tools do as you go. And certainly there is no unique determination of what a GOOD photo is, a photo that looks GOOD to you may not look good to someone else, but that's kind of irrelevant, its your photo, it should only matter that it looks GOOD to you.
You said you watched tutorials, are these tutorials helping, or not? Do you feel you have learned the basic purpose of (some of) the develop sliders and develop tools, or not?

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.

Diference between filter Lens correction and Camera Raw Lens Correction

Whats is the main diference between tools: filter lens corection and Camera Raw Lens Correction.
I am using PhotoShop cs6, OS Windows 7
I already asked support team in Poland, but they send my back message: "we dont support any longer PhotoShop sc6"

Swila, were your "other images" previously edited in Camera Raw? I.e., do they already have saved image settings? The defaults that you save via the flyout menu will only apply to new images, or if you reset an existing image to the defaults. (e.g., choose "Camera Raw Defaults" from the flyout menu).
Eric

Lens correction and DNG

I have upgraded from Ltroom 3 to 5.2 and lots of differences straight away.
I have a question if
1) enable profile corrections
2) setup is Auto or Custom Or Default
3) the camera is correcr ( canon)
4) Model of the lens is correct EF17-40
5) Profile is shown as EOS-1D Mk 3
the arrows do not show any other camera and Mine is a Canon 50D, How do get the correct Profile to register also unable to update DNG files.
what is going wrong??

LR does not ship with a separate profile for each body, against each lens. The camera model info here, AFAICT just notifies you what camera the lens was mounted on, when the profile was created.
The same profile can quite happily work for other camera models too - even so far as, automatically extracting just the relevant middle coverage out of a FF lens profile, to correct images taken from a crop sensor body with the same lens mounted. (This will of course not work the other way around).
The profile's aim is to characterise the lens optical performance, which does not per se change when you move it between cameras - (although this may not be quite 100% precise, e.g. in terms of vignetting off microlenses etc, it is normally quite good enough IMO). In the past, profiles used to address CA as well, and I believe this issue was more sensor dependent (the newer LR CA correction does not depend on the profile).
If the need is a critical one, then your individual lens copy and your individual camera body can be used to "close the loop", and generate an empirically "perfect" custom profile. It's not very hard to print out and photograph the special targets, and then run the free DNG Profile utility; you can put as much or as little effort as you like into the number of focal lengths and apertures that you include. But if the supplied standard profile is good enough to save you that trouble altogether, it may not matter that it is not the theoretical best.
AFAICT, the installed / downloaded profile is likely more subject to LENS sample variation (between your lens, and the one used to make the profile) - than, anything to do with using a different camera model.
RP

Lens correction and my Sony DSLR-A700

Lightroom 3 doesn't recognize my camera or my Sigma
70mm Macro. My other lens isn't imcluded yet
but my Sigma lens and camera is. Why doesn't Ligtroom recognize them? Is it me or Lightroom?

There was a similar post a day or so back for this lens. I suspect your problem is the same as the previous poster - lens ID isn't being picked up or isn't matching with current lens set.
You already know that the lens is supported so you can go to the Lens Correction panel and select it from the list under Sigma then from Setup pop-up choose Save New Lens Profile Defaults. This proile should be automatically selected the next time you activate the profile for this lens.

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.

Micro Four Thirds lens correction and Lightroom

Obviously LR seems to use some of the lens correction information it gets from Micro Four Thirds cameras. This shows when compared to results from RAW converters that don't.
I have noticed this for my Olympus OM-D and the 12-50 mm zoom. Is that the reason why there is no lens profile for that lens in Lightroom? And is this the case for all MFT lenses?

Already been answered here: http://forums.adobe.com/message/3194920#3194920

Aperture 3, lens corrections and Micro 4/3rds?

Does anyone know if Aperture 3 supports the lens corrections that are part of the Micro 4/3rds spec? Presumably this is what was holding up support from being added but can anyone confirm or deny whether they actually do support it now?

I see that Aperture 3 supports the RAW format from Panasonic Micro Four Thirds cameras like the GH1 but does not support the Olympus Pen cameras like the EP-1, EP-2, EP-3. Unfortunately I own the EP-1 and have been waiting since July 2009 for an update. Since it's not in Aperture 3 I must assume that they will never support Olympus Pen cameras. Adobe's Lightroom 3 DOES support Olympus RAW and you can download a beta. I won't be moving to Aperture 3 until Olympus RAW support is there. I won't be moving to Aperture 3 at all if Adobe beats them with Lightroom 3.
WAKE UP, Apple! Either support it or let us Olympus owners that you won't.

Camera RAW Lens Correction and Chromatic Aboration

Looking in the Camera RAW Lens Correction table I can't find a profile for my lens - Nikon AF VR NIKKOR 80-400mm 1:4.5-5.6D. The nearest in the table is Nikon AF-S VR Zoom-NIKKOR 200-400mm f4G IF-ED. Is this near enough or is there any manual data I can enter.
When shooting at f5.7 400mm 1/800sec ISO3200 with my D3S it is showing some Chromatic Aboration can this be corrected by entering data manually? and what are the figures I should use?
Kind regards,
Alan

The first thing you should do is update photoshop cs6 by going to Help>Updates from within photoshop cs6.
I don't know if camera raw 7.4 has a profile for that lens or not, so you might have to install the 8.1 beta i linked to in post #2.
some info about correcting Chromatic Aberration in versions of camera raw 7.1 and newer:
http://helpx.adobe.com/creative-suite/using/correct-lens-distortions-camera-raw.html

Does sending as PSD from LR 3.3 to PS CS4 send lens corrections and other edits?

I shoot RAW files with my Canon XTi (400D) and G12. I have a copy of Creative Suite 4 and am using it with Lightroom 3.3, which adds some goodies that ACR for CS 4 doesn't support, like being able to understand the G12's RAW files, plus doing profile-based lens corrections, improved noise reduction, etc.
If I use PSD as the format to send images back and forth among Lightroom and Photoshop, are they in synch in terms of what the image looks like, including the advanced features I just mentioned? Is there any reason to use TIFF instead of PSD?
I'd like to postpone moving to CS 5 until I'm better able to afford it - the question really is whether LR 3.3 can serve as a substitute for ACR 6.3 by writing an equivalent PSD with all the advanced features done for PS by LR instead of ACR.

I have worked with the combination of LR 3.3 and CS4 for a while.
These two are not fully compatible.
CS4 cannot read the ACR (RAW) file of LR 3.3. So when you edit a RAW-file, LR creates a PSD that is then opened in CS4.
In CS5 the RAW image is opened (as RAW) and a PSD / TIFF is created when you save your edits.
Furthermore: Lens corrections are not read by CS4 - or not completely.
I have never found a difference in quality of behaviour between TIFF or PSD, although some sources I've read say that it's better to save in PSD as it is the native format of PS.
WW

Lens correction, and Raw or JPEG

Please bear with me, sometimes I'm a bit slow.
I just loaded a friend's JPEG into ACR, to see if I could fix the distortion. The image has no EXIF. The list of Nikon-fit lenses was much shorter than usual - is this because it is a JPEG, rather than a raw file?
I was surprised that the 16-85mm lens wasn't in the list, as I know this was added in 6.2. After hunting for the LCP files, I see that there is a RAW version only, so this ties in with my guess. So, my next question is: why does Adobe supply two profiles with some lenses (raw + jpeg) and one with others?
I gave up on ACR, and loaded the JPEG into CS5. In CS5 Lens Corrections, I was allowed to assign a raw-only profile to my JPEG. This is good, but why am I allowed here, and not in ACR?
And, a less important question, but niggling nonetheless, and maybe a little off-topic, why does CS5 Lens Correction offer both "NIKON" and "NIKON CORPORATION" as a camera make, when others just have one listing?

Yammer P, yes the list is shorter because it's a jpeg rather than raw, and we have more profiles for raw than for jpeg.
For the set of lenses supported in CS5's initial release, we created profiles for both raw and jpeg. Since then, we have been concentrating on raw-based lens profiles, for a number of reasons (one of which is that we feel we can consistently deliver the highest quality results this way). This is why you see some lenses supported with raw & jpeg profiles, but many more supported with raw only.
CS5's Lens Correction plug-in does indeed let you choose raw-based lens profiles even though it is processing a rendered file (e.g., jpeg, tiff). This will work in many (but not all) cases for distortion correction, but will often work poorly for chromatic aberration and vignette correction. I don't recommend this workflow and it is a key reason we don't let users mix/match in ACR & LR.
Eric

Lens correction and Develop defaults

Similar Messages

Maybe you are looking for