Comments

Gary James wrote on 6/27/2012, 10:59 PM
After working 35 years as a software design engineer, believe when I tell you that almost every new version of a released software product, is based on the source code of the existing released version. There are exceptions, but this is very rare.

This means that when Sony Vegas Pro v12 appears. You can bet the farm that it contains all of the v11 source code, plus whatever new features they threw in to tease you into paying for the upgrade. And that in-turn means that all the hidden bugs in v11, will hitch a ride right into the v12 release.

I tell you this so when the time comes, you can make an informed decision to upgrade or not. If you are one of the lucky ones who have no v11 bugs, it probably will be safe to upgrade (maybe). However, if your experience with SVP v11 has left you swearing like Ralphie's dad fixing the furnace, then you shouldn't expect a v12 miracle that will make all of SVP v11's problems magically disappear.
videoITguy wrote on 6/27/2012, 11:39 PM
Gary makes a very practical statement. Most of us know that there are particular peculiarities that have been following VegasPro releases far before Vegas 9.0 came out and now they still show in V11. Software coding is an evolution of processes- identified usually and purposely to make the succeeding version better- but as it works as a double-edge sword - also works against success as bugs are not dealt with and they compound to a worsening of the succeeding version.

Those of you who might hope for a "revolutionary" different version next time around, well, I would like to bet you some sizable amounts of money that you won't see it.

A lot of turnarounds of this magnitude even for a large a company as SCS would come (as shown historically in software development) from acquisition of somebody else's code. A NEW Product! Perhaps some remember how Vegas came into Sony.
Simes wrote on 7/2/2012, 4:10 AM
Has a very standard spec, low cost, easily available brand PC been identified as a system that runs Vegas 11 perfectly.

For example, I'm running on an ASUS P5N32-E SLI PLUS with 4 gig mem, GeForce 8400 GS & no disk paging file - and - touch wood (dare I say it!), the system is very stable. (I also reduced the cpu voltages down to the VID figure shown in the Core Temp app (as before, the cpu was overheating while rendering and switching off).

I'm probably not pushing vegas too hard, though this is essentially quite an old low cost system now - at least if a used system is obtained from ebay.(approx 300-400 dollars). I'm imagining that there are ibm, dells, hp models that are very standardised that are also run vegas very stable. (Like I described in another post, back with vegas 5, when all else was crashing during long renders, I found that a cheap Acer laptop with 256k ran it perfectly).

I realise it's not like anyone's got money to throw around, but if such a low cost system can be identified, the investment might be considered worthwhile - in terms of all the saving of stress & time with crashing apps. I realise this doesn't solve the actual issue of software bugs (and/or driver interface bugs) - but it might be a way round for now for some who really want to use V11.

Who else has a standardised widely available low cost off the shelf system, that is stable. And anyone else with a stable ASUS P5N32-E SLI PLUS based system like mine above.
gpsmikey wrote on 7/2/2012, 10:29 AM
The problem isn't that the software has bugs - all software has some "undocumented features" (having worked in the flight critical software field, I know what it costs to REALLY test software - you don't want to go there !!! ). The big issue that I see is the number of bugs that have been clearly documented as to what they are and how to re-create them that SCCS takes 6 weeks to even acknowledge (if at all) then with a canned response that doesn't solve the problem, only allows them to check it off in their "we've taken care of it" list. And they are still around several versions later. That is what really tends to hack people off - especially when the same folks that carefully documented the problem that is impacting how they make a living and then SCCS sends them the next email suggesting they should rush right out with their credit card and buy the new version. I have done beta testing for a number of companies and most of them have actually been pretty good about responding once you can document how to create a problem and what the conditions are. If they can re-create it, it gets fixed pretty soon.

mikey