fullscreen[browser]
'Fit image to window' has a slight delay of about 0.5 secs on my PC before filling the screen with the high quality enlarged image--and I have an very fast CPU. I'm fitting 1024x768 images onto 1600x1200 screen size. Zoom-in and zoom-out works performs instantly and doesn't have this delay. Is it possible to make 'fit image to window' happen instantly? Perhaps make image fill screen instantly [in low quality first] then apply high quality redraw?
V 1.90 RC1
'Fit image to window' is slow
Moderators: helmut, XnTriq, xnview
Re: RC1: 'Fit image to window' is slow
I have the same delay with zoom and fit, perhaps could you use 'option/fullscree/use delay'?TsunamiZ wrote:fullscreen[browser]
'Fit image to window' has a slight delay of about 0.5 secs on my PC before filling the screen with the high quality enlarged image--and I have an very fast CPU. I'm fitting 1024x768 images onto 1600x1200 screen size. Zoom-in and zoom-out works performs instantly and doesn't have this delay. Is it possible to make 'fit image to window' happen instantly? Perhaps make image fill screen instantly [in low quality first] then apply high quality redraw?
Pierre.
Re: RC1: 'Fit image to window' is slow
good to know, thanks. but is it possible to make 'fit image to window' work instantly like high quality zoom-in/out? perhaps optimize the process a bit?
Re: RC1: 'Fit image to window' is slow
But for me 'fit image to window' work like high quality zoom-in/outTsunamiZ wrote:good to know, thanks. but is it possible to make 'fit image to window' work instantly like high quality zoom-in/out? perhaps optimize the process a bit?
Pierre.
- foxyshadis
- Posts: 395
- Joined: Sat Nov 18, 2006 8:57 am
Yes, this is due to the HQ resize algorithm being rather slow. It's only fast with zoom because HQ isn't applied there in the fullscreen - if you try it with view mode, watch as it gets unbearably slow as you resize from 100% to 800%.
It is most likely possible to optimize it, but I don't think that's a priority. (It would be fastest to use the graphics card, which has hardware bilinear, but I'm sure that's not easy.) If "read ahead" at some point includes the resized version, then I think it will become a moot point anyway.
(GIF animations suffer some crazy slowdowns with HQ fullscreen, probably because frames aren't queued at all. Cool effect, but ultimately too slow. ;_; )
It is most likely possible to optimize it, but I don't think that's a priority. (It would be fastest to use the graphics card, which has hardware bilinear, but I'm sure that's not easy.) If "read ahead" at some point includes the resized version, then I think it will become a moot point anyway.
(GIF animations suffer some crazy slowdowns with HQ fullscreen, probably because frames aren't queued at all. Cool effect, but ultimately too slow. ;_; )
Good summary. Another suggestion has also been made. All this has already been suggested elsewhere (this thread could be 'closed').foxyshadis wrote:Yes, this is due to the HQ resize algorithm being rather slow. It's only fast with zoom because HQ isn't applied there in the fullscreen - if you try it with view mode, watch as it gets unbearably slow as you resize from 100% to 800%.
It is most likely possible to optimize it, but I don't think that's a priority. (It would be fastest to use the graphics card, which has hardware bilinear, but I'm sure that's not easy.) If "read ahead" at some point includes the resized version, then I think it will become a moot point anyway.
Might be worth disabling HQ with animated GIF for 1.90, then...foxyshadis wrote:GIF animations suffer some crazy slowdowns with HQ fullscreen, probably because frames aren't queued at all. Cool effect, but ultimately too slow.
Olivier