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 20 prompts for C1 12

Comments

14 comments

  • Jerry C
    Hummm. Others report, C1 12 conflicts with C1 20 and should be removed. There seems to be an unending number of oddities with this update. I filed a support case related to a very odd upgrade event, my not having to enter the activation key when I installed C1 20 -- it just upgraded my beta version without asking for the key. After many days, C1 support gave me some generic hints unrelated to the key non-requirement issue and noted they were inundated with installation and upgrade questions.

    Jerry C
    0
  • Permanently deleted user
    How are you starting Capture One 20? From the Dock? Did you delete the icon from the dock when you removed Capture One 12? My guess is that the item in yout dock may be pointing to Capture One 12. It is easy to determine if that is the case... when Capture One 20 is running do you have two Capture One icons in your dock?
    0
  • Permanently deleted user
    It dies nit matter how I start C1, from the Dock, the Applications folder or by clicking on a library file, it always prompts for Capture One 12.

    I removed the icon fron the Dock and recreated it. First by selecting “keep in Dock†while Capture One is executed and then by dragging C1 from the Applications Folder to the Dock. I also tried to remove the C1 files in the “Applications Support†Folder to start with a clean set of settings.

    I am still not sure, if the dialoge promoting for C1 12 is initiated by the Operating System or by Capture One itself.

    What might be related: I started C1 12 once after I installed C1 20, because I wanted to open a library without concerting it to C1 20, but now my libraries are converted.
    0
  • Ian Wilson
    Moderator
    Top Commenter
    AlexJ wrote:
    It dies nit matter how I start C1, from the Dock, the Applications folder or by clicking on a library file, it always prompts for Capture One 12.

    I removed the icon fron the Dock and recreated it. First by selecting “keep in Dock†while Capture One is executed and then by dragging C1 from the Applications Folder to the Dock. I also tried to remove the C1 files in the “Applications Support†Folder to start with a clean set of settings.

    I am still not sure, if the dialoge promoting for C1 12 is initiated by the Operating System or by Capture One itself.

    What might be related: I started C1 12 once after I installed C1 20, because I wanted to open a library without concerting it to C1 20, but now my libraries are converted.

    So (sorry to be apparently doubting your competence!) are you absolutely sure that when you start it from the applications folder, you are choosing Capture One 20?

    Ian
    0
  • Permanently deleted user
    No problem. I know, that it is sometimes hard to see your own mistakes! And thanks for your help!

    But, yes I am sure, that I selected Capture One 20. I first noted the bug after removing C1 12, so that it was not present in my Applications folder. After reinstalling C1 12 I can provoke the bug by renaming the C1 12 application bundle before starting C1 20, I tried this several times.

    In an other thread I found instructions on how to completely uninstall old C1 versions. I will try this out when I am back at home, probably tonight or tomorrow night.
    0
  • Permanently deleted user
    Another thing to try...

    Select your catalog and cmd-I to show info. About 1/2 way down on the page is "Open With". Click the disclosure triangle to see the data if necessary. Ideally it will say "Capture One 20.app (default)". If not change it to Capture One 20.app and click on the Change All button.

    I don't know if that will make a difference when clicking on the Dock icon, but it may be worth a try. It should do the right thing when double clicking on a catalog.

    Marc
    0
  • Permanently deleted user
    Thanks for this tip, I will try this too!

    Uninstalling the old versions of Capture One, as mentioned in the other thread did not help.
    0
  • Permanently deleted user
    marchyman wrote:

    Select your catalog and cmd-I to show info. About 1/2 way down on the page is "Open With". Click the disclosure triangle to see the data if necessary. Ideally it will say "Capture One 20.app (default)". If not change it to Capture One 20.app and click on the Change All button.
    Marc


    I checked this out, but it was already set to Capture One 20.

    I will open a support case and see, if Phase One as any idea...
    0
  • Permanently deleted user
    Today I updated to C1 20.0.1, but the problem persists.

    Currently I am a litte bit anxious to use C1 20, as I am not sure if it somwhow uses parts of the C1 12 libraries and will corrupt my library.

    I opened a support case with Phase One, but there only reply was, that C1 currently does not support macOS 10.15.2. I informed them, that the problem also occured with 10.15.1, but no reply to that...

    I can not say, that I am overly pleased with the "10.15.2 is not support answer, for me this only seems to be a way to get rid of the customer as fast as possible. At least I would have expected to learn, if this is a known issue.
    0
  • Permanently deleted user
    Have you tried to reset the permissions of your system ?
    What you describe sounds like the system not being (internally) "authorized" to take action.

    Here is the official procedure:

    https://support.apple.com/en-us/HT203538

    That said, MacOS Catalina is not (yet) the most stable system ever - so problems could pretty well originate from Apple.
    0
  • Laurent Fabre
    I had the same problem last year and just now with the update to Capture One 20. I don't think it's a bug related to the system but with Capture One. It's like it is looking for a component, maybe from a preference file that as been deleted with the old version of Capture One.

    I solved this issue by selecting the Capture One 20 Application in the dialogue box asking for the Capture One 12 version.

    LF
    0
  • Permanently deleted user
    First, thanks again for your help. I tried to reset the permission, but this did not resolve the issue.

    Today I did a little bit of testing using fs_usage and indeed, the Capture One 20 process is accessing the Capture One 12 application files, when they are present. So I agree, that this is most likely a problem with C1 and not the operating system. I will try your approach and select C1 20 when prompted for C1 12, even though I have a bad feeling with these „tricks“.

    When this is a known problem for some time, the answer of the support team was not very adequate...
    0
  • Permanently deleted user

    In case someone else has the same problem, today I found the solution to by pure luck:

    In the ~/Library/Scripts/Capture One Scripts folder was an Apple Script, that had the clause "tell application "Capture One 12". The script was not executed, its presence alone was enough to get the prompt for Capture One 12 when starting C1.

    To not break existing scripts I suggested to Phase One, that the version number is removed from the application name.

    Alex

     

    0
  • Jerry C

    I have a script with the same clause referring to C1 12. I compiled it for C1 12, but it still works with C1 13 as originally written. The script is executed after C1 has loaded by selecting it from the script drop down. It has no effect on loading C1 13.

    How to explain both of our experiences. Perhaps the "tell application" command is superfluous if C1 is already running before the script is executed, but might try to call for C1 12 if it is a script that runs before C1 is loaded. Is it possible your script is being run before the program is loaded?

     

    0

Post is closed for comments.