6.2.1 Processing Issues
Anyone have the problem where the processing queue just ejects all the files in the queue? I can't process more than 35-40 files at a time without it doing that. When reviewing the logs, "There was an error during the processing of the output file." The only way to restart processing is to restart the program.
0
-
See also
viewtopic.php?p=48652#p48652
Might help.0 -
I have done everything under the sun, and I know its typically a temporary fix. The biggest problem I have is that phase will not acknowledge the problem, they blame it on user error. 0 -
OK, you've tried everything, but have you tried this:
Before you start processing, restart your system, start Capture One and create and start the batch. Just checking.0 -
[quote="Paul_E" wrote:
OK, you've tried everything, but have you tried this:
Before you start processing, restart your system, start Capture One and create and start the batch. Just checking.
Whoa, wait a second. Respectfully, this amounts to "did you to touch your toes and dance in a circle first" when a client is waiting for their files.
I realize I should be posting this to my previous thread but I have tried but I have tried clearing the history and rebuilding permissions so far and the problem still persists. Next I'll clear the cache and preferences, but what a drag. It seems to crop up after the App has been running for a while and there have been a fair amount of actions completed - such as adjustments, deletions, switching sessions, etc.
And, although I am not suggesting Phase is ignoring the issue, I would love to see it simply work with having to wear my grass skirt and carry my voodoo stick. 😊0 -
[quote="Brion " wrote:
...
It seems to crop up after the App has been running for a while and there have been a fair amount of actions completed - such as adjustments, deletions, switching sessions, etc.
That was exactly the idea behind my "restart..." suggestion, which could make a case for Phase One acknowledging this. Note that the OP did not mention any hardware detail like amount of RAM so I have to start poking around with some suggestions. Thank you for bringing this up.0 -
Computer is a 17 Macbook Pro, i7 Processor with 8GB's of RAM and striped 256GB Crucial SSD's.
C1 Pro version 6.2.1
OS X 10.6.7
What else can I tell you?
As of right now this issue only seems to happen when processing out tif's, I just ran a large batch of jpegs and it ran smoothly. As soon as I switched to tif's the program started spitting them out again.0 -
When you process to either tiff or jpeg, do you set the same output profile (like sRGB, AdobeRGB) in the output recipe.
And, while I understand from your hardware description (thank you), I assume you talk external disks here. Could you process to tiff to your internal disk once for a change? A trial-and-error process, you'll understand. 😉0 -
The output profile is selected in the output recipe.
The disks I'm referring to are internal disks, one SSD in Main bay, another in the optical bay and they are striped using Disk Utility. Every time I process I process out to the internal disk.0 -
[quote="NNN634243906943059380" wrote:
The output profile is selected in the output recipe.
Yes, I understand, but is it the same for both tiff and jpeg. And which profile do you use if I may ask? And have you experimented with different tiff settings like 8 or 16 bit, compressed non-compressed. Have you created a new recipe with the same parameters?
I just try to show you that you can rule out potential causes by focussing on different parameters.0 -
I have not tried different color profiles. This client requests Adobe RGB for everything. Bit depth is 8, uncompressed with tif's and jpegs have a compression of 8. I have also deleted all recipes and recreated them to rule out any issues with recipe creation. 0 -
I am afraid I run out of options as well. Either RAM fills up more with tiff processing (Activity Monitor can show that, that's why I suggested a clean start with a reboot) or CO6 with tiff processing does not like the disk striping. Not sure you informed Phase One about this in your support case and whether or not they responded to it. 0 -
For the record, this issue has recently been occurring while I have been processing Adobe RGB 1998 JPEGs but it has happened, in the past, with TIFs in various color spaces as well.
It is actually an issue I have noticed in before, who know exactly when, but within the last couple of years. It would happen every so often but kind of rarely, so i chalked it up as a minor glitch. It is only recently, 6.2 on, that I have been seeing it occur with more frequency.0 -
Thanks Brion, I had the same idea. It goes as it comes, pretty foggy. Frustrating though. 0 -
IT IS VERY FRUSTRATING! I just wish phase would acknowledge it. I've been in touch with them twice regarding this issue and both times they blame it on me for not knowing how to use sessions and processing recipes. If they took a minute to read these forums they might realize its actually an issue. 0
Post is closed for comments.
Comments
14 comments