Preview Image Size and faster preview
I've been meaning to discuss/ask about this for years. What is the ideal Preview Image Size? C1 defaults at 2560. Is this just for the preview as you flip through the images? If so, it would seem to me to set that size at either the size of your preview or maybe slightly larger, correct?
I ask all this because I am trying to figure out how to get the previews to come up faster. All my machines are usually the fastest and latest from Apple with all solid state drives and maxed out RAM. But still there is always that slight delay as an image "snaps" in to preview. It almost seems like there is no cache in C1 as it seems to redraw the preview each time I go back to an image (if I have 10 images, look at image 1, then go to image 2, then go back to image 1, it seems to "redraw" it even though I just looked at it 2 seconds ago). Even iPhoto can draw the images faster (there is actually never a delay in iPhoto—you click on an image and it is 100% non-pixelated, perfectly displayed immediately). How can I get C1 to behave the same?
I ask all this because I am trying to figure out how to get the previews to come up faster. All my machines are usually the fastest and latest from Apple with all solid state drives and maxed out RAM. But still there is always that slight delay as an image "snaps" in to preview. It almost seems like there is no cache in C1 as it seems to redraw the preview each time I go back to an image (if I have 10 images, look at image 1, then go to image 2, then go back to image 1, it seems to "redraw" it even though I just looked at it 2 seconds ago). Even iPhoto can draw the images faster (there is actually never a delay in iPhoto—you click on an image and it is 100% non-pixelated, perfectly displayed immediately). How can I get C1 to behave the same?
0
-
What is the native resolution of your viewing screen?
For fast previewing you might consider setting the default to the same value or, depending on how you work and what your output needs are, slightly smaller in order to minimise both rescaling effort and file sizes.
It could be an interesting experiment to see how much perceived difference such changes would make. There seem to be a number of factors involved.
Grant0 -
[quote="SFA" wrote:
What is the native resolution of your viewing screen?
For fast previewing you might consider setting the default to the same value or, depending on how you work and what your output needs are, slightly smaller in order to minimise both rescaling effort and file sizes.
It could be an interesting experiment to see how much perceived difference such changes would make. There seem to be a number of factors involved.
Grant
Yes, many factors involved. I shoot commercially, tethered, so we shoot many images very fast. As they come in C1 has to create the "Preview Image". From experience, I know that when I process a bunch of jpegs, setting the resolution at 2500 pixels vs. 1800 pixels takes more than twice as long for them to process. So I figure if I have smaller Preview Images then when I am shooting quickly, C1 will be able to spit out the Preview Images faster (I assume C1 uses the same code to create jpegs as it does to create Preview Images). My large monitor is 2560 pixels wide but by the time I have menus and my image browser on the right, the preview images are about 2000 pixels wide. So does it make sense to set my Preview Image size to 2000 pixels wide to increase speed of creating the Preview Images along with browsing through the session? Is there something else that should be set/changed to get the fastest performance out of this? How does iPhoto make it happen so instantaneousy? I guess I can try experimenting but I was hoping someone would come in and lay down the law!0 -
screen shot the image in the viewer, get info (cmd+i) that file and see how big it is, then set your preview size in prefs.just above that size. If you quickproof jpeg process and want your images larger then up the size in prefs. 0 -
It also bothers me that there is no faster preview in Capture One Pro. I compare multiple images by quickly switching back and forth to see the differences but Capture One Pro most of the time re-renders the previews so this technique does not work always. Though "sometimes" it works. Tried different preview sizes but can't see any changes in speed.
To the Capture One Pro software developers:
There should be a cache where Capture One Pro saves the preview image and only re-renders it when you really add modifications to it.0 -
[quote="danielschweinert" wrote:
It also bothers me that there is no faster preview in Capture One Pro. I compare multiple images by quickly switching back and forth to see the differences but Capture One Pro most of the time re-renders the previews so this technique does not work always. Though "sometimes" it works. Tried different preview sizes but can't see any changes in speed.
To the Capture One Pro software developers:
There should be a cache where Capture One Pro saves the preview image and only re-renders it when you really add modifications to it.
Yes! My exact problem!0 -
[quote="danielschweinert" wrote:
...
To the Capture One Pro software developers:
There should be a cache where Capture One Pro saves the preview image and only re-renders it when you really add modifications to it.
The preview image is saved after when it is created on first opening. It is never altered. Adjustments or modifications are not saved to the preview but applied in real-time on the preview image. This rendering might cause delay on certain systems. You could either:
- provide more details about your hardware here to discuss them with other users, or
- open a support case and discuss your best options with the support team0 -
[quote="Paul_Steunebrink" wrote:
[quote="danielschweinert" wrote:
...
To the Capture One Pro software developers:
There should be a cache where Capture One Pro saves the preview image and only re-renders it when you really add modifications to it.
The preview image is saved after when it is created on first opening. It is never altered. Adjustments or modifications are not saved to the preview but applied in real-time on the preview image. This rendering might cause delay on certain systems. You could either:
- provide more details about your hardware here to discuss them with other users, or
- open a support case and discuss your best options with the support team
My current hardware: 27" iMac / CPU i7 / 32GB RAM / 1TB SSD / GPU GTX780M 4 GB /
I also didn't see any difference in more powerful hardware. I've tried it on a PC too. Rerendering does seem to happen 99% of the time. The curious thing is that "sometimes" it really works without rerendering but only for a couple of seconds.
The machine is brand new and there is "only" Capture One 7 Pro installed (not even Photoshop). I wanted to see how CO7 performed on a new machine because for me CO7 was a huge disapointment (with new updates it got better but Capture One Pro 6 is still the king in stability and performance). Okay CO7 had some cool new features but the instability and the gazillion of bugs made these new features fade away very fast.
Just yesterday when I opened a session file for a client the settings of my raw files magically disappeared. The image was there but the settings were all reset to 0 - "zero". I really hope Capture One Pro 8 will have a "LOT" of new features & improvements or I see me swtiching to LightRoom 5 or 6. Thats a pitty because I really like to work with Capture One Pro but version 7 had too many quirks for my taste that made me loosing faith in that version.0
Post is closed for comments.
Comments
7 comments