XnView Software

not sure if this has always been there with Xnview or not. Doesn't seem as fast as other apps but DAMN straight it opens faster then other apps great work by the way. Is there away the make the scroll transition from pic to pic smoother ???? I don't want to compare but I just find this useful in the other app I try out and love to see it here in this great app

thanks

XnView 1.82 -

How would you like it to behave? Faster jumping to next picture on mouse wheel?

X.

would like it to be smooth and fluid ..... it is neither

you would need to compare it to another app to get and idea

thanks

I know quite a few and still don't know what are you talking about.

You cannot use your own subjective feelings to describe program behaviour. Definitions of 'smooth' and 'fluid' in relation to image browsers are quite broad I think.

X.

I just made a quick test:
(no Buffer/Cache of images, no EXIF rotation -> we are comparing Loading+Display)

JPEG (3072x2048x24b => 2.53MB)
- ACDSee 5 (no HQ & all HQ)=0.7s
- XnView(no HQ)=0.4s
- XnView (HQ resized)=0.8s

TIFF (2616x3900x48b => 58.4MB)
- ACDSee 5 (no HQ & all HQ) =0.6s
- XnView(no HQ)=0.4s
- XnView (HQ resized)=0.7s

Quite close...

Where XnView is lacking is in the way it displays&buffers images after a key/mouse action: image are not partially shown, they are instead fully loaded or simply skipped (in 1.82RC)... which doesn't provide a feeling of 'smooth' and 'fluid'. This thread makes a suggestion to address this issue.

Olivier

Edit: I modified the HQ/no HQ timings after finding that strange behaviour...
...and I find quite suspect the impact of HQ (bilinear) in XnView... especially when you see that ACDSee does better in HQ just because of that...

From some post I remeber Pierre saying that image IO routines he currently uses don't support "partial" display.
But if someone wants such display or "full display before skipping to next picture", that's OK for me -> Suggestion for next version.

X.

Xyzzy wrote:From some post I remeber Pierre saying that image IO routines he currently uses don't support "partial" display.

To be more accurate: Pierre says that 'displaying image while loading' is not supported by his IO library. But being able to retrieve what has been partially loaded on interruption is different... and might be possible with current library.
It would help a great deal for this (ie: immediate response/display when navigating through images)

Olivier

OliverG is right on the money for what I am talkin about. If you disable the cache the delay between switching from one pic to the next is not there. Xyzzy if you have many pics in a folder like 50 try it for yourself with the mouse scroll... scroll from one pic to the next it will give you a delay in moving to the next pic. I can scroll faster then the apps responce. If you do that same thing in ACDsee (any version) it's transition from one pic to the next there is no delay


thanks for the no cache tip OliverG

seems like removing no EXIF rotation but leaving on cache seems to be inbetween, which is something I can live with I can always disable the cache setting if I need it to be faster

sullysnet wrote:Thanks for the no cache tip OliverG

Well... it wasn't actually a tip, for I did not expect any improvement from disabling Cache... (I used it for comparison purposes only).

You just found a bug: behaviour for wheelmouse with Cache enabled is really chaotic! It is probably related to the interruption+caching mechanism that don't go along very well...

To Reproduce bug:
- Options>View>File list>both Cache=ON (Read ahead/Keep current)
- Go to View and navigate through images with the wheel (give 2 big rotations while still loading current image => you will advance A LOT, and skip many images!). This behaviour is obviously problematic.
- Then try with both Cache=OFF: you will skip less images, but it is still not acceptable.

Olivier

Olivier_G wrote: - Options>View>File list>both Cache=ON (Read ahead/Keep current)
- Go to View and navigate through images with the wheel (give 2 big rotations while still loading current image => you will advance A LOT, and skip many images!). This behaviour is obviously problematic.
- Then try with both Cache=OFF: you will skip less images, but it is still not acceptable.

Yes, a bug. With read ahead cache disable TOO LITTLE images are skipped. EDIT: this happens for really fast rotations, usually there are 1-3 skips too little. Tested on 2.5MB JPEGs, maxed quality, high quality delay on.

Two full mouse scrolls are, depending on mouse, like 10-15 notches. You would expect it would skip just that much images, wouldn't you? One notch- one image, two notches two images, 2 big rotations- many images.
Would you like to have instant image show- wait for the all images to display in sequence?

X.

Xyzzy

Hi L. !

…One notch- one image, two notches two images, 2 big rotations- many images. …

- A bit aside the topic : I never use the mouse-wheel to browse the images because this is not configurable.
- My mice are rather ticklish at wheels, so the images switch too quickly, this is exasperating for me.
- So, I would like be able to set i.e. 2… 3 … n … cogs for one image.

KR
Claude
Clo

sullysnet wrote:OliverG is right on the money for what I am talkin about. If you disable the cache the delay between switching from one pic to the next is not there. Xyzzy if you have many pics in a folder like 50 try it for yourself with the mouse scroll... scroll from one pic to the next it will give you a delay in moving to the next pic. I can scroll faster then the apps responce. If you do that same thing in ACDsee (any version) it's transition from one pic to the next there is no delay

ACDSee 8 (whole SEVEN days of trial, what a generosity) shits itself when trying to skip images with wheel. I scroll wheel 7-8 notches, I get 1-3 image skips. In XnView I get that exact number of skips, and it's FAST! Bravo!

ACDSee fullscreen skipping between images (default settings) is faster ONLY when all image quality settings are ON in XnView AND delaying full quality display is OFF.

So your request seems to be simply faster rendring of images in high quality, right?

EDIT: Does anybody notice difference with browsing when thumbnail cache is turned on/off?

X.

Clo wrote: - So, I would like be able to set i.e. 2… 3 … n … cogs for one image.

Clo

Agreed, this should be configurable as there very are different mouses.

X.

sullysnet wrote: thanks for the no cache tip OliverG

It is related to topic below (the more files used, the worse it gets. It appears as freeze at certain levels):
http://newsgroup.xnview.com/viewtopic.php?t=4657