Skip to main content

Sessions: "The selected image is either unavailable...



  • SFA
    jdmuys wrote:
    I created a session yesterday, worked a bit in it. I created half a dozen albums, dispatched my photos in them, and stared my photos. Then I quit. No problem.

    Today I open the session again, and all photos are marked with a big question mark instead of a thumbnail.

    When I select any photo in any of my albums, I get the message:

    "The selected image is either unavailable, in an unsupported format, or corrupted"

    Why doesn't C1 tell me which of three it is? It knows whether it found the file at all, which type it is if found, and whether it managed to read it!

    Right-click, "Locate in Finder", tells me

    "The original file cannot be found. This image is offline and its file is not available on disk. To view it in the Finder, please plug in the disk containing the file or relocate the file."

    So it was the first case. The file is not available.

    However, when I look in the Finder, my photos are there where I left them yesterday.

    How can I see where in the file hierarchy Capture One Pro is expecting my photos to be?

    This was my first time using a session. What a cold shower!

    Are your files on an external drive?
  • jdmuys
    No, all files are on my internal drive. That's the idea for using a session actually: to edit this jo on the move, with the intent to move everything back in my usual big external hard drive when done.

    Looking around, I found some additional info.

    Important to note:

    I created the session inside the directory where all my raw photos were located, and then I Imported them into the session main directory (as I couldn't find an option to leave the imported photos at their original locations).

    This is why the session file structure is the following, in my ~/Pictures directory:

    My session
    |My session
    ||My session.cocessiondb
    ||all my raw files, copied here by C1 when I imported all my photos in the session, choosing here as destination
    |all my raw files, from which I imported them into the session

    Note that I now realise all this is the result of my poor choices when creating the session...

    (I omitted above the "CaptureOne" directories created by C1).

    So I found the answer to my most important question, "how to find out where C1 is expecting the missing photo to be?": right click on it and select "Locate in Library", which will select in C1 the directory where the photo should be.

    In my case, C1 is expecting all my photos to be inside ~/Pictures.

    Yes, this is the parent directory of the session, even though I never did anything there. AFAICS, this is buggy behaviour, my weird and bad photo location notwithstanding.

    This also suggests a fix, to move the photos to ~/Pictures using the FInder, and to move then back using C1.
  • Ian Wilson
    Top Commenter
    Can’t you right click the folder where the images actually are (in the Library tool) and choose to set it as the Capture folder?

  • SFA
    Assuming all of your images are within the "Capture" folder under you second "My Session" sub folder under your "Pictures" library (if I have read your post correctly) just copy the second "My Session" folder and everything under it to the "Pictures" folder.

    That will take it out of the extra "My Session" layer (you may need to play about with some folder naming - hence the reason for suggesting copy for the start of the process.)

    Your overly incestuous likely commonly named folder structure is likely to be the source of confusion - I had something similar in my early days of using C1 when I chose to dive in without properly considering what I was doing and why it was so beneficial to take a little time to understand it (and the flexibility available) in order to work out the best working methods to suit my needs.

    Once you have something like "Pictures>My Session>Session folders plus the Session ".cosessiondb" file click on the .cossiondb file and that should open the session.

    You may have another .cossesiondb file with the same name somewhere and it may be that that you are trying to open.

    Alternatively just start again (Unless you have already performed a lot of edits). It makes for good practise I found.



Please sign in to leave a comment.