Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

C1 10 slow performance on two computers, simple files

gbal30
Hi guys,

I'm finding C1 10.0.0.193 to be incredibly slow when browsing from one image to another, it's taking about 4 seconds, often longer, to even acknowledge the click or cursor key and display each image, often showing the beachball of death too. It is also again equally slow when you press 'C' to show the crop. These are not unusual files, just normal 5d3 raws. This happens on both my machines (which aren't super-duper powered but perfectly adequate and have been totally fine on C1 9 etc), one being MBP retina 13" 2.6ghz dual i5, 8gb RAM, SSD, Intel HD 4000, the other being Mac mini 2.7ghz dual i7, 16gb RAM, SSD, Radeon 6630M 256mb, both on Sierra 10.12.1. Turning off display OpenCL on the mini slightly improved switching between images but not the crop, and it seems to have had no effect on the MBP.

What can I do to speed things up? C1 9 was perfectly fine on but this is practically unusable - what have you changed to affect this so much? HELP

Thanks
0

Comments

5 comments

Date Votes
  • Neonsquare
    I see similar behaviour on C1 10. It is actually really bad with TIFF files. If I try to zoom into a TIFF file my MacBook Pro Retina i7 with 16GB RAM sometimes hangs for Minutes!
    0
  • NNN637254559064198001
    Tech support told me to turn off OpenCL options, and, to do this: "In addition to disabling openCL there is another item you can try which is to delete this folder: Hard Drive (your hard drive name) > Users > Shared > Capture One > Image Core."
    0
  • Christian Gruner
    [quote="Triumph Steve" wrote:
    Tech support told me to turn off OpenCL options, and, to do this: "In addition to disabling openCL there is another item you can try which is to delete this folder: Hard Drive (your hard drive name) > Users > Shared > Capture One > Image Core."


    Just to clarify what Support have already told you:
    Remember that the files in that folder are used for OpenCL. So if you are already on Never for Hardware Acceleration, there is no point in deleting these kernel files afterwards.
    It has to be done the other way around. Delete the kernel files first, try your flow, and then, if still present, set HW Acceleration to None.

    In general, setting HW Acceleration to None, should only be done as a last resort, as doing so can greatly affect performance in a negative way. However, for testing- and debug-purposes, of course flick it back and forth
    0
  • SFA
    Christian writes:

    "In general, setting HW Acceleration to None, should only be done as a last resort, as doing so can greatly affect performance in a negative way."

    I assume that an exception to that advice would be where the currently installed GPU driver may be suspected of causing processing problems and therefore disabling it for C1 as a test would make sense.

    Likewise temporarily changing the Hardware acceleration preference setting to "none" is also a reasonable test to undertake when looking for an instant "fix" of some sort or attempting to diagnose a problem.


    I think this is implied in Christian's responses on the forum.

    However some people may be taking the statement literally and therefore completely compromising their ability to use C1 at all rather than ending up with a functional though perhaps somewhat slower system for a short period whilst their problem is assessed and a solution identified.

    My thoughts for what they are worth.

    Grant
    0
  • Christian Gruner
    [quote="SFA" wrote:
    Christian writes:

    "In general, setting HW Acceleration to None, should only be done as a last resort, as doing so can greatly affect performance in a negative way."

    I assume that an exception to that advice would be where the currently installed GPU driver may be suspected of causing processing problems and therefore disabling it for C1 as a test would make sense.

    Likewise temporarily changing the Hardware acceleration preference setting to "none" is also a reasonable test to undertake when looking for an instant "fix" of some sort or attempting to diagnose a problem.


    I think this is implied in Christian's responses on the forum.

    However some people may be taking the statement literally and therefore completely compromising their ability to use C1 at all rather than ending up with a functional though perhaps somewhat slower system for a short period whilst their problem is assessed and a solution identified.

    My thoughts for what they are worth.

    Grant

    Good point about wording, I have edited my suggestion. Thanks.
    0

Post is closed for comments.