LR 4.3 lens corrections issue (bug?)

Hello,
I'm having trouble with LR 4.3 lens corrections panel, that I didn't have with LR 4.2.
I'm running LR 64bit on Windows 7 Ultimate. Camera is Pentax K5.
This is what the lens corrections panel looks like after import in LR 4.2. I did setup the "Enable Profile Corrections" as default for my camera, so everytime I import photo's this is autmatically checked.
Opening the same photo in the same catalog with LR 4.3 this is what I get:
Notice "Setup" has changed to "Custom" and Lens Profile says None.
Changing Setup to Default again, Make and Model display the correct information, but Profile says None.
Clicking on the Profile arrows gives me the correct lens profile but...
... selecting that profile turns everything back off and setup is changed to Custom again.
Now setting Setup to Default makes no difference! Lens Profile displays None but...
... selecting Auto gives me the right Make and Model!!
And finally, when I leave the image with settings as here above, go the another photo and change the lens corrections, and then go back to the initial image, everything's gone again!!!
As far as I'm concerned, this is a serious bug, unless I'm missing something obvious.
Did anyone have this same problem?
I've downgraded to LR 4.2 again, and everything is back to normal.
Regards,
Peter

No, that's not it either. Lens Corrections appears in the right panel, between "Detail" and "Effects".
It's just that when I click on the "make" under the Lens profile, all I get is Nikon and Sony (and not the other brands I used to see) and under model there is only one lens if I remember correctly...
This is frustrating, and it will be more so if it turns out that I did something silly!!
thanks
christos

Similar Messages

Lightroom 5 and Lens Correction-issue

Hi, sometimes in LR4 I used the lens correction. Most pictures nowadays I take with an old NIkon 24-85:2.8-4 lens. When I tick lens correction and choose as manufacturer Nikon it automatically gave me the Nikon 24-85:3.5-4.5 (as the 2.8-4-version is not present), but usable. In LR5 it always gives me a Nikon Coolpix-lens and I have to manually change it. Quite annoying.

LR has not automatically assigned that lens profile, since it does not exactly correspond.
But it's no biggie...after manually selecting a particular lens profile, you can set that as a user default to be used in future (for any other pictures that report the same lens data as the current active image does).
It's an option in the drop-down menu within the lens profile panel.
Your LR default settings or import preset affecting these future imported images, will just need to ensure that Profile is active, and that the selection of profile is set to Default (instead of Manual) within this same drop-down menu.
Hereafter, LR will adopt whatever profile is the factory default or (as an override) is the user selected default, or (failing both) no profile at all, for each image imported.

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.

Odd Issue Editing in Photoshop with color and lens corrections

First off, I'm on LR 4.4 and PS CS6 (Camera Raw 7.4.0.137) using ProPhoto RGB as my LR colorspace and have my PS color settings as Working Space: ProPhoto RGB and my color management policies to preserve embedded profiles.
When I right click on a DNG in LR and choose "Edit in Photoshop", LR sends it to PS and PS does its "Reading in Camera Raw Format" and opens the image. However, the colors are off (very muted) and any lens corrections I've applied in LR are missing. My monitor (iMac on OSX 10.8) is calibrated with a Spyder. I've also noticed that if I choose to edit in another application, it renders the tiff fine and the color and lens corrections are correct in the tiff.
Anyone have any ideas what my issue is?
Thanks,
Matt
ETA: After some experimenting, it seems that the "Adobe Standard" profile is what gets sent to Photoshop. The rest (Camera Landscape, Portrait, etc.) are ignored. What's going on here?

Sounds like you need to reset your warning dialog. Preferences>General>Prompts [Reset all warning dialogs]
Then try it again and make certain of the three choices you are Editing a Copy with Lightroom Adjustments.

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?

PS CS2 lens correction causes "Maximize Compatibility" issue in LR

