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

Session(s) Trash - Empties, but it seems to have to re-empty

FirstName LastName

I use sessions. I empty my session trash, per session. But, it seems like it re-empties it. E.g., just emptied session trash for a shoot yesterday with approx 2800 images in it. When it went to empty session trash, though, it ran through emptying a little over 14000 images, which corresponds to the total number of photos that I've trashed since January 1, 2022, when I re-started from scratch.

0

Comments

6 comments

Date Votes
  • SFA

    Have you in fact emptied the system trash, not just the particular session trash?

    0
  • FirstName LastName

    Not sure what you mean by “system trash”. Certainly have emptied catalog trash (nothing there). Hadn’t emptied the Trash Bin recently until today. If a image file were moved into the system trash bin and that hasn’t been purged, will it continue to want to be emptied by C1? I guess I may find out next session.

    0
  • gb

    You refer to C1 Catalogs and Sessions at the same time.
    Which are you using?

    0
  • FirstName LastName

    I use both (I eventually import sessions into a catalog). But with respect to trash, I'm talking about session trash and only session trash for each session. I empty the trash from each session when I'm done with the culling and editing. I pretty much never have anything in my catalog trash.

    The behavior I am describing happens when I empty session trash. Last night, I emptied the system "Recycle Bin", per the suggestion above. I will see whether that solves the problem when I work on my next session.

    0
  • FirstName LastName

    Alas. Nope.

    Totally emptied system Recycle Bin. All prior sessions had nothing in session Trash. Created new session and imported photos. Put 734 photos in session Trash. When I emptied session Trash, Capture One went through 4408 photos--which I believe might have been the sum of the prior two session's trash plus this session.

    The good news, I guess, is that it wasn't 14000 again. It's just a weird behavior that doesn't make sense--and consumes time.

    0
  • gb

    Agree, weird.
    The whole point of sessions is that they are meant to be independent of each other.

    0

Post is closed for comments.