Terrible C21 functionality degradation

Comments

8 comments

  • AndyE

    +1

    Nearly 200.- bucks for a yearly update and just a few new additions is quite a price for a software. And adding the many bugs that come and go and reappear again adds even more to this.

    Don't take me wrong, I love C1 and use it for many years. But please make this thing more stable and reliable.

    2
    Comment actions Permalink
  • CSP

    ....this was already apparent for years it only is more in focus because the update was a let down too. the level of issues is really astonishing and unmatched.

    0
    Comment actions Permalink
  • Dave R

    I was also a beta tester for the windows version of CO21 (I chose to major on the de-haze function, the least said about its early implementation the better ;-( but it is now performs similar to the LR version.). Most off the other new functions did not excite me though speed edit is slowly growing on me.  I am a long retired Systems Engineer and was fascinated by Apple's system on a chip design so I treated myself to a bottom of the range Apple M1 Mac mini for Christmas.

    Capture one sort of runs on it but I have hit all sorts of oddities, colour readout was not working properly but started working perfectly when I switched to no proof profile. Finding the seemingly single pixel to click on to open the cursor tools drop downs is a test of patience.  Carefully deleted unwanted clutter popping up again in outputs is well documented and so it goes on.

    One of the problems CO has, I think, is that a few years ago it majored on OpenGL/CL and many functions are dependent on this. Apple support for this definitely on the way out and as many people have being saying for some time the CO Mac version must switch to Metal. 

    CO have a big job on their hands porting to Apple silicon and to metal,  I shall be interested to see how long it takes, we may be pleasantly surprised.

     

    0
    Comment actions Permalink
  • CSP

    ...." but it is now performs similar to the LR version"  hm, seems I´m using a different c1 because in my last test it was still not even near and not only because it behaves totally different to the adobe dehaze.  

    metal was released 6 years ago and apple was clear about the future of open GL/CL on the mac platform but this seems did not concern p1, so I doubt they get a smooth running native m1 version out this years also considering the state of this software.  but when they fail to deliver and the bug galore continues they will have destroyed their reputation beyond repair after this underperforming release. 

    1
    Comment actions Permalink
  • Maarten Heijkoop

    I have disabled openGL/CL and on my MBA M1 C21 runs much faster, big tiff files (>250mb) don't result in big black patches anymore, that fill up later. Hopefully C1 takes this serious and will decide to make a good technical redesign

    0
    Comment actions Permalink
  • Maarten Heijkoop

    so one thing is solved, the clone/heal layer problem originated in a brush opacity slider that was low, set it to 100% and it works fine

    0
    Comment actions Permalink
  • Dave R

    Maarten

    Simply disabling openCL/GL as you suggest seems to be all that is needed to do the trick for me.  Thanks for the tips.  By the way I presume you know that the way to cure the color readout problem is to select View/Proof Profile/no profile.

    Dave

     

    0
    Comment actions Permalink
  • Maarten Heijkoop

    I never had that problem

    0
    Comment actions Permalink

Please sign in to leave a comment.