Distortion correction?

Hi folks
I am a new lightroom user, and I have been reading tutorials and guides for the last couple of days. As far as I can tell, Lightroom does not have the ability to correct barrel distortions (I have version 2.6). I have read about PTLens, but I dont fancy the idea of working with an additional program. I have an olympus ep-1 and my 'olympus master' software would perform distortion corrections on RAW files, but again, this requires the use of an additional program. It also didnt seem to work perfectly - ie the horizontal lines are still distorted.
I apologise for asking this question which I see has been asked before in this forum, but the older posts were from 2007 and I was wondering if anything has changed.
So, I guess my question is What is the best way to correct for barrel distortion in conjunction with lightroom 2.6 as my processing software.
Thanks in anticipation
Dale

Dale,
LR does not provide for distortion correction, even not in LR 3 Beta (a often requested feature, who knows what's coming with LR 3 GA ...).
I use PTLens as an external editor in LR to perform distortion correction. This workflow produces a TIFF image in LR upon launching the external editor, which is processed by PTLens, written back and stacked with the original RAW in LR upon return.
Even if you use Olympus Master to correct the distortion, you still would have to export the image as TIFF after the correction and reimport this TIFF into LR, as LR won't be able to interpret the RAW adjustments made by Olympus Master (this is a guess, as I don't know Olympus Master, but I assume it will not write an XMP file interpretable by LR).
So, right now, you cannot do the correction without any external edits.
Beat Gossweiler
Switzerland

Similar Messages

How to disable distortion correction for micro 4/3 lens

Hello,
I have an Olympus E-P2 and Panasonic 14-45mm lens. Adobe Lightroom 3 and Photoshop CS5 appear to be performing some very heavy-handed distortion correction at the wide-end of the zoom (running the file through a different raw converter yields dramatically different results at the edges). This is without selecting any lens profile or enabling manual correction. How can I disable this?
Thanks,
Dara
P.S. Strangely, ACR 6 is not doing any correction of chromatic aberration. Given that the system is set up to try and fix distortion and vignetting automatically, it would make a lot of sense to fix CA too.

That's a solution. It doesn't however answer my question. Clearly there is some metadata tag that tells ACR what corrections to apply. Using EXIFTool, I can replace all the metadata with that from a shot with a non-correctable lens. Unfortunately, this screws up my cataloguing by replacing other things like focal length, aperture and so on. It would be nice to know the exact tag. Thanks.

How do I apply timestamp and barrel distortion correction together?

Hi guys! My first time posting a question here and I hope to get your sound advice on this editing challenge. At the moment I am using Adobe Premiere Pro CS6 and FastStone Image viewer to do some image and video editing. I am using GoPro Hero 3 HD cam to take photos at certain time interval and then combine then it into a timelapse video. The capture settings are 7mp at medium angle. I know the GoPro take pictures at 12 mp W, but as you know the GoPro is notorious for barrel distortion, so at higher settings, it's even worse.
I am tasked with both correcting barrel distortion and adding timestamp feature on my timelapse videos. I've used the FastStone Image viewer to add time stamp or Premiere CS6 to correction distortion. However, I've been unable to do both at the same time. Now I know that the CS6 has some sort of timecode feature that allows time stamp to be shown, however my time timestamp data needs to be extracted from the original meta data, whereas the timecode feature in CS6 only shows just the total length of the video, not the original date and time when data was captured. Using the FastStone allows me to show a real progression of time on data capture from beginning to end (I am working JPEG images in this case).
Now because FastStone extract the timestamp data from original images and shows them in text label format, when I tried to apply the lens correction on CS6, it would also cause distortion in the text label itself. I've tried the other way too, where I've corrected the barrel distortion in CS6 then imported the images to FastStone, but then I would lose the original metadata (the date and time of capture), FastStone is then forced to work with the modified date and time. Now usually I am working with anywhere from 1000 to 3000 images, and FastStone allows the timestamp to be added in batch conversion. It also has this feature to change time stamp to a desired or specific date and time, however, this cannot be done in a batch, but rather on individual frame or image, and thus isn't very practical when I am working with thousands of images.
So my question is if there's any way I can combine both barrel distortion and timestamp (which is using the capture data)? Thanks guys.