Question: why does PS CS2/3 convert the layer "Background" to "Layer 0"?
This is the problem (and solution):
I encountered the widely discussed "Maximize Compatiblity" issue with a bunch of PSD files (slide scans) that contained only one layer. Puzzled as I was that the layer thing apparently could not cause the problem, I reopened some of those files in PS CS3 and I noticed that each of them had had a lens correction. Just to make sure I was on the right track I applied a lens correction to a file that had been already imported into LR successfully and used the SaveAs command and unchecked the Maximize Compatibility option. The new file could not be imported into LR. So no more lens corrections? - I thought.
A closer look on the troublesome files made me learn the (only) layer had been renamed from "Background" to "Layer 0" after the lens correction was made. I used the "Flatten Image" command and this turned it back into "Background". After this, the file could be imported into LR without a problem.
I can now apply this trick to all troublesome files that have had lens corrections and thus avoid the huge increase in file size (130MB is a lot already).
Now I write this for those of you who have the same problem and are still puzzled (to help out) but I also would like to have some insight into why PS CS2/3 lens corrections mess with the layers.
Thanks.

>My conclusion would be that LR can only import PSD files that meet the following requirements:
>1. must contain only one layer
>2. that layer must be called "Background"
Your conclusion is only partially correct.
Lightroom will import multi-layered PSD files that have been saved with the preference for "Maximize PSD and PSB File Compatibility" set to On. This is clearly stated in the Release Notes and Help documents:
>Photoshop format (PSD)
>Photoshop format (PSD) is the standard Photoshop file format. To import and work with a multi-layered PSD file in Lightroom, the file must have been saved in Photoshop with the Maximize PSD and PSB File Compatibility preference turned on. Youll find the option in the Photoshop file handling preferences. Lightroom saves PSD files with a bit depth or 8 bits or 16 bits per channel.
As to the original point -
PS CS2 lens correction causes "Maximize Compatibility" issue in LR.
Photoshop renaming Background Layer to Layer 0 is a Photoshop issue, not Lightroom. When it occurs the files effectively becomes a multi-layered file, even if there is only one layer (i.e layer 0). Why using the Lens Correction filter causes the background layer to be renamed is currently unclear, but I have raised it in the "appropriate" place. In the meantime, I recommend that you set the Maximise Compatibility preference to
Always. Doing so will save non layered files as normal and multi-layered will have the
necessary* composite preview. You can continue to use the flatten command to fix the errant files.
*Enabling the Maximise Compatibility preference ensures that Photoshop creates a composite preview of multi-layered images. It is intended to enable applications that can't read layers to preview the images. Lightroom cannot read multi-layered files, therefore the composite preview MUST be present in such files.
>Has anyone noticed different behaviour with the Lr v2 beta? I'd hate to double the size of all my multilayer PSDs just so they can load into Lr(?)
Lr 2.0 will function as per Lr1.x; i.e. not using Maximize Compatibility when saving multi-layered files will mean that they are not compatible with Lr2.0.

BUG (?): CA correction off after reenabling lens corrections

I would like to inform all about an (in my view) incorrect behaviour of LR:
In order to speed up my workflow i disable detail and lens corrections for all images immediately after the import (select all, auto sync is on, turn off detail and lens corrections). With this panels turned off I can do basic operations like cropping etc much, much quickier. I shoot badminton sport and have to process hundreds of images.
After the basic corrections I reenable detail and lens corrections for all images which should restore the previous settings of this panels or at least the default (ISO specific) settings (which is the same in my case). But the "Remove Chromatic Aberrations" remains off, even if it was on before and on by default for all my lenses! I consider this to be a bug. It isn't a big problem because it can be turned on manually but it can easily be forgotten.

