Search found 4 matches
- 2018-10-06T08:55:57-07:00
- Forum: Bugs
- Topic: suggestion: improved error message compared to "not authorized"
- Replies: 1
- Views: 7691
suggestion: improved error message compared to "not authorized"
I just spent a very long time tracking down the source of the error message in my web application: convert: not authorized `upload.pdf' @ error/constitute.c/ReadImage/412. This is because I assumed "not authorized" meant something to do with file permissions, directory permissions, apache's systemd ...
- 2011-03-28T10:32:14-07:00
- Forum: Bugs
- Topic: 32-bit TIFF vs 16-bit defaultQuantum: silently corrupts data
- Replies: 4
- Views: 10600
Re: 32-bit TIFF vs 16-bit defaultQuantum: silently corrupts
Version: ImageMagick 6.6.8-10 2011-03-27 Q16 http://www.imagemagick.org
Oops - didn't see that! I was looking for it in the features list. Thanks for tip.
Oops - didn't see that! I was looking for it in the features list. Thanks for tip.
- 2011-03-28T03:27:57-07:00
- Forum: Bugs
- Topic: 32-bit TIFF vs 16-bit defaultQuantum: silently corrupts data
- Replies: 4
- Views: 10600
Re: 32-bit TIFF vs 16-bit defaultQuantum: silently corrupts
see http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=17839#p67735, which I believe works with Q16 IM compiles. Thanks - but this doesn't work. I actually need the full precision of 32-bit integers. Anyway, I've resolved this by rebuilding IM with 32-bit quantum. However I still ...
- 2011-03-16T13:13:14-07:00
- Forum: Bugs
- Topic: 32-bit TIFF vs 16-bit defaultQuantum: silently corrupts data
- Replies: 4
- Views: 10600
32-bit TIFF vs 16-bit defaultQuantum: silently corrupts data
When looking at a 32-bit greyscale TIFF (for example, to dump pixels out as integers, using 'stream'), ImageMagick silently "corrupts" the data, converting, for example., a TIFF pixel whose real value is 0xffeeddcc into a reported value of 0xffeeffee. This turns out to be because the default quantum ...