Did you see dialogue about installing USB drivers - I got this when trying out the beta version, couldn't work out what this had to do with installing a graphics card and bailed.
I did my clone backup for the just in case stuff, installed the latest driver and got the same poor results I always get with the later drivers.
I read in the release notes that after a certain driver (200 something) they would no longer support over clocked cards. My card (560ti) came over clocked from the factory so that might be at least part of the problem.
Anyway, from all that I have seen it looks like the writing is on the wall for the cheaper cards. They are game cards and Nvidia is going to keep treating them that way.
Just for kicks I installed the oldest driver I have which is 275.33 and it works better than the 296.10. I can get full playback rate with the earlier driver on a project that shows 3 cams at once. Almost there with the 296.10 driver and poor with the latest driver.
Render is fastest with the oldest driver.
Note: I can make things better with the newest driver if I set the preview ram to zero and it will be a little bit faster than with GPU=off BUT nowhere near as good as with the earlier drivers!
So it is either a way overpriced pro card or the one I have and an earlier driver.
I will save my money and use the earlier driver. The earlier drivers will not show up as an option in Vegas with Windows 8 so I will need to stay with Windows 7 until my 560ti dies or something else happens.
The latest driver causes Vegas to stop rendering half way through a render and/or crash.
I am not using the build 486. I am using the earlier one. Will 486 work better? Maybe, but I doubt it because it is a driver issue deliberately created by Nvidia to discourage us from using the cheaper cards!
Danny I am with you. I tested this early last year with my GTX460 and then with my GTX570 and 275.33 is by far the fastest driver. 296.10 is very good too and I switched over to it as overclocking with the GTX570 is a bit more stable. I use Preview RAM at the default 200, again tested it serveral times and this is the best on my system.
I also feel that Nvidia doesnt like us to use the lower end cards succesfully for "pro" applications. I recently tweaked Solidworks 2009 to accept the GTX570 as a supported card and it works as good as any Quadro card, maybe even better.
A driver for a graphic card is like tires for your car. The best and most powerful car is nothing without a matching tire.
I've updated my GTX 460 drivers so many times I've forgotten what's loaded! Checking in device manager just tells me; "Driver version: 8.17.12.8562" Any clues there??
I do not know exactly what Device Manager displays - it certainly is a strange set of numbers. Open the NVIDIA Control Panel (right hand click on the screen). At the bottom left click System Information, the first line tells you the currently intalled driver version.
I beleive the GTX560 isnt fully supported under the 275.33 driver as it came out later. I think that is one addtional reason why I changed to 296.10 as I had a 560Ti together with my 570 in my system; now I am waiting for my second GTX570 to SLI them.
was reading this thread with interest, have gtx570 Vegas build 486 Win 7 Ultimate 64 bit did clean install back to 296.10 from I think the one before this thread title and Vegas running nice again, was really starting to irritate me. Thanks for posting :)
I would like to thank everyone for contributing to this thread. I was able to install $140 GTX 570s in (2) workstations and so far they are rendering 1.5 hour test projects just fine. I am actually rendering (2) projects at once on each with no crashes.
On my primary editing rig, a 4 ghz 6-core 980X, I am seeing a 40% improvement. On my capture/backup rig, a 4 ghz 4-core I7-920, I am seeing over a 100% improvement.
I've had these workstations for (3) years and am holding-off on upgrading to Sandy Bridge CPUs until Intel releases the 3980X with 8 cores.
Hour-long program successfully rendered to MXF under 314.22, took 12 hours to render (long but understandable render time due to multiple filters, Neat NR, color corrections, sharpen, etc). Same exact render failed 5 times on 2 different setups under 314.07, both with & without GPU acceleration enabled, FWIW.
Also shorter renders to DNxHD all successful thus far with this driver.