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

Capture One Pro 20 (SONY) Crashes When Importing Sessions

Comments

5 comments

  • gb

    Are you opening a session which is on the external disk or are you importing images from the external disk into a session on an internal drive?

    0
  • Danny Burns

    First I tried just importing the session which is on the external SSD. When that failed, I tried just importing the images from the session folder on said drive. Both methods fail, repeatedly.

    On my Mac, this seems to work fine. I'm only experiencing this issue on my PC.

    0
  • gb

    Doesn't really solve the problem but you could just copy/paste the session folder from the external to the internal drive and open the session .cosessiondb from there.

    0
  • SFA

    Danny,

     

    Just for clarity ...

    When you write "session" are you referring to importing an existing Capture One "session" to another session or a catalog or are you referring to a "shoot" whereby the images are failing to import to either a C1 Session or catalog?

    Or something else entirely?

    Your description sounds like a data problem of some type or maybe a compatibility issue but without being certain to understand the process you are following offering any suggestions.

     

    If the external SSD does indeed have a C1 Session that you are importing are you perhaps moving it from Mac to Windows via the external drive? Or something else?

    0
  • Danny Burns

    SFA,

    The session is an actual Capture One session, from a shoot on my laptop, saved on an external SSD drive. I bring that session to my PC (desktop) and try to import the session into an established catalog. This is where the first failure happens. When trying to import the session, Capture One crashes.

    The second failure happens when I try to import the images from the session's capture folder into the catalog.

    I will add... this only happens on my PC version. The Mac does not have this issue.

    0

Post is closed for comments.