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

Capture One 23 16.2.1 Windows

Comments

7 comments

  • Arnel Ian Dela Gente

    Yes, I do have the perpetual license. Bouth it recently from B&H. It's working on my Mac but can't use it on my Windows after the update. 

    0
  • Arnel Ian Dela Gente

    I turned the Firewall and Anti -virus during activation and still not going through. I even did a restart. And now even my C122 isn't working on my windows machine. 

    0
  • Arnel Ian Dela Gente

    it's done. I fixed it.  

     

    0
  • Filthy Lucre

    If the license is for 16.1 (or earlier) it will not support the update to 16.2.

    This is a sore spot with me and likely other holders of a perpetual license—the fact that the C1 overlords consider a dot release to be a "new" version. 

    0
  • Filthy Lucre

    No, the alternative policy that doesn't screw users would be to provide updates to the version bought, 16 in this case, until such time as a legitimate new version (17) is released. Sure, C1 could call a dot release 17 but that would just be semantics and would be no more palatable than what they're doing now.

    I understood the policy before I bought in, I just don't happen to agree with it.

    1
  • Filthy Lucre

    A well thought out reply, thank you.

    Of the subscription models I'm aware of, I tend to favor the one now used by Topaz. One is entitled to a year's worth of updates—features, bug fixes, et al.—which stop when the calendar runs out. The software remains fully functional and the user can monitor the subsequent releases to see if any of the updates are appealing. If so, he can opt in for another year.

    ...the traditional dot release was intended to be for fixes and, occasionally, new functionality that was intended to fix stuff that did not work as it should as it was or was overdue for a re-write to improve its operation...

    The crux of my issue with the present system. My memory of how things used to be is hard to suppress.

    To eliminate such service and maintenance updates as part of a "No new features without payment" policy seems to be a mistake. 

    And not a small one.

    There must be other ways to present and manage totally new features in a way that does not strand existing users with software functionality problems forever in the event that they have a perpetual license that they would never need to update were it not for the software faults.

    One of the primary reasons for my move to the latest version of C1 is that my old one, 13/20, stopped supporting the newest Nvidia GPU driver updates; hardware acceleration was effectively disabled. Of course there will be no fix from C1 and Nvidia currently cannot be bothered to respond to support emails (or even allow them to be sent for that matter). I didn't want to be tied to an old driver forever so I paid up during the recent half-off promotion.

    From C1's perspective, separating bug fixes from feature updates may not be an easy thing depending on how the code is written. I hope at some point they could make it modular enough that features and fixes could be managed separately and thus more intelligently and favorably for the user... assuming there is any incentive to do so.

     

    1
  • ernst.w

    it's done. I fixed it. 

    Would be fine to know HOW You did fix it.

    1

Please sign in to leave a comment.