Manual lens profile creation?

Hi all,
Just looking for tips or "best way" to create profiles for lenses old manual lenses that do not record exif data in the images. What is the best way for me to take these images and in a batch modify the lens name, aperture and other relavent exif info that I would need to properly identify these images in ALPC and CameraRaw?
Thanks all,
Greg

Eric wrote: > "Hi Greg, if you regularly supply missing EXIF metadata (e.g., lens name, f-number, focal length, focus distance, etc.) for these images, then you can proceed in the usual way".....
OK, making some progress here. I've shot all the charts with a D700 and a legacy (old) 24mm Nikkor f2.8, and now I'm pulling the metadata from a new AF 24 f2.8 that was mounted to the same body. Shooting with the legacy lens produces some erroneous metadata, and leaves some blank, so shooting a frame with the new lens gives me everything I need. Except for the subject distance.
Shooting for the metadata on the D700 with the new AF lens, both of these entries are ALWAYS listed as 3/100, no matter what my focus distance:
<exif:SubjectDistance>3/100</exif:SubjectDistance>
<aux:ApproximateFocusDistance>3/100</aux:ApproximateFocusDistance>
Testing just to see what those numbers should look like, I tested with my 5D and a Canon 35mm lens, and with the lens set to manual focus, I ALWAYS get 203/100. With the lens set to auto focus, I always get 4294967295/1, no matter what my focus distance.
So my question is, does it matter what I put in there?
Thanks for any insights,
George

Similar Messages

Lens Profile Creation

I created a set of lens profiles with "adobe lens profile creator" and saved them in /Users/(User Name)/Library/Application Support/Adobe/CameraRaw/LensProfiles/1.0. When in CS5 or Bridge I cannot locate these profiles. Where did I go wrong?

I saved the photos as DNG files. I took 9 pics of each f-stop, focal length, etc. than saved the file using the default save location and name. Where I got confused was each set of 9 pics when saved in the default location used the same name so I added A, B, C etc to the name of each file so the saved file looks like A Canon EOS 5D Mark II (ef24-70mm f2.8L USM) - RAW.lcp; B Canon - - -. and so on. What I was trying to accomplish was Appending the LCP files, maybe that is where I have gone wrong. The "Adobe Lens Profile Creator User Guide" is a little confusing to me in the section of "Appending an Existing LCP File"

Lens Profile for Tokina 11-16mm for Canon?

Does anyone know where I can obtain the profile for the Tokina 11-16mm Canon lens? I don't really want to try and reinvent the wheel since someone has likely done this already.

Even if Tokina is aware of the lens profile tool, they would have to be convinced that dedicating any effort would be worth it. No good deed goes unpunished, and this is doubly so for corporations. They would be in a position where they would be responsible, in some manner, for these profiles. Which sort of hitches their wagon to Adobe, for better or for worse. There are subtle corporate implications to this sort of thing, which is why corps move slowly on stuff like this.
As for the Adobe tool that allows you to browse lens profiles, I believe there is a field on the profile that indicates who created it. It has been a long time since I looked at it.
The fact is there are many, many lens and body combos out there, and what is obvious and common to you very well might not be, or those who use it are not interested in Adobe products. As in all things, there is going to be a ranking, and the higher profile vendors are just going to be addressed first.
Meanwhile, Adobe has made the tool available for easy lens profile creation anyone who wants to DIY their own profiles and share them. It really isn't that hard to contribute to the community with a few hours of work. It beats complaining it hasn't been done for you already.

How do I create an ACR custom lens profile if camera exposure can't be set to manual?

How do I create an ACR custom lens profile if camera exposure can't be set to manual?
I ask this question for the Nokia 808 PureView 41MP camera. It produces stunning image quality but exposure can only be controlled via EV +/- compensation. I need a lens profile to correct for vignetting to get even skies in panorama (which turn out stunningly otherwise). There is no profile for the Nokia 808 PureView I am aware of and I'd like to produce one.
Is the Adobe profile creator able to correct for varying exposure using EXIF or overlapping parts of the chart or background?
Or would the Adobe profile creator ignore EXIF if I use studio flash to enforce a constant lightning situation, even if shutter speed would vary (aperture is constant and ISO can be set constant, just not the shutter speed)?
Or did Adobe produce a profile internally they can share?
Thanks.

