Saltar al contenido principal

⚠️ 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 2

Comentarios

7 comentarios

  • Okular

    It seems you have copied the software while C1 was open on the iMac. This will create a file called "writelock" in the C1 directory. Search for it on the MacMini and delete it.

    0
  • Nikon Shooter

    See if you could open in a session instead of a catalogue.

    0
  • FirstNameStanley LastNameWaterman

    I can open a new session but even if I change the name of the catalog which contains ALL my images, it still tells me that "original" name of the catalog has been opened my me elsewhere therefore I cannot open it!

     

    0
  • Nikon Shooter


    I only use sessions but was hoping…

    0
  • Permanently deleted user

    A somewhat common problem.  When Capture One opens a catalog it creates a lock file.   The lock file indicates that the catalog is in use.  It is removed when Capture One is shut down normally.  Getting this error when you are the only one using the catalog indicates that Capture One crashed or the computer was shut down while Capture One was running or something similar.  I'm guessing you copied the catalog while Capture One was running so the lock file was copied, too.  In the future don't do that.

    Fixes:  The easiest it to remove then re-copy the catalog making sure Capture One is not running on the source machine.  If you don't want to do that you can manually delete the lock file.

    • Quit Capture One.
    • Open a Finder window.
    • Navigate to the folder containing the Capture One catalog.
    • Right click on the .cocatalog file and pick Show Package contents.
    • Remove the file named "writelock".
    0
  • Nikon Shooter

    "writelock"!!!

    Learning every day. :P

    0
  • FirstNameStanley LastNameWaterman

    Many thanks to all who offered suggestions.  I'd forgotten about 'Writelock' — had the same issue a couple of years back.  The issue is now sorted!

    0

La publicación no admite más comentarios.