I disable and reenable the panels "Lens Corrections" and "Details" with the switch on the upper left. The tooltip says "Turn off lens corrections".
You can test it with the following steps:
1) Be shure that the panel "Lens Corrections" is enabled and "Enable Profile Corrections" and "Remove Chromatic Aberration" are active for all images.
2) Select 2 or more images and (with "AutoSync" on!) disable the panel "Lens Corrections" (see above).
3) Enable the panel "Lens Corrections" and check the "Remove Chromatic Aberration" option: it is on for the first image, but OFF (!!!) for the second one (and all others if you have selected more).
"Remove Chromatic Aberration" should not be turned off for the other images. Reenabling this panel should just reactivate all previous settings (or the default settings)!!!
FYI: All my default ISO specific camera and lens settings have this options on. Clicking "Reset" activates all this options. So why it gets off disabling and reenabling this panel? I consider this to be a bug.

Sync Settings Bug w/ Lens Corrections

I'm having an issue with "Sync Settings" and Copy/Paste. Even though I have it *unchecked,* Lens Corrections are being applied. Obviously I only notice it when I try to sync some develop settings, for example, from an image shot with a 135mm to one shot with a 24mm -- the distortion correction is synced even though I've not check it in the Sync dialog.
Running Mac OSX 10.5.8, Lightroom 3 64-bit.

Here is a thread from yesterday. Apparently, already known.
http://forums.adobe.com/thread/684192?tstart=30

Lens correction bug, bad artifacts with contrast adjustments...

Something has changed between LR3 and LR4 in the processing chain for lens corrections. Doing an extreme correction (e.g. using a LCP for a fisheye lens) with increased contrast causes bad halos at contrast edges. The effect doesn't occur with the same settings on LR3. It is almost as if the LCP is being applied after the basic controls rather than before?!?!?!?!
Ken

So I did a bit more checking. It is actually the highlights slider that does it - contrast just makes it more obvious. It is as if the highlights "masking" is getting created in the pre-transformed data and then distorted in some way when going through and extreme LCP like with a fish-eye. Here is an example, contrast at 100 and the "Strong Contrast" tone curve used in both. The one of the left has highlights at 100. Notice the "shadows" in the sky of the leaves, as if the mask was somehow stretched differently from the image data. This was with a fisheye lens and fisheye LCP. You can actually recreate the problem to a degree yourself with any image. Just apply any of the fisheye lens profiles from Adobe (Nikon 10.5mm for example) and look at high contrast regions near the edges of the frame with highlights set to 100%. You'll see shadows like this (again, easier to see with extreme contrast settings). Without an extreme profile applied no such effect.

Lens correction time out bug w7 , solved disabled Desktop Composition

Hi
i 'm running photoshop cs5 under windows 7 ultimate 32bit
every time , i run the lens correction filter i got a time out error
today i tried to run photoshop ,i checked in the compatibility disable desktop composition and the error disapeard
with disable desktop composition do i lose some photoshop feature , colors and so on?
because when i run it now , w7 pop up a warning
thanks

You should normally be able to run Photoshop with Aero enabled. I suspect your video drivers may need updating. What video card/interface do you have, and what version drivers?
Also, how much memory does your video card have on it? You may also find some improvement by altering the Advanced OpenGL Mode in the Edit - Preferences - Performance dialog, e.g., changing from "Normal" to "Basic".
-Noel

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.

Incorrect Canon Lens Identification in Lens Correction.

All,
Reported, but wanted to repeat here to see if anyone else has similar issues. EXIF in Library correctly picks up Canon 70-200 + Canon 1.4 TC. The Lens Correction module in Develop defaulted to a Canon EF-S 18 - 200 F/3.5 - 5.6.
Jay S.

hillrg wrote:
function(){return A.apply(null,[this].concat($A(arguments)))}
JayS In CT wrote:
hillrg wrote:
Jay
Even if you have created profiles for a lens and the lens + TC it still will not pick out the TC version. Been there, done that, and confirmed by adobe Simon Saith in the lens profile creator forum.
Rory
Rory,
See my reply above. That image has EXIF with the lens in it. Why not use that as the mechanism vs. some calculated assumption? I haven't spoken with Simon, but would just seem more logical as a back up if there was any doubt.
Jay S.
Hey, I agree. I pointed out the same thing to Simon.
Well, I put it into the system as a bug. I don't know what the difference in cycles it is. It seems in both cases you have to have some EXIF information associated with the image. I don't know Simon, does he come on to the forum?
Thanks.
Jay S.

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.

