Blurry previews when the viewer is hidden?
Hi all,
I've recently noticed a rather annoying issue: whenever the viewer is hidden (View > Hide Viewer), the previews / thumbnails are quite blurry, as if they were down-sampled in a very rough way.
This is especially visible when the previews / thumbnails are set to the largest size. This issue makes culling very, very difficult, since I hide the Viewer for culling.
I have OpenCL enabled both for processing and for display. I tried with it off and no change. My native resolution is 2560x1440, which is the exact same resolution that I set for Preview Image Size (px) in the preferences.
For what it's worth, I have 2 x GTX 980 graphics cards, with the latest NVIDIA driver. This is all running on the latest Windows 10 64 bit with the latest Capture One Pro 10 update (build 10.0.2.😎.
Before reaching out to Support, would any of you have any suggestions or recommendations?
Thank you. 😊
I've recently noticed a rather annoying issue: whenever the viewer is hidden (View > Hide Viewer), the previews / thumbnails are quite blurry, as if they were down-sampled in a very rough way.
This is especially visible when the previews / thumbnails are set to the largest size. This issue makes culling very, very difficult, since I hide the Viewer for culling.
I have OpenCL enabled both for processing and for display. I tried with it off and no change. My native resolution is 2560x1440, which is the exact same resolution that I set for Preview Image Size (px) in the preferences.
For what it's worth, I have 2 x GTX 980 graphics cards, with the latest NVIDIA driver. This is all running on the latest Windows 10 64 bit with the latest Capture One Pro 10 update (build 10.0.2.😎.
Before reaching out to Support, would any of you have any suggestions or recommendations?
Thank you. 😊
0
-
Thumbnails and previews are different files as far as I know.
Are you by any chance looking at the thumbnails at full resolution in a large browser window?
Grant0 -
I might have gotten the terminology wrong.
What I'm talking about is the many photos that you see when you hide the viewer and the viewer space is replaced by a grid of many photos. Those photos (I guess they are thumbnails?) are quite blurry.0 -
[quote="NN635474536475599539UL" wrote:
I might have gotten the terminology wrong.
What I'm talking about is the many photos that you see when you hide the viewer and the viewer space is replaced by a grid of many photos. Those photos (I guess they are thumbnails?) are quite blurry.
At what size? There is a zoom control. On a high resolution screen you would expect to see a lot of small thumbnails. Zoom them up to something like a viewable image size and you will likely be enlarging them a lot us9ing the screen.
Do the same thing with a preview and things will either be there already or close (if your previews are set at your native size) or C1 would recalculate and redisplay. That won't happen with a thumbnail from the browser. The size will always be small. The thumbnails are there to provide a reasonable means of selecting images that want to see in the browser or for processing/batch processing selection tasks. If they look ok at thumbnail size they have performed the task they were created for.
On the other hand if they are simple a blob of blur then you have a problem somewhere.
Can you post a screen grab? You would need to host the file somewhere and link it to the forum post.
HTH.
Grant0 -
Grant, thank you for the detailed response.
It's indeed about thumbnails, not previews. I'm on a 1440p screen, so not that high, but not that low either a resolution.
The issue is most annoying when a) the viewer is hidden and b) the zoom is highest (so the thumbnails are biggest): the thumbnails become quite blurry.
Here's a screenshot crop (otherwise unresized): look how blurry the thumbnails are and how your eyes are continuously trying to focus.0 -
I think that Grant is right that thumbnails need only be good enough for the user to identify which images to open in the viewer and work on. I wouldn't expect, for instance, to be able to tell just from the thumbnails which of the four images in your screenshot was the best one to use for further work, apart from obvious things like whether it was grossly over or underexposed (which yours are not) or the slightly different framing between your shots. I would expect to have to use the viewer to check which of them really was sharpest, for instance.
Small thumbnails probably are a good thing for the sake of fast loading and minimising demand on storage resources. For each image we already have the original raw file (large file size) and the preview (quite large file size), and adding a large "thumbnail" rather than a smallish thumb-nail-sized one would perhaps be a significant extra use of storage. I'm looking at this on a MacBook Pro at the moment. If I keep the tools panel on and pull up the thumbnails to their largest size, there is only room to see 2 landscape format images side by side, with the second row cut off partway down the frame, so not really useful for scrolling through the images. And they are approximately half the length and half the width of the preview seen at zoom-to-fit level.They do look a bit pixellated, but do I need to see them that big instead of using the viewer? Only two fully visible at a time is not really useful for anything.
Ian0 -
I just ran a quick check on the thumbnail folder for one of my sessions.
The largest file size I saw was 33kb the smallest 5kb.
Yes I do mean kilobytes!
Clearly they will be somewhat compromised for anything other than viewing an approximation of content in order to select and view in the viewer.
It might be better for you to consider turning off the Browser and looking at use Sets or something via the Viewer.
HTH.
Grant0
Post ist für Kommentare geschlossen.
Kommentare
6 Kommentare