Changing a lens profile in Notepad?

I recieved a Samyang 14mm F2/8 (used on Canon 50D) this weekend, and can not find a profile for it. I did find one for the Canon 40D using the Adobe Lens Profile Downloader, and it is not recognized in LR 5.3, on Windows 7. After looking at in Notepad, I tried changing all references to Canon 40D to Canon 50D, hoping it would work, at least enough for me to test this lens. It is still not recognized in LR, and I am wondering if anyone has tried to make a change such as this, and had it work for them. If all elses fails, I will create the profile!
Thanks,
Larry

retiredff wrote:
I recieved a Samyang 14mm F2/8 (used on Canon 50D) this weekend, and can not find a profile for it. I did find one for the Canon 40D using the Adobe Lens Profile Downloader, and it is not recognized in LR 5.3, on Windows 7.
The Adobe Lens Profile Downloader should automatically install the profile to the correct user folder. Check as ssprengel has outlined to be sure the profile is actaully in the correct folder. The only profile I see is for raw image files. If you are using JPEG image files this raw profile will not show inside LR in the Lens Profile list. You can edit the lens profile in Notepad so that it will work with JPEGs and save it with a different name (add_JPEG). Keep in mind the vignetting correction is slightly different for raw files than JPEGs, but the distortion correction should be the same. You may need to set the Vignetting slider to a higher or lower setting than 100 to get a closer match for JPEGs. Procedure here:
http://forums.adobe.com/message/3393879#3393879

