I'm amazed at how little changed between v9 and v11.

in terms of problems or features?

if features i think you need to look a little deeper*....

*or were you thinking along the lines of fcp vs fcp x ;-)

@Steve Mann
I noticed this, too. But when I scrolled down in the "Render As" window the "Save Markers" option was unchecked, where in V10 and before this was default-checked.

My response: They are checked by default if I remember correctly and I always double check. I'm still thinking this is the Vegas Pro/New Blue FX Titler Pro 'dance'.

BTW: My UAC is also set to never notify upon installing a fresh build of Win 7. And yet the crashing continues...Only in Vegas or Titler Pro It's annoying to have to reboot the PC everytime but at least I can edit/save to muddle through a project.

Deleted
Tomthumb

could someone please explain how uac could have any bearing on software, other than refusing to install it?

for the record, i have always left it on - after all, there's only about 6 or so programs on my editing pc.

Very well stated.

I can't explain it technically but it raised hell with Shuttle pro (would not let it function or open) and DVD-A Pro 5.2 (would prevent it from opening). I had to re-install DVD-A Pro 5.2 after shutting down UAC. And since the UAC would not allow 5.2 to open it would not allow it un-install it either. So I had to wait for the new build of 5.2 before I could install it again.
JJK

"I'm amazed at how little changed between v9 and v11.

In terms of posters - it's largely the same group from version to version.

Not all crashes are really crashes!

This morning I was doing a test and imported a DVD. When the import finished or at least seemed to I selected the project manager to see and move the files to the time-line. When I did I got the message that Vegas is not responding. Clicking again would have brought up the milky screen which I call the ‘milky way crash’.

Instead of trying to close Vegas I simply waited because from previous experiences I knew that Vegas was doing some background tasks on the imported videos. Would help if there was a dialog box to make this known and say ‘please wait’. Anyway, after a few minutes Vegas started working again and worked fine and I put the videos on the time-line.

In another situation while editing, Vegas had seemed to stop and I got the Vegas is not responding message. I waited a few minutes and Vegas went right back to normal. I hadn’t saved my project yet so I used the opportunity to save it then. After a few more edits Vegas once again stopped with the not responding message. I then closed it because it was behaving sluggishly anyway.

I then re-booted the system and cleared the cobwebs in the memory and all was fine from then on.

Seems that memory gets fragmented and whatever’s and the system needs a refresh now and then especially when the editing gets heavy.

Recently I was installing drivers for the 550 Ti card I had. It told me to restart the computer and so I did. On restart it tried to run and I got the program is not responding and the ‘milky way crash’. I did nothing with it because my system still has old DSL settings that delay the network on boot and I usually have to wait a minute for the system to be ready to use. I will fix that when I get around to it. Anyway, after a minute the install program continued as if nothing ever happened and finished just fine.

As for the OP, the latest drivers are not always the best ones. I can install the wrong version of drivers (Old or new) and crash Vegas like crazy! I can also over-clock the video card and/or CPU and/or whatever and also cause Vegas to crash. One time while playing with the test boot and a driver, Vegas crashed as soon as I pressed the space-bar to play a video. What I get depends on if I have the old ATI card in the system or whatever is in the system!

So, yes, hardware and how it is configured MATTERS!!! That is why it is very important to know the system specifications if the crashes in Vegas are to be solved. I will update my own system specifications when I get done upgrading my system. The GPU (CUDA) support took a rewrite of code so naturally there are going to be some systems that are more vulnerable than others.

This is NOT Vegas bugs this is Vegas issues with certain system configurations and/or even certain system configurations issues with Vegas.

I can make my system crash Vegas like crazy, a little bit or for the most part not at all. And like I said at first, not all crashes are really crashes!

"V11 64-bits / Win7 with all drivers up to date."

If you use the nVidia "auto scan", it will likely report that you have the latest version.

http://uk.geforce.com/drivers

