Zum Hauptinhalt gehen

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

What a ripoff

Kommentare

33 Kommentare

  • Jerry C

    A lot of us have used Capture One for many years and versions and have adapted to its idiosyncrasies. This seems to indicate that we like it and that it satisfies our needs better than other software or are we hanging on to Capture One by our nails until we can find the exit?  Wanting more and paying less is natural, but what features is it exactly that folks want that would make them start over with another product? Wouldn't this be the same even if the perpetual license was done in a way everyone liked?

    1
  • BeO
    Top Commenter

    @...

    Hi John,

    "so immense as to be unimaginable". Seriously?

    Not my words

    Sorry, my fault.

    Yeah, a bit of hyperbole, but I was just trying to make a point that it really doesn't matter what you or I want here

    Maybe not you and me, maybe not today.

    But I can imagine my suggestion (provided it is feasible and at reasonable cost) could be a way out of the biggest negative consequence of the policy change for perpetual license holders, i.e. the reduced bug fix period, without sacrificing the desire of many users for subscription or upgrading to new features, and even lift it to a better than competition level. Which in turn could help in attracting new and keeping existing customers.

     Incrementally adding or not adding a new menu item is no big deal.

    Yes, a few features from the past years come to my mind immediately, Luma curve, Magic brush and eraser, C1 engine in base char., new camera models, HDR white and black slider (can be more tricky though in case a clean UI is the goal and not just disabling the sliders; but the latter could be a marketing reminder), AI masking.

    But refactoring code that changes both interface and underlying functionality as some feature area moves forward suddenly has a whole bunch of new questions and design considerations if you're trying to preserve the prior functionality as it was in a prior release in the same code base so the new stuff is not offered to people who don't have a license for it.  That can get complicated really quickly.

    Yes, there are edge cases. The new layout of the layers tool, renaming background layer (excl. AI masking) etc. could be made available to all without licence check, same it true for the UI changes in 15.4 (bigger icons). 
    The culling window (in case it replaced the import dialog?) and new features of it I don't know because I am not familiar with it.

    There were and would be more edge cases where complexitiy starts to creep in, in which case product management together with development and QA can decide to open it up for all licenses, make a gift to customers and spread the word around.

    Admitted, the topic is not black and white, but I still have to see an example (in my job) where this approach did not work out, license dependent feature enablement rather resulted in commercial success in every case I know of.

    But yes, if today they would offer something around your proposal - this is easier and faster to achieve and better than nothing.

    0
  • Jerry C

    Some people buy dogs, other buy cats. It's hard to prove which is better, as long as they are as described and in good shape when you acquire them from the pet shop. We all have theories about why subscriptions models are being pushed at us. I think we agree that we all want predictability and equity in the choices being offered. So far, we get the same product regardless of the license model, but those with perpetual licenses would like to have the same value, which includes bug fixes. How long these bug fixes should be available is debatable, but at minimum, those known to exist within 6 months of the products rollout, just to propose a number, ought to be fixed regardless of how long it takes. The only way it is reasonable to roll out software with its inevitable flaws is to make good on correcting the ones that are obvious.

    If subscriptions must be bought in order to have bugs that interfere with performance corrected, this does drive folks toward subscriptions. If Capture One are truly are not going to deprecate the perpetual license, it would be reasonable to support that last version or two with respect to bugs fixes since they will already be fixing these bugs as they develop new versions.

    If they do this, we can focus more on the advantages and disadvantages of subscriptions and perpetual licenses. 

     

    1

Post ist für Kommentare geschlossen.