Previews - Which Size Is "Right"?
I've read a number of differing opinions on how to set the optimal preview size, i.e., to maximize the quality of the displayed preview while at the same time minimizing the need to re-render the preview image during editing.
The most common opinion suggests that if you determine the width of your viewer window in pixels and then specify a preview image size one increment larger than the viewer window width, that should be the "sweet spot" in terms of preview display quality while minimizing the need for re-rendering during editing/viewing.
I have a 25" 2560 x 1440 monitor (117 ppi) and my viewer window in C1 (in the middle, between the Tools column on the left and the Browser column on the right) measures 16.5 inches wide. Crunching the numbers, 16.5 inches x 117 pixels/inch = 1930.5 pixels - this is the width of my viewer window. Under Preferences>Image the closest (slightly higher) increment for Preview Image Size is 2048 pixels, so this is what I have selected.
I've tried a number of different preview image sizes (being careful to "Regenerate Previews" for each attempt) and frankly I don't see a noticeable difference in the quality of the preview images... they always look somewhat soft, unless I invoke a proofing recipe at which point they look dramatically improved.
Am I doing something wrong? - shouldn't different preview image sizes result in visibly sharper or softer previews, or am I just missing something here?
Any help or advice would be greatly appreciated!
-
Michael your logic is right, according to the C1 help page.
https://support.captureone.com/hc/en-us/articles/360002484457-Capture-One-Preferences-The-Image-tabHowever after changing the preview size in preferences you have to select all the photos you want to have that new preview size, then regenerate the previews. Took me half an hour to find that out.
I always assumed (I guess like most people) that C1 would just automatically change all previews.There is a default output recipe in C1 called JPEG Quick Proof (preview size).
The pixel dimensions of this recipe are directly related to the C1 preview size.
This is the only place I can see a difference after changing preview sizes.
With my 30" screen setting 640 or 3840 makes no difference to the display quality that I can see, (edit) even at 100% and above.
I think C1 always displays to the maximum screen resolution, the only question is whether it grabs a straight full screen preview or has to up-sample a low one. Maybe this was more relevant in the past with slower processors and less memory.0 -
Michael,
One of the settings in a Recipe elates to Output Sharpening - whether or not it is applied and how much.
You might want to check whether this is influencing the differences you observe between proofing and not proofing.
As for the size of the preview question - there are clearly differences in most situations between the full resolution available from a RAW file (or tiff or jpg, etc.) and what a screen can provide if an entire image view is required.
The recommendation for a default size to match the native screen display size offers the option for the preview to be slightly compressed to enable the "fit" view when the full screen is not available, or for the entire preview to be available in Full-Screen mode.
If you zoom in C1 will also be able to make some adjustments on the fly based on the preview display. However, if you want to the full detail at 100% it will usually need to recalculate and make use of the full file resolution, bypassing the preview file to achieve that.
Similarly, if one had a large preview file but wanted to display the data in a smaller number of pixels the application would need to recalculate and compress the image by discarding some data. Choosing a preview size that minimizes the amount of recalculation required to service your usual workflow can be important - especially for those involved in high volume and rapid results processing activities.
If one happens to run 2 or more screens that are significantly different pixel dimension sizes the choice of default Preview can be even more "interesting".
Always bear in mind that if you wish to see the ultimate resolution possible with the data you are working with you really need to be looking at it when the output is 100%.
If you want to see what can be produced at smaller dimensions for screen (depending in the viewing screens capabilities) and printed then a well defined Recipe and Proofing turned on should give you a good impression of what those results will look like. (On your screen(s)).
Bear in n=mind also that the Preview file is just a starting point for processing. A proxy for the full extent of the data on the source file. What you see on screen is the result of the Preview with the additional edit instructions applied or, at a zoomed in level that is outside the Preview's adaptive resolution, a recalculation from the original source file data so long as it is accessible.
0
Post ist für Kommentare geschlossen.
Kommentare
2 Kommentare