Read one image backward (reverse pre-cache)

[eque]

Hello,

First of all I have to say this is a really great image tool, with tons
of superior features, which you will hardly find in any other application!
Really great work, thank you!


I have a small feature request:

right now xnview is able to cache pictures while viewing ('read one
image ahead') in only one viewing direction: forward.

this is nice, but xnview lacks the option to pre-cache pictures when you
view them backwards.

so if you start at image200.jpg and go back to image199.jpg, 198, 197,
..., it won't pre-cache the images and the loading of each image takes
alot time.

pre-cache only works in one direction and my suggestion is that it
should work in both directions: while viewing pictures forward and backward.

btw. old ACDSee 3.1 supports this


Many thanks and kindest regards,
-Eque

[xnview]

pre-cache only works in one direction and my suggestion is that it
should work in both directions: while viewing pictures forward and backward.

You have 'cache behind'

[eque]

Thanks for the quick reply!

I have just downloaded the latest version 1.92.1 29/Jan/2008
and I couldn't find this feature in the options or help file, hmm.
Where do I have to look for it? It's not in options->View->misc.

Btw. the download files on the german xnview page are still v1.92..


Cheers!

[xnview]

Thanks for the quick reply!

I have just downloaded the latest version 1.92.1 29/Jan/2008
and I couldn't find this feature in the options or help file, hmm.
Where do I have to look for it? It's not in options->View->misc.

Yes option/View/Misc/Keep current image

[eque]

Yes I tried "Keep current image", but this is not what I am talking about.

This feature only caches one image - the current, nothing else.

Just try yourself to view 10 different 5MByte pictures backwards, from image200, then image199, 198, 197, etc. There is no pre-loading/caching
like there is, when you view them forward.

[xnview]

Yes I tried "Keep current image", but this is not what I am talking about.

This feature only caches one image - the current, nothing else.

Just try yourself to view 10 different 5MByte pictures backwards, from image200, then image199, 198, 197, etc. There is no pre-loading/caching
like there is, when you view them forward.

Oh ok, sorry...

[eque]

Hello again

so do you think this feature will be included in the future?


Regards,
-eque

[Karl02]

Currently there are the following options:
- Read one image ahead
- Keep current image in cache

As I understand it, currently "one image ahead" always means the next image in ascending order according to the current sort order. When moving in descending order, this is the same as the previous image, and the actual next image in descending order will not be decoded in advance.

I would suggest to rename the options as follows:
- Decode next image in advance
- Keep previous image in memory

What is "next" could be automatically detected: If the user moves in ascending order, the next image to decode in advance would be the next in ascending order; if he moves in descending order, the next image to decode in advance would be the next in descending order. If he clicks on an image in the middle of the list, both neighbours could be decoded in advance.

[pic_viewer]

IMHO this is somewhat ridiculous. There should be just one option called 'Preload Caching'. The fact that this functionality is not fully working (means as every normal user would expect), but is only partially implemented, is no reason to come up with three options and a cluttered settings dialog.

[eque]

Hi again,

being back from a 1-month-trip I downloaded the latest XnView
version and noticed, that the pre-cache is still not improved.

I am really sorry to complain, because I love XnView. But
when it comes to 7000 pictures, each 3-5 MByte, browsing
and viewing speed is one of the most important things, really.

It would be very nice, if the pre-caching would be improved
in XnView.

I know its the last thing you would like to hear, but ACDSee 3.1
is simply alot faster browsing through large images - and this
tool is from 2001..


Thanks again, regards
-Eque

[xnview]

I know its the last thing you would like to hear, but ACDSee 3.1
is simply alot faster browsing through large images - and this
tool is from 2001..

But acdsee don't cache more than 1 picture

[eque]

Hi there,

well, I don't know the number of pictures ACDsee (v3.1) is caching
while viewing and I don't mind too much about technical details.

What I know from my experience while viewing thousands of
pictures: XnView is slower than ACDSee v3.1.

Not only it is much slower viewing pictures backwards (as
described in the first post), but it is also slower viewing pictures
forwards (the difference here is however not too big). Just compare
yourself.

I am using a 3.2 GHz PC with 2 GB RAM and a brand-new 500 GB
S-ATA II hard disk.


Cheers,
-eque

[eque]

Hello there,

I was wondering about what happened with my suggestions
many months ago? Is there any chance this will be included
in one of the next releases?

As you can see, I am not alone with this problem (Karl02).
And I believe its a simple thing to fix.. no?

It would make browsing pictures in fullscreen much faster..


greetings,
-eque

[Danny]

And I believe its a simple thing to fix.. no?

Nobody knows but Pierre.

It may work by reversing the image list and always skip forward internally, instead of having a fixed image list and skipping back and forth.

But then again... Nobody knows but Pierre.

[thibaud]

IMHO this is somewhat ridiculous. There should be just one option called 'Preload Caching'. The fact that this functionality is not fully working (means as every normal user would expect), but is only partially implemented, is no reason to come up with three options and a cluttered settings dialog.

I can't agree more with that.