Trying to fix the C1 mess... unbelievable
Just to get an idea of how convoluted the C1 perspective is, and how badly the software needs a rewrite, just have a look at the process one needs to go through to simply uninstall/reinstall the program. This is NOT normal. All this just to troubleshoot a recurring Capture One log error, to which the support response in an email began, "Hi there,I cannot tell what is going wrong from these messages as they're largely unknown errors."
https://support.captureone.com/hc/en-us/articles/360002402377-How-to-uninstall-Capture-One-
Just resetting preferences, which are cached by a background daemon, requires running Terminal commands. Huge FAIL.
-
But I don't think it's Apple's fault that you can't reset C1 by manually deleting .plist files. I can do that with every other application on my machine.
0 -
Deleting plist files MAY work on other apps. User preferences are cached and depending upon what you are doing the cached version may be used and re-written to the new plist file. It's been that way for several OS releases.
If you don't like firing up a terminal then grab the app named AppCleaner => https://freemacsoft.net/appcleaner/
Use it to remove your app. You can drag/drop or use File -> Open to select the app to delete. App cleaner will also find related files to delete along with the App bundle. I just ran it for Capture One 20 (you are given the option to cancel or actually remove the app). If took a minute or two but found 3 GB worth of stuff to delete including the app, logs, Application Support files, crash files, etc.
1 -
Marco Hyman
— " If you don't like firing up a terminal then grab the app named
AppCleaner => https://freemacsoft.net/appcleaner/"
That is the app you suspected to be the cause of the problems I
had recently with CO! …and it was, CO runs way better now!0 -
Your issue was with something named CleanApp. CleanApp is NOT AppCleaner. I've yet to have an issue with AppCleaner and have been using it for quite a while.
0 -
Sorry for the wrong intrusion, Marco!0 -
I can't comment on Macs but on Windows I can choose to install at an existing location or simply create another installation in a different folder. So far doing that seems to have worked well.
Whether that comment would continue to apply if I then decided to uninstall and tidy up some of the older but recent installations I'm not so sure.
There is no way I would suggest anything other than the process that C1 recommends for an official installation/update if I was in their position. The recommendation should be a safe approach and, realistically, may be the only safe approach that can be suggested whilst still avoiding end user self generated problems that turn into accusative support nightmares.
It is also, at least in theory, an opportunity to undertake some regular "housekeeping" .
As a personal decision I will happily stay with what I do (using Windows 7) for as long as I have no problems. Windows 10 may change my approach if it does things differently. I am not expecting to have to learn the ways of Macs.
0 -
@Rob This is entirely an Apple OSX issue. Nothing Capture One can do about it. There is an operating system process that runs in the background that caches .plist files, if they are removed or corrupted, it puts them back.
In some circumstances OSX doesn't have a cached version of the ,plist file (if you haven't run the application since the Mac was last booted) or if you reboot immediately after deleting the .plist it may npt have chance to replace the file. So you and I as users, can somettiimes get away with manually deleting the .plist file. For C1 and other applications.
The later versions of OSX are harder to get round than the earlier versions. One reason I am still on OSX10.14
Absolutely nothing Capture One or any other SW vendor can do about this, this behaviour is part of Apples security system for OSX. "Thou shall not delete or modify a .plist file that doesn't belong to you"
0 -
Sounds like a "Reset Preferences to Defaults" menu item would be a much better option than sending people in to run Terminal commands. Or an uninstall script for crying out loud. You get my point.
3 -
I've done some research and found that my last post was not completely correct. Here is a better, more correct explanation.
See also a post from the Eclectic Light Company
From OSX version 10.9 onwards, Apple has introduced a background process, cfprefsd, which caches the preference files (this is not security feature - it's purpose is to improve application performance).
This background process copies the preference file to memory the first time that the application is opened in a session. At some point determined by the application developer, it may write the preference file back to disk (that won't help us).
If you want to delete the preference file you have these options:
1) Delete the preference file with Finder or Terminal before it has been cached - i.e. after the account has been logged off (or after a reboot) and logged on, and before Capture One has been run. (This is simple but only works under the certain conditions)
2) Use Terminal to access the defaults command, which handles both the cached and disk version of the preference file. This is more complex, but always works. This is the method recommended by Capture One.
defaults delete ~/Library/Preferences/com.phaseone.captureone13.com
Robs idea of a reset defaults button would save some hassles. I will try to write an Applescript for this.
2 -
A rewrite is required for Win 10, the instructions appear to apply to earlier versions of Windows and pre version 20 versions of Capture One.
Dave
1
投稿コメントは受け付けていません。
コメント
11件のコメント