Checking GPU acceleration
Hi,
How do I see that OpenCL and/or GPU acceleration are actually enabled in C1? Setting Display and Processing to Auto in the Hardware Acceleration section of the Preferences is just the expression of a wish but how do I verify that things are actually working as expected (beside doing my own tests)?
Will I get an error message if something doesn't work?
How do I see that OpenCL and/or GPU acceleration are actually enabled in C1? Setting Display and Processing to Auto in the Hardware Acceleration section of the Preferences is just the expression of a wish but how do I verify that things are actually working as expected (beside doing my own tests)?
Will I get an error message if something doesn't work?
0
-
There are 2 somewhat hidden way to check this:
1) Reset the image completely, enable the focus mask, and make an adjustment from the Exposure Tool (i.e. contrast). If the focus mask disappears during adjusting, OpenCL is being used.
2) Zoom to 100% and make an adjustment from the Exposure Tool (i.e. contrast). If the image stays sharp, OpenCL is used. If it pixelates, OpenCL is not used.0 -
Would be a nice feature to have this info anywhere in C1. 0 -
[quote="Christian Gruner" wrote:
There are 2 somewhat hidden way to check this...
Thanks Christian.
So my Quadro K620 is not used for hardware acceleration, which is rather surprising.0 -
[quote="Samoreen" wrote:
[quote="Christian Gruner" wrote:
There are 2 somewhat hidden way to check this...
Thanks Christian.
So my Quadro K620 is not used for hardware acceleration, which is rather surprising.
My Notebook has a Quadro K1000M which is perhaps marginally less capable than your K620 according to the figures at videocardbenchmark.net.
Until V9 it was not used by C1 although the reason may have been a very early performance assessment that suggested it was not worth using and seemed then to be referred to to bypass the performance tests. This was not of great concern since at the time many of the features I used, notably to do with adjustment layers, meant that C1 would almost always use the CPU anyway.
My K1000M is probably marginal for use when compared to the CPU (i7 3xxx) in the device. I don't see a lot of performance difference now it is functional. The performance assessment returns a value in the range 2.25 to 2.6. The target for anything really interesting is probably about .25 and lower would be better. The inbuilt HD4000 chip gives an assessed value of around 20. I mention that just for reference.
I also changed the driver (not something that Windows update thought necessary) at around the time I confirmed that the card is in use.
NVidia utilities have the option to specify which applications should use their card rather than some other and also a "monitor" of sorts that confirms which program "are actually using" the card.
As I run Windows 7 I also have a legacy gadget still running that claims to give me some performance information about the GPU and its utilisation.
HTH.
Grant0 -
Thanks Grant, [quote="SFA" wrote:
NVidia utilities have the option to specify which applications should use their card rather than some other and also a "monitor" of sorts that confirms which program "are actually using" the card.
I'm aware of this. Although I made sure that the Capture One settings in the NVidia Control Panel specify that the program should use the GPU, the GPU monitor doesn't show any activity when I'm using C1 (I can see such activity when editing in Lightroom, by the way).
On the other hand, I have a report created by a french engineer that shows that OpenCL is heavily used in C1 version 8 with the Quadro K620 ( - in french, sorry).
So there must be something wrong in version 9. My configuration appears to be OK since the GPU is used as expected in DxO Optics pro, PS, Lightroom and Camera RAW.0 -
Christian,
I have another question : is the GPU check done each time C1 starts or only once when installing? In the latter case, how to reset the result?
Actually, I recently replaced my NVidia GeForce GT440 with the Quadro K620 in the hope of making C1 work better on my system (it is rather laggy when editing - using i7 2600 @ 3.40 Ghz with 12 Gb of RAM under Windows 7 Ultimate 64-bit).
Is C1 aware of such hardware changes?0 -
Got it!
C1 disables OpenCL when editing/processing X-Trans RAWs. There's no problem with other RAWs.
No luck! I'm using C1 especially with X-Trans RAWs because Lightroom has so many problems with these files.
Adding this to the other features that are not working when editing X-Trans RAWs... Very disappointed.
By the way : not documented in the release notes.0 -
[quote="Samoreen" wrote:
is the GPU check done each time C1 starts or only once when installing? In the latter case, how to reset the result?
Yes, also the the GPU name, driver-version and Capture One version is check, and if any changes requiring a re-build of the binaries are detected, CO will do so.[quote="Samoreen" wrote:
C1 disables OpenCL when editing/processing X-Trans RAWs
Yes, this is a current limitation of the X-trans pipeline.0 -
[quote="Christian Gruner" wrote:
[quote="Samoreen" wrote:
C1 disables OpenCL when editing/processing X-Trans RAWs
Yes, this is a current limitation of the X-trans pipeline.
This should be advertised. I hope that "current limitation" means that it's something that will be fixed in the future.
There are more and more people using cameras equipped with a X-Trans sensor and many of them are switching to C1 because of the many problems in LR with these files. I compared outputs from LR and C1 before purchasing C1 and C1 was clearly giving much better results. I discovered after the fact, while doing "real work", that C1 was more laggy when editing and processing X-Trans files. So I purchased the Quadro K260 which was supposed to perform better. This is obviously the case with non X-Trans RAWs. Unless I missed something, there's no information from P1 warning against the lack of OpenCL support for X-Trans RAWs. I was not ready for the bad surprise...0
Post is closed for comments.
Comments
9 comments