Page 1 of 1
1.4.2 - batch convert - Border's Shadow incorrect size
Posted: Thu Feb 09, 2023 5:45 pm
by user0
XnViewMP 1.4.2 64bits
Windows11 64bit (22H2), display resolution 3840x2160, win scaling 150%
Batch convert
Border's Shadow effect has incorrect size on test file
Re: 1.4.2 - batch convert - Border's Shadow incorrect size
Posted: Fri Feb 10, 2023 8:13 am
by ckit
Confirmed.
Re: 1.4.2 - batch convert - Border's Shadow incorrect size
Posted: Fri Feb 10, 2023 7:15 pm
by winnylinny
It appears that certain types of PNG mess up this effect?
Here's what resulted on my tests:
Works
Using random PNGs, WEBPs, and JPEGs in my personal library
Broken
Using your sample PNG image
Broken
Resaving your sample PNG image as a new PNG image
Works
Saving your sample PNG image as a WEBP or JPEG image
Works
Using the converted WEBP/JPEG image and converting it back into a PNG image
It's really weird. I couldn't figure out if there's any metadata or property of the original PNG that breaks this effect?
Re: 1.4.2 - batch convert - Border's Shadow incorrect size
Posted: Fri Feb 10, 2023 11:04 pm
by winnylinny
@user0, I think I figured it out.
After some further testing, I narrowed it down to 32-bit PNGs
The effect works fine with 24-bit PNGs.
The bug occurs if it is a 32-bit PNG.
Perhaps this effect has an issue with the extra 8-bit "transparency" (alpha) channel.
Re: 1.4.2 - batch convert - Border's Shadow incorrect size
Posted: Sat Feb 11, 2023 5:58 am
by user0
thanks for digging it up
Re: 1.4.2 - batch convert - Border's Shadow incorrect size
Posted: Sun Feb 12, 2023 2:44 pm
by xnview
See
issue for current status and some details.
Re: 1.4.2 - batch convert - Border's Shadow incorrect size
Posted: Sun Feb 12, 2023 3:08 pm
by winnylinny
Awesome, Peirre!
Re: 1.4.2 - batch convert - Border's Shadow incorrect size
Posted: Mon Feb 27, 2023 9:56 am
by xnview
This problem is supposed to be fixed in
XnView MP 1.4.3. Please check and confirm the bug fix here.
Re: 1.4.2 - batch convert - Border's Shadow incorrect size
Posted: Mon Feb 27, 2023 1:56 pm
by user0
fixed in 1.4.3
