-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lensName does not return name of lens #2779
Comments
The intention is to return the lens name, which is easy, when lens name is stored as Ascci like in Exif.Canon.LensModel. But many cameras just write an ID, which then needs to be mapped to the name. So when an ID is shown, this means, that the mapping is not yet done. When you provide a link to a sample picture and the name of the lens, I can add this mapping. As mentioned in #2751 and #2750 you can also add the lens ID in your local configuration - as a workaround until a new release with this mapping is available. |
"But many cameras just write an ID, which then needs to be mapped to the name" That is what I would like this function to do, I am writing an app that loads images and displays the EXIF data. I would like a single function I can use to obtain the name of the lens used to capture the image. |
Using easyaccess is the correct way to achieve this goal, because it checks several tags (e.g. from Nikon or Canon). When we get aware of a missing lens and get the needed information, we add this lens in mapping. But as there are always new lenses, we will always have the risk, that a lens is not recognized. Do you have a concrete example? Then I can take care to add the lens. In #2750 I started a discussion, if a slight change in logic of easyaccess could give some improvements. Also in respect to this aspect, it might help, if I can get more details, e.g. the output of |
lensName returns 164 Photoshop lists lens as 70-200mm |
lensName returns 129 Photoshop lists lens as 150-600mm |
lensName returns 191 Photoshop lists lens as 60-600mm |
lensName returns 182 Odd. Photoshop lists lens as 1000mm. I don't think that's right. |
lensName returns 193 Photoshop lists lens as 14-24mm |
lensName returns 138 Photoshop lists lens as 105mm |
lensName returns 233 Photoshop lists lens as 28-300mm |
I had a look at the samples.
|
I am using version 0.28.0. Are the names you are showing coming directly from lensName? If you are using the executable, is it possible it is doing other processing to display the results? Those mappings look correct, but I do not see those strings coming from the lensName function. 191: Sigma 60–600mm F4.5-6.3 DG OS HSM | Sports [EDIT] For 182. If a teleconverter was used, could that account for the data? |
I am using Windows x64. |
I found the issue. I was using toString to get the name from the iterator. That works for everything in easyaccess except lensName This works
This does not.
I am just getting 191 and 193 as id numbers now |
Regarding ID 182: a teleconverter could have impact on the data. But I think, there is no teleconverter with a factor of 1.25, which makes 1000 mm out of 800 mm. If just one of the tags would show 1000 mm, I would take into consideration, that the value was changed manually. But there 3 tags, and one with 1015.9 mm (which deviates a little bit, because that does not store the value itself but a logarithmic value. So I have no reasonable explanation. Regarding 191 and 193 I will add the mapping. |
@DougRogers I think you were right with teleconverter. I found an andvertisement for "Nikon AF-S NIKKOR 800mm 5.6 E FL ED VR inkl. TC800 Konverter", Quote: "This premium lens comes with a special, custom-tuned 1.25x teleconverter that extends the focal length to 1,000mm at an effective speed of f/7 while maintaining superior imaging performance." |
Calling the print function of the iterator correctly reports the lens name |
In easyaccess, calling lensName can return an ID, not the actual lens name. The correct lens name should be returned in this function.
The text was updated successfully, but these errors were encountered: