File :-(, x, )
Anonymous
Anyone know a program that can handle extremely high-res images?
>> Anonymous
hey, open ttd :)

i think Photoshop has no Problems with high-res images.
>> Anonymous
Any half decent image editor can, as long as you have enough RAM (since images have to be loaded into memory as raw pixels, a fair estimate for RAM usage is the size of your image in bmp format.).
>> Shanyy !M4zajQtMXI
>>163283
Yes, when you have enough memory. XD~
>> Anonymous
Also Transport Tycoon rocks bigtime.

Depending on what you need to do, I'd recommend some lightweight, older app, like JASC Paint Shop Pro 7.4. It's superb for simple things and uses very low RAM compared to todays editors.
>> Anonymous
Transport Tycoon is win!
>> Anonymous
     File :-(, x)
finally got an image down to a reasonable size
>> Anonymous
>>163294
OK some thing's wrong here it works fine on my computer
>> Anonymous
>>163294
I don't see anything
>> Anonymous
>>163294
holy motherfucking shit

/r/ full size ver of that
>> Anonymous
I have this 200mb space image that can be loaded into photoshop, after some wating..
>> Anonymous
>>163294
ok finally got a working version of this online
http://image.bayimg.com/ka/bo/ia/ab/e.jpg
>> Anonymous
>>163294

What is this thingy? Some kind of sims game? explain!
>> Anonymous
Has anyone already found Waldo?
>> Anonymous
ITT people who don't know what the hell TTDX is.
>> Anonymous
I recently downloaded one of those 1GB+ of MARS from NASA with some 30,000 * 90,000 or something resolution. So are you saying there's no way in hell I can open this image, ever, unless I have 8GB of RAM? What if I increase my swap partition/file, would it work then?
>> Anonymous
photoshop?
>> Anonymous
>>163525
Actually my maths was wrong, that's 69.5GB of memory I need. I'll try some registry hacks in Windows to make myself 70GB's worth of page files later tonight. I'll see how that goes.
>> Anonymous
>>163284
Images don't have to be loaded entirely into RAM; it's possible to write a program that loads only the required parts from disk. Google for "memory-mapped files" for a nice technique.

The image should be uncompressed though to make the pixel bytes independent from each other.
>> Anonymous
>>163525
UNIX et al. are your friends, you can make a swap-partition that's big enough and it should load without problems (albeit slowly).

The best way to handle files this big should be with command line tools.
>> 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.
>> Anonymous
>>163281
perhaps the most depressing city ive ever seen...
>> Anonymous
photoshoop