Deep Learning fx's no show. Culprit Found!

Espadon wrote on 9/24/2021, 1:49 PM

… and the culprit is … intelopencl32.dll and intelopencl64.dll which were supposed to be removed in a windows update.

See the link below for solution.

Just removing the files enabled all the Deep Learning fx’s without going into the Registry. I did though just to make sure.

As an aside, for some time now Vegas would not load with Intel UHD Graphics 630 Enabled. It just triggered an OpenCL fault so I disabled it to carry on with Nvenc. It now loads with it enabled and I now have my QSV options to Render back again.

Hope this helps anyone suffering this problem.

See

https://community.intel.com/t5/OpenCL-for-CPU/Announcement-Windows-OS-Intel-CPU-Runtime-for-OpenCL/td-p/1145986

Copy of the link:

10-19-2018 06:16 PM

1,142 Views

[Announcement][Windows* OS] Intel® CPU Runtime for OpenCL™ Applications 16.1.2 to 18.1 upgrade path, troubleshooting, and fixes

Hello Windows* OS OpenCL™ users,

*Update 20181025*

Some users have reported platform interrogation discrepancies when:

installing Intel® CPU Runtime for OpenCL™ Applications 18.1 for Windows* OS over a 16.1.2 installation

after uninstalling version 16.1.2.

OpenCL™ programs are said to observe an extra, non-existant CPU platform and/or device. Uninstallation of 16.1.2 may leave assets on disk... the following system alterations should help complete uninstallation procedure for 16.1.2:

1) Remove following registry keys:

On 32-bit OS:

HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenCL\Vendors\intelopencl32.dll

On 64-bit OS:

HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenCL\Vendors\intelopencl64.dll

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Khronos\OpenCL\Vendors\intelopencl32.dll

2) (optional) Remove following files if they exist:

On 32-bit

OS: C:\Windows\System32\intelopencl32.dll

On 64-bit

OS: C:\Windows\System32\intelopencl64.dll

C:\Windows\SysWOW64\intelopencl32.dll

*End update 20181025*

For more information on manual installation of runtimes, users should refer to the guidance in section 5.1 of the release notes.

See full 18.1 release notes

Comments

Photo_G wrote on 9/24/2021, 2:22 PM

Thanks, I'm sure this will help the community! I went ahead and checked my installation and it's all clear.

Which ones are the Ai-enabled VEGAS plugins? I found "Colorization", is that the only one?

walter-i. wrote on 9/24/2021, 3:02 PM

Which ones are the Ai-enabled VEGAS plugins? I found "Colorization", is that the only one?

See Feature List, line 9
https://www.vegascreativesoftware.info/de/forum/release-vegas-pro-19--131059/

andyrpsmith wrote on 9/25/2021, 12:17 PM

Thanks worked well, they all were enabled (3).

Former user wrote on 9/26/2021, 12:26 AM

That even works on my Ryzen computer, also that link you provided was from 2018, my computer's windows10 was installed in 2020. I have to think it's unrelated to old windows installations and this could be considered a coding bug

Some people don't have this problem though. Maybe other software adds that registry entry and the Deep Learning module doesn't like it

Espadon wrote on 9/26/2021, 4:01 AM

That even works on my Ryzen computer, also that link you provided was from 2018, my computer's windows10 was installed in 2020. I have to think it's unrelated to old windows installations and this could be considered a coding bug

Some people don't have this problem though. Maybe other software adds that registry entry and the Deep Learning module doesn't like it

Yes. My thoughts also. My Windows was installed Sept 2020. As you rightly say the intelopncl problem dates back to 2018. On my 2021 Windows installed PC, which never had the Deep Learing no-show issue, there is no Khronos entry in the Registry keys, so I presume that I must have installed an old program that installed and required the old intelopencl.

These files also prevent Vegas using the Intel UHD Graphics 630 display adapter (QSV).

Since deleting them I've tested all my apps to see if any don't work - but they all do, so I've either uninstalled the culprit or it's been updated. I'll be wathching out for this when installing new apps from now on!