If you read the first post, this is the camera-app of a 41MP Nokia Pureview 808 camera-phone, so maybe someone could write a new camera app but the phone is Symbian OS which is dead, making that unlikely.
http://www.digitaltrends.com/mobile/the-skeptics-guide-to-nokias-808-pureview-five-reasons -41-megapixels-are-not-a-gimmick/
http://www.digitaltrends.com/mobile/the-nokia-lumia-820-and-lumia-920-too-little-too-late/
It would probably be easier for Adobe to rewrite the LPC to allow vignetting to be computed from a single shot of a blank wall without a target in the shot, than to have someone rewrite a camera app that allows manual exposure.
Another idea about how to get the phone to keep a constant exposure would be to experiment with putting darker and lighter objects in the field-of-view away from the target area to make the camera metering adjust things so it’s exposure is the same from one shot to the next. This would take some doing but should work, unless the LPC uses the part of the frame that doesn’t contain the checkboard target in its computations.
You’re basically varying the scene around the target so the camera takes the same exposure of the target each time.

ACR won't automatically identify Lens Profile Correction even though lens can be manually selected from drop-down

One of my most-used lenses is the new Canon EF 16-35L f/4.0
It does need lens profile correction; but Adobe Camera Raw isn't automatically loading it, as it does with all my other L lenses.
I can manually pick the lens from the list, so the profile has definitely been loaded, but manual selection takes time, and time is bad for workflow.

If that lens profile is indeed the proper one for your lens, rather than something being slightly different and why ACR isn’t selecting it, then the situation is easy to fix:
When you have a raw photo open that was taken with that lens, then in the Lens Corrections / Profile tab, first choose the proper lens profile, then under Setup, choose Save New Lens Profile Defaults. That should tell ACR you want it to choose that profile whenever it sees the lens the current raw file was taken with.
For this to work your CR defaults for photos opened with that camera need the Lens Corrections / Setup default set to Default and not Auto. Auto will skip the manually-defined defaults and Default won’t.
To set the Camera Raw defaults open a new raw photo that doesn’t have any adjustments, set the Lens / Setup to Default (rather than Custom or Auto) and choose Save New Camera Raw Defaults from the menu that appears after clicking on the small icon at the right of the Lens Corrections title bar.

Lens Profiles for Manual Lenses?

I'm just starting to play w/ LR3 and the Lens Profile Creator. Is there is way to create profiles for manual lenses that have no EXIF data captured? I've been shooting with various M42 screw mount and Pentax-A lenses with a K20D.

Please check out this thread http://forums.adobe.com/thread/630329?tstart=60.

Lens Profile Data

Lens Profile Data :
Biogon_T_2.8_21_ZM ;
Biogon_T_2.8_25_ZM ;
Biogon_T_2.8_25_ZM ;
Biogon_T_2_35_ZM ;
CBiogon_T_2.8_35_ZM ;
CSonnar_1.5_50_ZM ;
CZ_Distagon_T_2_8_15_ZM ;
LEICA_APO-SUMMICRON-M_50_mm_f2_ASPH ;
Planar_T_2_50_ZM ;
Sonnar_T_2_85_ZM ;
Tele-Tessar_T_4_85_ZM ;
Tri-Elmar-M_16-18-21_mm_ASPH ;
Tri-Elmar-M_28-35-50_mm_ASPH .
By sending this e-mail containing the attached lens profile data to Adobe, you grant Adobe a nonexclusive, worldwide, royalty-free and fully paid license to use, modify, reproduce, publicly perform and display, and distribute such lens profile data in products and services created by or on behalf of Adobe.
https://docs.google.com/open?id=0B6oTZqWrSBVCdnNLQmYwLXdFbkk

Hi Simon,
I don't think we're on the same page here... I'm asking about the creation of a lens correction profile, not the matching and application of a lens correction profile. I've been using exiftool to supplement necessary EXIF data (e.g. FocalLength, FNumber, FocalLengthin35mmFormat, SubjectDistance, FocalPlaneXResolution, FocalPlaneYResolution) to my images before using them to generate a lens profile in ALPC. Since I've started creating profiles, I've found a couple EXIF data tags that were missing. When I add them to the images and re-generate the lens profile with that same image set, the distortion and vignette parameters change, which proves that they are used by ALPC. I'm starting to wonder how many other ALPC input parameters (EXIF tags) I'm missing. So... Assuming someone has a fully manual system and has to add ALL of the EXIF data that ALPC would need to mathematically calculate accurate distortion and vignette models, what EXIF data would have to be added?
Thanks!
- Jason

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?

After upgrade to lightroom 4.3, my canon 7D is not showing up in lens profile correction

I think this happened after upgrading to lightroom 4.2, but I am not sure as I haven't used Lens profile correction in some time.
When I enable the "Enable profile corrections" checkbox in "lens corrections" The Make and model of the lens is recognized, but the profile field has only 2 optoins, "canon EOS 1D MK III" and "Adobe". It does not have any other options including the EOS 7D that I use. Tried uninstalling and installing again, that didn't help.
I found in the forum that for Win 7, lens profile is supposed to be stored in "C:\ProgramData\Adobe\CameraRaw\LensProfiles\1.0", in my case the LensProfiles directory does not exist. There is a CameraProfiles directory(C:\ProgramData\Adobe\CameraRaw\CameraProfiles).
How do I solve this?