Lens Corrections unavailable in Adobe Camera Raw 8.3

hello,
since i switched to photoshop CC (mac version), i am having constant problems with lens corrections in ACR 8.3. i am a professional photographer and i use various canon pro lenses that all exist as unique lens profiles already in photoshop and ACR's lens profile archives. when i open canon .CR2 files in adobe ACR 8.3, i encounter the message "unable to load lens profile" at the bottom right of dialog box and even though the correct lenses are identified, ACR cannot apply corrections (please see the attached visual). furthermore, this behavior happens to be sort of erratic, since it may sometimes decide to apply corrections without displaying the "unable to load lens profile" error message.
when i open the files into photoshop CC without being able to apply corrections, i try the "lens correction" menu within photoshop and it works. it is very cumbersome not to be able to do this at the ACR stage.
the ACR that came with photoshop CS 6 never had such problems and it corrected all the lenses that i had.
can you please help me to fix this issue ASAP, since this error makes me lose a lot of time in my workflow.
i also have photoshop CS6 installed in the same disk, could this have any effect?
best regards,
murat germen

Presumably you're shooting raw for everything, right, otherwise the issue can be that most raw-capable-camera's JPGs don't have lens profiles whereas raw files do, so profiles are found for raw images but not JPGs. The reverse is sometimes true, too, where a camera used to only have JPG output but now produces raw files. I believe the DJI Phantom Vision FC200 quadcopter camera is an example of such. The screenshot doesn't have enough of the ACR interface to see the name of the file.
Are the profiles that aren't found consistently the same lens or are they from various lenses that also have photos that work in ACR 8.3 at other times? And do the same photos that fail to have lens profiles load in ACR 8.3 at one point then work if you open them again, later? In other words does the intermittency seem to be tied to either the specific photos or the specific lenses or not? Specific photos could mean there is something corrupted in the photo. Specific lenses could mean that the lens profiles are missing, somehow, or inaccessible due to permission problems.
Is CS6 updated to the same ACR 8.3 version or is it older? If it is older then install the ACR 8.3 update for CS6. This will re-install the lens and camera profiles, again.
If CS6 is already updated to ACR 8.3, too, then install the DNG Converter 8.3, which also will install the profiles, again.
The DNG Converter can be found, here:
http://www.adobe.com/downloads/updates
If you can't figure it out, then uninstall PS-CC, log out of the CC Desktop app, log back in--so it sees that CC is missing, then re-download and install CC. This should reset ACR back to 8.0 or 8.1 after which you can install the ACR 8.3 update, again.

Adobe Camera Raw - lens correction profiles not found

I use Photoshop CC as part of the photography program of Creative Cloud. My platform is a Mac Book Pro (2013) with the latest Mac OS-X operating system. I have also installed Bridge CC and Lightroom 5.
Since about three weeks (maybe after an update but I'm not sure on that) Adobe Camera Raw's lens correction feature fails permanently. With older pictures (taken long before the error occured for the first time) as well as with new photos and with dng files as well as with cr2 files the ACR dialog always shows the error message (lens correction profile can't be found - since I have the German version of Photoshop this is how I would translate the error message). I didn't install or uninstall any programs, plugins etc. around the time of the first occurance of the error.
I already uninstalled Photoshop CC completely (using the uninstall function in the programs folder) and reinstalled it via Creative Cloud but it still shows the same error.
What can I do?

Hello, you can make sure the latest version is installed by going to help-updates.
Also, make sure that you are running the latest version of the creative cloud application, as it fixes a permission problem that might cause the issue you are facing. Just go to the creative cloud application on your menu bar, and restart it.

LR 4.3 lens corrections issue (bug?)

Similar Messages

Maybe you are looking for