VanGog wrote:So it cannot work faster? Ain't it the same like you would say "IM can't work faster because it is image processor?" I'm just saying that ain't logical to pass too much information then it is necessary. I believe there is alway way to improve programs. Even I don't know language in which IM works, I have close to programming.
I was talking about making txt: format do filtering. IM is an image processor and not a text processor.
IM reads all input images into memory before processing when using convert. Mogrify will process each image separately, but has more limited functionality.
IM was designed for quality and flexibility and not necessarily designed to have the most optimized speed, though it does allow multithreading.
IM is an open source system, so you are free to submit any software changes you would like.
Any speed issues with speed should be taken up with the IM developers and be specific about what function is slow and give an example with timing.
There may be other ways to use IM that make what you want to do faster. I don't know much about this, but you might be able to stream the images so that they read one line at a time and process that. Also you might get faster results using one of the APIs and adding your own special processing. Others may be able to suggest other ways to help you speed up your command.
