I am trying to create a dynamic profile rule which will match the Nikon NIKKOR Z 24-200mm lens, because RT 5.9 does not automatically select it in Profiled Lens Correction. Nothing that I enter into the lens field of the dynamic profile rule works. I have tried
NIKKOR Z 24-200
re:NIKKOR
re:.*NIKKOR.*
re:*NIKKOR*
and many other incantations.
I am running the 5.9 AppImage on Ubuntu 22.04. Attached is a sample NEF file.
Per exiftool and the RT 5.9 meta tab your Lens Model and Lens ID tags are both “NIKKOR Z 24-200mm f/4-6.3 VR” (no quotes).
I’m not sure if you can enter wildcards, though (haven’t read RawPedia on that lately). I had to put my two dynamic rules at the bottom to get them to work in all cases. Try NIKKOR Z 24-200mm f/4-6.3 VR,
I just tried that value again, just to be sure. No dice. And it doesn’t matter where I put the rule in the list. My rules based on camera model work just fine (“NIKON Z 5”) but I can’t get the lens rule to fire.
I ran into the same issue with other Nikkor Z-mount lenses and had to create a bit of a workaround to fix this.
You can’t solve this by trying to create just a dynamic rule, you need to create a dedicated profile too that will be used in combination with the dynamic rule.
Load a RAW that uses the lens you want to assign,
Manually set the correct camera and lens in the profiled lens correction module,
Create a profile from this module only (ctrl-click on save current profile to select appropriate part) using a unique, descriptive name,
With the RAW still loaded activate quick info (shortcut: i),
With the RAW still open go to the Dynamic Profile Rules and select New,
Set processing profile to use the profile created earlier,
Set Camera to the exact name shown in the quick info box,
Set Lens to the name shown in the quick info box !! Not the actual name of the lens!,
Press OK and restart RawTherapee.
That does the trick on my side of things.
I also have this issues, wrong lenses being picked up by RT, using F-mount lenses on Z bodies and used the same way of solving that as well (issue 6291).
Hopefully this issue will be fixed once the exiv2 PR is implemented. Do keep an eye out for that one, you need to remove the created rules/profiles once all is well again.