ImageMagick

Hi all, I got a intel atom 330 box with a 1.6ghz dual-core cpu and 4gb of ram. I'm running ubuntu 10.04 64bit linux on it and uses imagemagick from apt-get source. When i use the convert command to convert a bunch of pictures (standard pictures 2816x2112 ...

... Same thing happened last night, but the back button saved me, though not this time. A little more briefly: Multi processing: I didn't mean CPU, I meant the automating command calculating a number of algorithms and then weighting their output into the final output. So the user doesn't have ...

... Even if you use identify instead of convert, ghostscript will still crunch through the entire PDF. If it's a big PDF, you might just find your CPU maxed and memory consumed until you're out of memory (at least on my 6.5.7-8).

... <test_img2> <diff_img3> or: compare -metric PSNR <ref_imge1> <test_img2> <diff_img3> my problem is that sometimes this command is stuck my PC ( cpu =98%) and never end. i try -fuzz switch but with no luck. if images are not equal - it's OK for the application to throw exception or any other ...

... images using ImageMagick. IM uses "convert" to make an animations but sometimes "convert" freezes in a loop and starts using cpu/memory in big amounts until servers stops responding at all. It happends once a week. Maybe twice. I can't still find out the reason why it happends. ...

... if it could run through the loops without holding up on running one script at a time it would render much faster depending on the server spec's (cpu/ram etc...). I have also tried calling the script through exec() with no $return but it still waits until it's finished. Example from one of the ...

... ^ +repage +adjoin ^ x.png Now the time increases to about 1 minute per output file, for a total time of 7 days. (One dual-core CPU is saturated, the other is idle. There is negligible memory use or disk activity.) Am I doing something stupid, or is there a bug in "-set" ...

OK false alarm. I tried the FPX conversion on a more powerful server and my 80MB TIFs completed fine. So, it's something resource (CPU or memory-related). Discussion closed.

... none that have (4 times) as high RAM usage I've had with some other pictures. RAM usage is around 116MB with each of those samples, one of the CPU cores is used completely, but I'm expecting that to be normal. Second command: 42 . If I run into a troublemaker again, think I remember one so ...

... append 8 files: 941 seconds. 80% memory use. Heavy read/write to 4 magick files in %TEMP%. My laptop (4 GB, Windows 7) is also running a massive CPU-intensive job (IM is applying special effects to movie frames), so the append on Q16 might be reasonable on a quiet machine. But this test shows ...

2324 seconds? Yikes. I suggest you find out the load on your CPU, memory and disk. I suspect your memory fills up, so IM has to use the disk. (My calculation shows you may need 1.392 GB out of your 3GB for the total image.) See the architecture document: ...

... forever. I used a very simple command "convert img1.jpg img2.jpg img3.jpg ... img8.jpg +append combined.jpg". Here's my system info: CPU: AMD Athlon 64 3800+ 512KB Mem: 3GB Can anyone help? Is it because of some kind of memory limit in ImageMagick? If so, is there any other image ...

... 5 MB jpg file (here if you want to test it http://www.icona.it/downloads/page_0001.jpg). The file is on a local disk and nothing else is using up cpu on the PC we used for the test. Is there any way to speed up identify -verbose (we need the -verbose option) ? We cannot use -format because we ...

Hi all, I tried to use QuantizeImage to reduce the gif-image's color, and found that as I increase the load (using LoadRunner),the CPU keeps raising until it gets 94%,here is my code below, QuantizeInfo *q_info = AcquireQuantizeInfo( image_info ); unsigned long colors = q_info->number_colors; ...

... This takes screenshot of a fairly small window, uses no compression and stores result in ramfs, all kind of pauses seems to be set to zero. Used CPU time is almost equal zero (as expected), but actual operation takes almost a second (!). This delay seems to be independent of KDE compositing being ...