Aller au contenu principal

What should the preview image size be for an iMac 5k?

Commentaires

12 commentaires

  • photo by FA
    Technically it should be 5120 as this is your screen resolution. CO renders images of you go 100% and for some other adjustments.

    However I did some calculations and the widest image I can see with my setup is something like 3500 pixels so I use a lower preview size.
    0
  • Jerry C
    It depends on a lot of things, especially the pixel width of the window you are using. It also depends on the speed and location of your RAW image files, i.e., if they are on media on or attached to your iMac. With the speed of newer high end computers, preview size is not so important for efficiency. You can tell if this is the case for your system by taking a group of images and re-rendering the previews to be very small. If small previews do not slow things down when Capture One has to re-render them on the fly, select the smaller preview size - they take up much less space. If speed improves as your preview size gets larger, use the larger size.

    One caution. Even if your system is so fast preview size is not a factor, if your RAW images are off line, or on a NAS, or a web-based cloud server, a small preview size will not be useful.

    Jerry C
    0
  • NachoMama
    I think I have a pretty beefy iMac. It's the 2017 iMac 5k, 4.2 GHz Intel Core i7, 64 GB 2400 MHz DDR4, Radeon Pro 580 8192 MB, so I hope it's not an issue of processing power.

    I briefly tried changing my preview image size to 3840 but I still experience the same thing. I took a screen recording to try and illustrate:

    https://d.pr/free/i/zY3FEB

    I admit it's probably not the best quality, but if you notice, I tried cycling through a series of three photos, and even though they have no adjustments applied and previews should have already been generated, when I click on them they appear obnoxiously fuzzy for about a second before they look sharp. Maybe the really fuzzy version _is_ the preview, but if that's the case, something just seems really off.

    I recently watched a video series through CreativeLive on how to use Capture One Pro 10 and I noticed that the presenter's screen didn't seem to exhibit this behavior, so I'm wondering if I've just got something set wrong and how to fix it.

    It's not the end of the world but it does slow me down quite a bit, especially when I'm trying to select and rate photos that I want to process. The pre-rendered preview should make it quicker, but it seems like it's not really working.

    Thoughts?
    0
  • Jerry C
    I have seen a similar thing regardless of the preview size selected. 3840 px versus 640 px seems to make no difference on my iMac Pro with plenty of speed and memory. Capture One does not display the full resolution preview instantaneously. It takes between a half second and a second to display the image at full resolution. It is as if it were re-rendering the RAW file, but since this is pretty fast, I do not find it to be a problem. Capture One buffers the previous and next image, so if you scroll through images at the rate of about 1 per second, you would not notice the issue. If you want to scroll faster, it is an annoyance.
    0
  • Peter Svancar
    this is a know fact that C1 and 4K / 5K resolutions are not friends.
    The presenters on YouTube are using NTBs with 2k resolution, which is ok.

    Just switch the application to LOW Resolution mode to see the difference....
    https://www.youtube.com/watch?v=n65Pz53jFzo&t=199s
    0
  • NachoMama
    [quote="NN635680879799322049UL" wrote:
    I have seen a similar thing regardless of the preview size selected. 3840 px versus 640 px seems to make no difference on my iMac Pro with plenty of speed and memory. Capture One does not display the full resolution preview instantaneously. It takes between a half second and a second to display the image at full resolution. It is as if it were re-rendering the RAW file, but since this is pretty fast, I do not find it to be a problem. Capture One buffers the previous and next image, so if you scroll through images at the rate of about 1 per second, you would not notice the issue. If you want to scroll faster, it is an annoyance.


    For me, it does seem to take from around half a second to several (3?) seconds to render.

    I consider it a pretty big efficiency problem. Capture one already spends time during import to render previews, so there's that time for each photo plus the time switching between just a handful of photos adds up.

    Can anyone at Capture one comment on this issue?
    0
  • Doug Peterson
    [quote="NachoMama" wrote:
    [quote="NN635680879799322049UL" wrote:
    Can anyone at Capture one comment on this issue?


    This is a user-to-user forum. If you want input from P1, you should start a support case at https://www.phaseone.com/en/SupportMain
    0
  • NachoMama
    [quote="Digital Transitions, Doug" wrote:
    [quote="NachoMama" wrote:
    [quote="NN635680879799322049UL" wrote:
    Can anyone at Capture one comment on this issue?


    This is a user-to-user forum. If you want input from P1, you should start a support case at https://www.phaseone.com/en/SupportMain


    I just put in a ticket.

    Thanks Doug!
    0
  • Jerry C
    The more support cases, the better. I sent one in some weeks ago when we first began a discussion in another thread about the utility of previews when the RAW images are either in the catalog or on line (on a SSD or HD on or directly connected to the computer with the catalog).

    In essence, preview size makes almost no difference with fast well-resourced computers, and it is frustrating to still see the half to 1.5 second time to display a sharp image.

    I tested a variety of configurations on my iMac Pro (5k display). Nothing made a substantial difference. The comparisons included, a large set of 640px previews and another of the same previews at 3840px, and Hardware Acceleration for display on or off. I even deleted the previews folder from the cocatalog package, forcing Capture One to recreate the preview as each image was viewed. Except for a small fraction of a second more in this last case, preview size and and hardware acceleration did not improve speed of full resolution (sharp) display. They had a huge impact on catalog size.

    I have no idea how much of this problem is for Capture One to fix and how much is attributable to the operating system. So, until the developers find a way around this, there will be a lag, at least on a 5k display at full resolution.

    Jerry C
    0
  • photo by FA
    I don't think CO will ever admit, it is their problem. I find it really hard to believe iMac Pro is not capable of showing some lousy 5MB preview in matters of miliseconds.

    I think one of the main reasons is, CO is not optimized yet for 4/5K screen and also it is not optimized fully for macOS. A fully optimized software has to use Metal which is supported by Apple for a while.

    I too have problem with previews, luma masking, adjustments etc. and the solution by tech support was to turn of my GPU which is causing another problem on other tasks. So basically I had 2 separate issue and the solutions of those were contradicting to each other, one requires GPU off for a better performance and the other requires GPU on 😊
    0
  • Peter Svancar
    When i was first time claiming the performance of c1 i was told that my mac is slow to handle 5k.
    Now i see even imac pro cant handle it.

    The biggest problem i have is with the sliders lag.
    Therefore i do run the program in low res, which greatly increasing the performance.

    For next purchase of computer for capture one i will definetily avoid 4k+ screens
    0
  • photo by FA
    [quote="Peter Svancar" wrote:
    When i was first time claiming the performance of c1 i was told that my mac is slow to handle 5k.
    Now i see even imac pro cant handle it.

    The biggest problem i have is with the sliders lag.
    Therefore i do run the program in low res, which greatly increasing the performance.

    For next purchase of computer for capture one i will definetily avoid 4k+ screens


    Or Capture One should update itself, properly.
    0

Vous devez vous connecter pour laisser un commentaire.