Legacy ImageMagick Discussions Archive

Thanks! I actually had notes in my codebase saying not to us -auto-orient, but looks like it was due to a bug that was fixed (viewtopic.php?f=3&t=24749)

That did the trick!

Also, I just looked at the exif data, and found this:
which gave this info:

I've noticed that some images lose rotation information when I use -strip. Is there a way to rotate an image based on it's information, then strip it after?

For example, this causes the image to be the wrong orientation:

Also, I used
when I was installing, perhaps I should be building from source to get the latest, 6.7.7 vs. the latest 6.8.8

I get this DELEGATES bzlib djvu fftw fontconfig freetype jbig jpeg jng jp2 lcms2 lqr lzma openexr pango png rsvg tiff x11 xml wmf zlib The entire output is below if this helps: convert -list configure Path: /usr/lib/x86_64-linux-gnu/ImageMagick-6.7.7/config/configure.xml Name Value ...

After running "convert -list format", I got: JPEG* JPEG rw- Joint Photographic Experts Group JFIF format (80) JPG* JPEG rw- Joint Photographic Experts Group JFIF format (80) Which I'm guessing means 8.0 For your other question: $ convert -version Version: ImageMagick 6.7.7-10 2013-09-10 Q16 http ...

Again, thanks for the help everyone! This has been very helpful. CORRUPT IMAGE Regarding the possibility of the corrupt image. This could be the issue, and if so, I'd like to let everyone know so it's not a mysterious issue for imagemagick and I'll do my best to verify this case. It's possible that ...

Thanks for the replies! I've posted another corrupt image plus the input, as well as the system information requested (except libjpeg version, how can I find this?). Here is another example with input and result: INPUT: http://8b7ba2e22fc2d1253129-be2542a8acdb7986862370633c0fe913.r99.cf1.rackcdn.com ...

I've been running into rare occurrences where an image will have missing pixels and the area is simply gray: https://b0c8025ff93679be66fe-34fbaafa6fc33d006464a39c24d8e053.ssl.cf1.rackcdn.com/1252180a8b2ad03582a7f1640d17fd2a.jpg The commands that I've been running that have caused such results are ...