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!

Similar Messages

  • 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 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:

  • 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

  • How can I work with my adobe Lightroom Version 5 which was added to my Samsung NX3000. If I want to load an .SRW File it is not possible, only the .JPG File. How and from where can I the Module and how is it to install ?

    How can I work with my adobe Lightroom Version 5 which was added to my Samsung NX3000. If I want to load an .SRW File it is not possible, only the .JPG File. How and from where can I the Module and how is it to install ?

    You need Lightroom 5.5 or later (the most current version is 5.7.1). This is a free update if you have already purchased an earlier version of Lightroom 5.
    Product updates

  • Javascript is not working in the published file

    Hi ,
    I using the javascript in the captivate 5.5 to generate the text from variable in the textbox. It is working when I press the F12 button, But it is not working in the Published file.
    I called the function in the button and I written the script in the slide.
    Please let us know how to proceed..
    Thanks
    Sathish BC

    This is the Script I used in the captivate 5.5 and I called the text using variable in the text box.
    var objCP = document.Captivate;
    function valText()
    var a  = objCP.cpEIGetValue('A');
    var b  = objCP.cpEIGetValue('B');
    if (b>=5)
    objCP.cpEISetValue('B',0);
    GetAryVal(b);
    objCP.cpEISetValue('rdcmndGotoFrameAndResume', objCP.cpEIGetValue('currSlide'));
    function GetAryVal(e)
    var a1  = objCP.cpEIGetValue('Txt');
    var b1 = a1.split("#");
    var c1 = b1[e-1].split("$");
    objCP.cpEISetValue('C', c1[0]);
    objCP.cpEISetValue('D', c1[1]);
    valText();

  • Camera raw is not working on my NEF files D600

    camera raw is not working on my NEF files D600.. I ALREADY TRIED all of the updates ( first 7.3, 7.4 even the 8.1) i have the photoshop cs6 and im not finding a way to make it read my files!!! even the DMG converter its not reading them!!

    It might be the way you are downloading them. I believe that Nikon Transfer has been updated to overcome a corruption bug which affects Adobe products.
    If you are using Nikon Transfer, it might be worth updating to the latest version, and downloading your photos again. Or use Adobe Photodownloader instead (I would).
    Also, accepted wisdom is to download photos off the memory card using a card reader, rather than via the camera USB, as it is less prone to problems. YMMV.

  • GoPro Camera Raw Lens Profile settings not working for image sequence in Photoshop/AE/Premiere CS6

    Hey Everyone,
    I'm in need of assistance in either Photoshop CS6, After Effects CS6, or Premiere Pro CS6.  I just installed the trials after seeing Russell Brown demo the GoPro Lens Profile correction feature in Camera Raw.  Basically what I'm looking to do is make adjustments (in Adobe Camera Raw) to a series of still images (shot with the time-lapse mode on the GoPro) and then either export those stills through Photoshop or Bridge to a temporary movie file that will be imported into a timeline (with other video clips), or import the JPG files (with Camera Raw settings) directly into After Effects or Premiere as an image sequence.  The latter would be preferable as it'd avoid the extra step of having to render the intermediate/temporary movie file.
    Right now, my current workflow for GoPro time-lapses is:
              - use Bridge CS4 to do basic color correction on the still images
              - save those as TIF files
              - run the TIF files through a custom script to have Hugin 2012.0.0 (open source pano stitcher) remove the fisheye distortion
              - open the new TIF image sequence into QuickTime Player 7 (Pro)
              - export the image sequence as a QuickTime movie file
              - import the movie file into Premiere Elements 10 to place on a timeline with other video clips (as Premiere Elements can't handle the sequence(s) of thousands of still images without crashing)
    If I can go directly from Bridge to a timeline, it'd save a lot of processing time (and it'd be much nicer to preview the images in Bridge without the fisheye distortion)!
    I can prepare the GoPro JPG files through Adobe Camera Raw in Bridge CS6, though when I go to import the JPEG image sequence into Premiere Pro CS6 or After Effects CS6, none of the Camera Raw settings are applied.  If I export the Camera Raw files in Bridge CS6 as DNG files (a step I'd really prefer to avoid) and then import the DNG image sequence into After Effects CS6, the Camera Raw settings are applied except for the Lens Profile settings -- I can pick other cameras but not the GoPro lens profiles when the DNG image sequence loads in After Effects.  It also appears that once I open the DNG files in After Effects CS6, I can no longer access the GoPro Lens Profile in Adobe Bridge CS6 -- the list changes to the same list I get in After Effects.  Premiere Pro CS6 doesn't let me import the DNG files at all.  I've also tried to import the JPG files (as well as the converted DNG files) into an image sequence in Photoshop CS6, though it doesn't allow me to do so (the Image Sequence checkbox is grayed out after I apply the Camera Raw settings in Bridge).
    There could be an issue going on with different Camera Raw versions.  I didn't have Premiere Pro CS6 installed during my initial testing, though now do notice that the Camera Raw dialog in Bridge CS6 only lets me choose compatibility up to "Camera Raw 7.1 and later" when I choose to export the files as DNG.  I thought Camera Raw 8.2 was an option there a couple days ago when I only had installed Photoshop CS6 and After Effects CS6 (though am not 100% certain).
    Please let me know if there is some workaround to get the GoPro lens profile Camera Raw corrections applied in an image sequence in one of the Adobe CS6 products (without having to export the files as temporary TIF or JPG files out of Camera Raw).  I'd greatly prefer to shorten my current workflow for these files.  (I just updated the CS6 trials and have tested all three programs again though I still get the same results described above.)
    Does Lightroom 5 have any option to export Camera Raw image sequences as movie files (or any other feature that might help in simplifying my current workflow)?  I can't install the trial right now as it's not compatible with OS X 10.6.8.  I'd consider upgrading OS X if I knew Lightroom 5 would do what I need, though am waiting for any potential color profile issues to be resolved in OS X 10.9.
    I can open the image sequence in Photoshop CS6 if no Camera Raw settings are applied and then use the Lens Correction Filter to apply the GoPro Lens Profile settings, though I really prefer the Camera Raw interface in Bridge for tweaking image settings.  As soon as I apply Camera Raw settings to the first image, Photoshop CS6 grays out the image sequence checkbox.
    If there isn't a way to take Camera Raw files straight from Adobe Bridge to a timeline, I may stick with my current workflow using CS4 and see what I can do to better automate some of the steps as the TIF export in Bridge, fisheye distortion removal in Hugin, and render in QuickTime Player all take quite a while.  I won't mind waiting for all the processing if I can set it and check back on it in later the next day when it's fully complete.  Is there a way to have Adobe ExtendScript execute an external shell command (i.e.: a command I could type into the bash shell in Terminal in OS X)?  If not, is there a way to call/run an ExtendScript script from the command line and pass a parameter to it that my custom script could use?
    Thanks in advance,
    Mark

    Can you zip up a few of your GoPro images, upload them to dropbox.com and post a share link, here, so others can experiment with them, or do you mean this issue is global to all camera models?

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

  • Canon 24-70mm f2.8 II - profile correction not working

    The profile correction in LR5 for the above lens is not working. It appears it's a blank profile with zero distortion data. On the other hand, the profile for the older lens, the canon 24-70mm 2.8 I works well.
    Having owned both I know version II of this lens has less distortion, but it's by no means zero across the range. This is one of the most important top of the line lenses for Canon, I'm sure many like me would appreciate this profile corrected.
    Thank you.

    I also for got to mention that the data in this profile may actually be invalid as the minimum focus distance for that lens is 0.38m
    Another more basic reason to regard it with suspicion, would be that it reports a crop factor of 0, which is (of course) impossible.
    The fact someone in the community may have rated it 5 out ot 5 for quality, is not exactly authoritative AFAICT .
    The profile already installed along with LR is distinguished by being generated with the 5D Mk II, not the 5D Mk III, but IMO this is no reason not to prefer it in other respects. Adobe seem to have done a thorough job of the task here.
    It sounds in this case, as if a (apparently invalid) profile that has been downloaded by the user, has taken precedence over the "built-in" one. (These two classes of profile are stored in different file locations with differing user permissions.)
    In case you are unaware, the profile that is to be auto-selected against a given Lens ID on the images, can be controlled by the user. Choose "Set as Default" from the profile selector, after manually choosing one there. All images with the same Lens ID, where the profile selection reads "Default" (which is a safe setting to impose across all images), will hereafter adopt a user-corrected choice of profile, all by themsleves.
    RP

  • 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

    I would like to know if there is way to correct a lens distortion (Barrel Distortion) inside Lightroom. If not, how can I do it.
    ex. Nikon D70 lens 18-70mm

    And this is really a thread for the main forum. This is Feature Requests, and this one is already in.
    Don

  • Secondary color correction not working in Premiere CC

    Greetings,
    I'm unable to build secondary color correction masks in Three Way Color Corrector, RGB Curves etc in the current version of Premiere CC.
    In any of these plugins, when I check "show mask" I get the usual white slate filling the frame. But when I use the color picker to make a selection the whole frame stays white. It appears that I'm making selections but it's not building the mask for some reason. When making an extreme color change I can see that the mask is not building as it affects the whole frame.
    This started after upgrading to CC. I've recently updated to the most up to date version (yesterday) and am still having the same problem.
    Premiere CC 2014.1 Release
    8.1.0 (81) Build
    Macbook Pro Retina, 15" Late 2013
    2Gh Intel Core i7
    8Gb
    Intel Iris Pro 1536Mb
    Yosemite Version 10.10
    *note-my Colleague is not having this problem, he's working on the same OS and same CC build but he has an Imac. So I'm guessing this problem is unique to my hardware config.
    Anybody else have this problem or know of a fix?

    I have the same Problem new MAC OS Premier Pro CC or Premier Pro CS6 both have an issue with the Title Tool. If you open the title tool and try to make color changes or change size of the font it sticks at the default color and default font. SOmetimes the title tool will work and then when I exit it's back to the default first type location, default font and default color. Sometimes it will not even let me exit the Title Tool.
    Please help I have Projects I'm working on Deadlines and I pay a monthly Fee for Software that works and it's not working.
    Model Name:          Mac Pro
      Model Identifier:          MacPro5,1
      Processor Name:          6-Core Intel Xeon
      Processor Speed:          2.4 GHz
      Number of Processors:          2
      Total Number of Cores:          12
      L2 Cache (per Core):          256 KB
      L3 Cache (per Processor):          12 MB
      Memory:          16 GB
    Software  OS X 10.9 (13A603)
    Graphics  ATI Radeon HD 5770 1024 MB

  • Lens profile was not working!

    i generated lens profile data lcp, with Canon EOS-1Ds Mark III, samyang f=14mm lens.
    it is good working on at the same camera and nikon D3 shooting images.
    but at the Canon EOS-5D Mark Ⅱ shooting images (these are CR2 format) it is not working !!
    what is the reason? is it different camera or different image format?

    canon 5D mark ll (poor)
    canon EOS 1Ds Mark lll , nikon D3
    it's a good working !!

  • 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

Maybe you are looking for