If you are using a late-model nVidia/GeForce video card, the 285.79 Beta driver may fix some problems.The 285.79-Beta driver seems to fix a lot of problems in Vegas installations.

http://www.nvidia.co.uk/object/win7-winvista-64bit-285.79-beta-driver-uk.html

Download it, install it and run Vegas. check for your "Vegas Bug" and let us know your results. You can always roll-back the latest released driver.

I have an Nvidia GTS450.

Will try 285.79 beta driver and see if it helps

Thanks Steve

Rob

New beta driver with GTS 450 seems better and less crashes but I couldn't test if long enough and I still have this problem either with the older driver and the beta driver:

The video in the preview window strobes and flickers when playing it and is not even playing the video where the playhead is positioned. Sometimes the video turns purple.

Only way to fix is to quit Vegas and reopen but the problem occurs more often now.
If I disable GPU acceleration in V11, then no more strobing.


Here is a link to a youtube screen capture I did:


Rob

RoS,

Looking at your specs the GeForce 9500 GT is severely below par and unlikely to work well if at all. The 450 should work. I got a 430 to work but like the 450 it is well below par for Vegas!

Ordered a 560 Ti and will see how well it works for me. Had the 550 Ti and it works fine but just a little below par for my needs.

I should of mentionned it was with my GTS450.

This is just a new problem that just occured weeks ago and just can't pin point it.

Rob

I have a new Win 7 64 bit computer running Vegas Pro 9.0 with no problems. I thought the stablizer might be worth the money but I think I'm going to pass on this update. I never did get Pro 10.0 to work well.

I'm not a video pro, just serious amateur with limited requirements.

Thanks for saving me the money!

This is my first post on these forums, but I would like to state that my Vegas Pro 11 also crashes. I have pinned down at least one of the crashes. If I double click on NewBlue Titler Pro Default Preset on the Media Generators window it crashes. If I just pull it out to a screen I have 60% chance that it will work for a while. But I do believe that the pluggin is causing most of my crashes. I do hope they fix it. I really like it.

I too had many crashes after installing the NewBlue Titler. I uninstalled it and now no more crashes. I made the mistake of not deleting the titles before uninstalling so now I get an error message that the plug-in is not installed.
I would like to use the new titler so I hope that problem will be fixed.

I notified Sony of the NBT crashing Vegas issue. I didn't really have a problem until I made some presets. Vegas automatically puts the preset in the media generator preset window. In clicking on the preset in the window it was instant crash. It seemed that at times that just entering the window with the pointer crashed the program.

The workaround is to drag NBT from the media generator view box to the timeline and then using it's drop down box to apply the presets. It has been good so far, but what is the point of having the preset in the preset window if you can't use it?

It has crashed on other occasions with the NBT and BCC7, but I'm thinking it is more of operator error by not allowing time for the software to work. Then now and again I do get the mystery crash...save baby, save!!!. Lets hope their is a cure for the ills.

I thought about starting a new thread, but thought I'd post the following here:

I seem to have taken a HUGE leap forward in the stability of using Vegas, without actually doing anything to Vegas.

Here's my long story:

As I have noted in other threads, I was suffering from crashes. The most common were when using Color Curves and NB Titler. I quickly learned not to touch NB Titler, as it seemed to consistently crash. However, the Color Curves one was inconsistent and seemed to show up at odd times, sometimes even when it was just in the chain, without actually being used. I could work around the plugins by reminding myself, "Don't touch NB TItler or Color Curves". I'm not saying that's right for a product, just that I could live with it.

The more troubling crashes were the ones when I previewed or rendered. Plus (and here's the one that really got me frustrated), I was having random (meaning at a different point in every render) dropped/repeated frames in renders to the Quicktime Handbrake template (which I can't live without, given the excellent work of Jerry, et al. to provide us all a workflow for down-rezzing to 720p and 480p). The dropped/repeated frames acted like a decrease in the frame rate of the rendered/encoded video. Thus, I had to check every second of every clip I encoded, and then fix the troubled areas. Not fun.

