PROBLEM
I'm having problems with exporting/processing images.
My images have artifacts in them when viewing/processing.
Processing/viewing images is slow.
SOLUTION
The quickest way to see if OpenCL is causing these issues is to set it to 'Never' under Preferences > General. For more information, see below:
The issues described above are usually associated with OpenCL (Open Compute Language) / Metal which enables the effective utilization of thousands of computing units within modern graphics cards. For Capture One, only relatively new GPU cards have enough computing power and onboard RAM to be utilized effectively. Whilst Hardware Acceleration is designed to increase performance in Capture One, you may also find some instances when it can decrease performance instead or cause some issues while processing and editing images. Such issues usually occur on the machines which do not meet our recommended system requirements for running Capture One. You can find those system requirements in the release notes for the particular version of the Capture One software you are using.
The issues that might be related to OpenCL / Metal
- Scrambled or somewhat 'glitched' previews when making adjustments
- Crashes when processing/exporting images
- Artifacts in processed images
- Slow processing times
- Slow mask drawing
- Crash when opening Capture One
How to define whether Hardware Acceleration is initialized?
- Ensure that OpenCL is set to 'Auto' in your Preferences.
- Reset adjustments on an image.
- Enable the focus mask by going to View > Show Focus Mask in the Capture One main menu.
- Slide the exposure slider gradually.
If the focus mask is disabled while you are increasing your exposure, Hardware Acceleration is being utilized. If it remains visible while making these adjustments, then Hardware Acceleration has failed to initialize or is not in use.
If Hardware Acceleration is stuck at 0% on initialization (Windows OS)
This is an access issue with Capture One enumerating installed OpenCL platforms. You can fix that by following the steps below:
- Close Capture One, then hold down the Windows key and press the R key on the keyboard.
- Type regedit in the window. This brings up the Registry Editor.
- Select Yes to make changes.
- Go to Computer -> HKEY_Local_Machine -> SOFTWARE -> Khronos -> OpenCL -> Vendors.
- Right-click on IntelOpenCL64.dll and choose Modify.
- Enter "1" (without the quotes) in the Value data field. Press OK.
NOTE: The name of the ' .dll ' file might differ from the one mentioned above. It usually depends on the processor embedded in your system. The path might also differ in the part Khronos -> OpenCL -> Vendors where the folder with the processor's manufacturer name might be there.
NOTE (for AMD Radeon RX 5700 graphics card users)
Delete the version-specific preferences folder:
C:\Users\UserName\AppData\Local\Phase_One\CaptureOne.exe_StrongName_y3yh4brhpfi14u41fltdrpfruizxirsn
The last part \(...)_Strongname_(...) might be different for you.
Then restart the computer and Capture One. That way, Hardware Acceleration should be fully initialized.
Learn how to find the AppData folder on Windows
Rebuilding kernels
If you have a machine that meets our recommended system requirements, you may need to rebuild the kernels needed for OpenCL / Metal to initialize properly.
Capture One 20.0.0 and later versions
macOS
Close Capture One and then delete the contents of the ImageCore folder as shown in the image below. You can find this folder by navigating to ~/Library/Application Support/Capture One/ImageCore (this can easily be done in Finder via Go > Go To Folder menu item). When you restart Capture One, OpenCL / Metal will rebuild the hardware acceleration kernels- let it finish before quitting the software. This rebuild will only need to be done once.
Windows
Similar to the procedure on macOS, delete the contents of the ImageCore folder and restart Capture One, whereby OpenCL will re-initialize.
C:\Users\User_Name\AppData\Local\CaptureOne\ImageCore
Learn how to find the AppData folder on Windows
Capture One 12.1.5 and earlier versions
macOS
Close Capture One and then delete the contents of the ImageCore folder as shown in the image below. You can find this folder by navigating to /Users/Shared/ImageCore (this can easily be done in Finder via Go -> Go To Folder menu item) When you restart Capture One, OpenCL will rebuild the hardware acceleration kernels- let it finish before quitting the software. This rebuild will only be done once.
Windows
Similar to the procedure on macOS, delete the contents of the ImageCore folder and restart Capture One, whereby OpenCL will re-initialize.
Disable Hardware Acceleration in Capture One
General guidelines
If viewing, processing, or exporting issues still occur, set the OpenCL options to Never in the General tab. Navigate to the Preferences -> General -> Hardware Acceleration (Use OpenCL for) and set the Display and Processing options to Never. Restart Capture One.
Disable Hardware Acceleration in Capture One in case of a crash at startup
Windows:
- run the script DONOT_useopencl.reg and restart Capture One (the download also contains a restore script to re-enable OpenCL useopencl.reg) Download here.
macOS:
- download OpenCL_HelpTool_21.app;
- run the app;
- you'll get an error if you didn't allow apps from unidentified developers; in this case go to System Preferences - Security & Privacy - General tab and click Open Anyway:
- in the help tool select "Disable" to disable OpenCL, "Yes" to rebuild the cache and "Relaunch" to confirm;
- you can see exactly what this script does if you control-click on the OpenCL_HelpTool_21.app, select Show Package Contents, go to Contents/Resources/Scripts and double-click the main.scpt file:
NOTE: M1-macs only
How to delete Metal kernels
Open Terminal and type:
find /private/var/folders -type d -name ‘*captureone14*’ 2>/dev/null | xargs rm -rv
The directory into which the kernels are saved are not always the same, so if you want to check where they are, try the following:
find /private/var/folders -type d -path ‘*captureone14*’ -name ‘com.apple.metal*’ 2>/dev/null
Comments
25 comments
Hi.
First of all thank you very much for your article and i hope you are healthy.
I'm using a Radeon RX 5700 and the weird thing is that i have this problem (Scrambled or somewhat 'glitched' previews when making adjustments) only when adjusting the sliders in the HDR section.
Everywhere else the adjustments are working flawlessly.
Haven't tested everything else so far but i'm wondering why only the HDR part is broken.
Any idea?
My other question is how much of a difference is there between HW-Acc on/off when using a Ryzen 2700x.
Thank you and take care.
Hi,
after deleting the content, the software still doesn't work properly, and when I reinstall C1, the files still missing.
I'm having the issue where hardware acceleration is stuck on 0. I followed the instructions in this post, but
I'm not getting the the IntelOpenCL64.DII.
What I do get is
C:\\Windows\system32\drivers\filerepository\IGLH64.INE_AMD.
The weird thing is I am not aware of having any AMD components on my computer. I have an I7 processor and an Nvidea GTX 1070 graphics.
Any help would be greatly appreciated. I have reached out to Capture One support but these days they seem a bit slow, probably because of the pandemic and everyone sitting at home working on picture files. I'm guessing.
Well, I was getting some help from Capture One support, but it seems to have disappeared with no explanation.
I have a fresh installation of Capture One and a 5700XT. The Open CL fix did not work as the issue is still persisting. I'm happy to submit logs or anything to help resolve the problem
Hello everyone
i have the same problem ....this only happens when I apply the same adjustments to many images to do a time laps ....this does not happen on all images ....but a large part of outgoing images present artifacts ....and that's a problem for me .... I followed the procedure above but I have not resolved and than the problem is not the OpenCl .... a patch must be released as soon as possible bye
I can confirm that OpenCL hardware acceleration using an AMD Radeon 5700 XT and Capture One Pro 20 is broken. Here is a demo video of the issue when editing a photo: https://www.youtube.com/watch?v=zMOD4RW7AQ0
The troubleshooting steps for the 5700 did not help. Please read the video description for more information and for other links that point to this or similar OpenCL issues related to the AMD Radeon 5700 XT.
Please Capture One, escalate this issue with AMD. This bug may loose you customers and AMD won't hear us.
Specs for reference:
Sadly, same problem here with Radeon 5600 XT (Adrenaline driver 20.7.1)
I believe they're roughly the same chip family, so that isn't surprising.
I mostly see the artifacts when using the HDR tool, or switching between presets. This is really frustrating - especially when I just upgraded to this graphics card hoping it would help speed up my photo editing flow!
I have the same problem.
I read that Capture One 20 had this problem fixed so I bought it, but this problem persist. I did all the troubleshooting and nothing. Its pretty anoying since is only the OpenCL in C1 that I have this type of problem.
5700XT user here. Tried the steps in this article. Only the last option of disabling hardware acceleration in capture one stopped the problem. Earlier attempts(regedit, deleting the preference folder which btw is in Capture_One, not Phase_One) had no benefit.
This was a real headache. Please fix it. Lots of people have this graphics card.
Hi Jeffrey,
Thank you for your comment.
In Capture One 20 (13.1.2), there is a bug fix for where Radeon RX 5700 XT GPU’s could cause Viewer glitches.
Download Capture One 20 (13.1.2) here
The issues with my 5700 XT (see https://support.captureone.com/hc/en-us/articles/360002404937/comments/360000739257) have been resolved with version 13.1.2
Thank you!
Fantastic. My faith in capture one is restored. I can confirm the recent update fixed this issue for me.
I'm still having the issues, I have an iMac 5K 2017 with a Quad-Core i5, 16GB DDR4 and Radeon Pro 570 4GB. I've never experienced other than excellence from CO. That changed after ver 13.0, I'm seeing the artifacts and discolored areas in my exports, 2 updates later nothing changes. The only way to get usable exports is by setting OpenCL to 'Never' for Processing, wich makes exporting way slower.
I hope a new update can fix this issue for good, I'm a Fujifilm user and I'm currently running Build 13.1.2.37
I downloaded v13.1.2 and it fixed my issues with my Radeon 5600 XT. Thanks so much for debugging this - I can't imagine it was trivial to figure out and fix!
Finally an update that fixed the issue. Now the OpenCl on my RX5700 is working :)
I can confirm that this update also works on Radeon 5500XT. Thank you for fixing the issue, as I built a new computer specifically for Capture One and now I can utilize the hardware as intended.
The problem still exists in Intel HD Graphics 630 onboard graphics adapter in Dell Optiplexes.
Hope that C1 will continue the fine effort on the Radeon cards and fix the Intel HD displays.
I'm having the same issue as Simon. I will need to go back to Lightroom until this gets resolved. Mine is pretty severe.
I'm having the issue where hardware acceleration is stuck on 0. I followed the instructions in this post, but
I'm not getting the the IntelOpenCL64.DII.
What I do get is
C:\\Windows\system32\drivers\filerepository\IGLH64.INE_AMD.
The weird thing is I am not aware of having any AMD components on my computer. I have an I7 processor and an Nvidea GTX 1070 graphics.
Any help would be greatly appreciated. I have reached out to Capture One support but these days they seem a bit slow, probably because of the pandemic and everyone sitting at home working on picture files. I'm guessing.
I'm still having the issues, I have an iMac 5K 2017 with a Quad-Core i5, 40GB DDR4 and Radeon Pro 580 8GB. I've never experienced other than excellence from CO.
I'v tried the steps explained here without any luck my images still have artifacts in them when procesed
The only way to get usable exports is by setting OpenCL to 'Never' for Processing, wich makes exporting way slower. I hope a new update can fix this issue for good
Dear Lily, I'm using CaptureOne 13.1.3.13 and NVIDIA GTX 1660Ti but during editing or when I save and process the image, CaptureOne uses only the integrated Intel GPU.
In the NVIDIA control panel I've forced the use of the NVIDIA GPU for the APP CaptureOne, but still the system uses only the Intel GPU. Currently I'm using Windows 10 ver 2004 build 19041.508
I've already tried to rebuild the kernel delating the ImageCore but without any sucess. However in the log file of captureone I've found this error:
2020-10-20 01:11:03.094> (ERROR) bin file failed parse [C:\Users\Archimede\AppData\Local\CaptureOne\ImageCore\13.1.3.13\ICOCL.bin] (verificationCode=2)
2020-10-20 01:11:03.094> (ERROR) bin file failed parse [C:\Users\Archimede\AppData\Local\CaptureOne\ImageCore\13.1.3.13\ICOCL1.bin] (verificationCode=2)
And for some reason the Intel GPU is the device zero, instead of NVIDIA:
Found 1 OpenCL devices on platform 0 (Intel(R) OpenCL)
Found 1 OpenCL devices on platform 1 (NVIDIA CUDA)
OpenCL Device 0 : Intel(R) UHD Graphics 630
OpenCL Device 1 : GeForce GTX 1660 Ti
Please help me to have a good performance when using captureone.
Thanks.
Dear all I have good news!! Finally I can use the NVIDIA GPU with all its potential also with CaptureOne.
First be sure that in the NVIDIA panel control your CaptureOne must use the NVIDIA card and not the internal GPU. But as you know also with this setting, CaptureOne does not use the GPU.
But, right now checking some setting in the windows settings (Select Start > Settings > System > Display), in the display tab at the bottom of the page there is graphics setup (System > Display > Graphics Settings). In this new window, The Hardware-accelerated GPU scheduling option is displayed. I did several test and for my hardware setup is it better to have GPU scheduling OFF.
In the same window at the bottom of the page you can setup other parameters such as select the software you want to manage with graphic card. In our case I choose CaptureOne selecting the option for max performance (external NVIDEA card).
Now what I did is:
This is the first time I see the NVIDIA GPU load in the task manager during kernel re-building
Here more details: https://support.captureone.com/hc/en-us/community/posts/360013722838/comments/360003400678
Enjoy
Hi Lily,
Display and Editing (CaptureOne.exe) looks use GPU1, however, Image Processing always use GPU0 (Intel) and never use GPU1 (NVIDIA) even if ImgCoreProcess.exe set as high performance on Windows 10 settings.
Could you tell me how to use NVIDIA GPU for ImgCoreProcess.exe?
I could not solve my problem with the help of this article. The problem was the graphics driver.
I have the Matebook x Pro 2020 and the original graphics driver from Microsoft Update for the Intel card caused a freeze when exporting to C1. The described manual didn't help me but gave me the idea to try the original Intel driver directly. The current driver version is 27.20.100.8935 Build Date: October 28, 2020. After installation, C1 redetects the hardware support for OpenCL. If not, then follow the instructions to delete the Image Core C:\Users\User_Name\AppData\Local\CaptureOne\ImageCore.
Hello Lily
I have the same problem on a MacBookPro (2018/I9/32GB) with a eGPU Vega64 on BigSur/Capture One 21 14.3.0.260(716b6f1). I set back the ImageCore with your script and also manually several times with no success, #97210 is open since 2 month.
Can you please advise on what to adopt or by when a fix can be expected?
Please sign in to leave a comment.