Re: Strange effects when just changing sizes (gmh: message 2 of 20)

On Sun, 17 May 2015, [email protected] wrote:

> Hello,
>
>> If you built it from source code yourself, did you do 'make check' to
>> verify that the test suite passes?
>
> I built from source and got the same result. That's what I did:
>
> Downloaded  GraphicsMagick-1.3.21.tar.gz from
> http://sourceforge.net/projects/graphicsmagick/files/
>
> ./configure --prefix=/opt/gm
> make -j4
> make check  # all checks passed or (a few) skipped

Unfortunately, the test suite does not test the many TIFF compression 
variants.  It only tests without compression and only with tiny 
images.

> LD_LIBRARY_PATH=/opt/gm/lib /opt/gm/bin/gm composite -compress LZW -geometry
> +0+118 -gravity North -resize 2244x3153 -units PixelsPerInch -density 300x300
> source.tif -size 2481x3508 xc:white result_src.tif
>
> Just the same result.
>
> Since you mentioned libtiff, I changed the result to result_src.png -> tadaa,
> that's how it should look... (with the debian package, too)
>
> gm reported the same libtiff-version for bob and for me, didn't it?

Yes, but Debian may have applied patches or special compilation 
options (e.g. for security, or due to some other bug report) which 
broke something in libtiff.  This has definitely happened before.

Definitely try '-compress none' and see if the problem goes away.

Bob
-- 
Bob Friesenhahn
[email protected], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y