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

keywords not deleting

Permanently deleted user
  • Edited

Is anyone else having issues where keywords are not deleting. I found that there was an associated image in theTrash and once I emptied the trash the keyword successfully deleted, but it was a horribly frustrating user experience. Additionally I found that when associating child keywords to an image and then removing the child keyword the parent keyword would stay associated, also frustrating user experience. And lastly, has anyone else experienced keyword association lag? Meaning, you assign a keyword to an image and then create a Smart Album but keyword criteria is not found until you create the smart album then edit it and whala! it all it works. Love the keyword power in C1 but have found them to be extremely buggy on the Mac.  

 

Any tips would be helpful. Thanks.

0

Comments

4 comments

Date Votes
  • Permanently deleted user

    I found that when associating child keywords to an image and then removing the child keyword the parent keyword would stay associated

    That would be because they are separate keywords.

    FWIW, I for would be most unhappy if deleting a "child" keyword also deleted the "parent".

     

     

    0
  • Permanently deleted user
    • Edited

    Don't have much experience with keywords but as Shane says, no matter how much mothers and fathers your keyword-to-delete candidate has, they are all separated keywords. Killing a child is not the same as deleting the whole family.

    And the trash is just another folder to keep users happy who sometimes delete a bit too much. Like me, i.e..

    If you want to terminate the bloody files to never come back, three keys will act as terminators: ⌃⌘⌫ and poof, they rot in byte dust, that will teach 'em.

    I agree, the user experience of C1 is far away from "always a pleasure to use", but I also could list a couple of worse apps.

    0
  • SFA

    @j.McCarthy

    The point about C1 keywords is that they are dynamic within the current editing session (session or catalog).

    If a KW is embedded in an image (or associated with an image that is not currently selected  - say something filtered out or in the Trash  - basically the same situation - it will not be deleted. Sounds odd but in principle is exactly the right thing to do in my opinion.

    Add in that any KWs embedded in source files  - i.e. jpgs delivered from an external application or re-ingested files exported from C1 with KWs included - will always have those KWs embedded unless some other application is used to remove them. This obey's C1 current principle of never changing a source file.

    As for the "laggy" aspect. I think that can depend on circumstances to some extent. 

    Basically a smart album is a list of selected images held in memory. If you create new potential entries for the smart album the list must be refreshed in memory. A trigger action within the Smart Album selection is required to run the refresh. Constant monitoring might be a solution but may be somewhat demanding on resources.

    If you are seeing a situation where you feel the refresh has already been subject to a request within the Smart Album operation but has not been actioned then I would recommend reporting it to Capture One using the "Submit a request" option to open a Support Case.

    1
  • Permanently deleted user

    Thank you all for your comments :) Your insights have helped me understand the user experience a bit better. I appreciate your time. 

    0

Post is closed for comments.