No Vegas 11 for me (yet)

CVM wrote on 10/22/2011, 8:42 AM
Thankfully there are diehards out in the community (you know who you are) who will frustrate themselves, lose hair, isolate friends and family, and post a bazillion issues with every new release of Vegas. I, then, will breeze in at version D or E and upgrade from my current version... and enjoy the fruits of your labor.

My thanks to all of you!

Dave

Comments

Wadro65 wrote on 10/22/2011, 11:17 AM
Version 10 never became stable for me. Hopefully 11 will. Still using 9e (rock solid) and paying to be a voiceless beta tester.
Ian Stark wrote on 10/22/2011, 3:02 PM
Glad the more community spirited among us can be of service.
Steve Mann wrote on 10/22/2011, 9:24 PM
"I, then, will breeze in at version D or E and upgrade from my current version... and enjoy the fruits of your labor."

And I thank you for waiting - and paying the higher upgrade price. It's generous people like you that keep the early adopter upgrade price down.
Serena wrote on 10/22/2011, 10:54 PM
Actually it isn't sensible to wait to buy an upgrade, other than the interest gained on money not yet spent. You can buy without installing.
Ian Stark wrote on 10/23/2011, 3:30 AM
No professional in their right mind who adopts early is going to use a first release on critical jobs. They will run concurrently and only make the switch when it's solid.

The thing that burns me is that people who frequent this forum and others like DVi will be quick to ask for unpaid help from the very people you're suggesting are foolish.

I thought that mutual assistance was one of the aims of a community forum, rather than taking the p**s.

AtomicGreymon wrote on 10/23/2011, 3:33 AM
Yep, that extra $50 is very well spent.

Not really.

What you say might be true if Vegas upgrades invalidated the key of the upgraded product, however that isn't how they work (though it's the case with a great deal of software these days) and there's nothing stopping any of us who upgrade to the new Vegas from continuing to use whichever version we upgraded from alongside 11.

So I'll save $50, get access to 11's new features, possibly contribute to improving it via error and bug reports/etc., all while retaining the use of my previous version (8, in my case) just in case I end up needing it.

I really don't see where I've lost anything by purchasing early, but I can certainly see where you're losing by delaying your purchase. If you weren't sure whether you were going to buy it eventually or not, waiting might make sense... but you seem fairly sure you'll be making the purchase. Unless you lack the money at this time, there's no logical reason to put the purchase off and cost yourself $50 extra in the process.
Steve Mann wrote on 10/23/2011, 9:10 AM
"No professional in their right mind who adopts early is going to use a first release on critical jobs"

Then I am of the wrong mind - but being crazy can be fun....

I have so much confidence in Vegas that I don't hesitate to upgrade mid-project. I've never been bitten, but I always do have a safety net by not deleting the older versions and by saving the veg files for the older versions. In ten years I have never had to revert back to an older version.
AtomicGreymon wrote on 10/23/2011, 2:25 PM
Sorry, but I'm not following your logic. If you're going to buy it anyway, you may as well buy it now for the cheaper price. It may come as a shock to you, I know, but buying 11.0 entitles you to use 11.0c or d down the road.

As for me, I knew I was going to upgrade regardless; I didn't buy 9 or 10, so it was about time. I plan to keep 8 installed as well, though, until the larger of the kinks are worked out of 11. As I mentioned before, the ability to continue using your previous version is one of the advantages of Vegas upgrades; and renders most of your 'argument' null and void. So the only real question for me was whether to spend $140 now, and possibly have to go back to 8 every once in a while on the off-chance I run into a problem, or $190 later on for something I was always planning to buy. You can keep posting all you want, but there's only one answer to that question that makes sense.

The only valid reason for not buying at the discounted upgrade price is if you're not sure if you'll ever bother with 11. But again, you seem pretty confident you'll be buying it eventually. So no, I really don't see any logic to your point.
Ian Stark wrote on 10/23/2011, 3:19 PM
>>>The $50 extra we pay is money well spent<<<

So after all that you're probably not spending the $50 on Vegas anyway! Put it towards a new GPU for Mercury performance. You probably can't afford a new GPU AND a Vegas upgrade anyway now you've spent all your cash on CS5 ;-)
Ian Stark wrote on 10/23/2011, 4:10 PM
Hmmm, same here actually . . . ;-)
Leopardman wrote on 10/23/2011, 4:16 PM
Some of us do have proper backup and regression strategies in place if the necessity does occur to regress to an earlier version of Vegas.

If one has not overwritten (or keep backup copies of the veg) file with the new version, it is still able to open it with the earlier version one created it with.

I have always happily updated/upgraded to the new versions without a hitch.

Eddie
cbrillow wrote on 10/23/2011, 4:20 PM
I don't understand starting a thread patting oneself on the back for not upgrading, as if you're somehow smarter than those who do decide to make the jump. I agree with those who opine that it's wise to purchase the new version within the discounted upgrade period, and then hold off installing it while the community develops a consensus whether it's ready for primetime or not.

Personally, although I do *some* for-pay work, I'm primarily a hobbyist and am not usually shy about jumping into a new version with both feet, even in the middle of a project, as long as it's a non-critical, home project.

"If you are using 11 and run into a problem, don't forget you won't be able to open your VP11 project in VP8. You'll have to start from scratch."

Very true, however it's a simple case to open the project in the latest version and immediately save it to a different name in order to minimize backtracking if something goes wrong. In this case, I'd probably append 'VP-11' to the file name and take off from there. Granted, if that blows up and you need to revert to an older Vegas version to finish up, you lose whatever work you put into the project with the newest Vegas, but sometimes everything works just fine and using new features from the latest version gives a more satisfying result than if you'd completed it with an older one.
notsopro wrote on 10/23/2011, 6:37 PM
deleted
CVM wrote on 10/24/2011, 11:19 AM
Everyone... please calm down. My original post was a compliment to all those smarter than I who have the expertise and willingness to work through all the nuances of a new Vegas release.

If it seemed like a smart-a**ed comment to you, and you feel I am less worthy to be on this forum because I can't do what you early-adopters do, I can't help that.

Think of it this way, would you still think ill of me if I said, 'Thankfully there are men and women in the Armed Forces who will risk their lives, willingly put themselves in harm's way, be apart from their families and friends, and do so for little monetary compensation. I then will walk the streets of my country feeling safe and sound... and enjoy the fruits of your labor. My thanks to all of you!'

Take my original post in the spirit in which it was posted.

Dave
Ian Stark wrote on 10/24/2011, 1:38 PM
Nope, still seems smart a*sed.
CVM wrote on 10/24/2011, 2:49 PM
Ian, me thinks there are some issues in translation across the pond. Cheerio.
Ian Stark wrote on 10/24/2011, 4:09 PM
Well yes, fair enough. In the spirit of fostering good international relations I'm prepared to concede that because of translation issues you are seemingly unable to see my point of view ;-)