After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 495515 - Scale creates black bands in output
Scale creates black bands in output
Status: RESOLVED DUPLICATE of bug 464222
Product: GIMP
Classification: Other
Component: Tools
2.4.x
Other All
: Normal minor
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2007-11-10 08:45 UTC by Javier Kohen
Modified: 2008-10-30 20:04 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Javier Kohen 2007-11-10 08:45:05 UTC
Please describe the problem:
Sometimes when I scale an image with the Image, Scale Image action the result turns up with one horizontal and two vertical bands with a width of one pixel each. If I save the image, the resulting file keeps the bands.

Steps to reproduce:
The source images I'm working with now are in TIFF format with dimensions 1407x2126 and 2900 DPI (that's what the photo lab's scanner gives me). I go to Image, Scale Image and pick the Lanczos3 method to scale that to 1200x794 at 72 DPI.

Actual results:
One black horizontal band appears at pixel offset 397 (output_height * .5) and two vertical ones appear at 300 and 900 (output_width * .25 and * .75, respectively).

Expected results:
No black bands would appear.

Does this happen every time?
No, only occasionally. As a matter of fact, the easiest workaround is to undo the operation and repeat it again with the steps detailed above. Simply going forward in the history after undo does not eliminate the bands.

Other information:
I have never seen this with the 2.2 version series. I think I might have seen this once with the 2.4.0 release candidates and today I saw it two or three times in 7-8 scale operations that I ran.
Comment 1 Sven Neumann 2007-11-10 15:42:37 UTC
Please don't use Lanczos for downscaling. This is a known problem and it has already been reported. 

*** This bug has been marked as a duplicate of 464222 ***