XnView Software

Hi. I've just upgraded to xnconvert 1.98 (Windows 10, 64 bit) and am seeing the following issue:

If I start with an image (png, gif), say 355 x 459 px.
Apply one "Border Action" to add a single frame of width = 1 pixel.
The resulting output image is 351 x 455 px with no visible border.

Using the old version of XnConvert (1.94) the produced image would have been 357 x 461 px, ie just a simple 1 px added on each side.

Basically, to add a 1 px border as previously, I have to specify a 3 px border in 1.98. This is problematic as I have a number of presets made which would have to be changed.

Is this expected behaviour ..... or am I missing something?

Also, I do not understand what the "Background" color selection inside the "Border" action is for.

Thanks for any replies,

Adding to this, I switched to the next earlier version 1.96 and it seems OK.

right an issue in 1.98

This still seems to be happening in 1.100.1 ..... reverting again!

please send one of your script that worked in 1.94

Hi. I think the following is the script I was using when I noticed the problem; basically resizing to 359 px wide plus adding 2 px border should yield 461 px wide image - but wasn't. I experimented a bit and observed the behavior as I described in my above post. Everything works fine on 1.96 and previous, as far as I know.
Regards,

<?xml version="1.0" encoding="UTF-8"?><XnView_script version="1.0" name="359 Resize and Border">
<Resize mode="2" width="355" height="0" unit="0" ratio="true" orientation="false" enlarge="0" resample="7" gamma_correct="false"/>
<Border frame1_radius="0" frame1_width="2" frame1_color="#00557f" antialias="true"/>
<Output folder="" filename="{Filename}" case="0" startIndex="1" format="GIF">
<Options overwrite="1" orgDate="false" keepMeta="true" keepICC="false" keepFolder="false" keepParentFolder="false" delOrg="false" multipage="false" allPages="false" openExplorer="false" openBrowser="false" clearItems="false"/>
<GIF interlaced="false" hdr87a="false"/>
</Output>
</XnView_script>

Thanks to your detailed description I can reproduce the problem.

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

Hi. I did retry the conversion using XNView MP 1.7.1 as suggested and it worked fine, thanks.

Q. Now that XNView MP has the tools for batch conversions, is XNConvert redundant? Should just be using XNViewMP for everything?

XnView had batch converter for years. Generally, if it could be called stand-alone without main app, XnConvert could become redundant. But I personally keep XnConvert always open, while open XnView only while I work with image.