search

AzWhaleLab / AragoJ

Official repo for AragoJ releases and issue tracking.
Apache License 2.0
8 stars 3 forks source link

Very large images do not open #35

Open ruiprieto opened 5 years ago

ruiprieto commented 5 years ago

Very large images (>10 Mpixel) load in AragoJ but then are not presented in the working panel. Even larger images (>20 Mpixel) will not load at all. Other, smaller images loaded in the same session will behave normally.

Tested in two different 64-bit machines (W10 pro) with the same result.

Does not seem to be a problem with memory size, but with dimensions.

Image 0 (Loaded and displayed normally; tested jpg and png versions) 2.2 MB (14 MB png) 5400X2700 pix created by NASA visible space

Image 1 (jpg; loaded, but did not display) ~41 MB 11458X10402 pix created with pix4D

Image 2 (jpg; loaded, but did not display) ~26 MB 21600X10800 pix created by NASA visible space

Image 3 (jpg & png; did not load) ~38 MB (108 MB png) 21600X21600 pix created by NASA visible space

franciscoaleixo commented 4 years ago

In 0.6 this is partially solved, this means that memory isn't an issue anymore. But it still doesn't load large images, and this is due to tiling issues (seems like depending on the hardware it can support from 4096x4096 to 16384x16384). For this to work independently of the software a tiling algorithm needs to be implemented. I'll work on this on the next release.

ruiprieto commented 4 years ago

Just tested with several jpg images; that is probably the root of the problem. It DOES load large images, but only some. For example, it is loading some jpgs as large as 15MB, but not other jpgs as small as 5MB.

franciscoaleixo commented 4 years ago

Try to compare the image resolution. The image file size doesn't really matter, when you have an image file, the image might get compressed (dependending on the format). But when you open it in the program, it has to uncompress the pixel values individually, so a very small compressed image file might be enormous when uncompressed.

Also because the problem is texture sizes and not memory, the only thing that matters is just the resolution.