Lens Correction problem - double vignetting?

On some but not all of older images, with xmp's deleted and all caches cleared, I end up with a over vignette effect, as shown below. Haven't been able to correlate it with other than images previously processed in 2003 then 2010. The .nef file date did not change. And before somebody asks the manual controls were all at neutral. D300 and 16-85VR lens with downloaded profile.
Richard Southworth

Shot the proverbial brick wall this morning at 42mm, very evenly illuminated. Vignetting correction with slider at 100 yielded the attached image. Slider at 20 corrects ok.
Adobe please help, this profile should not have made it thru your screening process. Other than this problem it works well.
Also posted in Lens Profile Creator forum.
Richard Southworth

Similar Messages

5D mark III lens correction problem with dark shots

Just found a new irritating problem with 5D mark III and Lightroom 4 (currently on 4.2). I shot quite a few shots in the dark over the weekend using high ISO (6400-16000), with EF 24-70 f/2.8L. If I enable the lens profile correction on the dark shots, the corners of the images all develop incredibly strong purple haze that renders the image unusable. Not enabling the correction allows me to use the images just fine. Also images that were shot with similar settings but were shot inside, with more light, don't have the purple fringing issue. Makes me wonder if this is some incompatibility between Canon's high iso noise reduction system and Lightroom's RAW processing when it does lens corrections.
Anyone else seen this?

Sulka Haro wrote:
Replicated the shot under a heavy blanket -> yes, the exposure looks the same. Whatever is causing the corner to be noisier than rest of the exposure doesn't seem to be caused by light.
At that very high of ISO you are actually seeing small differences in the sensor chip temperature due to heat from the electronics in the camera. The small amount of increased noise you're seeing in the corner at ISO 25600 is insignificant.
Sulka Haro wrote:
Interestingly enabling long exposure compensation doesn't seem to do very much to really improve the shots at these sensitivities. When enabled, the exaggerated corner noise does disappear, but also it looks like some areas in the middle of the exposure become more noisy with non-uniform noise blotches appearing instead of fairly uniform slightly higher noise pattern.
I haven't needed to use Long Exposure Noise Reduction with my 5D MKII, so have no firsthand experience. My guess is that at very high ISO settings (above 6400) a lot of what your are seeing is random noise or "shot noise," which changes from frame to frame. This causes the dark frame subtraction to "fail" in the way you are seeing. Just a guess.
There is an excellent 5D MKIII review that compares noise reduction with several other high-end camera models. The reviewer also states,
"The 5D Mark III's ISO 51200 and 102400 remain a complete mess even with strong noise reduction applied - You have to be desperate to use these settings. ISO 12800 and 25600 remain very marginal for my uses. I always shoot in the lowest standard ISO setting that will allow me to get my desired shot, but begin to cringe when settings above ISO 3200 must be employed. Your standards and applications may be different."

Lens Correction Problem

I'm using a Nikon D3 and Nikon professional lenses which are all recognised by the Photoshop CS5 (12.04) lens Correction function when inputting RAW images.
But...
If I process any of my RAW files through Photomatix (saving as JPG) and then open them in CS5 the lens correction function only recognises the images as having come from a Nikon Coolpix camera and I'm not given the option of selecting a Nikon D3 and associated lenses.
I can understand that there's some loss of functionallity due to the processing through Photomatix but I would have hoped that I would have been given the option to 'override' the lens correction feature and force it to recognise the Nikn D3 I'm using.
This isn't possible, or is it?
Any help/advice would be very welcome...
Richard

See if selecting Nikon Corporation instead of Nikon from the camera make drop-down menu makes a difference.

Lens correction works with my RAWs, but not my JPEGs?

Hi all, if I check "Enable Profile Corrections" for any of my RAW files, Lightroom automatically identifies the Make/Model/Profile of my lens. However for my JPEG files (same camera, same lens) when I check "Enable Profile Corrections" it defaults to none/none/none, and my lens doesn't even show up in the dropdown menus if I try to select it manually.
How can I get Lens Correction to work for JPEGs as it does for RAWs?

Update, got it working, sweet! I'll post what I did below, hopefully useful to somebody...
1) Probably the best thing would be to make my own Lens Profile -- http://labs.adobe.com/downloads/lensprofile_creator.html -- but I'm not quite ready for that now, I just wanted to make the built-in RAW profiles work for JPEG too.
2) I located the RAW profiles I wanted available as JPEG profiles, in this folder:
C:\ProgramData\Adobe\CameraRaw\LensProfiles\1.0\[MyCamera]\
3) In this folder:
C:\Users\[USER]\AppData\Roaming\Adobe\CameraRaw\LensProfiles\
4) I created the following subfolder:
C:\Users\[USER]\AppData\Roaming\Adobe\CameraRaw\LensProfiles\1.0\[MyCamera]\
5) I copied the RAW profile files from #2 above into this new folder.
6) I set the files to not be "read-only"
7) I opened those files into a text editor, and I performed a Find/Replace.
From: <stCamera:CameraRawProfile>True
To: <stCamera:CameraRawProfile>False
(Note that there are multiple instances, so I performed a Find/Replace ALL.)
8) I set the files back to "read-only" (probably not necessary)
And now when I turn on Lens Correction for a JPEG, it works! And it seems like my camera isn't performing any lens corrections (such as vignetting) when saving JPEGs, so it's pertty good as-is. Though, per #1 above, probably the best solution would be to make my own Lens Profiles from scratch.
Thanks to all & I hope this helps somebody...