What do I call a crash? Here were my four flavors: 1) "Vegas has stopped working." with the option to send a report; 2)"Vegas has stopped working" with no option to send a report; 3) nVidia video driver has stopped working (screens go black and then recover, usually accompanied by flavor 2) - this would happend while rendering or previewing, even with GPU processing disabled (GPU enabled anything would bring things down); and 4) screen goes black and the computer reboots with the "Windows was not shut down normally...". At this point, those more computer-savvy than me are seeing where this is headed...

I suspected that my video drivers were causing problems. Thus, I updated to the latest offficial and beta drivers from nVidia, using clean installs as many here recommend. I even tried to use "backdated" drivers, going back to older versions. None of this improved things in any reliable way.

Having recently bought a new nVidia GTX 560 Ti, I switched back to my old card. This helped, but I still had the dropped/repeated frames problem (which I was blaming on Vegas). Crash flavors 3 and 4 went away, and I seemed to be able to get through renders without crashing the video driver. So, I thought I was on to something. As I tried reinstalling my EVGA card, I thought I'd finally install those tools that they have for overclocking, just to check if my card was overclocked, unbeknownst to me. I had reasoned that those were "power-user" tools, mainly for the gaming set (which is not me).

When I installed the EVGA "Precision" application, it reported that an update was available. I ignored this and went on my merry way... until the whole system crashed when trying to run that application and my machine would not successfully reboot - choking every time windows finally got started. Thankfully, the system would successfully boot with my old card.

Trying one last thing before calling for a replacement card from EVGA, I updated the "Precision" program. To my surprise, the lengthiest part of the install was a systematic installation of a bunch of DirectX updates (starting with ones dated something like 2004 and reporting update installations through 2011). I have no idea if DirectX was the culprit/solution here. But, I just happened to notice these files were being installed during this program's update (why they weren't installed with the original program, I don't know). I then reinstalled the new card and everything seemed to work fine.

Here's the bottom line: With the new card now stable, I have now rendered/encoded several hours worth of video with zero crashes and zero glitches - including that I now have no dropped/repeated frames. I have spent only a couple of hours editing and still haven't touched the aforementioned troubled plug-ins. But, my Vegas 11 is now quite stable... so far.


Sorry for the long post. But, my point is to add another voice to voices here from those much wiser than me who have consistently said to have all drivers, etc. updated. I thought I did. In other words, don't just look at Vegas as the primary culprit.

Using the latest video driver from nVidia was not enough. I still have no idea how I would have otherwise updated things like DirectX (if that was even the problem/solution) without stumbling onto what I thought was optional software that came with my video card. I thought these things were updated automatically by Windows 7 (which I checked for problems along the way...).

I am definitely sympathetic to Sony's issue here in not being able to replicate certain problems, since it seems that some of my issues weren't necessarily inherent to Vegas, in that they work fine after certain system resources have been updated. I just wish that there could be some way to know what system software must be there and updated to make Vegas stable.

Windows 7 + video card drivers = lots of trouble for some installations. Mine was one of them for my online computer. Network/DSL operation is another grey area with Win 7. Anyway for me it is. Then add the UAC thing.
JJK

"...renders to the Quicktime Handbrake template (which I can't live without, given the excellent work of Jerry, et al. to provide us all a workflow..."Heh, heh. That should read "musicvid, et al" I'm just a vocal supporter.

...Jerry (part of the "et al" crew)

@Jerry: Yes - thanks for the clarification. Thank you to all, especially musicvid, who created the tutorial! It is very helpful, as it finally brought the best picture quality to my DVD's.

Thanks Steve. I installed the GeForce 285.79 beta driver for my GeForce GTX 260 video card and it seems to have solved the problem. I tried to make it crash and it won't.