Hardware acceleration doesn't work
My hardware acceleration has stopped working since updating my NVIDIA Studio Driver to Version 471.11 yesterday.
It was working fine on the previous driver version.
Anyone else have this problem?
NVIDIA GeForce GTX 1660 SUPER
C1 Build: 14.2.0.48
-
Yeah, I have the same problem with 471.11 on a GTX 1060. The OpenCL compilation fails at startup.
Here's my log from ImgCoreOCL:
2021-06-26 19:19:51.310> Logging is now active.
2021-06-26 19:19:51.310> CPU: AuthenticAMD [AMD Ryzen 7 2700X Eight-Core Processor]
2021-06-26 19:19:51.310> CPU features: MMX, SSE, SSE2, SSE3, SSSE3, SSE41, SSE42, AVX, AVX2, FMA, F16C, MOVBE, CX8, RDRAND, RDSEED
2021-06-26 19:19:51.310> CPU features: ADX, RDTSCP, POPCNT, BMI1, BMI2, LZCNT
2021-06-26 19:19:51.311> OpenCL initialization...
2021-06-26 19:19:51.345> Found 1 OpenCL platforms
2021-06-26 19:19:51.345> Found 1 OpenCL devices on platform 0 (NVIDIA CUDA)
2021-06-26 19:19:51.346> OpenCL Device 0 : NVIDIA GeForce GTX 1060 6GB
2021-06-26 19:19:51.346> OpenCL Driver Version : 471.11
2021-06-26 19:19:51.346> OpenCL Compute Units : 10
2021-06-26 19:19:51.346> OpenCL Nvidia Compute Capability : 6.1
2021-06-26 19:19:51.346> OpenCL CL_DEVICE_HOST_UNIFIED_MEMORY : 0
2021-06-26 19:19:51.346> OpenCL CL_DEVICE_GLOBAL_MEM_CACHE_SIZE : 491520
2021-06-26 19:19:51.346> OpenCL CL_DEVICE_GLOBAL_MEM_CACHELINE_SIZE : 128
2021-06-26 19:19:51.346> OpenCL CL_DEVICE_GLOBAL_MEM_CACHE_TYPE : 2
2021-06-26 19:19:51.346> OpenCL CL_DEVICE_GLOBAL_MEM_SIZE : 6144 mb
2021-06-26 19:19:51.346> OpenCL CL_DEVICE_MAX_MEM_ALLOC_SIZE : 1536 mb
2021-06-26 19:19:51.346> OpenCL CL_DEVICE_LOCAL_MEM_SIZE : 49152
2021-06-26 19:19:51.346> OpenCL CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE : 65536
2021-06-26 19:19:51.346> OpenCL CL_DEVICE_VENDOR_ID : 4318
2021-06-26 19:19:51.346> OpenCL CL_DEVICE_VENDOR : NVIDIA Corporation
2021-06-26 19:19:51.346> OpenCL CL_DEVICE_EXTENSIONS : cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_device_uuid cl_khr_pci_bus_info
2021-06-26 19:19:51.346> OpenCL CL_DEVICE_MAX_WORK_GROUP_SIZE : 1024
2021-06-26 19:19:51.346> OpenCL CL_DEVICE_ADDRESS_BITS : 64
2021-06-26 19:19:51.469> OpenCL : Loading [C:\Users\alanh\AppData\Local\CaptureOne\ImageCore\14.2.0.48\ICOCL.bin] started
2021-06-26 19:19:51.469> OpenCL : Loading [C:\Users\alanh\AppData\Local\CaptureOne\ImageCore\14.2.0.48\ICOCL.bin] Incomplete
2021-06-26 19:19:51.484> OpenCL : Building kernels on dev 0 [NVIDIA GeForce GTX 1060 6GB]
2021-06-26 19:19:51.606> Compiled 0/1265
2021-06-26 19:19:52.120> Compiled 25/1265
2021-06-26 19:19:52.542> (ERROR) Compilation of ApplyExposure_z3dbd1ff6828 failed : CL unknown error code : -9999
2021-06-26 19:19:52.542> (ERROR) Compilation of ApplyExposure_z3dbd1ff6828 returned : CL unknown error code : -9999
ptxas fatal : Unresolved extern function '__nv_fast_exp2f'2021-06-26 19:19:52.542> (ERROR) Failed to create ApplyExposure_z3dbd1ff6828 : CL unknown error code : -9999
2021-06-26 19:19:52.643> (ERROR) Compilation of ApplyExposure_z3dbd1ff68213 failed : CL unknown error code : -9999
2021-06-26 19:19:52.643> (ERROR) Compilation of ApplyExposure_z3dbd1ff68213 returned : CL unknown error code : -9999
ptxas fatal : Unresolved extern function '__nv_fast_exp2f'2021-06-26 19:19:52.643> (ERROR) Failed to create ApplyExposure_z3dbd1ff68213 : CL unknown error code : -9999
2021-06-26 19:19:52.643> Compiled 50/12650 -
we are discussing also here : https://support.captureone.com/hc/en-us/community/posts/360013722838--WIndows-10-2004-C1-13-1-3-13-introduces-new-bugs-in-windows-management?page=2#community_comment_4403113795345
my error message seems to be ERROR) bin file failed parse [C:\Users\XXXX\AppData\Local\CaptureOne\ImageCore\14.2.0.48\ICOCL.bin] (verificationCode=7)
try to delate the all the file in this folder C:\Users\YOUR USER\AppData\Local\CaptureOne\ImageCore\14.2.0.48, then the next time you open captureone, it rebuild the kernel and perfoms the bechmarking.
finger crossed.
0 -
Thank you for the suggestion, but deleting the 14.2.0.48 folder doesn't fix it for me.
I have the same error: (ERROR) bin file failed parse [C:\Users\XXXX\AppData\Local\CaptureOne\ImageCore\14.2.0.48\ICOCL.bin] (verificationCode=7)
0 -
You could try to manually install this KB5003690 because it seems to fix the GPU performance for games.
Or you can wait until 13rd of July when this fix is available in the cumulative update (LCU).0 -
That's interesting. Maybe my hardware acceleration was broken before this driver update due to one of these recent windows updates? ...
KB4023057 on 12th June
KB5003637 on 9th JuneI only normally check when I update C1 or the video driver.
0 -
It's the latest NVIDIA driver. After installing 471.11, OpenCL stops compiling, deleting ImageCore doesn't help. Reverting to any older version results in a shader rebuild and HW acceleration starts working again.
0 -
Thank you for the update. I hope the next driver update fixes this.
0 -
Do you think Capture One team will contact Nvidia developers in order to fix this issue or we should wait forever and ever? Do we need to "submit a request" to capture one team? I can do that right now, If you will do the same, then they will see similar requests :-)
0 -
Looks like it's a problem in Premiere Pro too,,,
Might be best to report it to NVIDIA directly.
0 -
@John Kane: for now I've wrote to captureone team and this the first reply "There is a known issue with the driver, ....... "
Then they know that...
Should we write and report also to NVIDIA?
0 -
I think it's a mix of things. I also have the latest studio drivers installed, and all software on my system is still able to use openCL. AffinityPhoto, several openCL benchmark programs, all still work. The Asus GPU tweak utility also reports that openCL is enabled.
So what i am guessing is that there are several ways to detect openCL support. And from what i gather from captureOnes support documents, they rely on a certain registry key to detect openCL support. And that has probably been removed by the latest driver.
There are obviously otherways to detect that openCL is there, and the other software on my system is doing this. When i examine the driver details for the 3090, it clearly has the opencl driver loaded in version 3.1.
My guess is that CaptureOne is using an outdated, not supported method (looking in the registry) to figure out if openCl is installed, and that key was removed.
So yeah, something changed in the nvidia driver. But only CaptureOne is effected, so i guess the bug is mostlikely on the CaptureOne side.
Frank
0 -
According to the log, it does detect OpenCL and starts compiling, it fails after successfully compiling several shaders. There will be a problem with just a single function or two, which Affinity and Adobe somehow managed to not use in their code. And NVIDIA's QA seems to work like "Photoshop works, let's release it".
0 -
I apologize, i overread the log output on top. The same error get's reported by the darktable developers on Linux. So it seems more likely that the opencl code that capture one is using is accessing a no longer existing function in the nvidia driver, and that is most likely a bug in nvidia's driver. It could also be a removal of a deprecated or old openCL api, that the code in darktable and CaptureOne is still using. On the linux side of things Nvidia promised to fix this in the next release.
Regarding the QA of NVidia, i am actually pretty surprised, given the complexity of their buisiness, that their quality is as good as it is.
Frank
0 -
There are also complaints from Topaz users about problems with the latest NVidia and that programs are crashing, etc. I rolled back the Nvidia driver and all is well for me. Until the next release of NVidia...
0 -
Hi Kevin, which NVIDIA dirver are you using?
I think the problem is with OpenCL 3.0 specification and the compatibility with older version (I guess captureone uses 1.2 version)
Highlights of NVIDIA’s OpenCL 3.0 Implementation:
Existing OpenCL 1.x based applications will continue to work with NVIDIA’s OpenCL 3.0 drivers without any changes.
In addition to full OpenCL 1.2 compatibility, NVIDIA’s OpenCL 3.0 drivers now deliver significant optional OpenCL 3.0 functionality
0 -
I went to nVidia and used the previous driver. So right now I have 462.59. The one that broke C1 is the current one 471.11 released 6/23/21. It may very well be the OpenCL 3.0. I assume (perhaps wrongly) that many of these software packages are using Qt framework, and perhaps Qt has not been updated to v3.0. But whatever, it is something that I am sure C1 and nVidia are working on from both ends.
0 -
it sounds good. As soon as you have news that they solved the issue, please tell us the solution. thanks.
0 -
same problem here: Graphics defects with new Studio Dri | NVIDIA GeForce Forums and here Photoshop 22.4.1 with 462.59 drivers | NVIDIA GeForce Forums
0 -
has anyone tried to install the KB5003690 or the latest KB5004237 ?
0 -
I have KB5004237 but nothing has changed :-/
HW acceleration doesn't work with latest driver.
I have rolling back to 462.59 and now HW accel its working ...
0 -
Known bug on NVIDIA's side now, will be fixed in next driver release. Only 471.11 (and 471.22 hotfix) is affected.
0 -
Thank you for the update - great news.
0 -
And it's fixed. 471.41 released today and confirmed working.
0 -
Yes, I see 471.41 is out. I will try it.
I think this is the key factor:
Added support for OpenCL 3.02, the latest major version of OpenCL maintaining backward
compatibility with OpenCL 1.2. NVIDIA OpenCL 3.0 continues to support existing OpenCL 1.2
functionality as well as Khronos and vendor extensions that are already supported with NVIDIA
OpenCL 1.2 drivers.Fixed Issues in this Release
[Capture One]: Hardware acceleration stops working. [3338552]Full details here https://us.download.nvidia.com/Windows/471.41/471.41-win10-nsd-release-notes.pdf
0 -
I updated to this driver and can confirm that, at least on my system, hardware acceleration is in use. Exporting 48 50MB raws to tif/uncompressed went from 75% cpu to 10% cpu, and a lot faster (like 2:40m to 0:25m).
Frank
0 -
Yes, this works for me! Many thanks everyone :)
0 -
Dear, I would update Capture One 21 to the v. 14.4.1.6 .
Does anyone know if this could cause issue with NVIDIA driver 471.41. Or do I need to update also NVIDIA video card driver?
Thanks.
0
Post is closed for comments.
Comments
27 comments