Keyword creation causes Capture One to hang & crash

Permanently deleted user

• 5. März 2017 01:35

I've just made five (5) attempts to create a "child" keyword in Capture One and each time, I've ended up with a the spinning beachball. The first four times, CO crashed and the fifth time I forced quit after about 10 minutes.

I've rebooted my iMac and also downloaded and re-installed CO - to no effect.

Any suggestions?

TIA

0

• 

  Permanently deleted user

  • 5. März 2017 10:17

  I may have a solution, and would appreciate comments from those better informed than me.
  
  It occurred to me that there may have been a problem with the keywords stored with the catalogue, so I opened the catalogue and exported the keywords to a text file. I made a couple of minor changes, saved the file and then imported the keywords text file back into CO. It now seems to work!
  
  Of course, I could be talking complete rubbish and it could be just a coincidence.
  
  Any thoughts anyone?

  0
• 

  OptionalAlias

  • 5. März 2017 13:28

  I've not used keywords that much yet but I have so far not experienced any problems.
  Did you use any special characters?
  What changes did you do in the text file?

  0
• 

  Permanently deleted user

  • 6. März 2017 00:10

  [quote="atenolol" wrote:
  I've not used keywords that much yet but I have so far not experienced any problems.
  Did you use any special characters?
  What changes did you do in the text file?

  
  
  To date, keywords have been ok for me - but not great. It's an area where Lightroom is still superior.
  
  As to my keywords, they're just names - people, places, things. No special characters.
  
  All I did was add a couple of people to my list, save, import and things were back to normal.
  
  Very odd!
  
  Regards

  0
• 

  SFA

  • 6. März 2017 00:30

  [quote="ShaneB" wrote:
  

  [quote="atenolol" wrote:
  I've not used keywords that much yet but I have so far not experienced any problems.
  Did you use any special characters?
  What changes did you do in the text file?

  
  
  To date, keywords have been ok for me - but not great. It's an area where Lightroom is still superior.
  
  As to my keywords, they're just names - people, places, things. No special characters.
  
  All I did was add a couple of people to my list, save, import and things were back to normal.
  
  Very odd!
  
  Regards

  
  
  If something odd had occurred in your original file at a specific point that was affected by the new KW you were trying to add might it have been resolved by re-importing which, presumably, has replaced what was in the KW library before?
  
  
  Grant

  0
• 

  Permanently deleted user

  • 7. März 2017 22:44

  Gidday Grant
  
  Yep - that's my assumption.
  
  Anyway - so far, so good.
  
  Regards

  0
• 

  Permanently deleted user

  • 9. März 2017 22:17

  The problem may not be with the keyword file but rather with CO being so slow in processing large scale changes to the catalog. I've seen cases where CO took many hours, even overnight, when I made a single change to the keyword hierarchy. I have found with experience that force quitting CO is a guarantee that the catalog will be unrecoverable the next time you launch CO. If that happens, you need to delete the catalog and replace it with a backup - either from Time Machine or a clone. That in itself can take a few hours for large catalogs. The spinning pizza and the fact that the dock indicates application not responding is not conclusive. Leaving CO alone has allowed it to complete its tasks and eventually return to normal operation. You can't hide CO while it is in this state. But you can bring other applications to the front by choosing them from the dock. So it is possible to do other work while CO churns.

  0
• 

  Permanently deleted user

  • 9. März 2017 23:53

  [quote="FredK" wrote:
  The problem may not be with the keyword file but rather with CO being so slow in processing large scale changes to the catalog. I've seen cases where CO took many hours, even overnight, when I made a single change to the keyword hierarchy. I have found with experience that force quitting CO is a guarantee that the catalog will be unrecoverable the next time you launch CO. If that happens, you need to delete the catalog and replace it with a backup - either from Time Machine or a clone. That in itself can take a few hours for large catalogs. The spinning pizza and the fact that the dock indicates application not responding is not conclusive. Leaving CO alone has allowed it to complete its tasks and eventually return to normal operation. You can't hide CO while it is in this state. But you can bring other applications to the front by choosing them from the dock. So it is possible to do other work while CO churns.

  
  
  Thanks, and all good advice. However, in this case CO crashed after a few minutes. Force quitting (which I would only do as a last resort for the reason you cite) wasn't an option.
  
  That said, at the moment I seem to have solved the issue. It shouldn't be an issue and Phase One really needs to do some work on catalogues etc, but it is what it is.
  
  Regards and thanks

  0

Post ist für Kommentare geschlossen.