Can Vegas 11 get any MORE buggy?

[Angelo Mike]

Vegas 11 has improved to where it’s actually functional for me now, with very occasional crashes. But that’s with two builds over the last few months.

I’d say be persistent in reporting bugs, crashes, and in sending emails to Vegas making suggestions. The more they hear about it, the more likely they are to implement change.

http://www.scenethroughglass.com

[Jeff Schroeder]

I wish I could have a good close look at some of your crashes. I’m sure Sony needs to fix something, but whatever it is, I glad it’s not on my computers.

Windows 7 64-bit, ASUS P6X58D, i7 960 3.20GHz, 24.0GB DDR3, 12TB connected storage

[Steve Rhoden]

OK everyone that LOVES Vegas 11 can now tell me that they
have everything running like butter …..Not for me Scott,
im not using Vegas 11 as yet, because i have few issues with it as
well. But being a Film Maker and a PC/Network Technician, i make
my workflow very comfortable around software and hardware
shortcomings.

Steve Rhoden
(Cow Leader)
Film Editor & Compositor.
Filmex Creative Media.
1-876-832-4956

[Lance Bachelder]

No you’re right. Sure there’s always a few fanboys who never have or acknowledge any issues. 11 has been the worst version ever of Vegas, not only for the bugs and constant crashes but for the changed features that didn’t need changing. There are features I counted on every day like audio busses being with the Master and Preview faders that were moved to the mixing console which I rarely used. This was not asked for, it was a change someone made internally and got the green light without user input.

I see it like a sports team, you bring in a new coach and his team hoping things get better, but when it doesn’t work, you fire them and move on. Sony needs to seriously consider getting more/new help for the Vegas team. I’ve been a Vegas fan and user for over a decade now but Premiere Pro is looking better and better as my go to NLE on my Windows machine. Time is running out Sony…

Lance Bachelder
Writer, Editor, Director
Irvine, California

[John Rofrano]

There is no doubt that adding GPU support to timeline preview in VP11 probably caused a lot of code to be affected. It also caused a once “hardware independent” Vegas to become very sensitive to the hardware it is running on with respect to GPU’s. Couple that with a user base that never had to worry about their GPU before (because Vegas didn’t use it) and you have a lot of potential problems that could cause instability.

Likewise, adding OFX plug-in support to VP10 cause a lot of code to be updated making things more unstable. That’s why a lot of things that use to work got buggy in the past two releases. I’m not making excuses for them, but at least I can understand the cause and effect.

Let’s hope that things will settle down and stabilize now. It was a big change for the Sony development team. The best thing we can do is report the errors and give them as much info as we can on what’s going wrong. The latest build of VP11 has been a lot better for me but I’m still running into issues, especially with rendering.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Scott Francis]

Well good point John about Sony TRYING to provide support for GPU, but as of now it is worthless for the most part. We DID ask for that big time and many of us where REALLY excited to see it here, unfortunately even buying hardware that Sony itself has tested seems to be lackluster. I am just really amazed however that 11 is worse than 10 in preview quality on the SAME project even without GPU enabled….here is hoping they get it fixed soon, before some honestly look to just ship…thanks for a little clarity!!

Scott Francis
Mind’s Eye Audio/Video Productions

[Mike Hinkel]

I have had problems with every release of Vegas since 9. All of the bugs were worked out of all of them for the most part. The trouble with it all is that just when one gets working pretty well they change things up. Some would say they cross things up.

I have been fairly lucky with VP11 so far. I made some additions to my computer such as the power supply and video card long before it came out. Most of that was to accommodate the third party plugins that I added to the system. I can only think that it was the best thing I could have done with this release. Sure, there were hair pulling crashes occuring at first, but then there were moments similar in every edition of Vegas. It is better and I can only hope that it all gets ironed out for the simple fact that I just can’t afford the alternatives.

[Nigel O’neill]

… and in 6 months time, SVP12 will be out, and like the Lemmings we are, we will part with another $139.95 of our heard earned cash to be on the bleeding edge.

I have stopped applying updates since 10c, which is the last stable version for my workflow and plug-ins. The OFX support has broken some third party plugins which the developer swears black and blue are NOT the problem. I now have an NVidia GT570 that I basically can’t get the benefit of, and SVP11 which is not stable enough for production work. All up, $600 I could have put into a replacement camera for my HDV work horses * sigh *.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Erik Davis]

“… and in 6 months time, SVP12 will be out, and like the Lemmings we are, we will part with another $139.95 of our heard earned cash to be on the bleeding edge.”

Don’t be so sure Nigel. I think this time really is different. I’ve purchased the last 4 versions of Vegas but I can promise you that I am not buying 12 as things are right now. No reason too, as I can’t use 11 (or really 10 for the matter) and still rely on V9 to get my work done.

erik

[Angelo Mike]

Yeah, I’m not sure there’s any way I’m buying Vegas 12 when it’s released. People would have to overwhelmingly say they’re pleased with it (not merely reviewers, who seemed to be very pleased with Vegas 11) for me to buy it.

Just keep reporting bugs to Sony, guys. They need to hear about it. In one case for me, they actually said that they were able to reproduce a bug I found and would send it to their software testers or whoever to fix. No idea if they fixed it since it was the bug that made footage with a PAR of 1 automatically change to 1.33 on my Cineform AVI footage, which made Vegas crash as soon as I loaded the footage, anyways. So now I use the AVCHD that comes straight out of my camera. But I’ll test that out at some point and see if that’s changed with the latest build.

http://www.scenethroughglass.com