agree with kimberly - leave it till the last minute and the early adopters reports are in.

that said, scs seems to have been kind enough to offer a point release to 11 (still waiting for the reports) which fixed my major bugbear, wacom bug, so i think they're trying....

unfortunately it looks more like marketing pushing 12 out the door rather than the developers. i somehow think it might be a tad premature....

Kimberly,

I forgot we had that long to decide. Good idea.

Dave T2

Some news is in on its performance DaveT2, I say it is good to go.

Even/odd a toss up DaveT2 - who would have thought that 9.0e would be the productivity machine that it has become...

Here is a list of what we are learning-
1) The export to other products including Premiere is a good first step but this implementation still leaves a lot of desire.
2) The proxy feature built-in is not as versatile as using GearShift
3) The stability with NewBlue Titlers is still touch and go
4) Don't do a concurrent install of V11 and V12 on same PC while V10 and V12 may in-fact be a better combination if you believe 10 ok
5) GPU support more than ever requires strict adherence to SCS pre-tested mentions in its support documents
6) There are many plug-ins still left in the cold as not operable on 64bit OS and hardware - they are missing now -but may be filled in later with new software development and that is likely for the good
7) Stability in general still depends on what you tend to stress in your setup, be it the hardware, or be it timeline -like unusually difficult combinations of codecs. Some will have it stable because they don't stress the system.
8) Implementation of good intermediate codecs (my favorite is Cineform) has got issues (note it also has issue in Adobe CS6.6) but does open the door for other good intermediates including Sony MXF.

and .......

DaveT2, I am also one of those fortunates who had a minimum of crashes in 11 compared to some of the horror stories of others circulating around these forums. I bought 12 faster than I could get a discount (I'll get reimbursed; it's happened to me before) and In the 2 or 3 days of long hours of work I've experienced just one of those frozen cursor curses and that's about it. I used to get those pretty much 1 or 2 times a day. I have noticed this pattern with others who were experiencing fewer problems in 11; they too report very few problems in 12.

Long story short, Vegas 12 is a disaster on my system. I went back to Vegas 11.

Maybe after a few more builds?

Posted by: DaveT2 Date: 9/26/2012 5:01:27 PM
I know I can buy 12 at the reduced price right now, but from what I am read, the news is not in about its performance yet. Money is a bit tight, so I can't decide whether to spring for it, or skip it. I have a 64 bit version of windows ready to go, but I would have to port all of my other apps to it.
I also, don't generally upgrade unless there are features in the new release that makes it worth upgrading. I.e. I skipped 11 but will be upgrading to 12 because I now have a CUDA V2 card that Vegas can take advantage of.

Similarly I've only been upgrading every other version of Cubase 2, 4, and now 6 because of feature sets in each release that I can use. I use the money I save to buy better plugins or just save for the next release.

Generally the versions of software I don't upgrade to are major overhauls or if they are really buggy. I think (hope) V11 shook out most of the CUDA compatible bugs and there are many "nice" features in 12 from 10 that I think I'd be able to use. But comparing 11 to 12 I don't see a huge step up.

Btw, I'm sure you already know that 11 is 64bit also.

If they included motion tracking with null objects.....it would have been a no brainer.

VideoITGuy,

- What plug-ins are you unable to use with 64bit? I haven't had a plug-in stop working for me.
- RE: NewBlue titler, I agree, it's terrible in Vegas, but I have doubts as to that being a Vegas thing vs. a NewBlue thing. Though all their other tools work very well for me, I am somewhat loathing of the titler track record, and I stopped using it, almost as quickly as I started using.
- I have 8, 9, 10, 11, and 12 all installed on the same machine and with no noticeable adverse effects, however if there's something that suggests that 11 and 12 don't play well together, I'd be happy to change that, can you point to something that has more info on that so I can do some research?

RCourtney,

- Granted Vegas is almost a VFX Compositor as well, Motion tracking and virtual cameras are usually reserved for full on compositing tools, AE, Motion, etc... I don't expect to see them in an editor natively. BCC has motion tracking though, so that's good :).

DaveT2, If it were me, I'd download the trial, open some old projects, see how stable it is, play with it some. If all goes well, or you like the improvements enough that you think that the upgrade is warranted, just plan to pull the trigger before the promotion ends ( and put a reminder on a calendar or something in-case you don't get an email reminder before the end )

Dave

Upgrade and sell your Vegas 11 for $100 or so on e-bay.

My comments in a couple posts back and seen above were meant to summarize what I am hearing from a variety of users. Of course, any anecdotal stories should be considered in the context of how that user made his/her finding.

Some users who have had a bad install with Version11 but change nothing on their system and do not uninstall that version, but choose to add an install of Version 12 appear to have corruption for both versions concurrently.

This could be an indication that something was very wrong to begin with and that neither version alone or concurrently will work properly.

I have not heard of an instance where a system that was working well with Version 11 was corrupted by an install of Version 12- but it is so early in the findings process, it is really difficult to say what the source of problems could be.

We all are awaiting more reports from a diverse group of users.

I was a little upset that SVP12 is out and imo they did not fix SVP11. I had to edit most of my older projects in 10 or the 32 bit version of 11.Right now I'm jumping back and forth between Adobe and Sony now so If they offer an upgrade at a fair price I might do it. I noticed this morning they released an update to fix a lot of the issues..lol So SVP11 64 bit version might work now.

I

As far as I can determine, Win7 32-bit users like me can't use Vegas12.

I'm running 32-bit Win7 Pro, and could do a complete reinstall of the OS to the 64bit version - except that I run LOTS of different software packages, some of which are still 32bit-only. (Can't afford to have several computers with one dedicated to video-editing, unfortunately.)

AFAIK, my only course is to stay 32bit, and thus stay with Vegas10 (I declined to go to Vegas11 when it came out, because most of its new features don't apply to me, and because of the many problem-reports I've read in this forum).
I guess I don't particularly mind becoming "obsolete," as long as my system still does everything that I use it to do...

@earthrisers,

AFAIK, Win7-64bit can run most, if not all, 32bit programs just fine.

I have both 32bit and 62bit VP11 installed and both run OK.

Tom

Tom, but you have to be careful. I have a few old 16 bit Windows programs laying around that I had been using until I upgraded to 64 bit Win 7 Pro. Win 7 64 bit will not run old 16 bit programs. I'm not sure if Win 7 32 bit will or not.

To get around this limitation I downloaded the free copy of VMware Player. This installed a Virtual Machine environment on my Win 7 Pro PC, that allowed me to install Windows XP inside the environment just as though I was installing it as my native OS. I run the VMware Player, select the Windows XP environment (you can install several), and a Windows XP window opens up inside the Virtual environment. The virtual window has access to my Windows 7 PC drives through a virtual sub-directory, so I can share files between them.

Agreed Gary,
But the question was 32bit on 64bit. I would not be surprised at having issues with 16bit on 64bit.

But you have given me an idea. I could install VMware and use it as a clean test environment for VP12. Yay!

Tom

You can also do a physical to virtual conversion of an old machine and keep it around to run under VMWare or the VMWare Player long after the hardware is gone. I've done a few P to V conversions of old desktop machines so I can get the application back up on more current hardware when the old hardware fails. Some applications don't need newer horsepower but the old hardware doesn't last forever.