Problems with LENS CORRECTION Photoshop CS5

Hello
I get up the dialogue box AUTO CORRECTION.
But I cant acitivate CORRECTION (geometrical distortion, chromatic aberration and vignette).
I cant press it, its is gray.
I have filled out everything as I have always done it.
I have never had this problem before, I have always managed to do lens correction.
What has happended?

You are in the Elements forum.
The Photoshop forum is there:
Photoshop General Discussion

Problems with Lens Correction in CS5

Hello
I get up the dialogue box AUTO CORRECTION.
But I cant acitivate CORRECTION (geometrical distortion, chromatic aberration and vignette).
I cant press it, its is gray.
I have never had this problem before, I have always managed to do lens correction.
What has happended?

You are in the Elements forum.
The Photoshop forum is there:
Photoshop General Discussion

Vignette Correction + Lens Correction in Camera Raw / Lightroom

Ok i merge 2 requests for both camera raw and lighroom...
-> Vignette Specific Correction: Using preset for Lenses like Canon DPP Does for Peripherical Illuminance Correction, the vignette tool in lighroom is good but can't adapt to a variable vignette profile of each lens...
+ Ability to user to add them using a png 24 bit or similiar for Lenses not present on the DB (think using old lens, with adaptors, old zeiss without automatic controls that obviously will be not profiled by Canon, Nikon, Sony.. for their bodies)
-> Lens Correction based on Preset... + exif reading like in photoshop cs5 + manual adjustments
thank you

So you use Photomatix to create a 32-bit HDR file and then tone that 32-bit file in ACR? Are the Photomatix 32-bit files that much different than the PS-CC 32-bit files? The Photomatix 32-to-16-bit conversion is quite a bit different and perhaps preferable, but I didn’t realize the 32-bit result file is also that much different. It’s been a while since I’ve tried 32-bit HDRs and even longer since I’ve tried them in Photomatix so things may have changed or I’ve forgotten.
If you are using Photomatix, then you are not using an Adobe raw conversion at all, so Adobe settings and raw lens profiles are not seen and used at the initial raw-conversion stage in Photomatix.
The choices would seem to be that you can use Adobe products to create 16-bit TIFs as an input to Photomatix, or hack an Adobe raw lens profile to be used with non-raw files in ACR, or do your lens profile corrections after you’ve saved your 32-bit HDR image back as a 16-bit one and use the lens corrections area in Photoshop if that is still possible, nowadays.

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

Sony FE 28-70mm in camera + Lightroom lens correction = double correction or overcorrection?

Hello,
I have a Sony A7 with Sony FE 28-70mm kit lens. On the Sony A7, if i select "Shading Compensation" in the camera menu, the camera corrects vignetting in the saved raw file. I have experimented by taking two raw photos, with in camera Shading Compensation turned on and off. I then imported the photos into Lightroom. I then tried turning lens compensation (vignetting) on and off in Lightroom. This confuses me. In the first image (In camera ON and Lightroom correction ON) it looks like vignetting is completely gone. With in camera ON and Lightroom lens correction OFF, there is still clearly remaining vignetting. With in camera OFF and Lightroom ON there is also clearly remaining vignetting
Can someone tell me what the recommended course of action is? Is the Sony in-camera lens correction worse or better than Lightroom? Neither the in-camera nor Lightroom's correction will correct vignetting completely on their own. Does that mean that the Lightroom correction is supposed to be used in tandem with the in camera correction to achieve full vignetting correction? There is lacking information/documentation of this feature, I have looked at both Sony A7 help guide and Adobes documentation about lens correction without finding any info about this situation.
Thank you.

"Shading Compensation" is probably saved as metadata tag in the raw file but the raw file data is not corrected. This metadata is probably used in the included Sony software to automatically correct the raw for "Shading Compensation" but Lightroom probably does NOT use this data. You will hopefully get a reply from a Sony user.

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.

Community lens correction works for me

A few days ago lens correction profiles showed up for my D300 with both 16-85VR and 55-200VR lenses. Brick wall testing indicates they seem to have nailed distortion/CA/vignetting, at least for focal length extremes.
So how do we know where these profiles originated, if for no other reason than to give credit?
Richard Southworth

I can think of one really good reason why a lens profile should be camera-specific for the best possible results:
Not every sensor responds the same to light coming in from various angles. Microlenses, for example, are different from sensor to sensor.
So the vignetting profile for one camera might be a general improvement on another, but it may not produce specifically accurate results on that other camera.
You cannot oversimplify the problem and achieve perfection.
-Noel

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.

DNG Conversion Of Sony ARW Not Carrying Over In Camera Lens Corrections

