Export processing errors using OpenCL
C1Pro for Sony ver 9.1
Getting "Error Output Processing File" for ~10% of my exports to .jpg using GTX 960 using driver 364.51, and one that was from November (about 5 or 6 releases older than this one which I just updated to).
Are there any settings in the Nvidia driver for 3D etc... that I should turn "ON" or "OFF" to have this work reliably? Sometimes it errors out on more than 20% of the files and then I have to go back and look at the log to see which ones to do again.
I bought the 960 card solely to speed up these conversions - I don't play games etc...
GTX 960 is stock clocked, Intel 6700k CPU, 32gigs ram, Z170 chipset - tried 2 different MB bios versions - same result.
Thanks for any insight.
Getting "Error Output Processing File" for ~10% of my exports to .jpg using GTX 960 using driver 364.51, and one that was from November (about 5 or 6 releases older than this one which I just updated to).
Are there any settings in the Nvidia driver for 3D etc... that I should turn "ON" or "OFF" to have this work reliably? Sometimes it errors out on more than 20% of the files and then I have to go back and look at the log to see which ones to do again.
I bought the 960 card solely to speed up these conversions - I don't play games etc...
GTX 960 is stock clocked, Intel 6700k CPU, 32gigs ram, Z170 chipset - tried 2 different MB bios versions - same result.
Thanks for any insight.
0
-
This is probably no help at all but my K1000M Quadro finally started to be available once I installed NVidia driver version 354.56 and it seems stable. I have not noticed any output problems so far.
Prior to that afaik the OpenCL feature set was not used on my system (assessed as not powerful enough to be worthwhile) but processing could drop a number of files for completely unknown reasons with nothing reported at the time.
Some combination of Windows updates and NVidia driver updates seems to have fixed the dropped process output problem and made the GPU available.
I have no idea whether the driver mentioned would be viable for your model of GPU.
Grant0 -
Do you have this issue only with OpenCL enabled? 0 -
I rarely will also have the issue without using openCL (cpu only).
Tried last night to adjust video card speeds / fans / memory clock and really couldn't reliably tell a difference even when over-fanned and underclocked.
So yes - it seems to be with or without using openCL, but much more common when using it.
And in regards to the first suggestion kindly offered, I haven't ever had an issue being able to choose "auto" or "never" in the openCL options. I've always had both options listed.
Thanks0 -
I have the same error from time to time, and the same gfx card. Can you look into the application.log to find more information? In my, there is something about abc.jpg.tmp file not found... 0 -
Looks like these would be the relevant lines in the application.log file when an error happens:
-----------------------
[2016-03-25 15:48:28.176][000][ID:053, ]{OUTPR} | ProcessToFiles for: D:\Photos\16-03 Costa Rica\DSC04773.ARW & D:\Capture One Catalog\Catalog 1\Cache\Previews\2016\3\17\188\DSC04773.ARW.cop
[2016-03-25 15:48:28.176][000][ID:053, ]{OUTPR} | Warning: ProcessToFiles: The file to move doesn't exist? D:\Photos\test output\DSC04773 raw.jpg.tmp
[2016-03-25 15:48:28.184][008][ID:053, ]{LOG } | User log: description = [Error Output Processing File DSC04773.ARW], details = [Error processing file DSC04773.ARW - Error [1 - resError]]
[2016-03-25 15:48:28.184][000][ID:053, ]{OUTPR} | Image DSC04773.ARW Developed
------------------------
D: drive is a samsung 850 ssd - wonder if the "turbo" function (some type of write cache, I think) could be a factor? I'll try to disable and re-test.
EDIT: Made no difference.
Notice that often the same files error out - sometimes several times if you try them singly, then they will work maybe the next time.0 -
Thanks. I have the exact same messages and behaviour (sometimes it works sometimes not). Would you file a support case too? 0 -
It may be of interest to you but I have just recently had an issue using CO 9.0.3 and nVidia 364.51 drivers with a GTX570 with 1.2GByte of GPU Memory.
The problem exhibited itself when processing moderate to large numbers of images. The first few images would process fine and then they would all be corrupted. Thereafter, all processed images were corrupted until I restarted CO. On restarting CO, I could process the images that had previously failed to process (until the problem occurred again).
Turning off OpenCL fixed the issue. I could then process large numbers of images without issue but at a performance cost.
On a suggestion from Support, I backed off the nVidia drivers to 355.?? and the issue went away.
However, subsequent to the release of CO 9.1, I have found that the latest nVidia drivers (364.51) are again working fine.
Whilst I was looking at this issue, I found that, using the 364.51 drivers with CO 9.0.,3 the GPU memory exceeded 93% utilization. Backing off the drivers to 355 reduced this to ~83%. With CO 9.1 and the 364.51 drivers the GPU memory utilization was reduced still further to about 75%.
Based on this observation, it, therefore, looks (to me) as if CO was experiencing some kind of GPU memory resource starvation and this was the cause of the corruption in the processed images.
Note: I am using an original Canon 5D which has, by modern standards, tiny 13MPixel files and so those of you working with larger files may experience issues when I do not.0 -
Interesting info - thanks.
I'm processing generally large files (42mp sony ar72) so maybe that has something to do with it, although some are cropped (.jpg exports) significantly so don't know how that factors in.
Maybe I'll revert to the 55 drivers and see...0 -
I also have Sony files but 24 Mpix.
[2016-03-25 15:48:28.176][000][ID:053, ]{OUTPR} | Warning: ProcessToFiles: The file to move doesn't exist? D:\Photos\test output\DSC04773 raw.jpg.tmp
does not sound like a graphic card or driver issue, does it? My card has 4 GB memory, btw.
Did you open a support call?
Cheers0 -
No - I haven't opened a support call. Haven't done that before - what is the quick process to do this if you don't mind my asking?
Thanks0 -
FWIW I have seen this problem back in V8 days. Any number of files in the process queue and it would drop up to about 10% on a bad day. RAW file size is not an issue for my cameras.
I thought V9 or a Windows update or an NVidia driver update had solved the problem AND introduced my low performance GPU to the Process process. However having checked the log file I find that is not the case for the reported errors and certainly for a period of a few days my GPU card seemed to go AWOL again, although it returned after a few reboots of the notebook. I suspect there was a Windows 7 update in there somewhere.
The log file tells me the problem has not occurred in the last 14 days.
Time to do some further analysis I think.
Grant0 -
My Application.log file for V9 tells me that I have had 7 process failures over what seems to be 4 batch processes (might be 3 batches and a random one off process) since the start of January.
The error in all cases seems to be "Warning: ProcessToFiles: The file to move doesn't exist? "
The log lines indicate that the "Develop" action succeeded.
I was seeing the same things in V8 although possibly with more frequency.
The log entries seem to suggest that the processing is working but there may be a work file handling issue of some sort.
We can analyse this further but I think we need some guidance about what might be worth looking at - much time could be wasted here digging into system process logs without really understanding what is and what is not important to understand.
BTW. I'm not convinced this is an OpenCL issue. Pretty sure my GPU was being rejected and not used back in V8 days when I had previous regular instances of this failure being reported.
Grant0
Post ist für Kommentare geschlossen.
Kommentare
13 Kommentare