メインコンテンツへスキップ

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

Capture One Pro 6.1.1 - Good, Bad and Ugly

コメント

3件のコメント

  • LadyRainbows
    [quote="Nelson1" wrote:
    Finally I got photos to process and used the latest CO Pro 6.1.1.

    Good:
    The Open CL redraw artifacts are gone.

    Bad:
    Processing photos causes CPU usage all 8 logical cores to go 100%. The UI response becomes sluggish until the processing is completed.

    Ugly:
    The UI freezes when deleting photos. There is no way to even minimize the COP 6.1.1.

    [color=#0000BF:xjhl45vn]Can the P1 programmers keep the UI refresh in a separate thread? This should be UI programming 101. The perception of the performance is largely based on the UI responsiveness.[/color:xjhl45vn]



    Try turning the openCL back on. (it sounds like you have it off)
    Whenever I have it on C1 6.1.1 bearly uses 35% of each thread.. And it runs extremely fast now without problems.

    I am using
    Phenom II x4 840
    9800 GT 512MB
    4GB DDR3 1066
    Win 7 64
    0
  • Paul Steunebrink
    Nelson,

    I do not recognize the behavior you describe. While processing a batch of images on my Core i7 950 based system (8 logical cores), the application is as reponsive as it can be and the same while not processing. I do not use OpenCL because my video card is not that sophisticated at all. While processing I open a browser to write this post and it is not affected by the processing going on in the background as well.
    Note that CO6 uses different processes (and therefore threads) for processing and the GUI. You can see that in Task Manager.

    What I suspect is that there is another bottleneck in your system, which it prevents from giving you the best performance. It is not CO6, believe me (or not).
    0
  • Joachim Neumann
    I too have problems with the performance and the CPU is working with 100% specialy when using the spot removal tool.
    I made a support case last week and PO told me that they know the problem and are working on it.

    You should make a support case and send your logg files. This can help to find the problem.
    0

投稿コメントは受け付けていません。