Previewing JPG pictures for me has always been very slow, even when the JPG is progressive or has a thumbnail, both of which you should expect would allow thumbs and previews to appear fairly instantly. Explorer shows them instantly, it's just that Everything never has.
I suspect this may be down to the preview/thumb handler, which must be in some way different from Explorer's.
Is it possible to install/configure something that would process progressive and thumbnail-embedded JPGs rapidly in Everything, just as Explorer does?
David
Preview/thumb handlers
Re: Preview/thumb handlers
For JPG files, Everything shows the 1024x1024 thumbnail for the preview.
I will consider showing smaller thumbnails while the larger one loads.
Thank you for the suggestion.
I will consider showing smaller thumbnails while the larger one loads.
Thank you for the suggestion.
-
meteorquake
- Posts: 495
- Joined: Thu Dec 15, 2016 9:44 pm
Re: Preview/thumb handlers
Thanks!
I'm not sure how the logic is currently implemented but I would anticipate could be -
1. Active (i.e. last-clicked) thumb receives thumb along with any Preview in the Preview pane.
2. Then, other selected thumb(s) visible on screen receive thumbs, at least low-quality but probably expedited to good quality since they are selected and of particular interest.
3. Then, all items showing on screen have at least some thumb showing (from the file's internal thumb or because it's a progressive jpg) even if it's of lower quality than the target quality.
4. Then, look at increasing the resolution of the thumb appearances wherever the target quality calls for it.
I think these 4 tasks should be effectively synchronous, and the items within them effectively synchronous (i.e. mostly one at a time but some way to deal with items that get stuck or are sluggish) because of the way people are likely to be using thumbs, for example with thumbs you are going to be skimming through quickly looking for something page by page and it's not helpful to have high-quality thumbs being built whilst some have not even been given a low-quality thumb, and likewise if too many thumbs are being built asynchronously you can end up waiting whilst none or few are showing, it's better to have them processed effectively synchronously. Similar problem with roadworks I notice - it's better to have a team of 8 going to 4 roadworks one-by-one (causing minimum disruption) than 4 teams of 2 working all working on the 4 roadworks simultaneously (causing maximum disruption). I once saw some roadworks that took 2 years to complete due to lack of manpower employed...
David
I'm not sure how the logic is currently implemented but I would anticipate could be -
1. Active (i.e. last-clicked) thumb receives thumb along with any Preview in the Preview pane.
2. Then, other selected thumb(s) visible on screen receive thumbs, at least low-quality but probably expedited to good quality since they are selected and of particular interest.
3. Then, all items showing on screen have at least some thumb showing (from the file's internal thumb or because it's a progressive jpg) even if it's of lower quality than the target quality.
4. Then, look at increasing the resolution of the thumb appearances wherever the target quality calls for it.
I think these 4 tasks should be effectively synchronous, and the items within them effectively synchronous (i.e. mostly one at a time but some way to deal with items that get stuck or are sluggish) because of the way people are likely to be using thumbs, for example with thumbs you are going to be skimming through quickly looking for something page by page and it's not helpful to have high-quality thumbs being built whilst some have not even been given a low-quality thumb, and likewise if too many thumbs are being built asynchronously you can end up waiting whilst none or few are showing, it's better to have them processed effectively synchronously. Similar problem with roadworks I notice - it's better to have a team of 8 going to 4 roadworks one-by-one (causing minimum disruption) than 4 teams of 2 working all working on the 4 roadworks simultaneously (causing maximum disruption). I once saw some roadworks that took 2 years to complete due to lack of manpower employed...
David
Re: Preview/thumb handlers
To set the preview thumbnail load size:
To set the thumbnail load size:
- In Everything 1.5, from the Tools menu, click Options.
- Click the Advanced tab on the left.
- To the right of Show settings containing, search for:
preview - Select: preview_load_size
- Set the value to: 256
(default is 1024) - Click OK.
To set the thumbnail load size:
- In Everything 1.5, from the Tools menu, click Options.
- Click the Advanced tab on the left.
- To the right of Show settings containing, search for:
thumbnail - Select: thumbnail_load_size
- Set the value to: 64
(default is 256) - Click OK.