Capture One Pro (16.3) is out now – and we want to thank you...
We are delighted to announce the release of Capture One Pro (16.3) – this is a feature release and will require you to have a subscription, or a perpetual license that was purchased on or after September 26th.
We want to make new license purchases as cheap as possible for our loyal customers, so it's worth checking out the details of the Loyalty Program to ensure that you are paying as little as possible for your perpetual license. We're proud to provide the option to purchase a perpetual license and will continue to do so.
Release notes for Capture One Pro (16.3)
Sign-up to our livestream this afternoon (17:30 CEST) to see 16.3 in action.
One of the many features included in this release is AI Masking – something that has been frequently requested in the community for a while now. It makes us incredibly proud to be able to deliver a major feature like this based upon your feedback and needs as Capture One users.
Also included in this release, as a result of direct contributions from the community are:
- Ability to duplicate a layer
- Keyboard shortcut for toggling the Black & White tool
- Capture One Live comments in Capture One Pro
- Notifications about reviewer activity in Capture One Live
- Added keyboard shortcut to reset crop
- Speed edit reset
- Improved Luma Range window interaction
(coming in a service release, didn't quite make it into 16.3)
I'll use this as an opportunity to make everybody aware that if there is something that does not exist in Capture One, then we are completely open to implementing it.
Request a new feature, or improvement to Capture One by going to Improve Capture One Pro, clicking "New Post" and using the pre-filled template to let us know your thoughts and ideas.
The next headline feature of Capture One could easily come from one of your suggestions. Even if it's not a fancy idea, it could be something small that makes a big difference to other users.
Lastly and most importantly, thank you for all of the incredibly helpful feedback and the influence you have had on the work we do at Capture One. Let's keep this going.
Enjoy the new release and speak soon! :)
-
Thanks Brian. Capture One has always been good to me. I usually don't download new versions until after several updates have resolved the softwares bugs. I wasn't thinking straight. That is why I'm glad I found where the community part of the support was to be here reaching out. Thank you once again Brian.
0 -
VaL Happy to help! :)
1 -
> 16.1, 16.2, 16.3, are all major releases. Within a release are 16.1.1, 16.1.2, 16.1,3, etc.
Sorry for visiting thread so late, but a correction is necessary - I don't know any versioning standard which would make the above true: these are commonly minor releases. Major would be 16, 17, 18...This totally makes for an interesting legal question if "old" permanent license holders (with minor upgrades included) are supposed to get all subsequent minor versions or not. Previously it was a clean cut - new major version stopped upgrade cycle for the permanent license owners regardless of how long they had this license (between a month and a year). Refusing upgrade to next minor would need a very precise basis in the license used a year ago.
0 -
You call this a major release, then why not number it 17.0? Immediately clear to those that bought a perpetual license somewhere during 16.x.x that this is not included in their license apart from some last month(s) discretion on your side.
By the way, I was thinking about it, too. Why not name the major annual release with significant changes 17.0 and begin to develop it within a year? That's logical. But the reason and logic, which cost only the name 16.3, and even removed the name 21, 22, 23 - is not clear. From my point of view, this creates more confusion for users. Imho.
0 -
That's it. That's all these version nubmers mean any more. You can't mark a "big" release by the first number changing. It's fairly clear that Capture One is NOT doing it that way any more. To us customers, that should be no big deal. Judge the book by its content (by what new features it has), not by its cover (the version number).
Okay, thanks for the explanation. But I'm a developer in the past. And from experience, I can say that there is a generally accepted logic for numbering releases in the field of software development. The point is that while some small functions are being finalized, the release has the numbering "release number. number-1. " If this is a correction of only code bugs, then usually number "release number. number-1. number-2. " As soon as significant cumulative changes and innovations appear, the main release number itself changes. The addition of AI masking tools still seems to me more like a significant and decisive change. Thus, if you had given the title to Release 17.0, it would have been understandable, logical and not questionable for most users. But when you called a significant release as some kind of ordinary addition small functions, it causes confusion among users. But to decide on the release number, of course, to you. :-)
1 -
Technically in simple terms, minor releases are for features, that don't break things, meaning that in Capture One's case you could work with sessions created on 16.x on any other 16.x version, earlier or later. If files or sessions stop being compatible, this is a sign of major release.
0
Post ist für Kommentare geschlossen.
Kommentare
36 Kommentare