Thanks guys! Turns out it's CS6 is intuitive, I can just combine the two sequences into a single sequence with two different tracks with crop effect superimposed. However, it seems with the distortion correction and crop effect added, I am losing some of the details of original sequence without the distortion correction applied. What tools in CS6 can I use to get some of the clarity and vibrant colors back?

Digital Camera RAW Update 5.02 breaks Sony RX100 lens distortion correction (AGAIN!)

Just like with the Digital Camera RAW Update 4.08, the latest 5.02 update breaks the Sony RX100 lens distortion correction again. I'm reverted back to 5.01 until this is fixed.
From your Time Machine backup, restore the previous versions of
/System/Library/CoreServices/RawCamera.bundle
/System/Library/CoreServices/RawCameraSupport.bundle

Yes, I noticed it too, but I wasn't certain it was 5.02 that did it as I sold my RX100 and haven't processes any files for a while. Then as part of the NR discussion here I looked at some old RX100 files, and the distortion correction now disappears. Unfortunately I can't really revert to 5.01 because I was waiting on the A7 support 5.02 brought.
Apple are aware of it, so hopefully the fix will be quick to arrive.
Andy

Perspective/lens distortion correction

About the only thing I ever have to go out of LR2 to do is correct for perspective or for lens distortions (esp. on wide angle lenses). I know this might not be an easy thing to fit in the interface, but it'd be very useful. Especially if you can set it up to do a stored lens distortion correction for a given lens at a given focal lens (+ maybe focus distance).
-Lars

