Open MStraeten opened 1 month ago
In exiv2 0.27.x only the first match was printed. In 0.28.x the Canon detection/dealiasing code was improved, but all matches are printed in the rare case it can not narrow it down.
Unfortunately, there doesn't seem to be anything in the metadata the considers today that makes these two lenses distinguishable.
why does it work with LensModel? If you can’t distinguish LensType but LensModel, why not use the matching attribute to narrow down the matches?
why does it work with LensModel?
LensModel
is an actual string (as confirmed by -pv above), there is no ID number lookup necessary.
Not all Canon bodies used to output LensModel
, and I think LensType
predates it.
Feel free to use LensModel
if you prefer and is suitable for your application and use case.
Describe the bug
while lens model is properly detected, lenstype is not properly set:
To Reproduce
Steps to reproduce the behavior: file to reproduce: 20150718-IMG_7039.CR2
Expected behavior
exiv 0.27.6 properly identified that lens
Desktop (please complete the following information):