Bug: Scaling error

Ideas for improvements and requests for new features in XnView MP

Moderators: XnTriq, xnview

Post Reply
torxx
Posts: 2
Joined: Thu Dec 20, 2012 12:49 pm

Bug: Scaling error

Post by torxx » Thu Dec 20, 2012 1:08 pm

Hello
Thanks for the new version!

I observe a scaling error in a special case:
My screen resolution is 1920 x 1080
The image is 1800 x 1800 pixels.
If displayed fullscreen with "Fit image to window, large only", i see a horizontal and a vertical black line within the image.

This problem is not new in 0.53, i observed it in 0.51 as well.

Regards,
torxx
Last edited by torxx on Thu Dec 20, 2012 1:55 pm, edited 1 time in total.

torxx
Posts: 2
Joined: Thu Dec 20, 2012 12:49 pm

Re: Bug: Scaling error

Post by torxx » Thu Dec 20, 2012 1:53 pm

Additional info:

I can reproduce the black (= background color) lines on most images: they must be scaled to 48%, 60%, 75% or 96%.

Only the 32 bit Version of XnViewMP seems to be affected.

torxx

Bolthier
Posts: 3
Joined: Thu Mar 14, 2013 11:47 am

Re: Bug: Scaling error

Post by Bolthier » Thu Mar 14, 2013 12:41 pm

I experienced the same bug in the MP x64-version.
Image resolution is 1158 to 1077, scale is 88%.

So far only noticed it with this exact resolution with any format with the below added set of elements.
http://img51.imageshack.us/img51/3402/s ... 141332.png

Gav80K
Posts: 5
Joined: Fri Mar 15, 2013 5:38 pm

Re: Bug: Scaling error

Post by Gav80K » Fri Mar 15, 2013 6:01 pm

I have this problem as well, and it seems that when viewing certain resolutions you can get vertical and/or horizontal black lines:

For example, I created this 1690x2450 blank image:

http://sadpanda.us/images/1469667-HKO7NJO.jpg

When I view it in full screen mode on my 1920x1200 monitor I get a horizontal black line:

http://sadpanda.us/images/1469668-BKTDHPK.png

You can also get vertical lines at some resolutions.

User avatar
XnTriq
Moderator & Librarian
Posts: 5448
Joined: Sun Sep 25, 2005 3:00 am
Location: Ref Desk

Re: Bug: Scaling error

Post by XnTriq » Fri Mar 15, 2013 9:00 pm

This is a known bug.

Post Reply