Unlike past releases both Sony and New Blue FX seem to be making a lot of effort to engage with our concerns and hopefully this will lead to them fixing any reproducible bugs that crop up. There are a lot of competitive products out there so it's good to see this level of support which hopefully will keep customers, attract new ones and maybe draw a few back who had sadly given up.

P.S. Look how much good will is being generated just from this increased attention to our support needs. We're not only customers but we're also advocates of these products ;)

The part about New Blue Titler Pro 2 causing a crash on startup confirms the problem I had with it. Thank goodness I had a cloned backup!

Here is something I did that might help others. As many here do, I do not have my editing system normally connected to the internet. Because of that I did not get any updates.

So before testing Vegas 13 again, I connected to the internet and did all of the updates. This took quite some time with a number of restarts. And even after I did a set of updates, another set would then be needed.

I then went through the install of Vegas 13 and things went a whole lot smoother. I even have the latest NVidia driver installed and am getting full speed with it so I am no longer stuck in the past with driver 296.10.

Overall system response is better and has an even better sense of stability than what I had before.

I did have one unusual Vegas 13 crash that I am not sure if Vegas was actually the cause of. While test rendering, a yellow warning sign showed-up in my task bar with a big ! mark. I thought, what in the world is that? I have never seen anything like that before. And then there was a dialog telling me that the memory was getting low and that Windows needed to shut down an application to bring the memory back up. And then it said it was shutting down Vegas 13. Vegas 13 became unresponsive and then closed. Maybe it was actually telling me that the memory in my brain was getting low. LOL!

I had been doing a lot of going back and forth from a number of programs and apparently that chewed-up all of my ram. I think it has to do with having SSD's because that was also mentioned in the dialog. I am not going to assume which application actually caused the memory to go low the most. I restarted the system and all was fine. I had not saved the test project but when I started Vegas 13 again it told me about the shutdown and an auto-save and I was back to where I was just before the render minus one simple edit. Yea Vegas!

I figure all of the issues will get ironed out soon and I greatly appreciate the feed-back from SCS! Give those guys a standing ovation!

Ok, when I get done here, I will finally spend my money on Vegas 13 and even on that headache-ware New Blue Titler Pro 3. At least they are trying to help.

The procedure is to make a confirmed backup of your system. This is NOT an option! Then get all of the updates which can take multiple restarts. Install Vegas 13 and the latest .NET which means being connected to the internet and then do another set or two of updates. Finally when all the other included apps are installed and updated and all the dust settles, then one can go back to non-internet mode again.

I hope this helps.

good on ya scs!!!

this sort of response / posting gives me / us a warm, fuzzy feeling that we're not alone out here ;-)

+1 ushere :)

+2.
Communication is a magical thing.
Even if everything is having a pear shaped moment (not saying it is, but even if it was), at SCS, just letting us know it is being worked on keeps the faith alive.

It's all good.

g

It's certainly a good omen.

Bob.

It's all good "Omen"s - then?



g