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

Catalog Opens on PC, not on Mac

Comments

4 comments

  • Paul Steunebrink
    Key is whether the images in the catalog are fully managed (stored inside the catalog) or referenced. In case it is referenced, you could run into an issue that existed in CO7 and might still in CO8 (not tested recently).

    You could for a test create a catalog with a few managed images (inside) and see whether that makes any difference. That would provide some additional troubleshooting information.

    Hope to hear back from you.
    0
  • www.sedetweiler.com
    I will give that a try, but most of these images are not in the catalog as I have terabytes of work. My thought was to work on a few images from my mac when on the road. Should I move them into the catalog, work on them, and then move them back? Is that how this is supposed to work?

    Thanks for taking time to help me on this, it is one of the more frustrating issues I have run into.

    -sed
    0
  • Fredrik Timour
    I have the same problem. I have a catalog created on Mac OS X Yosemite (capture one 8 ). All the images are located in the catalog.
    Once opened on a PC (running windows 8.1 capture one 8 ) I can not open the catalog on the mac again. It says there is something wrong with the catalog.
    I run the verify tool and it says that nothing is wrong with the catalog, trying to open after verification result in same message about "unable to open catalog"
    0
  • PhaseoneUser55657
    I thought I remember a previous post and response that I through said that the catalogs are not comparable between a windows and max. You may want to do a search. But I thought the problem was that windows use a '\' for directories and the mac uses a '/' between directories. So while the PC can actually use a '/' for directories (Try is in cmd.exe), when it updates the db, the update changes them to a '\' which to the mac either means that character or 'escape' the next character and you get a really long file name.

    (OK, the next is a guess as I don't put any files in the catalog, but mine are all referenced).

    In the DB the mac puts a relative path to the image, (All directory names made up).

    /2014/11/16/file.dng -- file.dng in directory 16, in directory 11, of directory 2014, in catalog.

    Windows can read that, then updates the DB to the following

    \2014\11\16\file.dng -- file.dng in directory 16, in directory 11 of directory 2014, in catalog.

    The mac then tries to read the file and sees either:

    20141116file.dng -- file 20141115file.dng in catalog ---OOPS file not found

    or

    2014\11\16\file.dng -- file 2014\11\16\file.dng in catalog -- OOPS file not found.

    That is my guess as to what is happening.

    Verify would probably not find anything wrong, as it is checking the DB structure, while the application is actually trying to use the information and reporting that the expected files cannot be found.

    Please, take with grain of salt. It is my best recollection of a previous thread.

    Robert
    0

Post is closed for comments.