There is nothing wrong with your lens profiles.
The issue is that you are adjusting a JPG not a raw file. When adjusting raw files the camera model is not listed with the profile because it doesn’t matter and all of them say Adobe as their source for Canon cameras at least, but when adjusting JPGs the camera may have done certain adjustments internally so it does matter and is why you see the wrong lens-distortion occurring when choosing the 5D Mark III profile with your 7D JPGs.
For the record, I have profiles in both the locations mentioned: under Program Files\...\CameraRaw and under ProgramData\...\Lightroom 4.x. This makes sense because I have both Photoshop CS6 and Lightroom installed. The ones under Lightroom are all dated 12/2012 while the ones under Camera Raw are mostly dated 2/2012 with some from 11/2012 and other dates. The profiles are probably the same, but the Camera Raw ones retain the date of the original profile creation whereas the Lightroom ones all get updated to the same date. Lens profiles can also be installed with the DNG Converter, although I'm not sure which of the two locations those install to.

Erratic behaviour of Manual Lens Correction in Develop Module

64 bit Windows 7
Sometimes - not always - using the manual lens correction, with Constrain Crop activated, leads to the image jumping around very quickly and erractically and it being impossible to achieve fine control using the mouse: tiny movements of the slider by dragging with the mouse result in large jerky movements of the image. I have only used this for correcting converging verticals and cannot comment on the other adjustments.
Moreover, on a subsequent crop when this has happened, it may be impossible to crop as you would like using the crop tool - the top edge of the image jumps above the intended crop outline. The only way to get the crop you want when this happens is to adjust each edge individually, rather than by dragging the corner.
Apologies if I have not explained this well. In short, it seems to be a bug whereby proper mouse control of the lens correction is lost. I often correct converging verticals in buildings and have never seem the same behaviour in version 3. I cannot always replicate it in version 4, but it happens a lot.
Hope this feedback helps. I cannot see that it has been reported elsewhere in this forum.

Hmmm, this is going to be tricky. I just tried to replicate it on two photos on which I know I had the problem, by going back to the original import setting, but both behaved fine this time! Both, as it happens, were portait format, having been rotated 90 degrees counter-clockwise from the original. I cannot recall, I am afraid, whether or not other ones with which I had an issue had been rotated first. I will try to replicate and keep more detailed notes. In at least these two instances, I had not applied a lens correction profile first. The vertical transformation slider would be set to somewhere between -25 to -35.
Having played about with this for a while now without full replication, I have one idea which may or may not be correct. When I reset the Develop settings and started on the Lens Corrections first, absolutely nothing untoward happened. Now I have gone back and done a number of other adjustments first (as I would often do, before correcting the perspective). In this case, the vertical adjustment slider seems more sensitive to small mouse movements - definitely discernible, but not nearly as bad as the examples I have seen previously when I was not looking for them, nor is there yet any sign of the cropping problem. Maybe the effect becomes more pronounced as the number of edits accumulates before applying the manual Lens Corrections. If this is correct, I do not know whther the effect is cumulative across all edits to all images (as if memory is not being released - but that should not be a problem, since I have 12GB of RAM and nothing else running) or whether it is a per image phenomenon, since I have only recently re-opened Lightroom. You will know better than I whether this is a possiblity, but it is just a thought as I play with this without so far being able fully to replicate the issue. I have some work to do on a number of images and if I get time, I will come back to these images to see if the problem manifests itself more clearly after a larger number of edits across multiple images in a single session without closing Lightroom.
I am very sorry this is so vague and quite speculative. I hope I will be able to give you more accurate feedback later.

Should I bother with the Adobe Lens Profile Creator?

I am concentrating mostly on architectural photography these days and I need a pep talk about the "Adobe Lens Profile Creator". The process seems laborious and error prone - in other words it could end up being a waste of time and money (for the printing of the calibration charts). Has anyone used it to good effect? And with what lenses?
I do the bulk of my work with the 24mm PC-E Nikkor f/3.5 lens and I also use two older lenses - the 28mm PC Nikkor f/3.5 and (my favorite) the 15mm Nikkor f/3.5. All three lenses suffer from a small amount of barrel distortion and chromatic aberration so some correction is usually needed.
I have two specific reservations about the lens profiling process -
1. It came out with Photoshop CS5. Since then the manual controls have increased in sophistication. Can't I get pretty much the same result using the manual adjustments?
2. In my drop-down menu in Adobe Camera Raw CC there are eighty-one lenses listed - but not the three I am using! This is crazy and reflects badly on the people who designed the whole process. Who cares about perspective correction in a 600mm lens?
Anyway, I would appreciate a reply from anyone who has gone through the profiling process. Thanks.
Kevin from Cambridge, Massachusetts

