Problem with 384 notebook drivers from NVidia

Cornico wrote on 8/3/2017, 12:45 PM

Since half of july I saw a problem using FX in al my Vegas versions.
After applying a FX there was no change in my preview.
But after closing the FX Window suddenly the effect appears in preview.
For me strange behaviour.

Installed was/were 384.76-notebook-win10-64bit-international-whql and to see if there was a fix later the 384.94-notebook-win10-64bit-international-whql.

Both had that strange behaviour.
Installing the older 381.89-notebook-win10-64bit-international-whql restored everything.
Am I the only one?

Comments

michael-harrison wrote on 11/9/2017, 7:48 AM

I've seen the same behavior when I set the GPU to Nvidia. I haven't gone to the trouble of downgrading the driver because I've found that if I set the GPU to my other chipset, Intel, that the previews work fine when editing titles or fx

System 1:

Windows 10
i9-10850K 10 Core
128.0G RAM
Nvidia GTX 1660 Studio [most likely latest]
Resolution        1920 x 1080 x 60 hertz
Video Memory 6G GDDR5

 

System 2:

Lenovo Yoga 720
Core i7-7700 2.8Ghz quad core, 8 logical
16G ram
Intel HD 630 gpu 1G vram
Nvidia GTX 1050 gpu 2G vram

 

vkmast wrote on 11/9/2017, 7:58 AM

Cornico did update his findings later e.g. here.

RogerS wrote on 12/12/2017, 3:55 PM

I have the same issue. Using my 1050 (laptop GPU) and Vegas the titles no longer update in real time. Switch to Intel and it is normal again. Annoying bug.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (latest available driver), dual internal SSD (1TB; 1TB), Windows 10 64 bit

VEGAS Pro 19.651
VEGAS Pro 20.411
VEGAS Pro 21.208

Try the
VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

michael-harrison wrote on 12/12/2017, 4:11 PM

I have the same issue. Using my 1050 (laptop GPU) and Vegas the titles no longer update in real time. Switch to Intel and it is normal again. Annoying bug.

It is, but there's a reliable workaround (so far, anyway). For Windows 10. Will probably work for 8 and 7 as well but I can't verify.

Open the nvidia control panel (rt-click on desktop) and under Manage 3D Settings | Program Settings find Movie Studio in the list or add it if it's not there. Choose "Integrated Graphics" in the preferred graphics processor dropdown. Save.

Open MS and choose the Nvidia GPU in the Video tab in preferences.

Now you should see that the titles/fx/etc update in real time.

But also...

When you render, it will use the nvidia gpu. You can verify this by opening the Task manager and watching the GPU Engine column (enable it if it's not there) and you'll see GPU 1 show up when you render.

System 1:

Windows 10
i9-10850K 10 Core
128.0G RAM
Nvidia GTX 1660 Studio [most likely latest]
Resolution        1920 x 1080 x 60 hertz
Video Memory 6G GDDR5

 

System 2:

Lenovo Yoga 720
Core i7-7700 2.8Ghz quad core, 8 logical
16G ram
Intel HD 630 gpu 1G vram
Nvidia GTX 1050 gpu 2G vram

 

RogerS wrote on 12/12/2017, 4:23 PM

Hi Michael, thank you for your message. I'm on Windows 10 and Vegas Pro 15. I just tried to do this and it seems to move Vegas to the Intel GPU for timeline playback as well. The Intel playback performance isn't as good as NVIDIA though.

I think keeping the driver set to NVIDIA and then switching Vegas internally to Intel for editing titles and fx only might be a better bet for me. It's hard to edit when you have low playback framerates.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (latest available driver), dual internal SSD (1TB; 1TB), Windows 10 64 bit

VEGAS Pro 19.651
VEGAS Pro 20.411
VEGAS Pro 21.208

Try the
VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

michael-harrison wrote on 12/12/2017, 6:36 PM

That's interesting. I understood that Vegas Movie Studio and Vegas Pro used a common codebase but either that's not the case between our versions (I've got MS 14) or our different hardware is giving us different results.

I'm consistently seeing gpu1 being used with my config.

no matter. at least you have a solution that works for you

System 1:

Windows 10
i9-10850K 10 Core
128.0G RAM
Nvidia GTX 1660 Studio [most likely latest]
Resolution        1920 x 1080 x 60 hertz
Video Memory 6G GDDR5

 

System 2:

Lenovo Yoga 720
Core i7-7700 2.8Ghz quad core, 8 logical
16G ram
Intel HD 630 gpu 1G vram
Nvidia GTX 1050 gpu 2G vram

 

Koji_K wrote on 10/14/2019, 11:31 PM

Thank you so much Michael, really. Saved me a whole night of searching online

Ganag wrote on 3/13/2023, 12:34 PM

Thanks Michael for the solution!

RogerS wrote on 3/13/2023, 7:15 PM

A better solution is to use NVIDIA driver 522.30 and keep Windows Graphics Settings set to NVIDIA.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (latest available driver), dual internal SSD (1TB; 1TB), Windows 10 64 bit

VEGAS Pro 19.651
VEGAS Pro 20.411
VEGAS Pro 21.208

Try the
VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7