>> |
Anonymous
Tips:
Older apps may consume less RAM in general use, but advanced algorithms in newer software - however bloated - will (or should, anyway) make them better for any extremely intensive use, such as FUCKING HUEG images.
If the entire image is to be displayed at true resolution, it will need to be loaded in to memory. If this is more than 4GB, you're fucked - that's the maximum addressable space of a 32-bit operating system. Note that if the combined size of RAM+swap is more than 4GB for a 32 bit kernel, you have swap space you will never use. If it's 64 bit, well, you can have fucktons.
Modern software should be able to deal with large images by only processing that portion currently being operated on or viewed, but it will still be a massive load.
Command line tools for image processing are few, but ImageMagick is really all you need; it's the best image editor ever written so long as you don't need to look at the thing while you edit (you always do, though, don't you?). Also, extremely vast options on the order of gcc.
Best free app for large image processing right now is probably Cinepaint over The GIMP; it's used by professional movie studios; it helped with the Lord of the Rings films.
|