German Jack ha scritto:
create an jpg/tif – profile
create a copy from the lcp
rename this copy with “ – RAW”
open this lcp with an editor
search any “False” and rename it to “True”
save it and you have a perfect raw - lensprofile
Ok, but what does it mean rename and correct the content of the lcp file?
It remains a profile created from jpg source, CameraRaw could consider it like a raw lens profile but it has no more value than a jpg profile, I believe...
Anyway, for whatelse it could be useful your suggestion to modify lcp file?
Thank you for your attention

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

Lens Profile Downloader Feedback

I'm curious to know what people think about Adobe's Lens Profile Downloader. Are people using it? What do you think of it? Are people even aware of it?
I think it has great potential. Adobe's been trying to play catch-up after releasing the Profiler (profiles are time-consuming to make, and there was no clear or easy way to request profiles from Adobe or the larger community).
However, it definitely feels a little half-baked. The need for selecting a profile based on the camera model is was built with is slim (if I am a D300 owner, I am equally interested in profiles created with the D90 or D300s, as well as the D7000 and so on). More importantly, there's no field for LENS MAKE. Hello? This means that if Nikon/Canon/Sony, Sigma, Tokina, and Tamron all decide to make a 12-24mm f/4 lens, there's no easy way to figure out which one the listed profile is actually for. More oddities: Apple listed under Camera Make? And a random half of the brands' names in full uppercase?
Here's the info we need when selecting a lens profile for RAW conversion:
Camera Make
Lens Make
Lens Model
Crop Factor
RAW or JPEG (do people use lens profiles for JPEG correction?)
Camera Model (only necessary for JPEGs or if crop factor is unknown)
Profile Creator
Profile Creation Date
User Rating & Comments
Cheers,
Cory
coryschoolland.com

The reason there is no selection for Lens Make is that, until very recently, it was not a standard EXIF field. Even with EXIF 2.3, manufacturers are generally not filling in the field. So there's nothing to search for, unfortunately.
Apple is listed because of the iPhone models.

Missing Canon lens profile into lightroom

Hi Guys
I have LR4.1 and I just realized that I am missing the one for my 100-400 f4,5/5,6
any idea how can I get it ?
Many thanks
have a super day, Thierry

It is possible to save a duplicate of the lens profile file, and "kludge" it from Raw to non-Raw using a text editor. This generally works well enough; much better than manual corrections alone - provided that the camera is not also applying lens correction, and so confusing matters.

Decision-making process EXIF = correct lens profile

I created a lens profile for my new camera Sony SLT-A77 with lens SAL-1680Z.
I use ACR 6.6 with activated feature "Enable Lens Profile Corrections" and Setup = Auto.
My new profile is found automatically because of EXIF information in the DNG file
and matching tags in the lens profile file.
EXIF:Make = stCamera:Make = "SONY"
EXIF:Model = stCamera:Model = "SLT-A77V"
EXIF:Model = stCamera:CameraPrettyName = "SLT-A77V"
EXIF:LensModel = stCamera:LensPrettyName = "DT 16-80mm F3.5-4.5 ZA"
But my problems start with the second lens. This is Tamron SP 70-300mm.
There is a lens profile provided by ACR 6.5: "SONY (TAMRON SP 70-300mm F4-5.6 Di USD A005S) - RAW.lcp"
But the tags in this file aren´t matching the EXIF in my DNG files.
So I tried to edit the tags like in my own lens profile.
EXIF:Make = stCamera:Make = "SONY"
EXIF:Model = stCamera:Model = "SLT-A77V"
EXIF:Model = stCamera:CameraPrettyName = "SLT-A77V"
EXIF:LensModel = stCamera:LensPrettyName = "TAMRON SP 70-300mm F4-5.6 Di USD A005S"
But in ACR6.5 this profile isn´t found automatically. I have to choose manually
in the Lens Profle menu the Make selector. But I have to choose "Tamron".
I can´t understand this behavior because the tag is stCamera:Make="SONY" and
there is no tag with "Tamron" in the profile.
I deleted all other lens profiles on the computer to exclude problems with another lens profile.
In the document "Adobe Camera Model V1.0" on page 11 I found the required EXIF tags,
but I suspect the mechanism ACR choose a lens profile is different.
Ingo

There is also a LensID field in xmp:aux that would affect the lens matching. Bring your photos in PS/Bridge, show the FileInfo dialog, go to the Advanced panel, you can tweak the metadata in the lens profile to match the same values shown in the FileInfo dialog.
-Simon

Manual lens profile creation?

Similar Messages

Maybe you are looking for