Capture One becomes unresponsive when editing keywords
When renaming, moving or deleting a keyword in the Keyword Library, Capture One becomes unresponsive for about a minute. It only takes this long the first time a keyword is renamed, moved or deleted after Capture One has been launched, additional changes are much faster.
Does anyone else see this?
(This is with a catalogue containing a little less than 40,000 photos and quite a lot of keywords. Capture One 13.1.2.37; macOS 10.15.7; MacBook Pro 2,9 GHz Quad-Core Intel Core i7, 16 GB RAM.)
-
I see this too and I am not surprised by the behavior. When a keyword gets changed, C1 has to go through all of the pictures with that keyword and update. This takes a while. When you change another keyword, the database and files are mostly likely already in the cache so the operation will be faster. That’s pretty normal behavior.
That’s my theory as a software developer. I may be wrong though.0 -
Thanks for your reply.
As it also happens when editing keywords that haven't been added to any photos, I don't think that explains it.
0 -
If the Keyword is in a keyword file but not associated with an image it would suggest that it cannot be in the cache that Hans mentioned and so another search would be required to see if something had added it since the cache collection was created.
It might be better to edit the library directly where unused keywords are concerned. Or, if they are part of a standard keyword library file obtained on line, leave them as they are supplied since, presumably, the compiler of the Library saw some value in having the word in the content.
On the other hand if you have a Keyword library which is mostly redundant and you have already used the words you are likely to need from it, then just get rid of it. It will have performed its service and the KWs will be in the edit information for the images so you will retain only the words you need and have used.
Could that be an option?
0 -
I'm sure there are other useful ways to handle keywords. I mention this as it's something that resembles a bug or at the very least a weakness in Capture One.
0
Post ist für Kommentare geschlossen.
Kommentare
4 Kommentare