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

File seen as read only

Comments

2 comments

  • Paul Steunebrink
    If you run a catalog, you could move some images to your internal disk or inside the catalog for testing. Same with a session, actually.
    If it still does not work, I would make a new session/catalog and try with both internal/external images.

    Have not tried the 10.10.3 beta yet, so no experience with that. You are running CO Pro 8.1.1?

    By the way, is there any indicator in the image, like an Offline sign in the viewer or a pencil with red line in the browser?
    0
  • Peter Sidell
    I believe I have solved the problem - at least in part.
    First the images do indeed have the pencil with the red line indicating read only. Yes I am running C1 Pro 8.1.1
    When I went back and looked at the external drives I have been using i discovered I actually have more than one copy of the catalog that was giving me problems.
    I found what appeared to be the most recent catalog on the hard drive where I had originally imported the images. When I opened that catalog none of the files showed read only.
    Next I transferred that catalog file to the other drive - my archival drive - and after opening it and then pointing it to the locations everything, including the ability to process seems to be working just fine.
    My guess is that I had modified something in the metadata or processing recipe of the files marked read only which caused the older catalog to consider them read only. Somehow the metadata and precessing recipes were out of synch (my guess.)
    I tried the synchronize option in the library module with the older library and that didn't help.
    I don't know if there is another way to recover from that kind of mistake.
    Obviously I need to keep my catalog files better organized and synchronized.

    One thing I did find confusing is that some of the old versions of the catalog were in dated folders that also contained folders labeled: cache and originals.
    Interestingly the library file that worked didn't have those associated folders.
    0

Post is closed for comments.