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. ⚠️

Do you find COP8 sluggish?

Gary Irwin
New user here. I've downloaded the COP8 trial version and am running it on an 4.0GHz i7 riMac 32GB 1TBSSD 4GB graphics card. Right now I'm processing individual 20MP 7DII CR2 files.

I'm finding response to global edits "fair" but notice response times start to lengthen dramatically when doing local edits. Even a couple of layers bog the system down to the point where selective painting masks lags by ten seconds or more. It gets worse when stacking clone and/or heal layers.

I'm thinking that the only practical way to use this software is to limit it to global edits then export to another editor for local edits.

What is your experience?

Gary
0

Comments

7 comments

Date Votes
  • brianmerwin
    This is pretty typical behavior, and your assessment isn't wrong really.

    That said, no other software on the market really offers the kind of local adjustment control you're getting with C1, and it's some pretty advanced stuff so extra rendering time is totally expected. It's sort of the tradeoff for having these capabilities in a non-destructive environment.
    0
  • Gary Irwin
    Thanks Brian. I have to agree the raw conversion that COP8 delivers is really good...likely the best I've seen from any converter.I guess the developers of CO want to expand the application to be much more than a simple raw converter. It looks like they're going to have to rebuild the core display engine first. Maybe they should consider hiring some NIK programmers from Google.

    Anyway, it looks like I'm going to purchase COP8, but all I'll do is open a session mode, apply some global edits then export to tiff and open in Capture NX2 (my former editor of choice) -- which I formally thought was a slow but it runs rings around COP8.
    0
  • Quentin Stafford-Fraser
    Brian... Well, yes, though the rather more sophisticated local adjystments in LR don't slow things down nearly as badly.

    For me, though, C1 becomes most painful while doing imports, if you want to get anything done at the same time; I'm getting used to it - I go and have a coffee - but LR or Aperture let me keep on working happily while they import in the background...
    0
  • SFA
    See if you can borrow the use of an equivalent spec Win PC and test CO8 on that with the same files.

    I'm using what is now a 2 year old last gen Dell notebook with a GPU that so lacks power CO ignores it and I just don't see the sort of laggardly speeds you guys are discussing.

    Either I am misunderstanding what you are describing or there are some very specific factors in play that differentiate Win/Mac configs. Alternatively some sort of CO config/settings that are loading the systems.



    Grant
    0
  • meanwhile
    That said, no other software on the market really offers the kind of local adjustment control you're getting with C1, and it's some pretty advanced stuff so extra rendering time is totally expected. It's sort of the tradeoff for having these capabilities in a non-destructive environment.


    Hmm, at least 3 others that I know of have non-destructive RAW-level local adjustments (Lightroom, Aperture, Bibble/Aftershot Pro), without huge speed issues with a few layers/adjustments. Or were you meaning something else here Brian?

    Not that I've really seen slowdowns of that level (10 secs wait for a brush) even on my machine that is less than half the specs of Gary's, but I'm working with slightly smaller files too.

    Maybe try turning OpenCL for Display to Never in the preferences and see if that helps?
    0
  • jacques
    Hi Gary,

    Just my experience: my Mac is not even half of yours, and I do not experience this kind of slow down at all - even though my files are bigger (Nikon D600, 24MP). Given your setup, if I were you I would open a ticket with the support, this does not sound right at all.
    0
  • Rolf Vassen
    New user here as well. I am running C1 on a new iMac Retina 5k (same config like Garys iMac) and on a 1st gen. MacBook Pro 15" Retina to process Nikon D800E raw files. On the MacBook it is running very smoothly and I am having no performance issues. On the more powerful iMac, local adjustments are almost impossible to use. So, same issues here like Gary reported in his first post. With Aperture and Nikon Capture NX2, I have no performance issues on the iMac. Those two apps are running super fast on my new iMac.

    So, after a lot of testing with C1 on the iMac, I am pretty sure that the problem is related to the size of the preview pictures that are created during the import of new images. The maximum size you can set in the preferences is 2880 px. This is to small for a screen that has 5120x 2880 pixels. C1 is constantly accessing the raw files when the C1 window is maximized and all is slowing down.
    If you resize the window so that the preview picture doesn't exceed 2880 px. then all is good and adjustments -even local adjustments - are applied super fast.
    My conclusion: If you own a new Retina iMac, don't use C1 in a maximized window 😊

    Merry Christmas from Germany,
    Rolf
    0

Post is closed for comments.