Page 1 of 1
Next/Previous image delay compensation
Posted: Tue May 29, 2007 6:27 am
by Flake
Image changing takes a while to go to next/previous image, but sometimes it goes skipping some images not even displaying them.
Does it need so much CPU to work without glitches? Cache options are enabled, but even then this delays and skipping are annoying.
Look on Google Picasa2 on AcdSee 3.0 (no any cache mention though) performance, they work perfect even with large images. And please don't say "if you like - so use them instead".
I hope it can be improved soon
Thanks
Posted: Tue May 29, 2007 10:13 am
by coverback
I'm experiencing something similar here, but not just on change, but rather on resize or on change in 'fit to window' mode.
and yes, asdsee 3 was doing the resize faster, but i don't know which algorithm was used there though..
Re: Next/Previous image delay compensation
Posted: Tue May 29, 2007 10:37 am
by xnview
Flake wrote:Image changing takes a while to go to next/previous image, but sometimes it goes skipping some images not even displaying them.
Does it need so much CPU to work without glitches? Cache options are enabled, but even then this delays and skipping are annoying.
Look on Google Picasa2 on AcdSee 3.0 (no any cache mention though) performance, they work perfect even with large images. And please don't say "if you like - so use them instead".
Do you have tried with 'Read ahead' option?
Re: Next/Previous image delay compensation
Posted: Tue May 29, 2007 2:09 pm
by Flake
xnview wrote:Do you have tried with 'Read ahead' option?
Flake wrote:Cache options are enabled, but even then this delays and skipping are annoying.
Yes, I've tried
Posted: Tue May 29, 2007 11:25 pm
by AlterMann
If you disable "High quality zoom" options, speed is icreased!
So, i think the problem is relevant to this algorithm.
Also -another suggestion- "read one image ahead" options must be work backward too!... (Even more than "one" image.)
Posted: Wed May 30, 2007 8:20 am
by xnview
AlterMann wrote:If you disable "High quality zoom" options, speed is icreased!
So, i think the problem is relevant to this algorithm.
High zoom is slow and can be slower for big picture!
Posted: Sun Nov 18, 2007 10:51 pm
by pepemosca
AlterMann wrote:Also -another suggestion- "read one image ahead" options must be work backward too!... (Even more than "one" image.)
I vote to that: more than "one" image ahead and back!
I have 2GB of RAM, I should be able to manage more than 1.
