Vegas Pro 13 and Windows 10

Gibbo wrote on 4/15/2016, 3:21 AM

I have Vegas Pro 13 installed on both my desktop and a laptop computer.
The desktop was running Windows 7 64 bit and the laptop is running Windows 8.1.
The desktop has an Intel Core i7-4790 processor and the laptop has an Intel Core i7-4710HQ processor.
The desktop has an NVidia GeForce GTX 970 graphics card and the laptop has an NVidia GeForce GTX 850M graphics card.
Both computers have 16 Gb of RAM
In both computers, Options – Preferences - Video – GPU acceleration of video processing, was set to the name of their graphics card.
With Full-resolution rendering quality set to Good in the Properties menu, when playing the video from the timeline, both computers gave quite good rendering quality.

I have now changed the desktop computer over to Windows 10 Home 64 bit.
I have made no changes to Vegas Pro 13, but when I check the Options – Preferences - Video – GPU acceleration of video processing on the desktop, it is now set to OFF and there is no option available to set it to the graphics card.
So the graphics card is obviously not being picked up in Windows 10 and the resulting playback quality from the desktop timeline is now so bad that it is completely unusable.
Has anyone else had the same problem?
Can anyone please help with a solution?
Gibbo

Comments

Steve Grisetti wrote on 4/15/2016, 7:35 AM

Have you uninstalled/reinstalled the program since upgrading to Windows 10?

Gibbo wrote on 4/15/2016, 10:36 PM

No.
There have been no changes to the computer or the programs, other than downloading and installing Windows 10..

Former user wrote on 4/15/2016, 11:14 PM

What drivers are being used by Windows 10 for your video cards?

Gibbo wrote on 4/17/2016, 4:41 PM

Driver version 10.18.13.6451 dated 7 March 2016. which I understand is the current driver.

PeterDuke wrote on 4/18/2016, 1:23 AM

I have had a few problems after upgrading to Win 10 where uninstalling and re-installing the programs fixed them.

I suggest that you try that before doing anything else.

Gibbo wrote on 4/20/2016, 8:59 PM

I have tried an uninstall and reinstall of VP13 without success. For some reason in Windows 10, the graphics card is not being picked up when I start VP13. Can any one please advise how to correct this.

ushere wrote on 4/20/2016, 9:10 PM

did you do clean installs or updates?

updates went fine on our office boxes but our two nle boxes had strange quirks that disappeared after clean installs...

OldSmoke wrote on 4/20/2016, 9:36 PM

Check the "OpenCL Memory Filter Size" setting on the internal tab under preferences. Maybe the value is higher then your GPU memory and if so, VP wont list the card as an option for GPU acceleration.

Gibbo wrote on 4/21/2016, 12:19 AM

Thanks ushere.
I reinstalled from the downloaded file for the upgrade from VP12 to VP13
I will try a clean install later

Gibbo wrote on 4/21/2016, 12:23 AM

Thanks OldSmoke.
I could not find the OpenCL Memory Filter Size tab in VP13.
Could you please detail all steps on how to get to it.

Gibbo wrote on 4/21/2016, 1:53 AM

I tried a clean install of VP13, without success.
Since then, while trying out different settings I have got the video playback from the timeline now rendering OK. But I am not sure which changed setting did the trick.
I have now also noticed that New Blue Video Essentials VI is not working.
I may have to revert to Windows 7 unless I can get rid of these Windows 10 bugs.

OldSmoke wrote on 4/21/2016, 11:40 AM

I believe with "clean install" a clean install of Windows 10 was meant. I also had issues on one PC that I upgraded from 7 to 10; after a clean Win 10 install all is working well and better.

The "Internal" tab will appear when you press and hold SHIFT while clicking "preferences" under the options menu.

Gibbo wrote on 4/22/2016, 8:30 AM

In the transition from Windows 7 to Windows 10, two problems arose with VP13.
Video playback from the timeline was not rendering properly, but changing the timeline rendering quality setting, fixed that.
New Blue Video Essentials V! was also not working and following a suggestion from Edward of New Blue, I checked and found that the Bypass Effects option had somehow become selected. Unchecking it fixed the problem.
I am unsure how or why those settings became changed during the transition from Windows 7 to Windows 10, but VP13 is now back in full operation, so thanks folks for your assistance.