C1 11.1 not using OpenCL
Hello,
I have a gtx 1070 and i7 3770k. I enabled(set to auto) the use of OpenCl in the c1 menu but it's not working. The export times are the same for Auto and Never. I have the latest build o win 10 and the lates drivers from nvidia. The CPU is at 100% and the gpu at 2-3% utilization. I event used the Enable/Disable open CL .reg files that c1 provides. Now i want to export ~650 24mp photos and it takes about 77 minutes.
I have a gtx 1070 and i7 3770k. I enabled(set to auto) the use of OpenCl in the c1 menu but it's not working. The export times are the same for Auto and Never. I have the latest build o win 10 and the lates drivers from nvidia. The CPU is at 100% and the gpu at 2-3% utilization. I event used the Enable/Disable open CL .reg files that c1 provides. Now i want to export ~650 24mp photos and it takes about 77 minutes.
0
-
Really? Even after all those windows updates and after installing the latest drivers?
Truth be told - I'm currently sufficiently frustrated by this to actually consider doing that as well..0 -
I strongly suspect that opening a support case will yield a way to get C1 to recognize that changes have been made and it should reevaluate its support of Open CL. 0 -
I did that. A long time ago.
The bug was recognized but no solutions were offered.
If a fresh Windows installation is necessary I would do that but I don't want to interrupt my workflow for no reason at all.0 -
After a restart and a 3-4 crash-es c1 lost my catalog. And the gpu acceleration is so bat. CPU 90-100% and gpu 0-9% utilization. The worst c1 version ever. 0 -
I can confirm that a clean Windows-Installation resolved the OpenCL issue and also resolved other problems for me (such as CaptureOne still running as a background process after closing it). 0 -
Well I think my celebrations were a bit premature.
When changing the Exposure it's pixelated and the CPU usage is still at 30%+ while GPU usage is 0,5-2%.
So it gets detected. It says it's using it. It just doesn't do it anyway.
Oh well, now I at least have a clean system. Oh, the joy.0 -
[quote="C-M-B" wrote:
Oh well, now I at least have a clean system. Oh, the joy.
Image your system as soon as you get everything up and running; and then every now and then as a backup.
Perhaps clone to a spare SSD that you can boot from.0 -
[quote="C-M-B" wrote:
Well I think my celebrations were a bit premature.
When changing the Exposure it's pixelated and the CPU usage is still at 30%+ while GPU usage is 0,5-2%.
So it gets detected. It says it's using it. It just doesn't do it anyway.
Oh well, now I at least have a clean system. Oh, the joy.
In the log file, what value do you see for the OpenCL benchMark?
I'm not sure if this is still the case but in the past OpenCL was not pursued if certain tools had been used in an edit because CPU processing would be required anyway and there was no advantage to be gained from using the GPU.
I think it is probably still true to say that CPU processing can still be preferable depending on the relative power (for a specific type of editing tool purpose) between the CPU and the GPU. My Notebook some years old now, has a GPU that is just about worth considering sometimes and a CPU that, 6 years ago, was quite well up the processing power range for a notebook. The CPU tends to get most of the one-off processing work. However, send along a batch of work and it's shared out between CPU and GPU if the system thinks there is a processing speed benefit to be gained.
I suspect that the decision making process is potentially complex enough and with so many variable factors that to even attempt to describe it in a published document for mass consumption would be an unwise distraction into technicalities of unfathomable nuances of decision making that might distract people from the point of their business or hobby. Making images.
Grant0 -
Hi Grant!
You were absolutely 100% correct. I went through every adjustment I made and reset them one after another to see which one blocks the Hardware Acceleration.
The culprit is the dust removal in the LCCs. When I enable dust removal the hardware acceleration is gone, when I disable it, it's active. Come to think of it - I remember that it was mentioned that HA would not work when using Spot Removal - however I wouldn't think that the same applies to dust removal using a LCC calibration file - especially considering the fact that everything else (Colour Cast and Uniform Light) works with HA...
Oh well, lesson learned 😕
I know, it works without HA but I really, really like have both the GPU and the CPU working in tandem. Not only does it significantly improve the visual quality during editing (the pixelation isn't very easy on the eyes) but it also allows other processes to run very smoothly in the background and leaves some headroom for multitasking.0 -
Ah ha!
Spot adjustments - I remember that particular one now. I would guess that LCC was another I was thinking of fomr the early days of OCL. If, as I would expect, the spot removal process is the same whether via LCC data or hands-on adjustments, the reason for using CPU rather than GPU for that task would also be the same.
I guess one can manage the process by considering leaving spot removal, especially via LCC, to be the last step in a work flow in most cases.
In my case the majority of my output involves lens wide open shots so dust spots are not a regular worry for me and the content would not usually be critically affected anyway for everyday output. So I don't claim any relevant experience to compare to in this case.
Grant0 -
True, my first thought was that they simply too the dust layer and kind of created an overlay to subtract the dust spots - but that wouldn't make any sense 😉 after all they need to "fill" those blanks and that is better done by the CPU...
I guess you're right, dust correction is going to be the last step in my workflow from now on.0 -
So does that mean that OpenCL is working for you overall? 0 -
After a complete format an re-installing Windows etc - yes. It's working! 0 -
The issue returned. CPU 100%, gpu 1-3%. Did a c1 reinstall, delete the imagie core. The export begins with 100 CPU and 1-3% (the time is 8-9 minutes) and after some time(~45% of the loading bar) the CPU goes to 70-80% and the gpu to 27-35%(the time goes to 1 minute). 0 -
[quote="NNN636359987389438358" wrote:
The issue returned. CPU 100%, gpu 1-3%. Did a c1 reinstall, delete the imagie core. The export begins with 100 CPU and 1-3% (the time is 8-9 minutes) and after some time(~45% of the loading bar) the CPU goes to 70-80% and the gpu to 27-35%(the time goes to 1 minute).
How do you monitor GPU load ?
Can you see a difference with HW acc set to disable and set to Auto?0 -
[quote="Christian Gruner" wrote:
[quote="NNN636359987389438358" wrote:
The issue returned. CPU 100%, gpu 1-3%. Did a c1 reinstall, delete the imagie core. The export begins with 100 CPU and 1-3% (the time is 8-9 minutes) and after some time(~45% of the loading bar) the CPU goes to 70-80% and the gpu to 27-35%(the time goes to 1 minute).
How do you monitor GPU load ?
Can you see a difference with HW acc set to disable and set to Auto?
Hello. I monitor the gpu usage with the task manager in win 10.
In the first half of the export if i switch between GPU and CPU, the export time is the same. For some reason after ~45% export time, the GPU acceleration starts and the time get's to 1 minute.
I also monitor the export director. In the first half of the export the pictures are exported slow and after the GPU usage goes up(~45% export in the export menu of C1), the pictures are exported really fast.0 -
<del> 0 -
[quote="NNN636359987389438358" wrote:
[quote="Christian Gruner" wrote:
[quote="NNN636359987389438358" wrote:
The issue returned. CPU 100%, gpu 1-3%. Did a c1 reinstall, delete the imagie core. The export begins with 100 CPU and 1-3% (the time is 8-9 minutes) and after some time(~45% of the loading bar) the CPU goes to 70-80% and the gpu to 27-35%(the time goes to 1 minute).
How do you monitor GPU load ?
Can you see a difference with HW acc set to disable and set to Auto?
Hello. I monitor the gpu usage with the task manager in win 10.
In the first half of the export if i switch between GPU and CPU, the export time is the same. For some reason after ~45% export time, the GPU acceleration starts and the time get's to 1 minute.
I also monitor the export director. In the first half of the export the pictures are exported slow and after the GPU usage goes up(~45% export in the export menu of C1), the pictures are exported really fast.
Sadly, the GPU monitor in Windows Task Manager does not monitor OpenCL usage. Instead use a utility like GPU-Z or similar.0 -
Hello.
Did the test with gpu-z vers 2.9.0. i get the same result.0 -
[quote="NNN636359987389438358" wrote:
Hello.
Did the test with gpu-z vers 2.9.0. i get the same result.
Please contact our Support Team.0 -
i can't. i use the demo version. 0 -
[quote="NNN636359987389438358" wrote:
i can't. i use the demo version.
Yes you can. That's one of the really good things. Fully featured trial.
https://www.phaseone.com/en/SupportMain ... pport.aspx0
Post is closed for comments.
Comments
52 comments