Another read-only issue
I have an issue with read only files. I ll explain shortly my workflow and the issue.
I do fashion photography on location , I do tether shoot or import my pictures to macbook with os-x sierra.
I open a session for the job, and shot each dress to a new folder inside session. And I take a backup to my external HD. When I came back to studio I upload the session to my NAS. And use my windows 10 computer to edit the pictures. This is my workflow for over 10 years since captureone 3 times.
Now the issue is: After c1 9.x upgrade it start to make some pictures read only inside the session, with the little eye icon on the corner. To solve the problem what I have to do is shot down C1, delete the Captureone folder inside the folder and reopen C1 and let it make new previews and if the files are EIP, which they are usually the situation is more worst, I have to unpack all and proceed the procedure. Some times I have to do it to more then 1000 picture and unpacking takes too long.
If somebody have a solution about the issue it would be very helpful.
I do fashion photography on location , I do tether shoot or import my pictures to macbook with os-x sierra.
I open a session for the job, and shot each dress to a new folder inside session. And I take a backup to my external HD. When I came back to studio I upload the session to my NAS. And use my windows 10 computer to edit the pictures. This is my workflow for over 10 years since captureone 3 times.
Now the issue is: After c1 9.x upgrade it start to make some pictures read only inside the session, with the little eye icon on the corner. To solve the problem what I have to do is shot down C1, delete the Captureone folder inside the folder and reopen C1 and let it make new previews and if the files are EIP, which they are usually the situation is more worst, I have to unpack all and proceed the procedure. Some times I have to do it to more then 1000 picture and unpacking takes too long.
If somebody have a solution about the issue it would be very helpful.
0
-
Tolga wrote:
I have an issue with read only files. I ll explain shortly my workflow and the issue.
I do fashion photography on location , I do tether shoot or import my pictures to macbook with os-x sierra.
I open a session for the job, and shot each dress to a new folder inside session. And I take a backup to my external HD. When I came back to studio I upload the session to my NAS. And use my windows 10 computer to edit the pictures. This is my workflow for over 10 years since captureone 3 times.
Now the issue is: After c1 9.x upgrade it start to make some pictures read only inside the session, with the little eye icon on the corner. To solve the problem what I have to do is shot down C1, delete the Captureone folder inside the folder and reopen C1 and let it make new previews and if the files are EIP, which they are usually the situation is more worst, I have to unpack all and proceed the procedure. Some times I have to do it to more then 1000 picture and unpacking takes too long.
If somebody have a solution about the issue it would be very helpful.
Have you created a Support Case to discuss this problem directly with the Phase One team?
Do you think the problem is in some way connected to changes in the operating systems used - perhaps Window 10 has some differences? Or maybe an OSX update at some point introduced some conflicting differences?
Your description of the problem makes me wonder if for some reason the thumbnail files are being opened as if they are the original images - or rather C1 for some reason is attempting to open the thumbnails for edit and failing.
Does it only fail after you have uploaded the session to the NAS?
If your original files on the Mac are stored as EIS file are you shooting with a Phase One system?
Grant0 -
SFA wrote:
Have you created a Support Case to discuss this problem directly with the Phase One team?
Yes I did and the answer was:0000FF:3hsx55n7] "First thing I want you to do on a new session is go to Preferences > Image and enable "make new files writable by everyone." This is particularly helpful for controlling EIP permissions where you have had significant issues." I ll try, but doesn't sound to me that ll solve the problem because the problem is not on all folders just some, and it is not always on EIP files some times also on CR2 files, and when a folder is affected all files inside became read-only .
Do you think the problem is in some way connected to changes in the operating systems used - perhaps Window 10 has some differences? Or maybe an OSX update at some point introduced some conflicting differences?
No, it looks to me more that the session get corrupted.
Your description of the problem makes me wonder if for some reason the thumbnail files are being opened as if they are the original images - or rather C1 for some reason is attempting to open the thumbnails for edit and failing.
Yeap thats also what I thought, but I delete all CaptureOne folder where all the tumbnails and settings are, and let c1 regenerate new previews, that still doesn't solve the problem.
The best way I found is to copy the folder with that issue outside session folder, delete CaptureOne folder, then delete the folder inside session and import again the pictures to a new folder inside session. Even when I copy the folder outside session and check the pictures at c1 library they look ok I can just copy them to a new folder inside session. That why I m thinking that the corrupted is the session not the files. 3hsx55n7]
Does it only fail after you have uploaded the session to the NAS?
FF0000:3hsx55n7]I always work from NAS, I don't have any job inside my computer. My computers are just to work, storage is always NAS. 3hsx55n7]
If your original files on the Mac are stored as EIP file are you shooting with a Phase One system?
FF0000:3hsx55n7] No I sold my Phaseone system last year I was shooting with Phase One more then 5 years now I m on Canon. EIP files are just like zip, it is a way that c1 zips your raw file and setting to one file, that's good u dont lost your setting when u transfer your file to another location and is faster to transfer or backup eip then transferring raw and some 1-2 kb setting files. 3hsx55n7]
Grant0 -
From your description should I understand that you always use the same Session to shoot to?
Or maybe set up the session from the same saved Session format file?
If so, what happens if you start with a fresh new session? Is the problem still there?
I think the concept of sessions really works best if each shoot has its own session. That's how I work with my event photography activity.
However I also keep some sessions that collect similar activity over time - especially for random shots or some forms of experimental activity.
I'm a Canon user. I do not often work with EIP files.
The only time I have seen a session based problem was related to an edit file (.cos) in V6 or V7 days. The .cos file looked OK but the preview and thumbnail showed some issues that turned out to be affecting the application causing it to hang randomly. I suspect a bad "write" somewhere had messed up the internal operating system links to the on-disk file parts mapping references. (This was using Windows but there is no reason to suppose something similar is impossible on a Mac.)
In my case it affected a single session of several thousand files. When I finally saw the problem preview and discovered I could not make it work correctly I deleted the .cos file for the image and created a new one and the problem was solved.
That seems to be quite close in terms of actions to what you have discovered in your own experiments with copying folders out of the session and back into it. On that basis I think your feeling that the session data is the basis of the problem is likely to be correct. However, if the problem is folder based (some folder are OK, others not) it may be possible that the "problem" folders are not actually the problem in the same way that the images that would "hang" in my session were the innocent "victims" of what I think was a bad internal reference for an unrelated file.
I assume you have tried the session verification process? That would not necessarily find the problem of course. Some things are not easy to predict or thought so unlikely that time spent writing and trying to test the code (how could one do that?) would be wasted. Nevertheless it should be tried and I assume that Support have covered that with you?
HTH.
Grant0 -
SFA thanks for your answer.
But no I don't use same session. Each job has is own unique session. Always at beginning of the shooting we open a new session.
I think there is some bug or something, that the session becomes unstable. Anyway thanks for your answers.
Regards0
Post is closed for comments.
Comments
4 comments