Page 1 of 1

0.99.7: DPI change is not correct

Posted: Tue Mar 22, 2022 9:47 am
by Mapaler
0.99.7
win10 64bit

Found in the process of making ID photos.
  • Photo size and DPI are not read correctly
    1647939994894_xnviewmp.png
  • If I calculate DPI 72, the automatically calculated size is completely different from the original image size
    1647941884284_xnviewmp.png
  • Then I crop and change the print size (Use the automatically calculated DPI)
    1647941997438_xnviewmp.png
  • Got the wrong DPI and print size
    1647942108388_xnviewmp.png
  • If I specify DPI and print size, the automatically calculated pixel dimensions of the resampled image are also incorrect
    1647942507028_xnviewmp.png
    1647942507028_xnviewmp.png (13.13 KiB) Viewed 12269 times

Re: 0.99.7: DPI change is not correct

Posted: Thu Mar 24, 2022 8:06 am
by xnview
not easy to understand the problem, could you send me the sample file?

Re: 0.99.7: DPI change is not correct

Posted: Thu Mar 24, 2022 8:54 am
by Mapaler
The first problem, when resized, can not automatically read the size and DPI
1648110510210_xnviewmp.png
The Second
I've cropped it to the ID pic ratio 7:9
1648111595622_xnviewmp.png
Change to the required print size 35mm x 45mm. Uncheck resample, and only change Width, The Resolution will then be calculated automatically.
1648111420903_xnviewmp.png
1648111420903_xnviewmp.png (17.19 KiB) Viewed 12230 times
Clicking back on it found that it was different from my previous set number.
1648111475825_xnviewmp.png

Re: 0.99.7: DPI change is not correct

Posted: Thu Mar 24, 2022 9:54 am
by xnview
Mapaler wrote: Thu Mar 24, 2022 8:54 am The first problem, when resized, can not automatically read the size and DPI
If 'Load default values' is not checked, previous one are used
Change to the required print size 35mm x 45mm. Uncheck resample, and only change Width, The Resolution will then be calculated automatically.
:bugconfirmed: Thanks to your detailed description I can reproduce the problem.

Re: 0.99.7: DPI change is not correct

Posted: Mon Mar 28, 2022 10:23 am
by xnview
This problem is supposed to be fixed in XnView MP 1.00 beta. Please check and confirm the bug fix here.