Artificial Intelligence problem

BREDOK wrote on 8/22/2022, 9:22 AM

I have a problem even after a deep reinstall of Vegas 18 -20 I don't see many plugins
for example


FLICKER CONTROL
Artificial Intelligence
COLORIZATION
and others


Intel(R) Core(TM) i7-8750H 
64.0 GB
GTX 1080
W11

Comments

RogerS wrote on 8/22/2022, 9:45 AM

You installed the matching deep learning files for each version of Vegas?

https://www.vegascreativesoftware.info/us/forum/faq-where-can-i-download-vegas-pro-and-other-vegas-software--104782/

BREDOK wrote on 8/22/2022, 10:04 AM

hi,
Of course I have DEEP Learning Models installed. I have GPU rendering.
It doesn't work in any Vegas 18-20

I have GPU rendering.




Howard-Vigorita wrote on 8/22/2022, 10:14 AM

@BREDOK There was mention in another thread of someone having to clear cache and do resets on startup after plugin and fx listings got messed up.

RogerS wrote on 8/22/2022, 10:24 AM

Since you have the models installed I'd try the reset then (hold shift and control when you double-click to start Vegas).

I would also disable legacy GPU rendering as you have a modern GPU and can use NVENC.
Just curious but do you really use all of those old features?

BREDOK wrote on 8/22/2022, 10:30 AM

I have done the reset several times, everything returns to the original values.
It still doesn't see the plugins even though everything is at the original values.
I use the old functions often. For example, the QUICKTIME plugin is important.



 

BREDOK wrote on 8/22/2022, 10:32 AM

RogerS wrote on 8/22/2022, 10:36 AM

Does this help in your case?

https://www.vegascreativesoftware.info/us/forum/missing-smart-zoom-in-vegas-pro-19--131572/?page=2

BREDOK wrote on 8/22/2022, 11:03 AM

Many thanks to RogerS and  Espadon 

Problem solved!

 

Espadon wrote on 11/19/2021, 1:17 PM

 

You may have the Intel Opencl problem. To check, on your C Drive search for intelopencl*.dll

If intelopencl32.dll and / or intelopencl64.dll show up do the following:

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

This has worked for me and some others. Hope this helps you.

BREDOK wrote on 8/22/2022, 11:11 AM

andyrpsmith wrote on 8/22/2022, 11:11 AM

Interesting solution as I had this issue some time ago (i5 intel) and what was happening was the tbb.dll file was being read from the intel folder rather than the Vegas folder. So the solution was to copy the Vegas tbb.dll file to the intel folder location (reversible so long as you rename the existing tbb.dll file in the intel folder first). This solved it for me and some others who had this issue at the time.

Howard-Vigorita wrote on 8/22/2022, 1:07 PM

Many thanks to RogerS and  Espadon 

Problem solved! ...

1) Remove following registry keys: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: ...

C:\Windows\System32\intelopencl64.dll

C:\Windows\SysWOW64\intelopencl32.dll

@BREDOK Out of curiosity I checked my systems. None have those dlls, older systems have nothing in registry below

../Khronos\OpenCL\Vendors\

and newest 11900k has no references to Khronos at all. I think yours may have been leftovers from old Intel drivers. I regularly use DDU when rolling back Intel graphics drivers which I believe clears out obsolete references like that.