Minor upgrades are sooo painnnnful
Implemented
Dear CaptureOne team,
You could simplify minor upgrades. The process is annoying. All few weeks C1 alerts, there would be an upgrade. If I ignore the message it comes again the next time I start C1. This is fine, because I wouldn't want to finally forget about an upgrade that might be important for me.
But is this upgrade important? I don't know. There is no release note with a bugfix and feature list around. At least it can't be found, when following the normal alert-download-install process.
So, I click download in C1.
Now I am in the browser. I need to look up my password with Capture One ...,
then log in.
I click "Go to downloads"
I click "Download" again
I run the downloaded Capture One Setup
Confirm that I am using English
I receive error message "Setup has detected that Capture One is currently running. Please close all installations...", because the installer wouldn't close C1 automatically although I just started the installer and it is clear that the outdated version needs to close.
By the way, nothing tells that the outdated version would be upgraded and cannot stay in parallel in case I would need to keep it for instance for file exchange with another user on another system. Happily I don't have such need. I want the old version to be overwritten.
I go to the running C1 instance and close it.
I return to the setup and click OK.
I confirm that I accept the license agreement (although I did it multiple times and my license did not change since I am on C1 20).
Next > Next > Next > Finish
Now the new C1 build is installed, but at most updates (3.2.2. being my first exception) for each and every Session it will ask whether to update it, although I don't have the old build anymore so that I could avoid the update. I also can't chose "Yes to all" Sessions which I may open in the future. And finally I will manually delete all the Session backup files:
I start click the cosessiondb to open the session.
It asks "Do you want to upgrade the session Capture One?" I click Upgrade.
It works quite a while on all the updates.
I do some smoke testing whether I can still work with the Session. As always I can. No flaws.
I go to the Session's folder in Windows Explorer and delete Capture One.cosessiondb.backup .
This time, build 3.2.2, the cosessiondb file format did not change. I am getting around all the updates.
On the startup splash screen on the WHAT's NEW tab it shows "Click and it's gone" - "Watch this quick tutorial on our new heal and clone tools...". Is this really new again in 3.1.2? I enjoyed the big improvement in 3.1.1.31 already. Let's see whether again something changed. I click "Watch now". I sends me to https://nag.captureone.pro/pro/whats-new/clkn/https/learn.captureone.com/webinars/new-healing-tool-in-capture-one-20/?utm_medium=nag&utm_source=capture-one-pro&utm_campaign=latest-version&language=en&remainingTrial=-1&variant=3&version=13.1.2&isTrial=False&shopRequested=False .
The browser returns "We're sorry, but the link you followed appears to be invalid."
Same happens when clicking "Explore new Styles".
So also from the startup splash window I do not see anything that changed with this new build 3.2.2.
Dear C1 team,
We are in the age of CI/CD (continuous integration/continuous delivery) which generates faster and much more updates than in earlier times. So, also updates on client devices are becoming more and more automated and silent. Users would normally just confirm the standard update policy and everything would happen automatically unless they opt out from the automation.
Thanks
Peter
-
Speaking very personally I find Major upgrades as well as minor upgrades on many of the CI/CD apps on mobile devices entirely eliminate my potential use of the application with no response at all from reports of problems made to the vendors.
Courier companies introduce unnecessary "New and Improved" applications that do the same as the previous one - but not on devices running OS versions more than 1 release old.
Banks push their latest Mobile Banking Apps without bothering to mention that it probably won't work on most devices.
Virus "Track and Trace" apps only work for populations with the latest and greatest tech.
"Agile" seems to provide Microsoft and Apple with plenty of continuous new opportunities to disrupt their customer experiences in much the same ways.
I have never know there to not be a set of Release Notes for any Capture One release - usually mentioned and linked in the emailed announcement and certainly linked from the support pages on the web site. Running a proper check on what I am likely to discover seems very possible. Not so the last time I was allowed to update a Banking app with no way to revert to the older one.
Oh well, different experiences for different folk I guess.
0 -
@SFA: Existing bad examples of auto-updates of Web apps on mobile devices should not be an argument against a good automation for C1. Good automation is possible. And usually C1 is quite well tested before roll-out of a build.
If you for instance look at the Windows OS you almost wouldn't anymore be able to manage all the bug fixes and security patches coming your way without the standard automation, They all get installed automatically and silently if you don't explicitely opt out, create a lot of manual work for yourself and stay longer exposed to known security vulnerabilities. Also with Microsoft Office, today the majority of installations is auto-updated on Office 365.
But there can always be cases where the well tested automation brakes or where the use case is not the standard use case of a normal user and therefore the automation would hurt. To address these rare cases you probably noticed my closing sentance: "Users would normally just confirm the standard update policy and everything would happen automatically unless they opt out from the automation."
I do agree with you that major C1 upgrades are even more of a hassle (searching and down-loading my license key to present it to the new major release ...). But I didn't want to go too far here.
0 -
Hi Peter,
Thank you for the post.
There are already several similar requests on simplifying the process of updating the software, so this one is taken on board as well.
Meanwhile, please refer to this article when planning to install the updated version of Capture One - How to update Capture One?
0 -
I forgot mentioning that after each minor upgrade I need to make the same customizations again to the toolbar, the set of tool tabs and the tools in the tool tabs - or live with the uncustomized UI. Also this is quite some effort.
0 -
Peter,
If you customize as indicated then you should save the Workspace with a unique name so that it remains available in perpetuity.
If you simply save the "Supplied on installation" "Default", for example, your modified "Default" will be overwritten by the next delivery of "Default" - and there will always be a next delivery of Default. From time to tome this may change format and so is the way that new features and changes are delivered.
Your own personal stuff is retained and ready for re-selection (and/or further modifications) provided you give it a unique name that is not likely to be used in the future for a "Standard" update direct from Capture One.
The same goes for any changes you have made to the Keyboard Shortcut definitions.
Some variables that you create during use of C1 are more volatile changing as you use the application and these are held in a User Configuration file. Normally these will also be discovered and used after an update or new version install. There may be times when some of the settings need to be changed or re-established because of operational or operating system related changes but mostly those things can be carried forward seamlessly and previous version of the file will be saved in case one ever seeks to revert to an earlier installation.
You should be able to avoid major disruptions, possibly to the point of no disruption at all although is changes have been made to workspaces and new tools have been added or existing tools changed and you wish to make use of the new stuff there may be a little adjustment required. Personally I think it is always a good idea to take a look at new Workspaces as defaults in order to see how they are presented and what they contain even if one then returns to one's original tailored versions of them.
1 -
Peter,
Referring back to your comment about Windows updates - yes I experience a the Microsoft message deluge for changes to Office 365 daily. I rarely use Office other than for email and the occasional dive into Word or Excel. But it comes as a business package and so I do what I need to do. Which is as little as possible since my need is low.
I have so far avoided Windows 10.
The beauty of Win 7 is that it has been quite mature for some time and the updates slowed to a manageable rate such that if anything when awry after a handful of updates one had a reasonably good idea of which update might be the problem and could undo it, usually with no loss of amenity and a problem solved.
Part of the reason, of course, is that MS want it that way because it fits with the long term strategy of providing everything as Software as a Service and via subscription. No subscription, no access. Unlike the old days where, potentially, one could simply keep old systems running as required, off line so reduced or no obvious security risks, and doing what you needed them to do without further monthly costs (whether used or not).
I think the availability of Licence key management activity is C1 is simpler and more accessible than I find it to me with MS products despite their re-seller's best efforts to provide a similarly comprehensive and self managed system. Is it possible that you have missed some options that have been introduced with recent releases?
It sounds to me like you may have missed a few of the recent process changes that should make the process quite seamless considering the options for activation on multiple systems that one can control should one need to do so.
Might it be worth revisiting the process to see if your use of it can be made more comfortable?
0 -
Thanks SFA for the hint to store a custom named Workspace. I missed that one.
0
Post is closed for comments.
Comments
7 comments