Legacy ImageMagick Discussions Archive

When I run a script from the cli using export MAGICK_THREAD_LIMIT=4 and
convert it uses all four of my cpu cores. When I run it through
nginx+uwsgi via a webpage it uses one core and leaves behind a 1.5G
/tmp/magick-* temp file. Does anyone have any ideas?

Ha, thanks to you guys. If it wasn't for the help in this thread I'd still be floundering in my own ignorance. Here is the main part of my script: _colourmap() { unset cj cm nc if [[ ${f##*.} == jpg ]]; then nc=$(identify -format '%k' "$f"[0]) (( $nc > 256 )) && return cj="+dither -colors $nc" nf ...

Is there a way to resize gif's so the file sizes does not become large? Here are two files I'm testing with, 01.gif and 0304.gif. 01.gif GIF 3000x2008 3000x2008+0+0 8-bit sRGB 256c 962KB 0.000u 0:00.000 Lanczos2-ewa-gamma1.6-depth8-complex-cbz-01.png PNG 2390x1600 2392x1602+0+0 8-bit sRGB 2.972MB 0 ...

My test were before I added +repage

I do not have mozjpeg installed

That is very odd that it creates an edge-like result for either JPG or PNG? Perhaps there is an issue with your older IM version or older png and jpg delegates. Can you upgrade? Yes, I get it with either jpg or png. Yep I can upgrade. Thanks a lot for testing. I find catrom with ewa too sharp. I ...

The 8-bit png's are not useable, they are distorted In what way? Can you post one to show us what is happening and the command line you used? Are you running Q16 or Q8 IM? Here are the tests I posted earlier: https://dev.zco.mx/files/convert-depth.zip The command is what Nicolas posted: convert ...

In Steve's message above, he said "For me the favourite was Catrom-rgb-gamma1.3" but I am not sure if that was before testing with RobidouxSharp or not. Steve, have you come to some conclusion? The more complex RobidouxSharp command is slightly better than plain Catrom on the two images I tested. I ...

Steve: Pretty conclusive. ----- This is what I remember. (Anyone: correct me if I'm wrong.) If the input image is 8-bit and you are producing a png, you'll get an 8-bit png. If the input image is 16-bit and you are producing a png, -depth 8 may be worthwhile. I wasn't clear. The test above is using ...

P.S. Steve: I'm pretty sure you can omit the -depth 16 at the beginning. But not the -depth 8 at the end, unless you are producing jpegs, in which case it being there won't hurt. Here is a quick test with a jpg using -depth16, -depth8, no depth outputting to both jpg and png: https://dev.zco.mx ...

Put -depth 8 right before the output file name if you put a -depth 16 near the beginning. This tells IM that what you want from now on (and "from now on" means "for the output file" since it is just before the output file) is 8-bit per channel. Because you are using HDRI Q16, the result, by the ...

Catrom with ewa is too sharp. For me the favourite was Catrom-rgb-gamma1.3

The more complex convert command fixed the ewa+gamma bg problem but the file sizes are quite large. Removing '-depth 16' made no noticeable difference (to me) and the file sizes came in line with output from other tests. At first look, both RobidouxSharp-ewa-gamma1.6-complex-web-04.png and Catrom ...

'-depth 16' did not fix the bg problem when using ewa+gamma1.3 and it doubled the file size: $ stat -c "%s %n" Catrom-rgb-ewa-gamma1.3-depth16-web-04.png ../convert-ewa/Catrom-rgb-ewa-gamma1.3-web-04.png ../convert-ewa/Catrom-rgb-web-04.png ../convert-ewa/Catrom-rgb-gamma1.3-web-04.png orig/04.png ...

I see a much more yellow bg with ewa+gamma1.3

Here are the commands that were run: http://sprunge.us/cJeD

I'll try testing with -depth 16'

Here are my tests with ewa specifically:
https://dev.zcomix.com/files/convert-ewa.zip (158mb)

A good place to look is the bike engine on panel three of 04.png

Tomorrow I'll do testing with the more complex command.