My Capture One Pro 7 is Down!
This is ridiculous. Out of nowhere, CO7 is completely screwed up. The first symptom was that when I attempted to export, it dropped an unreadable tiff onto my desktop accompanied by an even log.
I read some inconclusive stuff about old workspaces and ditched all but the critical ones.
Currently, if I open a session and attempt to export a window pops up saying:
"The Specified output location is a read-only loaction" Please change the permissions on the specified output loaction or choose a location that you can write to and try again."
Click <OK>
A new window pops up stating: "Some of the selected variants are read-only. 5 of the selected variants are read-only variants. The process history of read-only variants will not be saved" <cancel> or <OK> are the only options.
The third window that comes up (and this one is starting to come up even if I don't attempt to export):
Session Save. Cannot save session to path: /volumes/xxxxxxxxxxxxx
"The session file is not writable. Try to change the session file permissions if possible".
<Quit Without Saving> or <Cancel>
I'm bloody dead in the water here! I shoot tethered to this thing with Nikon with Mac 10.8.2. I went into the Pegasus drive that contains my sessions and I can get it and launch a session without trouble. But that's it. Once it's opened up, I get all these dialog boxes and am forced to shut down.
What's going on?!?!?!?!?!
I read some inconclusive stuff about old workspaces and ditched all but the critical ones.
Currently, if I open a session and attempt to export a window pops up saying:
"The Specified output location is a read-only loaction" Please change the permissions on the specified output loaction or choose a location that you can write to and try again."
Click <OK>
A new window pops up stating: "Some of the selected variants are read-only. 5 of the selected variants are read-only variants. The process history of read-only variants will not be saved" <cancel> or <OK> are the only options.
The third window that comes up (and this one is starting to come up even if I don't attempt to export):
Session Save. Cannot save session to path: /volumes/xxxxxxxxxxxxx
"The session file is not writable. Try to change the session file permissions if possible".
<Quit Without Saving> or <Cancel>
I'm bloody dead in the water here! I shoot tethered to this thing with Nikon with Mac 10.8.2. I went into the Pegasus drive that contains my sessions and I can get it and launch a session without trouble. But that's it. Once it's opened up, I get all these dialog boxes and am forced to shut down.
What's going on?!?!?!?!?!
0
-
Can you write something (small text file for example) to the same folder(s) or any folders on the same drive using some other application? 0 -
Yes. The drive is a Promise Pegasus R4 in Raid 5. I can randomly grab files off my desktop and dump them into the Pegasus. Time machine also just did a successful backup to that drive. Since posting this, I did do a full restart of my system; straight to the power supplies.
Now, when I open a Session in Capture One, exporting still causes the "Events" log to open and states, "Could not process file"...
I don't think it's the drive...0 -
I think you have a permissions issue. It seams that you can´t read or write over a file.
While doing a back up on an external hard drive, I had the same problem (more or less).
What you can do is:
1. Select the FIRST archive (if there is one where your session is stored).
2. Select Finder-Archive- Get Info
3. Check if it is not blocked
4. Also, at the bottom of this window there is an arrow with Share and Permissions (sorry if this is not the proper word)
5. On each users Privileges, select "read and write".
6. On the "dented wheel" below this window, select "apply to included items" for each user.
I hope this can help
Saludos0 -
Thanks for lending the help! Can you explain better what you mean by "FIRST archive"? I'm unclear as to which folders I am to search. Though I'm going to look at them all while I wait.. 0 -
Sorry, my english is kind of "rusty".
What I meant was: Select the folder that "contains" the folder or folders that you have compromised.
I.E.
User - pictures - sessions- what ever it is session - and so on.
Here, you need to select "sessions". Or "pictures" if you want to unlock all other files that probably had permission problems.0 -
No luck. I went through and checked every folder involved with the session I'm currently troubleshooting. They all showed read/write for all users. It still logs an "Event" and spits out a TIFF on export that cannot be opened. When I double click the file, the error reads: "It may be damaged or use a file format that Preview doesn’t recognize."
http://chawncrawley.com/wp-content/uploads/2013/01/Example.png0 -
Just did a full reinstall of the software and it seems to back up and functioning. Kind of unsettling; a colleague just told me that he reverted back to v6.4.4 because of issues. Hopefully this was a one-off deal. Thanks for tossing some ideas out for me to check, though. I truly appreciate it!
Chawn Crawley
Chawn Crawley Photography0 -
If you haven't already done so I would create a support case about that. It might be a bit late to do much investigation of the problem you had (log files may be gone for example) but the description here seems usefully comprehensive and you know that the problem was resolved by a complete re-install so that may provide some clues. Or there may be a prior case already in the system.
Whatever the situation reporting it seems like a good idea.
Grant Perkins0 -
[quote="NNN634319595153020553" wrote:
The drive is a Promise Pegasus R4 ....
I don't think it's the drive...
From a quick look through some google links, I think this drive is the crux of the issue.
As a simple test, should this occur again, please remove this device from the workflow with a small session/catalog on the local drive to ensure software operation.0 -
I'm aware of some significant issues with the R6 Pegasus framework (thunderbolt) and that the Europeans are really struggling with them, but I haven't seen a significant string of issues with the one I have. I'll have to research it more.
In the meantime, I have opened a ticket with Tech Support and I'll post any new occurrences here, as well. In the meantime, I have a few sessions copied over to a WD hard drive and will use that to test if the situation returns.
Chawn0 -
Hi all,
I have just had exactly the same problem on a job and totally panicked as I couldn't save the session files.
My sessions and files are currently on an external hard drive I received from a client.
After some thought and testing I figured out a work around and everything is working fine now.
I located the session file xxxxxxxxx.cosessiondb crtl - clicked on the file, went to get info and checked the file permissions.
The problem is that it was trying to locate my system but instead said fetching. This should say your systems name. This option + staff and everyone was also greyed out.
The work around is to copy the session file back to your main systems drive and it rebuilds the permissions. I copied it back to my external drive and it now works.
Make sure to make a copy of your session file just in case.
Hope it helps and works for you.0
投稿コメントは受け付けていません。
コメント
11件のコメント