Quirk in NEF RAW Processing In V2 Compared with V1.10

[aps2011]

Whilst I can't say it is a bug, there is a difference in the way V2 handles some NEF images compared with V1. The particular case is using a Sigma DX lens on the FTZ adapter on a Nikon Z6ii where the lens is not in the camera's database and the image size (DX) is selected manually. AP V1 identifies the lens and starts with a normal display:

V2 also identifies the lens but the vignetting is incorrect. De-selecting 'Remove Lens Vignette' allows a more normal development to be used.

Any thoughts?

[walt.farrell]

Sorry for the delay in responding.

Did the 2.0.3 update that was released since your initial post resolve this problem, or does it still occur? If it still occurs, do you have a NEF file that demonstrates it that you could share here?

Also, what OS do you use?

[aps2011]

No, regretfully, the update has not altered the situation. I have attached an example NEF. (This was just a test shot so I'm not expecting critical acclaim!)

As I mentioned V1.10 gives a much better rendition.

The platform is:
OS Name    Microsoft Windows 11 Home
Processor    AMD Ryzen 5 PRO 4650G with Radeon Graphics, 3701 Mhz, 6 Core(s), 12 Logical Processor(s)
Installed Physical Memory (RAM)    16.0 GB

Display:
Adapter Type    AMD Radeon Graphics Processor (0x1636), Advanced Micro Devices, Inc. compatible
Adapter Description    AMD Radeon(TM) Graphics
Adapter RAM    512.00 MB (536,870,912 bytes)

 

 

 

DSC_0056.NEF

[Ron P.]

There appears to be a problem with the Auto Detect in the Develop Assistant. If I have it enabled, I get the severe vignette, like the lens is mismatched with the camera body. If I change it to None, the image appears normally, and it still shows as selected in the Lens panel.

I'd say this is a bug, Serif will have a look at this and should refer it to the Developers.

[aps2011]

7 minutes ago, Ron P. said:

There appears to be a problem with the Auto Detect in the Develop Assistant. If I have it enabled, I get the severe vignette, like the lens is mismatched with the camera body. If I change it to None, the image appears normally, and it still shows as selected in the Lens panel.

I'd say this is a bug, Serif will have a look at this and should refer it to the Developers.

Thanks very much for this. I will try some shots with some other (Nikon) DX lenses on the FTZ adapter. RAW from the full frame lenses on the FTZ are fine.

[carl123]

26 minutes ago, Ron P. said:

There appears to be a problem with the Auto Detect in the Develop Assistant. If I have it enabled, I get the severe vignette

With Auto Detect switched on Remove Lens Vignette is set to 100% in the RAW lens tab. Switching this to off or reducing it "cures" the problem

Still something wrong compared to V1 though 

[aps2011]

Just remembered my wife has an old Sigma Nikon DX fit lens. With Auto detect on this came up OK, even at 18mm (effective 27mm with crop factor). However, the lens is not correctly identified. It's just about visible on the screen shot with the metadata showing Sigma 18-200mm F3.5-6.3 DC OS HSM whilst in the profile it is Sigma 18-200mm f/3.5-6.3 DC Macro OS HSM. The two profiles give different results.

DSC_0195.NEF

[Ron P.]

25 minutes ago, carl123 said:

With Auto Detect switched on Remove Lens Vignette is set to 100% in the RAW lens tab. Switching this to off or reducing it "cures" the problem

Still something wrong compared to V1 though 

Yes there is. However if I do the same for one of my RAW images (CR2), I don't get the barrel vignette. Running the scale down or up. That effect seems indicative of using a APS-C lens on a full frame. If so that may be what AP is seeing and acting correctly?

FWIW, the lens I used to test this is a Tokina 11-16mm, more of an Ultra-Wide than the OP's.