1.3.1 - viewer - 'vignetting'/'old camera' default values

[user0]

XnViewMP 1.3.1 64bit
Windows10 64bit (21H1), display resolution 3840x2160, win scaling 150%

Viewer mode, Image menu -> Map -> Vignetting and Old camera dialogs
Incorrect values of <Default> preset after some manipulations.

To reproduce:
1. run clean portable XnViewMP

issue A
2. open Vignetting dialog
3. tick 'Add vignetting' checkbox
4. select <Default> preset

Suggestion
Also I do not understand the reason for 'Add vignetting' checkbox.
There shall be color picker to set background color instead (with black color by default).


issue B
2. open Old camera dialog
3. tick 'Sepia' or 'Shadow' checkbox
4. select <Default> preset

Actual behaviour (both dialogs):
Values changes to 0.01

Expected behaviour (both dialogs):
Values shall change to correct default values.

[XnTriq]

Also I do not understand the reason for 'Add vignetting' checkbox.
There shall be color picker to set background color instead (with back color by default).

I support this request!

[xnview]

issue A

See issue for current status and some details.

issue B

See issue for current status and some details.

[xnview]

This problem is supposed to be fixed in XnView MP 1.4.3. Please check and confirm the bug fix here.

[user0]

1.4.3
issue A - fixed
issue B - still remain,
plus new regression - app will crash on some images when 'Apply to image' checkbox is ticked at 'Old camera..' with default settings

test_img_Old_camera_plane_jpg.zip

(94.03 KiB) Downloaded 49 times

[xnview]

issue B - still remain,

I can't reproduce, value is changed to 1.00

plus new regression - app will crash on some images when 'Apply to image' checkbox is ticked at 'Old camera..' with default settings
test_img_Old_camera_plane_jpg.zip

Thanks to your detailed description I can reproduce the problem.

[user0]

issue B - still remain,

I can't reproduce, value is changed to 1.00

my bad, no issue here
probably I run prev version of xnview

[xnview]

This problem is supposed to be fixed in XnView MP 1.4.4. Please check and confirm the bug fix here.

[user0]

fixed