Similar Messages

  • Another Lens Profile Enable question

    I know this question has been asked repeatedly and I believe have read all the answers to date    but   is it possible to keep the check box checked for each new picture being developed in Lightroom 3.4.  The default profile works fine but the box has to be checked for each new photo and this is disruptive of a smooth workflow.  If it is not possible please let me know.  thanks  jc

    Thanks Beat, I was unaware of the performance impact Lens Profile corrections have on the Spot Removal tools.
    If you don't normally use the Spot Removal tool on your images (I don't), then you are better off enabling Lens Profile in the default Develop settings. For those few images that need Spot Removal work simply uncheck 'Enable Profile Corrections.' Don't forget to re-enable lens profiles when done to see your final results.
    I also suggest determining your own lens profile default settings. I use Distortion '0', Vignetting 50-75, and C. abberation 100. REASON: Distortion setting will cause some cropping of the image when applying correction and in most images distortion is not visible. I suggest manually selecting Distortion correction only for those images that exhibit obvious straight line curvature. I actually find most pictures shot with my highest distortion lens look better with '0' Distortion correction. The Vignetting setting at 100% can look unnatural and may cause areas toward the corners of your image to lose some sharpness, especially with very wide angle lenses. I set my default for 50% Vignetting and rarely see a need for more. The C. aberration control does an excellent job of correction and has no other issues, so I leave it at 100%.
    I suggest you try it for yourself with each individual lens and make your own judgment – Your mileage may vary dependent on lens performance and subjects. Certainly feel free to set your default lens profiles settings differently for each lens where you feel it looks best.....and that may be 100 for all of them. You can always "fine-tune" the adjustments for images that require it.
    To change the lens profile default settings, adjust all sliders to the new settings, click the down-arrow next to 'Setup' under 'Lens Corrections,' and select 'Save New Lens Profile Defaults.' You can also choose 'Reset Lens Profile Settings' to return to 100, 100, 100 default.

  • Lens Profile changes in ACR 6.2 update

    Before the update, I had perfectly aligned masks for hundreds of images using the Nikon 18-200mm lens.  However, when I now open their Smart Objects, make and change and close, a new distortion correction is being applied, ie. the masks are not longer aligned.  This is a major headache and it's not clear how I might go back to the original lens profile.  Even if it is worse, I am already invested in it with the masks.  Pushing out this change without due notice or way to ensure backward compatibility is a major shortfall.  I would be interested to hear how Adobe recommends I proceed?  Revert to ACR 6.1 and miss out on all future updates?  I highly recommend building legacy profiles into future updates.

    What ACR adjustments do you need to do to the image that can only be done in RAW format and cannot be done when ACR is editing a TIF after your initial ACR-conversion?  It seems as though you may need to modify your workflow to convert to TIF, and then re-edit that TIF with ACR and use that as the smart object on which to apply your masks.  TIFs only have relative WB adjustments, not absolute like RAW files, but if the WB is close you probably don't have to tweak things too much, although you'd want to be careful to create your initial set of TIFs with the same initial WB so you could tweak groups of images similarly with the same relative adjustments.
    For Adobe to accommodate what you're wanting they'd need to have the ACR version number where a profile came from as part of its name so ACR can match the specific profile used with old images.  I think Adobe messed up when they didn't do this, initially, but perhaps they feel it is still a beta period and don't want too many versions of each profile cluttering things until things have settled down.
    You asked, earlier, how to get the old profiles back. 
    On my Windows Vista/Win7 computers the Adobe-supplied lens profiles for Nikon are duplicated in two different places:
    C:\ProgramData\Adobe\CameraRaw\LensProfiles\1.0\Nikon
    C:\Users\All Users\Adobe\CameraRaw\LensProfiles\1.0\Nikon
    I think additional users-supplied profiles would go to the following place, although I'm not sure because I don't have any user-created lens profiles:
    C:\Users\-your-user-name-\AppData\Roaming\Adobe\CameraRaw\LensProfiles\1.0\Nikon
    The way to get your old profiles back would be:
    Find the current Adobe-supplied profiles on your computer and remove them.
    Download and install the ACR 6.1 update.
    Find the profiles installed with that in the same places you removed the other ones from and save all these 6.1 profiles somewhere else.
    Download and install the ACR 6.2 update.
    It may be sufficient to copy the old 6.1 version of the profiles for the lenses you use into your user-profile-specific location and those would override whatever Adobe-supplied profiles there are, but I doubt it. 
    And if not, then what you'd want to do is edit the XML in the LCP files for ACR 6.1 for your lenses that you have already put into your user-profile-specific location and change the name to have the ACR version in it, so when you run LR or ACR, you know which ones are your old profiles and which are the current ones that Adobe has supplied.
    The remaining task is to re-assign this relabeled ACR-6.1-specific profile to your underlying images that have smart-objects in them to be able to use your masks with the old correction in place.
    Going forward it might be wise to also copy and relabel each profile for your lenses that have been updated...you may have to test things yourself to see if there are any differences.

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

  • Lightroom Bug: with GoPro Hero4 Silver Lens Profile, crop settings do not sync properly in Lightroom 5.7.1 when Constrain To Warp is checked

    I was having a bit of difficultly in getting crop settings to properly sync in Lightroom 5.7.1 (running on OS X 10.10.1) when Constrain to Warp was checked.  This appears to be a bug in the latest version(s) of Lightroom that include(s) the GoPro Hero4 Silver Lens Profile settings.  I'm working with a lot of files from a GoPro Hero4 Silver camera shot in the time-lapse / interval timer mode.  All of them are horizontal with the same resolution (and dimensions).  I've tried various sequences to get this to work in terms of using Auto-Sync, resetting the settings on all images except one and then copy and pasting settings, etc, though the crop is not properly syncing regardless of what I do.
    Here's are instructions of how to duplicate this issue (there are some extra details/steps here, though this should be clear enough to produce the same result):
         1.  in the Develop settings for a single selected image, go to Lens Corrections, click to Enable Profile Corrections (in the Profile tab), and then pick the GoPro Hero4 Silver Edition (Adobe Profile) if it is not automatically chosen for you (if you are using files from a Hero4 Silver camera).  After this, click on the Manual tab, and set the Scale setting to 76.  (as you will see, you now have the full horizontal width of the image that was getting cropped off, though you do see white around the edges that have been warped/shaped to correct the fisheye distortion)
         2.  Press the R key (or click on the Crop Overlay tool just below the histogram).  Change the Aspect option to Custom.  Click to unlock the lock next to it (this seems to re-lock after setting to custom even if it was locked before).  Place a checkmark next to the Constrain To Warp option.  (At this point, you'll see the image gets cropped back to an approximately 4:3 ratio and the full horizontal width is not included in the cropped area)  Click the upper right most corner of the crop area and drag as much to the right and top as it lets you go.  Do the same for the lower left corner, dragging it as far to the bottom left as you can go.  (Now, you will see that your cropped area is the maximum rectangular width and height you can select without getting any of the excessive white area)  Click the Close button (or press R again) to leave the crop overlay tool.
         3.  Press G to go back to the grid of images.  Make sure the image you just adjusted the settings for is the only one selected.  Right click on it, go to Develop Settings, and click Copy Settings.  Click Check All on the window that appears and then click Copy.
         4.  De-select the image you were working on.  Select multiple other images in the grid.  Right click on one of these, go to Develop Settings, and click Paste Settings.  (at this point, you will see their aspect ratio has become more panoramic than the 4:3 aspect ratio the images previously were)
         5.  De-select these images.  Select one of these image, and then press D to go to the Develop settings for this image.  Press R to go to the Crop Overlay tool.  Here you will see the bug where the crop was not properly copied over from the first image.  The selected area is smaller than the full width and height available to crop.
    It seems that the bug is that Lightroom is only copying the aspect ratio (and the other settings), but not the actual crop selection.
    I just thought of a workaround that I've tested and can confirm works (and will also work in a slightly different workflow than above).  In step 1 above, for the Model (and Profile), manually pick the "GoPro Hero4 Black Edition" or the "GoPro Hero3-Silver Edition".  If using the "Hero3-Silver" setting, the Scale (also in step 1 above) need only be set to 79 (rather than 76 for the Hero4 profiles).  By picking one of these Lens Profiles and doing everything else the same as the other steps above, the crop settings do copy and paste properly.  This does also appear to work properly when selecting the "GoPro Hero3-White Edition" Lens Profile, with a Scale setting of 75, which yields a slightly more rectilinear image (with a wider aspect ratio -- almost, but not quite 16:9).
    While this isn't too big of deal as it does work by picking one of the other lens profiles (and the Hero4 Black Edition profile appears to make the same exact correction to the image), this was incredibly frustrating last night to notice that some files had the proper horizontal field of view / crop and others didn't, and other users may experience this or not even notice their crop is not copied properly (as, depending on one's composition and image, it's not extremely obvious with such a wide view).
    I hope this discovery helps someone else and provides feedback for Adobe to correct this issue in the next version of Lightroom 5.
    On a separate, additional note for Adobe:  Please allow the crop overlay tool to "crop" an image to a size that is larger than the original dimensions of the image.  This would allow for one to retain maximum original sharpness in the center of the image when using the Lens Profile tool to correct, or "de-fish" a lens, without having to scale the image down with the Scale option on the Manual tab of the Lens Corrections settings.  For example, when I do the above process selecting the Hero3-White Edition profile, my final image dimensions are 3840 by 2257 pixels, reducing the size of the image in the center by 25%.  If the tool allowed one to crop/scale a larger image size, and I kept the Scale option of the Lens Corrections settings at 100 rather than 75, my final image dimensions would be 5120 by 3009 pixels (larger than the 4000 by 3000 pixel dimensions of the original image which the tool now limits me to).  Yes, the edges would be a little softer but the center would retain the original detail.  (this is essentially what the Calculate Optimal Size button found in the Hugin open source software does, when using it on a single image for lens transformations/corrections)

    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 Profiles not working in Lightroom 5.4?

    I've got OSX 10.9.2, Lightroom 5.4, latest Camera raw, everything up to date.
    When I "Enable Profile Corrections" for an image shot with a Sony a7r and Sony FE 55mm lens, it should automatically retrieve this profile:
      /Library/Application Support/Adobe/CameraRaw/LensProfiles/1.0/Sony/SONY (Sony FE 55mm F1.8 ZA) - RAW.lcp
    Well, it doesn't.  The only Sony lens available in Lightroom's Lens Correction panel is "Sony DT 18-200mm."  But there are several dozen Sony lense profiles in the "Sony" directory.
    And more puzzling, the camera "Make" menu lists 8 manufacturers (Apple, Canon, DJI, GoPro, Nikon, Sigma, Sony, Tamron) but leaves out a number of others — Fujifilm, Hasselblad, Leica, Mamiya, etc.
    And as with Sony, only one Tamron lens is listed.
    I've tried re-installing Lightroom fresh, and no luck. 
    Photoshop works fine and has all the lens profiles.
    Anyone else noticing this?  Got a fix?
    Irked in Cambridge,
    Mike

    I only shoot in RAW, and I am having this same issue. I shoot Nikon with a Tokina lens. This morning, Tuesday October 14, 2014, I had this setting. I closed the program and restarted it, and now I only have Apple, Canon, DJI, GoPro, Nikon, Sigma, Sony, Tamron lens profiles. There was not an update, nor did I actually change any settings. What is going on here?
    I talked to customer support, whom suggested that I was stoned out of my mind because these profiles do not exist in lightroom. I did as the rep asked, followed the link and downloaded the "new" profile. Now I can't get it installed. Meanwhile, my photos are waiting for me to edit them. Can someone please help out here?!

  • Lost lens profiles in LR 4-5

    Recently Lightroom no longer finds my lens profile (sigma 17-50mm) on new pictures.  Same camera, same lens, same file format.  It can still use the profile on older pictures but newer pictures it only shows like 5 lens profiles vs the 50+ that were there before.  Similiar behavior on the canon side.   By the way it seems to have lost the ability to see many other lens manufacturers to on the newer pictures.
    So I know the profiles are physically on the system.  I know I can see them in older pictures just not newer ones on the same library.  No update I can think of correlates to the change either.
    Canon 60D jpg & raw, Sigma 17-50mm f2.8
    Lightroom 4 and now also the new lightroom 5.
    Thoughts ?

    Oh I should have known better...yes it was. Why that didn't jump out at me I don't know.
    I modified the RAW profile for jpg and dropped it in
    C:\Users\[username]\AppData\Roaming\Adobe\CameraRaw\LensProfiles\1.0\Downloaded,
    and I am off to the races.

  • How to use lens profile from Lightroom 5 in Lightroom 4

    I'm using Lightroom 4.4 on a five-year-old iMac.  I haven't been able to upgrade to LR 5 because it requires an operating system upgrade, but the technicians at the Apple Store say my machine is too old for the upgrade.  I just bought a new Sony 18-105 lens which requires siginificant software lens correction.  It has been included in the latest ACR in LR 5, but not LR 4.  Is there any way I can locate and load the lens profile for just this one lens in my LR4?  I've looked and there is no profile in the Adobe Porfile Downloader I can use.

    Zenfolio purposely disables saving of images from the gallery, so requires some deviousness to get to a smallish version of the underlying JPG image, here:
    http://fiegenschuhphotography.zenfolio.com/cdn/pub/uf9epzjb9ekl/0/null/mk/2ho0rvxl_mbq61ne tqcu/s2/v61/p207717972-3.jpg
    Figgie123, can you provide an original-sized raw file to test with?  Upload it to somewhere like www.dropbox.com then post the public download link, here. The file on Zenfolio is small, difficult to even download, and isn't what you're working with when the lens profiles are not working for you.  The idea is to repeat what you're doing to see if we have the same issues.
    Here is what applying a Sony E PZ 18-105 F4 G OSS profile looks like in Photoshop Lens Corrections and I don't really see any change compared with the Zenfolio image:

  • Light room lens profiles

    Does anyone know how to make this work reliably?  All my lenses provide exit data, yet if I have the lens profile set to auto it often will not assign the right lens. Worse if I choose a devoloo preset that specifies a lens, then set it to auto and then eg change the vignette or distortion value it will drop back to the previous lens.  The only sure fire way I've found to get it to work - or to make sure the right profile is there is to switch to another manufacturer and then back to the.correct manufacturer.  If it picks a lens I don't have as the profile then I've bussed wrong and have to pick another manufacturer. This is obviously Bonkers.
    PS the new forums are virtually unusable on mobile. For design software manufacturers this is not great

    Do your lenses have Adobe-supplied profiles that are listed on Adobe’s lens-profile page or are they ones you’ve created or downloaded because Adobe doesn’t supply these lens profiles?
    http://helpx.adobe.com/x-productkb/multi/lens-profile-support-lightroom-4.html

  • Help with importing lens profile to Lightroom 5.4 for Windows

    Hi,
    I'm running Adoble Lightroom 5.4 on Windows. I recently bought a Rokinon 14mm lens for Canon and have a couple lens profiles that I want to try out. I have already tried importing to the two following locations below and nothing showed up when I restarted Lightroom. Any solutions?@@
    C: > Users > User > AppData > Roaming > Adobe > CameraRaw > LensProfiles > 1.0 > Then I created a folder called Downloaded > Then I created another folder inside the folder Downloaded called Rokinon and dropped the lens profiles in there.
    Here is the other one I tried:
    C: > Program Files > Adobe > Adobe Photoshop Lightroom 5.4 > Resources > LensProfiles > 1.0 > Then I created a folder called called Rokinon and dropped the lens profiles in there.

    Something is weird about this lens profile file.  It appears to be for a Canon 85mm lens, not a Samyang 14mm lens, and, as you say, this profile is for JPG files not RAW files.  If you want it to apply to raw files you need to change the CameraRawProfile from False to True.
    After changing the False to True, because the Make is set to Canon you have to go to the Canon lens list not the Samyang list in the Lens Profile selection dropdown list, or edit the Make to have Samyang..
    Because there is an 85 for several focal-length numbers, not 14, I think the correction being applied may be totally wrong.   Where did you get this lens profile file? The other profile file you sent has 50mm in some focal-length areas and 85 in others.
    To be able to tell if this, or the other profile, is reasonable, you probably need to take a picture of something with a grid of lines, like a brick wall and see if there is barrel or pincushion distortion that is corrected or worsened.
    Here is a screencapture of the file as it looks in a text editor with notes about what seems wrong:

  • Directory of Lens profiles in Win 7

    In LR4 some lens profiles are not available that are in LR3. It may well have to do with the fact that I "downgraded" some profiles that were only available as RAW versions to non-RAW versions. Unforgivable but I just don't always shoot in RAW. They do show up in LR 3 as I mentioned and I believe that they are stored in C:\ProgramData\Adobe\CameraRaw\LensProfiles\1.0\ but get the idea that LR4 uses some otther directory... Is thatt right?

    Sorry, no idea why the change was made....I just know that it was.
    In the early days of the LR4beta there were quite a few comments about the respective size (within Program Files) of LR3 and LR4....the latter having a footprint of almost 800mb, LR3 being less than 100mb. To some, this was evidence of sloppy coding and application bloat, but of course they hadn't realised that over 300mb of camera/lens profiles had switched from Program Data (LR3) to Program Files (LR4b). That made the real difference about 400mb, almost all of which is attributable to the 200+mb of Book Templates and the almost 200mb of stuff seemingly video related (in the Support sub-folder).

  • Adobe Lens Profile Creator - ERROR (Detect corners failed because file reading errors ocurred)

    1) I have successfully created a lens profile for a Nikon AF Micro Nikkor 40mm 2.8 lens used in a Nikon D5200 Camera. For this I converted the raw .nef files to .DNG first using Adobe's DNG Converter.
    2) When trying to create another lens profile using the EXACT SAME .DNG files as posted in 1), I am no longer able to create a lens profile because of the message "Detect corners failed because file reading errors ocurred". I am also unable to create any other lens profile using different photos.
    3) I have also tried using a fresh install of Adobe Lens Profile Creator in another mac and I get the exact same error.
    4) I AM ABLE to create a lens profile if I use .jpg files (generated from the same raw .nef files as mentioned) but this doesn't help because then the profiles don't show up when trying to open a raw file in Adobe Camera Raw.
    Please help as this is exasperating.
    Thank you.

    Thanks! I had the same error message in Adobe Lens Profile Creator 1.0.4 for OSX and I found the problem to be the letter ö in the folder name for the DNGs. The lens is an old ISCO-Göttingen and the progress stopped at 2% with the mentioned error message. Changed the folder name and now it works!

  • Lens Profile Tool Addition – White Balance Offset Correction

    I have noticed that my Canon 17-40mm and 70-200mm F4 IS lenses have virtually identical color temperature and can use the same white balance setting. My Sigma 50mm F2.8 Macro lens is another story, requiring almost 200K and +15 change to White Balance sliders. I am sure there are cases where Canon’s lenses will differ more widely and exhibit a similar degree of white balance differences, not to mention use of UV or 1B protection filters. An 85mm F1.2 lens using “rare earth” low dispersion glass, will have a warmer color temperature than a lens using more common glass elements.
    I use the X-Rite ColorChecker Passport to create custom profiles for each of my camera bodies. I typically make separate correction presets for Daylight, Cloudy, and Tungsten (2700K). This requires changing the LR White Balance sliders to obtain “neutral gray in the ColorChecker image files shot in each of above described lighting conditions. It does not appear necessary to create a separate ColorChecker camera profile for each lens, just correction to the LR white balance slider settings.
    I did some measurements of change in camera profile for Sunny Daylight (~5,500K), Cloudy (8,000K+), and Tungsten (~2,900K) lighting. There was no measurable change in rendering of the ColorChecker Passport images for the extreme Sunny to Cloudy conditions, and only very slight changewhen comparing the Tungsten profile. This was done by loading a ColorChecker Passport image file and applying alternate profiles:
    EXAMPLE:
    Open a DaylightColorChecker Passport image file in LR, apply Cloudy Camera Profile, and adjust White Balance for the gray scale patches using the Eyedropper Tool. Then look at the 'Before' and 'After' images....you will see NO visual change to any of the color patches. I saw only a very slight change when doing this with the Daylight to Tungsten (artificial light source) comparison.
    The relatively small change in color balance between lenses (~500K max.) should have no measurable or visible affect to the ColorChecker Passport created "Camera Profile." The ColorChecker Passport or any other "Camera Profile" creation tool is first and foremost correcting for differences in the camera's image sensor color rendering.
    SUGGESTION:
    Since this white balance difference is a factor of the lens, it would be very convenient to add another tool in Lightroom's and Camera Raw Lens Profile panel for “White Balance Offset.” This allows setup of LR defaults for one specific lens type, such as your most used lens. Then you use the new ‘Lens Profile’ located ‘White Balance Offset’ correction tool to adjust white balance for all of your other lenses. In addition, Adobe or camera manufacturers could also provide the 'White Balance Offset Correction' as a function of the lens spectral response deviation from linear. This would provide a "uniform method" of calculating and adding the White Balance correction to the 'Lens Profile.' Since this is a factor of the lens only, the “lens offset correction” can be used with ANY lens/camera body pairing, The current LR and Camera Raw White Balance settings are then only used for “Global” correction of lighting conditions, and NOT for lens differences.
    This is a linear mathematical function,which should be extremely easy for Adobe to add the ‘White Balance Offset’ correction feature to LR’s and Camera Raw's Lens Profile GUI. Just like many other tools in LR that some don't use, you can choose to use it or not!

    Interesting suggestion. Thanks. -Simon

  • Why are no Pentax lenses in the Adobe Camera Raw lens profiles when processing JPG files?

    I normally shoot and process raw files and use the latest version of Adobe Camera Raw for processing. Some of these files are converted to jpg for use on the net or e-mailing etc. Sometimes I want to make minor changes to the now converted jpg file and often go to Adobe Camera Raw for ease and speed of use. Lately I have gone back to some files that were not thoroughly processed as raw files before conversion to jpg. When, in ACR, I go to Lens Corrections panel, Profile tab, I Enable Lens Profile Corrections and choose Setup: Auto (or Default) and get the message, "Unable to locate a matching lens profile automatically".
    I then go down to Lens Profile and click on Make with the intention of choosing the Pentax lens which I used for the photo. Here is the problem - there are only six choices under make, namely Apple, Canon, Nikon, Sigma, Sony and Tamron. I have no such issues when processing a raw file in Adobe Camera Raw. Pentax lenses are automatically detected and Pentax, along with Leica, Samsung, Zeiss, etc. are choices under Make of lens.
    Do other people have this problem? Is there some setting I have missed? Is Adobe just not permitting some makers' lenses, for which there are profiles, to be corrected if the files are jpgs?
    BTW, I have checked and the same issues exist for tiff files opened in ACR.

    Assuming I read your post correctly, and that you're trying to use Lens corrections on JPEGs and TIFFs...  I believe there's a completely different set of profiles for correcting already "developed" images (such as JPEGs and TIFFs).  If I recall correctly (and it's been a while since I read about this), it's the same set that's used inside Photoshop for the Filter - Lens Correction tool (I hope someone here will correct me if I'm wrong, but I'm sure I read this somewhere).
    If your lenses are known to Camera Raw when you develop raw files, I suggest you will need to go all the way back to your Raw file and reprocess it from that stage.  You'll get a better result anyway.
    -Noel

  • Hello, Can you tell me where I can found the lens profil for the Canon 500MM F4 Mark II

    Can some one tell me where I could find this lens profile for Lightroom 5.4.
    thanks

    Given the 600mm F4 IS II (February 2011) lens profile hasn't been created yet it may be a while (if ever). I wouldn't worry about it since the lens profile only corrects distortion and vignetting. There is virtually no distortion with either of these lenses and vignetting is within 0.2EV using the 600mm profile, which you can set as the "default" profile. Personally I think people put too much emphasis on the need for "automatic" lens profile correction. All my lens profile defaults are set to Distortion = 0 and Vignetting = 50. I change the setting only when an image appears to need more correction. WHY?
    REASON
    Distortion correction crops part of the image and increases "edge" stretching with wide angle lenses–It's a trade-off for straight lines in the image. IMHO-If it's not visible in the image you don't need it. 100% Vignetting correction setting can look un-natural and amplifies lens aberrations and softness in the corners, which is where vignetting correction is applied the most.
    My 2 cents worth.

Maybe you are looking for

  • HT1338 Updating iMovie in App Store

    I am the second user of my macbook air (boss got a new pro). His apple id is needed to update imovie in the app store. I have signed in on the App Store but i am still prompted to use his apple id to install the update. I don't need iMovie but I am f

  • Photoshop isn't detecting my Graphics Card

    I recently installed a Radeon R7 240 graphics card and am still having problems with CC.  Everytime i start it I received the "3d features require a minimum of 512MB of vRAM.  Photoshop has detected less than that on your system." I have 2GB of VRAM.

  • Are multiple instances of Spartan browser allowed?

    Build 10049 When I right-click on the Spartan browser icon in my "Quick Launch" taskbar, there are the options: * Project Spartan * Unpin * Close I was expecting the selection of "Project Spartan" would launch another instance of Spartan, but that do

  • LabVIEW 8.6 + SourceGear Vault is not working

    Hi there, when I try to configure LabVIEW with Vault as source control client i get the error message "2972 - An internal error occured during the source control operation." (see picture) So, what causes the problem and how can i configure the source

  • [Borders] need help to design a transparent shadow

    Hello ! After a long research about border topic, I have made my own shadow border. To do this I made a panel with a transparent background then I had my border, a gradient of transparent gray color (Color Alpha way). I do this because on Swing compo