No, I am attempting to do the latter.

I'm starting to have an awareness that maybe when SCS do do their "testing", they would do so on a squeaky clean PC. Of course they would. Which, unlike many Users here, who keep at least a prior Version, and for me that means 3 Versions of Vegas installed, and available all the time, would then maybe NOT be tested by SCS - just 'cos that's the way they DON'T proceed with their testing.

This is all conjecture on my side, but, if it looks like a duck, sounds like a duck . . . . . .

G

Hi guys, I've read this thread so far, and I'm pretty sure that creating a new user account in Windows won't solve any issues with VP11 crashes. I did a clean install of Windows 7 Pro x64, and VP11 still chrashed. I did two things that really helped, and now it's stable. First I downloaded and installed the latest beta driver from Nvidia, 290.53. This fixed the problem halfway, but I still had some BSOD combined with crashes from VP11. Then I realized that my browser, Google Chrome, has a memory leak, and it was stacking up memory without freeing anything. This made VP11 crash, which need recourses to work well, and finally the machine broke down in tears and gave me another BSOD. So, after installing the new beta driver from Nvidia and frequently cleaning the memory of Google Chrome, I have a machine that works perfectly on VP11. Happy camper so far!!!

Hi TSIG,

Well I don't use Google Chrome and I have the latest Radeon drivers installed. (I don't use NVidia drivers)
And as for you being "pretty sure that creating a new user account won't solve any issues with VP11 crashing", well you may be right about that one. I guess the only other possible explanation for my experience is that someone slipped some magic mushrooms onto my pizza and the realization of NO CRASHES was just a drug induced psychedelic fantasy. Perhaps I'll come down soon and realize the true reality of the situation. 8-\

Sir Graham wrote: I'm starting to have an awareness that maybe when SCS do do their "testing", they would do so on a squeaky clean PC. Of course they would.

Yes, of course they would - in the alpha testing phase - to clean out the most obvious issues.
But real-life-everyday-use starts with the beta testing - and the beta testers will test at their real-life-everyday-machines - and conscientiously report their findings in these environments back to the HQ...

...then, of course, it is a question how much that HQ listens...

"I guess the only other possible explanation for my experience is that someone slipped some magic mushrooms onto my pizza and the realization of NO CRASHES was just a drug induced psychedelic fantasy."

And to think I was the one being asked to cool my jets in this thread :)

Seriously, never work under the assumption that there is only one cause of these crashes. There could be multiple bugs with multipe routes that invoke them. To my way of thinking I'm also a bit concerned when users here say "they've fixed the problem" when they've done something that they should not be expected to do, all they've done is worked around the problem and their experience is probably of more value to the developers than the guy who cannot fix his problem(s).

One "fix" mentioned above related to another app's memory leak starving Vegas of RAM and causing it to crash. I don't think that should happen unless possibly there is next to no RAM left for Vegas. At the least Vegas should be able to shutdown elegantly, not crash, if it runs out of RAM. Anyway that's just my opinion but it should be reported to the developers for them to decide. It maybe a worthless piece of info or it may save someone days trying to get a handle on how a crash is happening

Bob.

Ritzy, and that WAS my point! - Maybe you heard it too?

And yes, again, we come here with mixed setups and multiple versions installed. My point was that that is exactly what SCS wouldn't be doing. And so, as they wouldn't be doing THAT I come along with my mixed bag of stuff, as a User, and have gotten instability.

SCS needs our feedback, but then again, in our real world, we are running around outside of the coral, away from neat workflows and installations we all have.

Completely agree on the Alpha > Beta process. Yes.

This is real hard for SCS and us Users alike.

Cheers

G

All of our workstations multi-boot from a choice of (3) hard drives. For the last 4 years whenever a new Vegas update appears I install it on a newly restored OS image that has no other programs on it, just Windows updates. When we are not using that workstation I boot to the OS with the new Vegas release.

To test I plug-in a hot swap drive with some of our most problematic VEG files & their respective source files. If the new release has problems with these VEG files, I wait until an update appears and try-again. This way I am not wasting any time getting current work done. Once the new release appears to behave correctly & others on this forum report success, I eventually install it on our main work drive.

Also, I do not install any other codecs (like AVID DNxHD, etc.) so that I know the problems are Vegas related and not a bad 3rd party codec or plugin.

With this test method, 511 crashed on problematic VEG files as well as VEG files that rendered OK in 10e. Therefore 511 is not ready for primetime.

Rhino, I like your approach! That surely will tell you quickly if the release is good to go....

Please post your results on the next new release. May save me some time downloading it.

Ted

Just thinking aloud here, but wouldn't a fresh user account be free from most of the bloat ware that comes on any off-the-shelf PC (yeah some of us don't build our own)? I usually uninstall the bloat ware but leave the original account intact as my own personal account. Maybe this isn't enough.

wouldn't a fresh user account be free from most of the bloat ware that comes on any off-the-shelf PC

I forget at the moment how Windows handles this but I think there's an "All Users" area that holds common information that every new user account will get. So uninstalling should get rid of the bloatware apps for everyone, and individual config and supporting files won't get copied to a new user account, but all of the "All Users" stuff gets added to a new account.

This implies that if your bloatware left some of it's bloat behind behind in an All Users area then new accounts could get copies of it.

It doesn't always work this way. For instance, the Start menu could have a set of global shortcuts and your own personal shortcuts. So sometimes this "All Users" stuff could just stay in its folder until you customize a settings file, and then you'd get a personal copy.

Getting confused? Microsoft probably has a document with recommendations on how to handle this but there's probably no enforcement. So I imagine creating a new account could solve some problems with some software but not others.

This is a pretty rough explanation but it's about the most I can manage to squooze out of my overtaxed brain at the moment. Vegas would be a welcome change from Flash right now.

And, no, I haven't tried creating a new account just yet.