I hope y'all don't mind if I think aloud a little more here.
We've been talking about perspective correction and lens distortion correction as if they were just about the same. They aren't.
Lens distortion correction is a fairly complex warp, but one that is completely determined by the lens and focal length (please corect me if I'm wrong). The main use of it would be to correct for the lens defects, not to create an artistic effect (like CA repair). It could therefore very reasonably be done as a preparation step, as with the Olympus cameras that actually store some correction information. It would be of relatively low user value to be able to change it later, and it would be much harder to implement.
Perspective correction is most definitely a user-driven correction. Not only does LR not stand a chance of figuring out what to do automatically, there would also be many cases where you'd want to correct in one dimension but not another, correct somewhat less that 100%, or in other ways fiddle with the amount of correction. Fortunately, it is a much simpler correction, merely the application of a small transformative matrix. Unlike lens distortion correction, it doesn't turn circles into strange wobbly shapes, but merely into ovals.
Let's take a look at the local adjustments: Crop, rotate, red-eye, spot removal, graduated filter and adjustment brush.
Crop would be well-nigh impossible to mix in with lens distortion correction, another reason to have the correction applied first. With regards to perspective, it should behave more or less like it does towards rotation.
Rotation can actually be done internally using the same operations that perspective correction would, but should probably still be separate in the interface.
Red-eye and spot removal both operate on horizontal-vertical ovals (restricted ovals for spot removal). These would be awful with user-adjusted lens distortion correction, even more reason to have that be an initial step. Perspective correction would stretch them somewhat. What happens when the user makes a dust spot fix, then fixes the perspective, then attempts to adjust the dust spot fix? We end up with the same situation as with vignetting: That there are pre- and post-crop versions. This distinction would now have to extend to pre- and post- crop+rotate+perspective adjustments. Obviously, you'd also want to be able to spot remove based on the corrected image, and it'd be strange to have a tool that's bent. It may be necessary to separate out dust spot removal from "subject matter removal" (including red-eye), as dust spotting should always be before perspective correction.
Graduated filter was really the thing that convinced me that the two corrections need to be split. Applying lens distortion correction after graduated filter would lead to a bent 'horizon line', a very bad thing indeed. Fortunately, it would be fairly resistant to perspective correction, though not entirely: If the horizon does not follow the perspective correction axis, the outer lines ought to tilt together. Probably overkill, though.
We already have an example of a similar situation: Red-eye removal and rotating. Try making a red-eye correction, then rotating the picture sharply. The red-eye oval will stay in the same position, even though that moves it from where it was supposed to be. I guess graduated filters could behave similarly.
The adjustment brushes are probably the simplest: Since they're already amorphous shapes, they can "simply" be bent and distorted along with the corrections and still make as much sense afterwards. Except if you want to use them to correct lens errors, but I don't know how often you'd want to do that.
Perhaps distortion correction and pre-crop vignetting should belong together. They would certainly interact.
That's my $0.02 plus inflation.
-Lars

Lens Distortion Correction Documentation?

I have seen in some discussions that LR corrects lens distortion for some lenses and some cameras. I have not been able to find documentation that indicates what cameras and lenses are supported for this - either for LR2.3 or 3.0beta. Is that documentation available somewhere?
Thanks!
David

Well, I guess that would be why I couldn't find it. ;-)
I'll try a more specific question. Are any DSLRs supported by the distortion correction? Specifically, I'm interested in a Canon EOS 5D, and what lenses (if any) Adobe has profiled for distortion with this camera.
I am hopeful that when LR3 comes out of beta, it will have distortion correction for most or all supported cameras and lenses, and that at least some of the specifics will be documented.
Thanks!
dbr

Lens Distortion correction not working on tonemapped jpg files

I have a series of photos exported from Lightroom 2 that I HDR tonemapped in Photomatix. Unfortunately after a disk failure I do not have the original RAW files and only have the 100% jpg saved tonemapped files from photomatix.
Now that Lightroom 3 is out I wanted to try some lens distortion correction on them. I imported them and immediately noticed after enabling the lens profile corrections and choosing my lens that although chromatic arberration and vignetting works there is no effect at all with the distortion correction! Even when I slide the slider from one side to the other absolutely nothing changes.
I tried it on other raw files and it works fines. I tried it on jpgs that I have that have not been combined and tonemapped in photomatix and they work fine. It is only the jpgs created from photomatix.
Is there something about the exif data that I am not considering or any other explanation as to why the photomatix jpgs won't take any distortion correction? thanks

If it's working for other jpg's, (and I though it didn't work on jpgs, so who knows?) then it does sound like the photomatrix program is wiping out the exif information that is needed.
Did you try using a viewer to look at the exif info, both before and after, to compare? Maybe there is a setting (in photomatrix) that you are missing when you save data?
Sorry, don't know photomatrix, so just offering generic ideas in the hopes it sheds light..
Cheers!

Lens distortion corrections in Camera Raw?

Chromatic aberration, lens vignetting, post crop vignetting
are possible in Camera Raw.
Why not have access to lens distortion corrections in CR?

Maybe show us a screenshot of what you see on the system that isn't want you expect. What version of ACR are you using in each? It should be visible in the title bar of the ACR plug-in if you unmaximize it, or you can do About Plug-ins / Camera Raw in PS.
Here is the Manual tab of ACR 6.7 on Windows in CS5:

Raw Update 4.08 removes distortion correction for Sony RX100 files?

I loaded raw update 4.08 on my 27 inch iMac yesterday. A while later, I opened Aperture 3 to export some RX100 files from a family event last week to Smugmug. To my horror, as the photos loaded when I viewed them, the automatically applied lens distortion correction was removed and obviously it was worst with the wide ones. The issue also shows up in iPhoto, so it seems a general OS thing. To confirm it was indeed due to the raw update, I exported the same raw files to my MacBook Air, which I hadn't updated yet. Sure enough, Aperture loaded them with distortion correction just fine. Obviously, I won't be updating the MacBook until this issue is fixed.

TBannor wrote:
I loaded raw update 4.08 on my 27 inch iMac yesterday. A while later, I opened Aperture 3 to export some RX100 files from a family event last week to Smugmug. To my horror, as the photos loaded when I viewed them, the automatically applied lens distortion correction was removed and obviously it was worst with the wide ones. The issue also shows up in iPhoto, so it seems a general OS thing. To confirm it was indeed due to the raw update, I exported the same raw files to my MacBook Air, which I hadn't updated yet. Sure enough, Aperture loaded them with distortion correction just fine. Obviously, I won't be updating the MacBook until this issue is fixed.
This may be disappointing, but it is expected. Note that Aperture has removed nothing, however. What you are seeing is caused by using a RAW Original instead of a JPG Original.
The Apple RAW Compatibility Update is part of the OS. The RAW converter in OS X is system wide. Any program can use it. Aperture uses it.
Aperture does not, afaik, do _any_ lens correction. Lens correction must be handled by a plug-in or external editor (or done outside of Aperture).
The files you had imported and viewed prior to the most recent RAW Compatibility Update were JPGs. They were converted in-camera. The camera contains the software to correct for lens distortion when it converts the sensor data to a JPG file. Now that you can view the converted RAW files, you can see that this distortion correction is not applied. That makes sense: Aperture is doing the conversion, not your Sony camera.
So there is no issue to be fixed. If you want to use Sony's lens corrections, you have to either use the JPGs created by the camera, or convert the RAW using Sony's RAW converter (Image Data Converter v. 4). Other software may also apply lens distortioin correction (I don't know). Aperture does not.
This is a much-asked-for feature request. If you would like to see it added to Aperture, tell Apple. The only line they listen to is "Aperture➞Provide Aperture Feedback". It certainly wouldn't hurt to add your voice.
HTH.
--Kirby.

I've done spot healing in my images but want to change lens distortion corrections. Does it matter?

- I originally corrected all the lens distortion in my images with the default Adobe lens profile for the lens, and also done all the spot healing too. However, I now want to change the lens distortion profile to a profile that i've made instead. The Adobe default lens profile and the one that i have made give different distortion corrections (Adobe's is a bit too strong).
- Will all the spots chosen in the spot healing still be mapped correctly? i.e will the source points for the spot healing and the area i'm sampling from still be in the correct positions after adjusting for the new lens distortion?
- Does Lightroom allow for this, or do i have to re-do all the spot healing?

Hey Paul,
Well, you could just try it to find out . But the answer is: Adobe adjusts spots (and paint, and red-eye...) to accomodate lens corrections. It's one of the reasons it is recommended to leave lens corrections until last if your Lightroom is performance challenged, i.e. it takes some horsepower.. (me? I like having lens corrections done up front, despite the performance hit).
Rob

Clarity/shadows + distortion correction = terrible artefacts in high contrast areas

common example (clarity and shadows +100):
without distortion correction
with distortion correction
Raw file: nycz.info/temp/castle.dng

The adhoc fix I'm using for images where it's causing problems is to paint out the problem areas with a localised adjustment brush with a very large hit of negative clarity. As most of the problem areas have been pretty small it's an easy fix, but I'd like to see the issue addressed before the final comes out as close examination has shown it up on quite a few images (reflective mike against black stage background, pier edges against a bright but cloudy sky, tree branches against the sky). I've also now set my default to having lens profile distortion off and only using it where I need it.
Edit to add: Unfortunately on the image I'm working on at the moment, it only removes it as long as clarity is set to less than 50 - I need the lens adjustment to get the horizon flat, and I want the clarity, but if I try to have both I'm getting nasty white streaks along the pylons of a pier and it shows at screen size let alone on prints or 100 per cent view. With this particular image any amount of clarity over about 15 and the profile image adjustment is producing ghastly results, visible at small sizes.
Edit again - urggggh. Manual adjustment to level horizons (beach images again) using lens correction plus clarity isn't good either. I've got rather a lot of those and basically can't use any amount of clarity or I start getting areas of light stripes along dark high contrast edges. However if i go to the crop and straighten settings, and straighten there, it's fine.
Edit again: Ok this is an app killer. Back to Lightroom 4.0 (If I can work out how!). Too many of my images are affected, and affected noticeably. What a shame as the defringing in RC2 is absolutely fantastic on long lenses, but this is affecting too much stuff.
I'm getting it on quite a few images I've done nothing to excepted converted them to LR4 - it's very clear on the before/after previews of PV2010 and PV2012. And the edges don't have to be that high contrast - I'm not sure if this screen shot shows it clearly enough but conversion gives a row of little white dashes along the green girder in the attached images Click on images to see them a bit larger- the first image shows small size before and after comparison with problem area highlighted - nothing done except change process PV2010 to PV2012; second image shows PV2012 magnified a bit. Turning off the enable profile corrections button returns image to PV2010 appearance. Removing clarity adjustment will also remove artifacting - in this case it's the clarity that is mucking things up. I can get the same artefacts with clarity on zero and the shadows pushed up above 70. Clarity gives problems at much lower settings.

Radial distortion correction

I noticed that the new SDK now exposes camera intrinsic parameters including radial distortion. Could someone please post a code snippet showing how to correct distortion for a given depth space point? The function that I wrote based on the link below doesn't
seem to be producing correct result. Perhaps the units aren't pixels. Thanks!
http://docs.opencv.org/doc/tutorials/calib3d/camera_calibration/camera_calibration.html
public static DepthSpacePoint CorrectRadialDistortion(DepthSpacePoint dp, Microsoft.Kinect.CameraIntrinsics ci) {
double dx = dp.X - ci.PrincipalPointX;
double dy = dp.Y - ci.PrincipalPointY;
double r = Math.Sqrt(dx * dx + dy * dy);
dp.X = dp.X * (float)(1 + ci.RadialDistortionSecondOrder * Math.Pow(r, 2) + ci.RadialDistortionFourthOrder * Math.Pow(r, 4) + ci.RadialDistortionSixthOrder * Math.Pow(r, 6));
dp.Y = dp.Y * (float)(1 + ci.RadialDistortionSecondOrder * Math.Pow(r, 2) + ci.RadialDistortionFourthOrder * Math.Pow(r, 4) + ci.RadialDistortionSixthOrder * Math.Pow(r, 6));
return dp;

Here's the code for both Distort() and Undistort() functions:
/// <summary>
/// The function is used to build a map for the inverse mapping algorithm that is used by UndistortImage().
/// </summary>
/// <param name="u">Image space column (x) pixel position in the distortion corrected image relative to top-left corner (0,0).</param>
/// <param name="v">Image space row (y) pixel position in the distortion corrected image relative to top-left corner (0,0).</param>
/// <param name="ci">Camera intrinsic parameters including distortion coefficients.</param>
/// <param name="x">Corresponding column (x) coordinate in the source image (that is, in the original image from camera).</param>
/// <param name="y">Corresponding row (y) coordinate in the source image (that is, in the original image from camera).</param>
public static void Distort(float u, float v, CameraIntrinsics ci, out float x, out float y) {
// first normalize image space coordinates to world units with origin at principal point
u = (u - ci.PrincipalPointX) / ci.FocalLengthX;
v = (v - ci.PrincipalPointY) / ci.FocalLengthY;
double r = Math.Sqrt(u * u + v * v);
double d = 1 + ci.RadialDistortionSecondOrder * Math.Pow(r, 2) + ci.RadialDistortionFourthOrder * Math.Pow(r, 4) + ci.RadialDistortionSixthOrder * Math.Pow(r, 6);
x = (float)(u * d * ci.FocalLengthX + ci.PrincipalPointX);
y = (float)(v * d * ci.FocalLengthY + ci.PrincipalPointY);
/// <summary>
/// The function corrects image distortion given supplied cameara intrinsic parameters.
/// </summary>
/// <param name="u">Image space column (x) pixel position in the source image (that is, in the original image from camera) relative to top-left corner (0,0).</param>
/// <param name="v">Image space row (y) pixel position in the source image (that is, in the original image from camera) relative to top-left corner (0,0).</param>
/// <param name="ci">Camera intrinsic parameters including distortion coefficients.</param>
/// <param name="x">Corresponding column (x) coordinate in distanation corrected image.</param>
/// <param name="y">Corresponding row (y) coordinate in distanation corrected image.</param>
public static void Undistort(float u, float v, CameraIntrinsics ci, out float x, out float y) {
// first normalize image space coordinates to world units with origin at principal point
u = (u - ci.PrincipalPointX) / ci.FocalLengthX;
v = (v - ci.PrincipalPointY) / ci.FocalLengthY;
double r = Math.Sqrt(u * u + v * v);
double d = 1 - ci.RadialDistortionSecondOrder * Math.Pow(r, 2) - ci.RadialDistortionFourthOrder * Math.Pow(r, 4) - ci.RadialDistortionSixthOrder * Math.Pow(r, 6);
x = (float)(u * d * ci.FocalLengthX + ci.PrincipalPointX);
y = (float)(v * d * ci.FocalLengthY + ci.PrincipalPointY);

Distortion Correction with Lookup Table

Hello,
I am trying to run an image through lookup tables in order to correct some distortion.
I have two 2D lookup tables "LUTsXnew.raw" and "LUTsYnew.raw" which locate the new (x,y) coordinates that i want to move the pixel intensities from original image "writing_final_D.raw" into the corrected image.
However, Labview takes too much time (12 seconds), if you have some experience with arrays and images can you please have a look at my code and tell me what i am doing wrong?
I am running the same algorithm in C on the same pc and it takes less than 1second.
Thanks,
CK
PS: I am attaching the VI plus the required raw images
Please ignore the resulting image, i just care about speed for the moment
Attachments:
images1.zip ‏287 KB
distortion correction_set pixel1.vi ‏81 KB

CK,
I cannot run your VI because Vision is not supported on my platform. So my comments are general rather than specific.
1. Your while loops can be replaced with for loops because you know the number of iterations in advance.
2. If you transpose the arrays before entering the loops, you can use autoindexing rather than using Index array in the inner loop.
3. If you only update the inner and outer iteration count indicators every 100 iterations you will not have displays that are meaningless to the user using up processor time. Eliminate them completely for the fastest performance.
4. Avoid coercion inside the loops. The IMAQ Set Pixel Value function has coercion dots on three inputs. Doing explicit conversions outside the loops may be faster.
5. The Tick Count functions should be in frames of their own to assure accurate timing.
6. Local variables are not needed and are generally slower than wires.
Lynn
Attachments:
distortion correction_set pixel1.2.vi ‏69 KB

Lens distortion correction in Premiere CS6?

I'm trying to correct the distortion caused by a wide-angle lens in Premiere CS6. From what I can tell, there is no filter or transform / distort feature within Premiere itself. I followed the steps in this tutorial to open the MPEG4 in Photoshop, apply the lens correction filter, and then export the video again to be re-imported to Premiere. http://podcasts.creativecow.net/adobe-premiere-tutorials-podcast/correcting-lens-distortio n
However this tutorial is for CS5. I am seeing no adjustment or filter layer in my layers panel, as it appears in the tutorial. When I go to export the video, it seems the Adaptive Wide Angle filter or the Lens Correction filter has only applied to a single frame of the whole clip. Bummer.
Any other suggestions for fixing lens distortion in Premiere?
Thanks!

Both these replies are a bit rude and unhelpful. I am editing in Premiere, and I am not very familiar with it. The question is about how to fix lens distortion in Premiere. Maybe there's a way to do this that I'm not aware of...? That's why I asked the question! There's nothing about it that I could find in the forums. The only fix I found didn't work—which was to use Photoshop *integrated with Premiere*. And two people tell me to use AEFX without pointing me in any directions of how to do that. Useless.
Anyway, I found some information that *was* helpful. This tutorial demonstrates that one critical step was missing from the prior tutorial, which is to convert the video layer to a smart object before applying the effect:
http://www.protechreviewgroup.com/tutorialsinformation/tutorial-fisheye-correction-in-phot oshop-for-gopro-hero-hd/
The same person provided a tutorial on how to do this in AEFX:
http://www.protechreviewgroup.com/tutorialsinformation/tutorial-fisheye-lens-correction-in -after-effects-for-gopro-hero-hd/
Now that these steps are taken, I have to take the footage back into Premiere. It's a workflow question. Other video editing software has this kind of stuff built-in to the effects panel.

Does the camera distortion correction filter in Elements 12 have automatic settings I can disable?

I have found that the filter makes automatic changes to images. For example, if I correct a vignette with no sturctural sliders touched, then save the setting, the image appears in my editing window signifcantly altered with altered barrel configurations. So, I have to redo and compensate or just forget about it. This is not a problem with an image I want to correct--architectural, for instance. But, who wants to start fixing issues that the software is creating? I would like to disable this but have not found a setting yet. Thanks.

As far as i know, the auto correction in pse 12's correct camera distortion filter can't be disabled.
One way around it would be to strip all the info from your file.
Open your image, then go to File>New>Blank File and from the Preset list click on the name of the document.
Go back to your original, Select>All and then Edit>Copy
In the new blank document, Edit>Paste and Layer>Flatten Image
Then hopefully when you open your new document into Filter>Correct Camera Distortion, no auto correction is applied

Distortion correction?

Similar Messages

Maybe you are looking for