AI Models Not Showing In Vegas 18 All Builds

Sassylola wrote on 10/30/2020, 3:49 PM

My AI models were not showing up in any of the Vegas 18 builds unless I had Hardware Decoder in file I/O set to off. So I put a new copy of Win 10 Pro on my PC, installed the latest AMD video driver and chipset driver. Updated Windows.

When I first installed Vegas 18 Build 373 on my new copy of Windows 10 Pro, I went to VideoFx and could see style transfer, but it said I needed the Deep Learning Models installed. I then download the Deep Learning Models and installed them. I thought I finally had it fixed. I started to add some of my programs back one at a time and then checked to make sure I was still seeing my AI Fx's.

I then added Internet Download Manager and added that extension to Firefox, I then added Sony Catalyst Browse ( I use that program to archive my video footage from my AX 700). I then checked Vegas 18 again and the AI models were not showing up. I then uninstalled Catalyst Browse, and disabled the IDM extension in Firefox. I restarted my PC. Still no AI in VideoFx. I uninstalled and reinstalled Vegas a few times along with the deep learning models and now if I set Hardware Decoder to off, none of my Deep Learning Models show up.

I have been in contact with support they said they will have to work on it on their end. They said turn off Hardware decoder for now. I thought maybe the new build would help but now when my decoder is set to off it is not working.

Any suggestions? Thank You.

My PC specs in my signature

Back to post

Comments

Illusion wrote on 11/6/2020, 2:45 PM

The solution worked for me also.

Can you check the driver update in help menu, it now only gives the system driver and nothing from the internet.

Same here, says "Not found"

andyrpsmith wrote on 11/6/2020, 2:56 PM

same as me, it worked before giving game & studio options. I have let Vegas Pascal know.

VEGASPascal wrote on 11/6/2020, 3:17 PM

Solution for both users. VEGAS Pro18 is using the wrong "tbb.dll" at start.

Both user replaced the "tbb.dll" in the Intel folders with the version in VEGAS folder. After this it worked.

andyrpsmith wrote on 11/6/2020, 3:44 PM

Many thanks indeed for helping us to resolve this issue - Rock on V18.

walter-i. wrote on 11/6/2020, 3:49 PM

I only have a single icon in the plug-in window - and all styles can be selected in the "Style" selection list.
Is that okay?

j-v wrote on 11/6/2020, 4:18 PM

I see something else on my laptop

andyrpsmith wrote on 11/6/2020, 4:52 PM

I only have a single icon in the plug-in window - and all styles can be selected in the "Style" selection list.
Is that okay?

Walter, you should see all the options in the window. Did you do the tbb.dll transfer or did you already have the AI FX showing?

andyrpsmith wrote on 11/6/2020, 4:53 PM

I see something else on my laptop

j-v do you have these

C:\Program Files\VEGAS\VEGAS Pro 18.0\models. Could you find in this path the file "style_model_01_v1.xml" and "style_model_01_v2.xml"?

what you see is a sign that V18 is not seeing the model files so you get half of the eye missing.

[j-v, grateful if you could help me - PM sent - thanks]

j-v wrote on 11/6/2020, 5:05 PM

This is what I'm seeing

BTW
I'm trying to give help only on this forum ( and other fora)

andyrpsmith wrote on 11/7/2020, 5:29 AM

Solution for both users. VEGAS Pro18 is using the wrong "tbb.dll" at start.

Both user replaced the "tbb.dll" in the Intel folders with the version in VEGAS folder. After this it worked.

The other thing I've noticed since replacing the tbb.dll in the intel folders with the Vegas one is that on start-up Vegas does not become static for 8 seconds where the menu commands do not respond, they are responsive immediately.

VEGASPascal wrote on 11/7/2020, 6:08 AM

I only have a single icon in the plug-in window - and all styles can be selected in the "Style" selection list.
Is that okay?

I will update the preset file for the German language

walter-i. wrote on 11/7/2020, 2:30 PM

I will update the preset file for the German language

Then this is only an "optical" problem that will be fixed in one of the next updates. I can execute the selection and thus the function.

Thanks you in advance @VEGASPascal