Just placed my order.

pah, I've already had my key for a day!

@kindergip

I didn't realise it was a competition.

I couldn't find WarpView 1.01 in Download section,
only 1.0?

Thanks

Regards,
Kotler

WarpView 1.01 is available for download on OS4Depot.

_________________
Read aMiGa=PoWeR !
--------
Go and subscribe !

Sorry, forgot to update the version text on the webpage. But the Download section on the webpage links to the OS4depot.net download anyway, so it'll get you 1.01

Nice to see new version of warpwiew,
for shure I register it in the near future.

Now some suggestion for the exif data:
ISO speed doesn't work for exif data written by ExifTool
(if you need some examples let me know)

it woul'd be nice to have the 35mm equivalence on the focal length

Exposure and metering mode can be usefull informations.

@pvanni

Please send me a sample via E-Mail.

I have very big TIFF, PNG and JPEG images I cannot display on my system (2GB). Is your software able to display part only of an image to circumvent memory problem?

Bye,
TMTisFree

_________________
The engineering approach to our non-problems: "build a better washer".
The scientific approach to our non-problems: "find a new energy source".
The environmentalist approach to our non-problems: "stop washing your shirts".

Order placed.

Just had a eerie moment with Warpview, I had selected a directory of Jpegs to test with and up came a picture of Stonehenge, whilst remembering a pleasant visit that day, the hairs on the back of my neck started to raise as I realised that one by one the other visitors in the picture were fading then disappearing completely until there was just the Henge left.... spooky!

That's when I remembered, I'd cleaned the other people off the image to use it as a workbench backdrop and what I was seeing was a slideshow of the interim saves.

It's a credit to Warpview that it all happened so smoothly, with the crossfade effect just removing the people as of course the main image of the Henge had'nt changed.

Regards Richard.

@COBRA,
I just sent you an example, if you need more examples or more infos
let me know

@TMTisFree

Huh? No image viewer I know of does that. Besides memory should be no problem now that we have a pager. On the other hand, even an image with a crazy resolution like 16384x16384 pixels in 24-bit will fit into 768MB of RAM, just how big are the images you're trying to view???

Quote:

Huh? No image viewer I know of does that.

I have a PC CLI program that can intelligently handle (convert) pictures in the GB size range with very little memory. I don't know for viewing.

Quote:

Besides memory should be no problem now that we have a pager. On the other hand, even an image with a crazy resolution like 16384x16384 pixels in 24-bit will fit into 768MB of RAM, just how big are the images you're trying to view???

I have some JPEG over 50MB that throw an 'insufficient memory' message and do not display at all.
16384x16384 is somewhat middle range for me, the biggest resolution I have is 86400x86400 (does not display on my 4GB wintel box either). I had to build a special image web server for viewing them on the web with a special TIFF format.

Thanks for replying.

Bye,
TMTisFree

_________________
The engineering approach to our non-problems: "build a better washer".
The scientific approach to our non-problems: "find a new energy source".
The environmentalist approach to our non-problems: "stop washing your shirts".

@TMTisFree

Quote:

16384x16384 is somewhat middle range for me, the biggest resolution I have is 86400x86400 (does not display on my 4GB wintel box either).

May I ask what generates images that large, and why??

_________________
- Don't get fooled by my avatar, I'm not like that (anymore, mostly... maybe only sometimes)
> Amiga Classic and OS4 developer for OnyxSoft.

@TMTisFree

If it's a JPEG file, because I use an internal JPEG loader, in theory it would be possible to do a "scale-as-you-load" kind of thing, IIRC Visage used to do that. Not sure how that should work though with a program like WarpView, e.g. in case the program finds there's not enough RAM available to load the image, then in what size it should load it. But in any case it would have to inform the user that there's not enough memory to load the image in full size and that it would have to load it downscaled, and in that case you would not be able to examine the image in its full resolution, e.g. you could zoom in, but you will not be able to see the image in full detail.

By the way did you try with a fairly large (e.g. 2GB or so) SWAP partition?

I don't know if it's possible and the effort to do that,
but maybe it's possible to render only the visible part
of the image, this way it's even possible to view it
at 100% or higher magnification

@pvanni

It's not about rendering only the visible part, WarpView already does it that way. But images are compressed, and have to be decompressed first. Most types of compression only allows sequential decompression, so if you don't have enough RAM to store the decompressed image, then you have to decompress the whole image. In case of libjpeg, you can make it decompress line-by-line, so that in theory, if you have for example an image with 50000x50000 pixels resolution, but you have only enough RAM for a 25000x25000 image, you can make libjpeg decode 1 line of the image, then you can copy every second pixel of that to your allocated image buffer, and you could throw away every second line which libjpeg decodes for you. The end result would the 50000x50000 pixel image loaded directly as half size 25000x25000. Then you can work with this image as if it was a 25000x25000 pixel image, but you won't be able to access the additional detail which you threw away during loading.

Another thing you could do is to only partially decode the image, e.g. you'd throw away information during the load process to give the effect of cropping the image, but again you would not be able to access the thrown away parts, for that you would have to decode the image again, and this time throw away a different part of the image.

@Deniil

Sorry, no Britney, just NASA.
See here to display the image from the web server I setup. There are other pictures as well. Btw the picture from the link is a pyramidal TIFF with a resolution of 86400x43200 (not 86400x86400 as I wrote) converted from a raw file of 1.2GB.

Bye,
TMTisFree

Last edited by TMTisFree on 08-Jan-2009 at 07:42 PM.

_________________
The engineering approach to our non-problems: "build a better washer".
The scientific approach to our non-problems: "find a new energy source".
The environmentalist approach to our non-problems: "stop washing your shirts".

@COBRA

Yes the one I tested is a JPEG file. Are you interested in testing with it? If yes send me an ftp link or whatever I can upload 59MB to.

I have no SWAP partition because as far I understood it, SWAP is not usefull with 2GB of memory as the system cannot handle more. But I'm possibly wrong here.

As I have already converted most of my bigger files to pyramidal TIFF (to be able to see them on the web), I will first check if I find a suitable datatype for this format.

Bye,
TMTisFree

_________________
The engineering approach to our non-problems: "build a better washer".
The scientific approach to our non-problems: "find a new energy source".
The environmentalist approach to our non-problems: "stop washing your shirts".

@TMTisFree

I have only 256MB or RAM on my uA1 so even something like this image, which is 16384x8192 is enough to simulate the problem of not having enough RAM to load an image, and as I found out, there is not even an "out of memory" error shown in this case, so I will definitely be looking into this situation.