Comments

diverG wrote on 3/14/2012, 8:36 AM
No problems so far.

Sys 1 Gig Z-890-UD, i9 285K @ 3.7 Ghz 64gb ram, 250gb SSD system, Plus 2x2Tb m2,  GTX 4060 ti, BMIP4k video out. Vegas 19 & 122(194), Edius 8.3WG and DVResolve19 Studio. Win 11 Pro. Latest graphic drivers.

Sys 2 Laptop 'Clevo' i7 6700K @ 3.0ghz, 16gb ram, 250gb SSd + 2Tb hdd,   nvidia 940 M graphics. VP17, Plus Edius 8WG Win 10 Pro (22H2) Resolve18

 

ThomasIslandStudio wrote on 3/14/2012, 9:34 AM
My driver failed to install every time I tried. Very odd. I was REALLY hoping that would fix all my V11 crashes that are happening, but can't even install it. V11 is useless to me right now... very frustrating.
JasonATL wrote on 3/14/2012, 10:27 AM
My driver failed to install every time I tried. Very odd. I was REALLY hoping that would fix all my V11 crashes that are happening, but can't even install it. V11 is useless to me right now... very frustrating.

The fact that V11 crashes so much for you and this driver won't install could be symptoms of the same illness. What that illness is, I don't know. But, I had some horrible issues early on that got much better when I did a full clean install of the software that came with my video card. It updated DirectX versions, going back several years. It made a huge difference. Also, subsequent to that, I had an issue with my video card. After contacting the manufacturer, they determined that it needed to be replaced and RMA'd it. Since getting the replacement, I've had no issues installing or updating drivers.

I suggest contacting your video card manufacturer to see if they can help with the driver update. That just isn't normal for a system, I don't think. Also, if you haven't tried already, you might try the "Custom" install option for the new driver and then select the "Clean Install" option. Finally, you've probably made sure of this already, but just double-check that you are installing the right driver for your OS (e.g., 32-bit vs. 64-bit). Again, just trying to help -- not suggesting that you don't know this stuff already. These are things that have caused me issues in the past.
Dan Sherman wrote on 3/14/2012, 11:13 AM
Thanks for the heads up on the new driver.
Installed fine.
OldSmoke wrote on 3/14/2012, 12:45 PM
I have not tried the new driver on my system (ASUS ENGTX570) but I can share my experience with Nivida drivers which I posted here:

http://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=804297&Replies=10

Maybe that helps.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

Zeitgeist wrote on 3/14/2012, 1:15 PM
Seems Vegas needs an update to match the new driver, so not updating the video driver would be better than updating. Is this correct thinking?
diverG wrote on 3/14/2012, 2:26 PM
>>Seems Vegas needs an update to match the new driver.

The logic behind this statement?

Geoff

Sys 1 Gig Z-890-UD, i9 285K @ 3.7 Ghz 64gb ram, 250gb SSD system, Plus 2x2Tb m2,  GTX 4060 ti, BMIP4k video out. Vegas 19 & 122(194), Edius 8.3WG and DVResolve19 Studio. Win 11 Pro. Latest graphic drivers.

Sys 2 Laptop 'Clevo' i7 6700K @ 3.0ghz, 16gb ram, 250gb SSd + 2Tb hdd,   nvidia 940 M graphics. VP17, Plus Edius 8WG Win 10 Pro (22H2) Resolve18

 

Zeitgeist wrote on 3/14/2012, 2:45 PM
The logic is the latest update of Vegas came before the update of the nvidia drivers, so the vegas update has never been tested on the newer nvidia drivers because they did not exist at that time. We need a new vegas version update tested with the newer nvidia drivers in order to have the most compatibility possible. I am asking if this is true or even partly true. I don't want to update my drivers and have vegas work worse than what it is now.

So, the release of vegas updates should state what video drivers were used during the testing of that particular update. Seems to me video drivers update more often than vegas and could cause some of the problems. Again, I am asking & have no absolute answer. Does anyone?
Steve Mann wrote on 3/14/2012, 3:11 PM
"Seems Vegas needs an update to match the new driver, so not updating the video driver would be better than updating. Is this correct thinking?"

It's usually the other way around. The Software Developer finds problems in the driver firmware and the drivers get update to fix problems. Admittedly the focus is on gaming, here is the release notes from nVidia. The thing to notice is that the driver is updated to fix problems running specific games.
http://us.download.nvidia.com/Windows/296.10/296.10-Win7-WinVista-Desktop-Release-Notes.pdf
OldSmoke wrote on 3/14/2012, 3:21 PM
I doubt that SCS is looking at all into driver issues. As mentioned in my other post, things got worse with each driver higher then 275.33. I am downloading the latest driver now and see whether it is any better then my current one; I am still using 275.33.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

vkmast wrote on 3/14/2012, 3:51 PM
You may or may not remember this in a recent thread on the forum

Reply by: ForumAdmin Sony Creative Software Moderator
OldSmoke wrote on 3/14/2012, 4:16 PM
Ok, I downloaded and installed the latest driver (296.10) and must report that it is the first driver (on my system) since 275.33 that is stable and produces the same rendering times.

