I still think PL is using the lensid nr.
George
Mistakenly, PL7 wants me to download the module for the Canon EOS 6D II + Zeiss 50mm f/1.4 ZE combination.
In my testing, I found it imperative to not assign a lens module to a file, otherwise, all bets are off as PL has other ways of âguessingâ the model.
If the lens isnât known, there wonât be a LensID
You should not be attempting to install a module.
If the lens is unknown then there is no lensidnr so pl doesnât read anything.
One can try to write down a known lensidnr.
George
A while ago, DPL had problems with finding the right modules (with a new/changed) method and the fact that some third party lenses use lens IDs that are already taken by some other lens or maker does not make that task easier.
Some of the posts referring to that issue are these:
- DPL 5 stopped processing files with certain body/lens combo
- Incorrect lens identification since 6.5 update
- PL7 takes wrong optical module and refuses correction
As we can see, lens recognition and module selection have come up as issues for a while now. DxO is trying hard to provide reliable automatic recognitionâŠand adding manual override would make us users happy.
1 Like
In fact I didnât download anything and I have to make the corrections âby eyeâ using a square pattern
Well, he can at least try and if it doesnât work well enough, he can delete it.
But what do I know - Iâm not in that metadata business.
I did some test. I deleted all lens tags one by one. I think where PL takes the name from is composite.lensid. Thatâs a composite tag and canât be changed. I donât know how and when that tag is created.
I also moved the image to another directory to be sure it didnât stick with the database.
George
As often Iâve to correct myself again. Changing nikon.lens did change what is shown in PL.
The syntax is exiftool -nikon:lens=â80 200 2.8 2.8â myfile.nef
80 200 2.8 2.8 refers to the minimum focal length, maximum focal length,minimum f-nr and maximum f-nr. 4 Values are required.
I see this is different from what @Joanna wrote.
George
My question is: all software reads the lens data at the same point, why not PL?
I donât know if thatâs so.
What I found is that thereâre 2 tags Nikon.lens and Exif .lensmodel. If both are used then PL reads Exif.lensmodel, if thatâs empty then Nikon.lens is read.
See what happens if you only use Exif.lensmodel.
George
Right. I took the lens off my Nikon D810 and took a shot. That gave me the following tags that mention âlensââŠ
[MakerNotes] Lens Type : MF
[MakerNotes] Lens : 0mm f/0
[MakerNotes] Lens F Stops : 0.00
[MakerNotes] Lens Focus Function Buttons : AF Lock Only
[MakerNotes] Lens Data Version : 0204
[MakerNotes] Lens ID Number : 0
[MakerNotes] Lens F Stops : 0.00
[Composite] Lens ID : Manual Lens No CPU
[Composite] Lens Spec : 0mm f/0 MF
RunningâŠ
exiftool -lensmodel="Carl Zeiss Planar 50 mm f/1,7 T*" _JNA0001.NEF
⊠doesnât change any of those tags, but does add the EXIF group tagâŠ
[EXIF] Lens Model : Carl Zeiss Planar 50 mm f/1,7 T*
This then is readable in PL7âŠ
@Promix , it would be very useful if you could make available a file that you have not yet edited in ExifToolGUI as well as one that you have added this lens to.
We really need to know which tags are being set from ExifToolGUI when you add the lens model.
Of course. Give me some time to prepare them.
Thank you
@Promix ,
How do you edit in ExiftoolGui. I canât.
George
You can enter goal data only in the Workspace panel.
@Promix could you change the thread title to refer to ExifToolGUI, since things seem to work with ExifTool on the command line?
Wow can i do it?
No, there is no edit command!
