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

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

Unacceptable performance on Retina iMac

Permanently deleted user
I have been through one support case with P1 and now onto my second one.
Capture One becomes slow and eventually goes unresponsive doing ANY 100% viewing of raw files on my 5k iMac.

I have tried limiting the workload on the software by using:
- the Focus tab and using the Pick Focus Point tool to set the viewing area
- using the Loupe only
- using 100% zoom on the entire image

I have tried lowering the screen resolution of the iMac using the native scaling modes in macOS.

I have tried raw files from different camera models including Leica TL2 and Nikon D750.

I have tried multiple catalogs including creating new catalogs from scratch.

I have tried wiping my Mac's hard drive and doing a completely clean install of the operating system (a process which by the way took a FULL day).

As far as I am concerned the software contains a fatal bug because a program that after 30-60 minutes becomes progressively more unresponsive before simply locking up, is not usable. I need concrete information from Phase One that this is going to be fixed, and soon, or a refund. The software is not fit for purpose as it stands today.
0

コメント

5件のコメント

日付 投票
  • Eric Valk
    Thanks for posting your information, I sense your frustration but you won't be able to resolve issues with Phase One here. This is a user to user forum; Phase One sometimes visits, but not often.

    If you want a refund becuase the SW doesn't work, then best open a trouble ticket and say that.

    It would be useful if you could say how many images you have in your catalog, and provide some details regarding your machine, particularly how much RAM, what kind of processor, what kind of graphics, and which operating system. And model and year of your Mac.

    Your problem description resembles a memory problem that I have seen before. It might be worth it to monitor the memory pressure in OS X Activity Monitor while your problem is hppenning - if the memory pressure grow and grows, and the memory assigned to COP keeps growing, somewhere beyond 40GB of memory asssigned to COP (or any one process) the system slows down and eventually grinds to a halt.

    One item that can cause a really big COP workload is the Filters Tool, if you have more than 10,000 images and if you have some metedata fields that are unique for every image. You might try removing the Filters Tool from the library tab, and see if that resolves anything.

    I haven't experienced anything exactly like you have; I have a late 2015 iMac, 4GHz i7, 24GB of RAM running OSX10.12.6. I'm just chatting with folks on an other frum who are having nasty issues withe OSX 10.13.4, with Timemachine snapshots taking over their main drive. I don't think I'm upgrading to OS X 10.13 anytime soon, and not to APFS file system in release 10.13, too many bugs.
    0
  • Christian Gruner
    Hi,

    We need some more information:
    - Both Support-case numbers
    - Mac Model number (and hardware specs)
    - CO Version number
    0
  • Permanently deleted user
    My support ticket is 284928

    C1 11.0.1
    macOS 10.13.4
    Late 2014 iMac Retina 27"
    Core i5 3.5Ghz
    8GB RAM
    1TB Fusion drive

    The first supporter I dealt with on my original ticket never mentioned total installed RAM as a possible issue. On my latest ticket I was asked how much RAM is installed. Checking the system requirements for C1, my system did meet the minimum with 8GB. Nonetheless, today I installed an additional 8GB of RAM in my iMac bringing the total to 16GB. With that in place, I can no longer reproduce the problem. It seems like perhaps memory compression and/or swapping was causing C1 to grind to a halt. With the increased amount of RAM, macOS is no longer compressing C1's memory leading to dramatically better performance.

    Might I strongly suggest that a KB article is warranted detailing this behavior and how to resolve it. I have spent months chasing this issue!

    P.S. A certain competitor's product ran fine for years on this machine. It does seem like there is some room for further performance optimization in C1.
    0
  • Permanently deleted user
    Thanks for the reply Eric.

    [quote="Eric Nepean" wrote:
    It would be useful if you could say how many images you have in your catalog, and provide some details regarding your machine, particularly how much RAM, what kind of processor, what kind of graphics, and which operating system. And model and year of your Mac.

    Your problem description resembles a memory problem that I have seen before. It might be worth it to monitor the memory pressure in OS X Activity Monitor while your problem is hppenning - if the memory pressure grow and grows, and the memory assigned to COP keeps growing, somewhere beyond 40GB of memory asssigned to COP (or any one process) the system slows down and eventually grinds to a halt.


    Turns out you are exactly correct. With 8GB of RAM, there just wasn't enough headroom for C1 and after working on several images, it would grind to a halt and literally lock up.

    [quote="Eric Nepean" wrote:
    I haven't experienced anything exactly like you have; I have a late 2015 iMac, 4GHz i7, 24GB of RAM running OSX10.12.6. I'm just chatting with folks on an other frum who are having nasty issues withe OSX 10.13.4, with Timemachine snapshots taking over their main drive. I don't think I'm upgrading to OS X 10.13 anytime soon, and not to APFS file system in release 10.13, too many bugs.


    I don't have APFS on my system because it doesn't currently work with Fusion drives. I am friends with some of the folks at Apple who are working on APFS and they are dedicated engineers, but there is definitely some work still to be done.
    0
  • Eric Valk
    [quote="NNN636444299432767673" wrote:
    Thanks for the reply Eric.
    ......
    [quote="Eric Nepean" wrote:
    I haven't experienced anything exactly like you have; I have a late 2015 iMac, 4GHz i7, 24GB of RAM running OSX10.12.6. I'm just chatting with folks on an other frum who are having nasty issues withe OSX 10.13.4, with Timemachine snapshots taking over their main drive. I don't think I'm upgrading to OS X 10.13 anytime soon, and not to APFS file system in release 10.13, too many bugs.


    I don't have APFS on my system because it doesn't currently work with Fusion drives. I am friends with some of the folks at Apple who are working on APFS and they are dedicated engineers, but there is definitely some work still to be done.

    I didn't mean to comment on the qualities of the developers, nor the eventual quality of the APFS feature.
    I'm a developer myself (telecom products) and fully aware that when a complex feature is released it's a lot of blood sweat and toil to find and remove all the bugs.
    As a cosnumer, I'm usually in favor of letting others find and deal with the bugs 😊
    0

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