Luminous Landscape Forum
Raw & Post Processing, Printing => Capture One Q&A => Topic started by: Paul2660 on January 27, 2016, 07:46:01 pm
-
Is anyone else on windows getting this error, see screen shot below?
Basically you get the error screen telling you the file did not process, which causes you to close the error dialog box and press process again, most times it works the 2nd time around.
Only started getting this with 9.0.3, earlier versions of 9 did not cause this, and there is no telling when the error will happen, you might process 1 file and see it or 20 or 100 but it eventually happens. Happens on any camera file I use, Nikon Canon, Fuji or Phase.
Windows, Win 7 64 bit, 32GB ram, C1 9.03
Thanks
Paul C
-
Yeah I often get this on the first RAW file conversion of the session after starting up C1P. If I click on Process a second time it works OK. I am wondering if there is some background process or something still going on for a while after C1P starts that has to complete before it can do the RAW conversion. It has ocurred on all versions of 9.0 so far for me but much more frequently with 9.0.3.
-
Is anyone else on windows getting this error, see screen shot below?
Basically you get the error screen telling you the file did not process, which causes you to close the error dialog box and press process again, most times it works the 2nd time around.
Only started getting this with 9.0.3, earlier versions of 9 did not cause this, and there is no telling when the error will happen, you might process 1 file and see it or 20 or 100 but it eventually happens. Happens on any camera file I use, Nikon Canon, Fuji or Phase.
Windows, Win 7 64 bit, 32GB ram, C1 9.03
Thanks
Paul C
Hi Paul,
Yes I occasionally get that as well, usually with the first file of a batch. With similar hardware & OS. I haven't reported it as a support case yet, should have. I'll also try to make a screen grab the next time for reporting to support.
The more reports they get about a certain error, the higher the priority they will assign to fixing it.
Cheers,
Bart
-
Thanks to both of you, it's been driving me crazy since 9.0.3. I agree it's almost always the first time you hit process during a session job, if not 1st then 2nd time, and hitting process again sends the file through fine.
Still liking the results from this version very much, especially in shadows with Phase files, so just another annoyance to put up with.
I will also get a case opened with Phase.
Paul C
-
Had it two times since, but as I only have to click once more, it doesn't bother me yet.
-
It is a bit unnerving the first time it happens... :)
-
This issue had calmed down, but today I had over 20 instances of this. One file just would not process until I changed the receipe from 16 to 8, processed that, then went back to 16 bit and finally got the file through. Before that I had closed C1 and reopened, but the file still would not process.
Strange, as I have not ever seen this type of error before.
Paul
-
This issue had calmed down, but today I had over 20 instances of this. One file just would not process until I changed the receipe from 16 to 8, processed that, then went back to 16 bit and finally got the file through. Before that I had closed C1 and reopened, but the file still would not process.
Strange, as I have not ever seen this type of error before.
Paul
Same thing happened to me yesterday!
-
For those, like me, who experience(d) similar events, do report it and raise a support case. If hardly anybody makes a support case, it will remain a low low priority issue on their To-Do list.
Cheers,
Bart
-
For those, like me, who experience(d) similar events, do report it and raise a support case. If hardly anybody makes a support case, it will remain a low low priority issue on their To-Do list.
Cheers,
Bart
You are of course correct but it is hard to conceive that they don't already know this since it happens to virtually everybody and on both platforms.
-
For those, like me, who experience(d) similar events, do report it and raise a support case. If hardly anybody makes a support case, it will remain a low low priority issue on their To-Do list.
Cheers,
Bart
Hi Bart.
I have opened a case. Would like to hear from David Grover on this.
Paul C
-
You are of course correct but it is hard to conceive that they don't already know this since it happens to virtually everybody and on both platforms.
Perhaps/presumably they know about it, but how can they prioritize it if they receive relatively few reports they need to answer or escalate to the development team, and perhaps more requests for DNG file support. Cold hard numbers of support requests do help. The answer to my latest (minor) bug report (for which they didn't have a direct solution), with a screen capture to illustrate, was: "Thank you for this feedback. I will forward it to R&D."
Cheers,
Bart
-
Hi Bart.
I have opened a case. Would like to hear from David Grover on this.
Hi Paul,
Thanks, it will help everybody, and who knows what other issues are related to it that can therefore be tackled at the same time. I'm not sure it's David's job, but maybe he is kind enough to respond anyway.
Cheers,
Bart
-
I have some CR2 raw files from the 5DS R that corrupt also with 903. They still open fine and process ok with PS, LR, DXO, Fast Picture Viewer.
Windows 10. 32GB 2400MHz. Samsung 1TB 840 Pro.
-
Update, I did open a ticket with P1 on this, net, they added it to a bug fix list, not sure when they plan to fix.
Dear Phase One, this issue is a very big concern, as you no longer can process a string of images, as inherently one or more will error out as per my first post, so you have to write down the image numbers that got the error and go back and reprocess.
I am seeing this on all my windows machines now, and it seems to get worse over time, clearing out all presets and recipes fixes it briefly, but then it starts over again.
Today on 50 processed files I had the issue on over 30 files, some of which just refused to process unless I re-started C1.
In all previous versions that I have used back to 3.7.8, I have never seen such a bug before.
Problem happens no matter where the raw files are located i.e. NAS raid, external drive, internal raid, Drobo, internal hard drive.
Gets a bit tedious after a few hours.
Paul C
-
Just wanted to bring this to the top of the que again. With 9.1 this same issue is still there. In fact it appears to me to be worse.
Curious if other Windows users are still seeing this problem. I would say on my 2 win7 64 bit machines it's about a 50/50 hit rate, and when an images errors, many times it takes 3 to 4 additional attempts to get the file to process.
Batch is out for now as this really screws up a large number of files being processed.
Paul C
-
… since it happens to virtually everybody and on both platforms.
Never experienced it on OSX.
-
Just wanted to bring this to the top of the que again. With 9.1 this same issue is still there. In fact it appears to me to be worse.
Curious if other Windows users are still seeing this problem.
Hi Paul,
I experienced it twice with 9.1, so not as frequently as you. When the Graphics driver is updated, I sometimes need to switch Display acceleration Off. I have not tried also switching processing acceleration Off, since it happens so infrequently (with almost daily processing). Maybe it's related, and explains why with different (graphics)hardware we experience such different frequencies.
Cheers,
Bart
-
Hi Paul,
I experienced it twice with 9.1, so not as frequently as you. When the Graphics driver is updated, I sometimes need to switch Display acceleration Off. I have not tried also switching processing acceleration Off, since it happens so infrequently (with almost daily processing). Maybe it's related, and explains why with different (graphics)hardware we experience such different frequencies.
Cheers,
Bart
Hi Bart,
I have 2 PC's that run most of the work for my studio. One is a 3.4Gz i7, 2.5 year old Asus board and new 4GB Nvida 960x Video card. The other machine is a 4 month old Asus, 4.0Gz, 32GB of ram and 970X 4GB nvidia card. Both show the problem routinely. Since I mainly process only Phase files,
P45+, IQ160, 260 and 180, it may have something to do with that. But I have seen a few times on D810 files not as often. With Phase files, it's a given it will happen almost immediately. I have also seen on my Surface pro machines, running win8 and 10, but it's not as common a problem, still happens at times.
I tried turning off the Open CL for processing, also, but that did not help, left the Open CL on for display.
This issue for me is considerable as you no longer can run batch, as you will get errors during the run, and then go back, write down the files that failed and process them out one at a time.
This is the 2nd major issue I have had with Capture One since Vr8. Vr 8 had the terrible issue of locking up C1 if you minimized the program to the task bar, then tried to bring it back. Phase agreed with me it was a bug and it was fixed in 9. That bug was not as big a deal as I knew just don't minimize to the task bar. This error is more troubling as for the amount of time it now takes to process out 50 to 100 files, as the batch is worthless due to the error and time it takes to reconcile the files that erred out. I have never seen this type of problem all the way back to 3.7.8 days, and any previous version.
I also agree that it seems to be windows only related, as on my 2 Macbook Pro's with 9.1 BD and Pro, I don't see it at all.
Paul C
-
I guess this error has taken the prize for me. Yesterday I rececived it 25 times in a row on an IQ. 100 file that I had just previously processed. It. Is a bit like playing Russian Roulette as you never know when it will crop up but when it does it is fatal. Full restart of C1 and on this last occurrence a full reboot of the PC.
Paul C
-
I guess this error has taken the prize for me. Yesterday I rececived it 25 times in a row on an IQ. 100 file that I had just previously processed. It. Is a bit like playing Russian Roulette as you never know when it will crop up but when it does it is fatal. Full restart of C1 and on this last occurrence a full reboot of the PC.
After a long time of no issues, yesterday I also had a single occasion of a file not being processed the first time and everything was fine when I tried again, and no issues since. Maybe it's the position of the planets or the phase of the moon or such, but I cannot find any pattern in the (in my case infrequent) hickup occurring. I didn't have the time to make a documented support case but I will the next time it happens.
I also switched to Windows 10 (very smooth transition from Win 7, it just took a while), so want to have an otherwise stable running system before digging into logfiles. Given the infrequency in my case, it will be hard for Phase One to simulate the situation, and find the root cause. Maybe there is a log file stored somewhere in the hidden Apps directory, that can help them.
The upgrade to Win 10 did cost me one activation, but Support responded with a link to a webpage which detailed how I could reset all my activations, returning the number to 3, after which I could reactivate the necessary machine(s) without problems.
Cheers,
Bart
-
I guess this error has taken the prize for me. Yesterday I rececived it 25 times in a row on an IQ. 100 file that I had just previously processed. It. Is a bit like playing Russian Roulette as you never know when it will crop up but when it does it is fatal. Full restart of C1 and on this last occurrence a full reboot of the PC.
Paul C
Hi Paul,
I haven't seen the error myself.
Just a thought - something to do with naming convention?
Please do raise it with support. Have you?
D
0
-
Hello David:
I opened a case back in January, and C1 support had me totally remove C1, from the system. I re-installed but the issue came back within 1 hour.
This issue shows up with all C1 9.x versions, on all of windows machines, win7, 8 and 10. Frequency is hard to determine as the problem will happen sometimes immediately, other times after several processing sessions.
I do not use the catalog, just session mode in C1, and have never seen this type of error before until 9.x. I don't see this on my MacBook Pro with El Capitan.
Turning off open CL support doesn't make any difference.
Note, this is only during the processing stage of the file, everything else works fine. What is strange, is like the file that has erred out gets a tag. Sometimes I can just hit the process tab again and the file goes an through, but last night, I wanted to see just how many times the error would occur, and gave up after 25 attempts. To get the image to process, I ended up having to close C1 and then process a different file in the session then the problem file worked with no problems.
Paul C
-
Hello David:
I opened a case back in January, and C1 support had me totally remove C1, from the system. I re-installed but the issue came back within 1 hour.
This issue shows up with all C1 9.x versions, on all of windows machines, win7, 8 and 10. Frequency is hard to determine as the problem will happen sometimes immediately, other times after several processing sessions.
I do not use the catalog, just session mode in C1, and have never seen this type of error before until 9.x. I don't see this on my MacBook Pro with El Capitan.
Turning off open CL support doesn't make any difference.
Note, this is only during the processing stage of the file, everything else works fine. What is strange, is like the file that has erred out gets a tag. Sometimes I can just hit the process tab again and the file goes an through, but last night, I wanted to see just how many times the error would occur, and gave up after 25 attempts. To get the image to process, I ended up having to close C1 and then process a different file in the session then the problem file worked with no problems.
Paul C
Strange one! Have you reverted back to support?
-
Yes working with support through my dealer.
Appears to be an open CL issue but not if I am willing to totally disable open CL on the entire PC as other programs need it also.
Paul
-
I've had it on and off on Windows 10 x64.
Today I batch processed 92 files. Got one Error and one no process at all! ???
I had to go through all the processed files afterwards to find which one hadn't processed. I only knew there was another non-processed file because the folder had 90 TIFFs instead of 92.
But, both files processed second time round without a hitch.
D.
-
I had to go through all the processed files afterwards to find which one hadn't processed. I only knew there was another non-processed file because the folder had 90 TIFFs instead of 92.
Hi,
The log file should tell you which files didn't process. Not that it's not a nuisance, but it's also not predictable (although with me it's usually the first of a batch if it happens), and thus it's hard to nail the cause.
Cheers,
Bart
-
It gives the camera file number.
But, I had given the files a custom name and number, so I didn't know which one was missing, coz it no longer had its camera number.
Thanks.
D.
-
It gives the camera file number.
But, I had given the files a custom name and number, so I didn't know which one was missing, coz it no longer had its camera number.
I understand, I don't rename my Raws, so for me it's easy to spot the missing one. Maybe something that can be improved in the Log file as well then.
Cheers,
Bart
-
Just a quick update, it appears on my system logs that C1 is having issues with open CL, so I have been asked to run a script to keep C1 from using it. Will be doing this later tonight on return to studio and will see what happens.
Not sure what this mean as far as using C1 and process speeds since without open CL I will be only using the system ram and processors.
Paul C
-
I'm experiencing something similar with regard to processing files. Weird. Sometimes changing the output recipe helps, then reverting back to the recipe that I really wanted outputted. Annoying for sure.
ken
-
One last update,
Phase One provided a script file for me to run, which disables the open CL options in Capture One. After you run the script, the Open CL, box is no longer available to check.
With this option, I ran C1 through several processing runs, of 10, 15, and 30 images, and had no problems with the error, HOWEVER,,,,,,
It's readily apparent, Phase One does understand how to take advantage of the open CL processing in C1, as without, everything slows down, way down. Examples,
Processing out a IQ260, 100 file, goes from 5 to 6 seconds to 20 to 25", this a per file run time.
If you use a lot of adjustment layers, (I do), drawing a mask, will take a much longer time and and times will freeze the system, also the more masks, the
slower and more prone to problems
Zooming to 100%, now takes about 4 to 5 seconds to complete on a IQ100 file, whereas before 1 sec.
So, for me, as a heavy C1 user, turning off open CL really is not the solution, as unlike LR (which still can't seem to take any advantage of open CL), C1 does.
For now, I have just decided to live with the issue and if the problem becomes bad, I finish working on a series of images, then run the script, and then process them out without open CL, as that allows me to step away from the PC and do other things while the files process, as at least they all finish without errors.
This error only seems to happen with ver 9 for me, as I went back and worked with Ver8 for a bit and it processed as normal, with the Open CL selected.
Paul C
-
One last update,
Phase One provided a script file for me to run, which disables the open CL options in Capture One. After you run the script, the Open CL, box is no longer available to check.
With this option, I ran C1 through several processing runs, of 10, 15, and 30 images, and had no problems with the error, HOWEVER,,,,,,
It's readily apparent, Phase One does understand how to take advantage of the open CL processing in C1, as without, everything slows down, way down.
Hi Paul,
Thanks for the update. Obviously disabling the CL support is not a fix, but a bypass. But that the issue is Parallel processing and GPU acceleration related seems clear. It won't be simple for Phase One to find the cause, but filing support cases will give it a higher priority.
I have not experienced any glitch for some time, so I'll see if updating the video drivers to the new version from 2 days ago triggers anything undesirable (so I can file a documented support case).
Cheers,
Bart
-
On the main problem machine, I have a nvidia GTX960, which is not supported officially by Phase One for Open CL, they support the GTX970 and GTX980.
I have seen this issue on my other PC with a GTX970 albeit, not as frequent as on the GTX960, so I am off to newegg to get a GTX970.
It never ends.
Paul C
-
It never ends.
Indeed Paul, and now (released today?) C1 version 9.1.2 is available ...
Cheers,
Bart
-
Not to beat a dead horse, but did want to update.
Brand new GTX970 Asus card, same errors, processed 4 (only 4) as a test and failed on 2 so 50% error rate.
This is a supported card per Phase One. So for now I guess I will have to run the script to kill open CL to process files and run it again to work on files (enable open CL). Not a great working solution. Strange that this only showed with Ver 9.x.
BTW it occurs about the same on either of my main windows machines, win7 and win 10, 6 months old and 2 years old (Asus Main boards on both) both i7 3.4 and 4Ghz.
Paul C
-
You have visited Asus for latest firmware a.o. updates for cards and mbs?
-
Firmware is up to date per the Asus auto checker. Nvidia monitoring software is also current.
Paul C
-
Just wanted to bring this post back to the top.
Installed 9.2 on a Win 10 15" Laptop. This particular machine has never had any Phase One C1 on it, thus this was a clean install as it can be.
Same error, "error when processing a file", same random issue, a bit like Russian Roulette, as you never know when the bullet will fire, but when it does, the problem then start to re occur over and over.
This appears to be a problem across most windows platforms, Win7, and Win10.
Strange that more folks don't seem to have the problem, but on all 5 windows machines I have running C1, either DB or Pro, they all get this same error.
Paul C
-
Paul...... I have never gotten the error message that you have posted but, I have selected multiple files for processing with some not processed at all. I am running latest version of C1 (9.2) and Win 10 on a dedicated computer.
Victor
-
Hi Victor.
You make a good point. If you have multiple files selected what happens is the file that errors out just won't process. I don't believe the error box shows up. This is why I quit processing large groups of files as I had to go back to reconcile what did not process.
Paul C
-
Paul...... I have never gotten the error message that you have posted but, I have selected multiple files for processing with some not processed at all. I am running latest version of C1 (9.2) and Win 10 on a dedicated computer.
Hi Victor,
I had it happening on a single file (not even a batch) recently (nothing since), on Windows 10, while in the midst of a HardDisk defragmentation operation. So I'm not sure if that's enough of a reproducible situation for the C1 support crew to be of use. Maybe just unfortunate timing, such as could also be caused by a Virusscanner, I suppose.
Cheers,
Bart
-
Still happening pretty regularly here, even on Phase files.
-
Still happening pretty regularly here, even on Phase files.
Hi,
Maybe the most recent service release 9.2.1 changes something?
I do wonder, why some like Paul and yourself can hardly process any files without these issues and others, like me, only occasionally get a hit. Don't get me wrong, there clearly is a bug that needs to be tracked down and fixed, but why the big differences in the level of impact?
Hardware related issues do play a role, but even if people replace their graphics card to a supported model and update to the latest drivers, some still experience failed conversions. Motherboard/memory driver updates can also make a difference.
Have people tried if their Virus scanner or other file locking utility plays a role? Especially those who can hardly get a fail free batch conversion, does it make a difference if the Virus scanner is temporarily switched off (or TIFF and JPG/JPEG file extensions are excluded from scans)?
Cheers,
Bart
-
Hi Bart
Problem still occurs with 9.2.1. And about as often. I am still working with P1 through my dealer.
But the problem occurs on all my windows machines. As it now happens on my MacBook Provwith win 10 I am less concerned about my hardware from Asus.
Really seems to be a timing problem as it a call is made to open CL during processing and there is something out of sync so the process fails.
50 percent of the time if I hit the process button the exact same file will go through the rest of the time it becomes as if tagged by C1 never to process until I restart C1.
Paul C
-
Really seems to be a timing problem as it a call is made to open CL during processing and there is something out of sync so the process fails.
50 percent of the time if I hit the process button the exact same file will go through the rest of the time it becomes as if tagged by C1 never to process until I restart C1.
That's also my guess, timing issues. I mostly (luckily not as often as you) experience it on the first (or only) file of a batch.
Cheers,
Bart
-
I too think it is a timing issue of some sort. The failure rate is much much higher if you have just made an adjustment and immediately hit the process button than it is if you wait for a bit after a complex adjustment such as a color or skin tone edit on a multiple layered file. If you just use C1 for simple edits like exposure or contrast especially without layers it rarely fails
-
Sorry to sound negative, but really I am very frustrated on this issue.
With version 8, the main problem was that if you happened to minimize the screen to the task bar, then when you attempted to maximize it, the session froze and errored out. So off you go to task manager, close the software and reopen. I know maybe not a big deal for folks on multiple screens, but I use a single 30 inch and it drove me crazy. I opened a problem ticket on that also and Phase One worked with me and others and a fix was released with the last version of 8.x and IT fixed the problem.
This problem has been going on since the release of 9.x, and EJ brings up a great point, in that if you have a lot of adjustments, or layer or both, the issue will show up sooner and then create total havoc. I personally love C1 for all of the tools it offers so I guess I am seeing the issue more than others.
As Bart mentions, if you go via batch, you don't get the error, you just have to go back and edit your files to make sure all processed as if one got the problem, it won't process out. This caused me to start going one at a time (I know that is time consuming but so is going back and editing out a large batch job), so I am seeing the problem sooner or more often than most.
Where I am frustrated, is that it has shown up on all my windows environments, (various hardware and win7 and 10 and 8), Surface Pro, Macbook Pro, PC etc. So Phase One, should be able to see this pretty darn quickly. BTW all of those environments are using different video cards, all are "supported" by Phase for open CL, so it's not just my Asus PC's. Phase One's only answer, turn off Open CL, which to me is not the right answer especially with the investment I have made in video cards for C1 and LR, and the fact that I am mainly processing larger files in C1 to start with mainly Phase One back images. You can run a script that turns off open CL for C1, but that also effects the open CL for display, (drawing masks especially) and in a IQ100 or IQ280 file you really need the boost of open CL for the adjustments. Just turning off open CL for processing in the C1 preferences doesn't seem to help, you have to run the script. So for now, I work with Open CL for image work, then close C1, run the script, reopen C1 and start processing.
Paul C