One of the great features of the Sony NEX-7 is that the NEX-7 makes automatic lens corrections for vignetting, chromatic aberration and distortion problems. These corrections are written to the file and the preview. However, when converting these images from ARW to DNG the correction data seems to be lost, and the images revert to their uncorrected state. This requires all images to then be re corrected with the Adobe lens profiles, which is both tedious, an extra step, and also seems to produce results that are somewhat less optimal than the original corrections made by the camera.
Should not the ACR Converter and Lightroom retain the lens corrections made by the camera?

A Tonal wrote:
This is one of those confusing issues where the way Sony describes the feature makes it sound as though it's part of the ARW format, and the way Adobe describe ACR and DNG makes it sound like this would be one of those manufacturer specific details that DNG is supposed to convert into a the Adobe format.
Yes, that might be so. It's similar with the manual of my Nikon D600. Nowhere does it say explicitly that all these adjustments (including lens correction, Active D-Lighting, etc) work only for the JPGs. And it cannot be otherwise.
A Raw image is not defined yet, not written in pixels yet, heck it is not even an image.
The Raw image is only affected by the exposure, that's pretty much the only thing. Even White Balance is nothing but a metadata tag that - luckily - is read by Lr.
A DNG is Adobe's answer to the various Raw formats. But it is designed to behave like a Raw image. Therefore you cannot expect that camera settings that affect JPGs only carry over to DNGs.
A Tonal wrote:
There are so many features on cameras that are only supported with JPG output that it almost makes it not wroth bothering with RAW, as by the time you get to the end of the process, with all the extra steps and work involved in handling RAW, you pretty much wind up with something that looks like a JPG anyway, and you had to give up using some of the camera's features to use RAW.
This shows that you don't understand what Raw is and what its advantages over JPG are.
I would recommend that you educate yourself about the advantages of Raw. Your photography would benefit from this, believe me.
Google "Why should I shot Raw?" and you will find lots of good webpages.
Finally, Raw shooting is much simpler than shooting JPGs where you always have to fiddle with the virtual 100s of different settings for JPGs.
What do you have Lr for? In Lr you can adjust your Raw image by looking at it on a large calibrated monitor, whereas for the settings in your camera you have to rely on a 3" monitor - at best.
Make your life simpler and your photography better: Shoot Raw.

Bulk Lens Correction?

So, I've recently purchased Lightroom and love it. Only problem is adding lens profile to each photo. I worked out there is a bulk setting, but I use multiple Canon lenses, the 24-105, the 70-200 and 60mm Macro. If I apply lens correction in bulk to all images it will go by what's on the first image. Say for example the first image was taken with the 60mm it will apply that correction to all photos despite what lens they were taken with.
I went through the rest and unticked and reticked Canon and it selected the correct lens this time, but not in bulk.
Does anyone know the correct way to set this to happen in bulk or is it not possible?

The only way to "turn on" Lens Corrections for images shot with different lenses and already imported is to use the Library Filter Bar. Select by lens type, correct one image, and then hit the 'Sync Settings' bottom in the lower right-hand corner. Select only 'Lens Profile Corrections' and 'Chromatic Aberrations, which both should be enabled in the first image. Go to the next lens type and repeat, etc.
The best way to do this is by changing your LR 'Default Develop Settings,' then all future image imports will have Lens Profile corrections applied automatically.
1) Select any raw file (or a virtual copy of same) in the Develop module and hit the 'Reset' button in the right panel at the bottom.
2) Under Lens Corrections> Profile check 'Enable Profile Corrections.' I also suggest checking 'Remove Chromatic Aberration' under the Color.
3) Go to the toolbar Develop> Set Default Settings and click 'Update to Current Settings.'
You can add other setting changes to the Develop Default Settings such as the Camera Profile, etc. The Lens Profile default settings can be changed under the Profile tab by clicking on the up/down arrows next to the word 'Setup Default' and selecting 'Reset Lens Profile Defaults.' I set the default Distortion for all my lenses to '0' and manually adjust the images that have visual distortion. Distortion correction crops the image and can introduce softening with lens that have high distortion, such as wide angle zooms. I also set Vignetting to 50%, since 100% correction usually is too much for my taste. Feel free to experiment and set each lens default settings individually.

Do the lens corrections consider cropped sensors?

I tried using the supplied lens corrections for my Canon 70-200 2.8 with pictures from a 1DIIN (1.3X crop factor). I'm getting far too much corner vignetting correction by default and more distortion correction than necessary. Are the corrections defined only for full-frame cameras?

Actually I remove two data sets, which for f/1.4 and f/2.0, both are in same distance.
Note that, the original profile was created with 2 different distances.
So, I leave another distance set for correction module for interpolation.
And the problem found on the photo which around f/2.0.
But how the profile was generate, it may be my fault,
since I use too high shutter speed with my room fluorescent, the light source.
The flicker of the light may lead the optimazer to confusing.
I also observe that the distance reading from metadata record by the camera, with Lightroom,
was not corelate with the distance shown in the generated profile.
I'm not sure what the measurement unit, the profile used, but it should be meter.
For example:
I shooting at around 2 meters away from the chart, which close to the number in metadata.
But the FocusDistance in the profile is 11 meter.

Lens Correction problem - double vignetting?

Similar Messages

Maybe you are looking for