Nvidia 310.70 whql ruined my Vegas 11 totally

ritsmer wrote on 12/25/2012, 6:01 AM
Just updated my 310.33 to 310.70 whql, rebooted the machine and the new Nvidia driver ruined my Vegas 11 totally.

My current project is a 31 seconds time-lapse consisting of 241 jpg's.
I used track motion and track-FX to improve the stills.

I could edit, preview and render the project well.

After updating to 310.70 whql (whql is an acronym for Windows Hardware Quality Labs!!) the following happened when rendering:
1) some of the jpg's became just black frames
2) for about 1 of 10 of the jpg's the track motion was omitted.
3) for some of the jpg's the track-FX was also omitted.

I rolled back the update, rebooted the machine and now everything works as perfectly as always.

It is not the first time that a Nvidia driver update has ruined my super stable Vegas installation - I wonder how many of the reported "Vegas problems" in this forum actually are due to the immature Nvidia drivers....

@ForumAdmin: if SCS is interested, then just pm me and I can upload the project with media.

Comments

monoparadox wrote on 12/25/2012, 10:59 AM
I have also had some stability issues after upgrading. Turning off GPU playback has removed them, but I had Vegas 12 running pretty well with previous drivers.

tom
Paul Masters wrote on 12/25/2012, 11:17 AM
I have had problems with video drivers when using the one Windows update offers. Because of that, I hide those updates so they won't keep being shown.

While the drivers say NVIDIA in the installed programs list, I now always get the update from the video card manufacturer. Currently I am using EVGA so I get the updates from them. Since doing that I have had no problems with video driver updates.

Of course, I may have just been lucky. And, as they say: "Your mileage may vary".

Paul Masters
wilvan wrote on 12/26/2012, 2:40 AM
I did upgrade my quadro 4000's drivers to 307.45 WHQL because after effects being much more effective . ( and boris RED )

Tried to turn on GPU in vegas 12 , just for fun and testing , things got terribly slow in preview and noticed vegas 12 ( as it has been doing since beta testing ) using 8 % CPU power when doing nothing at all .
So turned GPU back off , as it has always been on my workstation .

I would have assumed at least the quadro cards being properly supported :-(


Sony  PXW-FS7K and 2 x Sony PXW-Z280  ( optimised as per Doug Jensen Master Classes and Alister Chapman advices ) Sony A7 IV
2 x HP Z840 workstations , each as follows : WIN10 pro x 64 , 2 x 10 core Xeon E5-2687W V3 at 3.5 GHz , 256 GB reg ECC RAM , HP nvidia quadro RTX A5000 ( 24GB ), 3 x samsung 970 EVO Plus 1TB M.2 2280 PCIe 3.0 x4  , 3 x SSD 1TB samsung 860 pro , 3 x 3TB WD3003FZEX.
SONY Vegas Pro 13 build 453  ( user since version 4 ) , SONY DVDarch , SONY SoundForge(s) , SONY Acid Pro(s) , SONY Cinescore ( each year buying upgrades for all of them since vegas pro 4 )
(MAGIX) Vegas pro 14 ( bought it as a kind of support but never installed it )
SONY CATALYST browse 
Adobe Photoshop  CC 2023
Adobe After Effects CC 2023 & Adobe Media Encoder CC 2023
Avid Media Composer 2022.xx ( started with the FREE Avid Media Composer First in 2019 )
Dedicated solely editing systems , fully optimized , windows 10 pro x 64 
( win10 pro operating systems , all most silly garbage and kid's stuff of microsoft entirely removed , never update win 10 unless required for editing purposes or ( maybe ) after a while when updates have proven to be reliable and no needless microsoft kid's stuff is added in the updates )