Rendering times are related to the SCS PressReleaseProject when rendered to XDCAM EX 1920x1080-60i 35Mbps VBR and MC 1080 Internet (these are the same templates used by SCS for their own tests).

296.10 works fine here.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

JJKizak wrote on 3/14/2012, 4:23 PM
Installed and no problems. Yet.
JJK
Zeitgeist wrote on 3/14/2012, 5:04 PM
I noticed things got worse when I updated my driver, too. So I don't think it is the other way around at all. In fact I think my argument is more logical than reversing it. Reversing it makes no sense, since drivers get updated more often than software. Nvidia updates for games devs more likely than for Vegas. SCS probably has a hard time keeping up with game advances.
Peter Riding wrote on 3/14/2012, 5:07 PM
Installed this morning and did a complete project of 30 mins from start to finish, then multiple renders in several DVD variants having nested 3 segments. No problems.

Nvidia GTX570. The previous driver was also up to date and problem free for me.

Vegas Pro 11 (most recent), 64 bit, Windows 7 Ultimate. i7 950 4 core 8 thread. Note this machine has never had a clean reinstall. Windows 7 is even over the top of Vista!

Pete
Zeitgeist wrote on 3/14/2012, 5:11 PM
You need to do more than that to stress out vegas. Trying using more plugs and different titlers. Render in different formats without restarting vegas. Try even going through million of New Blue animated thumbnails that take over the plugn list. Try keeping pro type titler open and adding transitions simultaneously. It is these gpu extensive activities that crash vegas.
paul_w wrote on 3/14/2012, 5:24 PM
Installed fine here, no problems to report. No change really.

However NB Titler is the same as ever, instant crash on copy paste - I dont use it anymore for this reason but tested it anyway.

Paul.
Zeitgeist wrote on 3/14/2012, 5:29 PM
Yeah, that titler and New Blue in general is very annoying & disappointing to me. I have many of their plugins and they are taking up so much room everywhere. They are the most narcissistic plug I have ever dealt with. I wish I could delete them in certain cases.
rhythmlake wrote on 3/14/2012, 9:37 PM

I'm one who HAS had luck with a fresh Win7-64 install. Original post is here:

http://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=798398&Replies=0

My last post in thread still applies... so far very stable.

After the fresh OS + Vegas 11 install (currently 595), I tested Vegas after each program installation, and all is still super stable. I have since re-installed all of my software EXCEPT the 4 NewBlueFX plugins: VideoEssentials I & II, Light Blends and Sampler Pack. Honestly, I just want to enjoy this stability for a while. I can manually create the same FX with a bit more work. I love the plug-ins and what they offer, but I have a sneaking feeling they are at the root of my previous crash-a-minute nightmare.

I just tested the NBFX Titler and copy/pasted a dozen times, in different ways, and could not get it to crash. This was all over a hearty key with the BorixFX Continuum keyer and lightwrap composite active, which, previously, would reliably crash with any fiddling.

I've now made a full backup image and next plan to install the aforementioned NBFX OFX plugs. If Vegas starts crashing, I will know exactly what is causing it. Video driver is 290.73--haven't installed the most recent version released this week.

Maybe I've just been lucky so far and haven't taxed the CPU enough, though I feel I have thumped on it pretty hard, and definitely not getting crashes during the routines that always white screened before the reinstall.

If someone is pondering a clean Win7 install, hold off installing any NBFX plugs (except the Titler) until after you have thoroughly tested Vegas without them. THEN, make a backup and take the plunge.
JJKizak wrote on 3/15/2012, 8:01 AM
Why should the user be required to re-install Win7 along with every app? This to me is totally unacceptable. There are better ways to spend two weeks trying to remember some 20+ applications and script modifications and options . All of the Win 7 updates take a morning by themselves. I might be dead before the final install.
JJK.
rhythmlake wrote on 3/15/2012, 7:37 PM
I agree.
NicolSD wrote on 3/15/2012, 7:43 PM
Paul W wrote: "However NB Titler is the same as ever, instant crash on copy paste - I dont use it anymore for this reason but tested it anyway. "

I get crashes like that once in a while but while rewatching one of NB's tutorials, they do not copy/paste. They save the title from within the interface itself; then reload it within another Titler they start from scratch. (I wasn't too sure how to describe this properly.) They must know something we don't.
Leee wrote on 3/15/2012, 9:58 PM
Has anyone else thought of bringing this problem to Experts Exchange? They have a lot of really smart professional computer experts there that have helped me solve problems on my computer at least a dozen times?

I think when I get some time tonight I'm going to post a question over there about my specific problems with Sony Vegas and see what kinds of suggestions (and hopefully answers) I get from the "experts".

I just put in a new graphics card myself, and had high hopes that Vegas would suddenly behave, but that was not to be. I'll post back here if I get any good responses to my post at EE.

http://www.experts-exchange.com/
Steve Mann wrote on 3/15/2012, 10:34 PM
"I just put in a new graphics card myself, and had high hopes that Vegas would suddenly behave, but that was not to be. I'll post back here if I get any good responses to my post at EE."

If you went from an ATI to an nVidia card, make sure you delete all of the ATI drivers.