Is it safe to update?

cybercom wrote on 2/6/2012, 11:45 AM

Now that some time has passed since the release of Build 521, I don't see as many posts decrying its faults.
Is this simply because everyone has either rolled back to the original release...
or found workarounds...
or does it actually work?
I've never updated from the original release based on this forum so I'm wondering where you folks stand on this issue now.

TIA,

< ")%%%><(

Comments

JasonATL wrote on 2/6/2012, 12:38 PM

My own experience has been that 521 is the most stable version of v11 that I have used. I have experienced some crashes, but they are quite a bit less frequent than with previous builds of v11. I would, however, wait for others to chime in.

CorTed wrote on 2/6/2012, 12:45 PM

Build 521 has been pretty good for me. Working on a 50 min project in HD and all is well.
Still some crashes, so I would recommend hitting the project save button regularly and you'll be fine.

Ted

Golfer wrote on 2/6/2012, 2:08 PM

I have 521 on computer.. I have had it hang on me when I first opened projects.. And also would provide me error message wen closing vegas... Yet, I have had better results as of late, download 32bit build 520, it seems much more stable, at least for me... No issues to speak of with 520

Ros wrote on 2/6/2012, 2:18 PM

I am gradually moving on to 521 and so far so good.

Having moved on to the NVidia beta drivers as helped.... and now with the 521 build, it's been great.

Experimental projects with NBTP that wouldn't open up anymore now open up without any problems with 521.

Did some chroma key today with BCC7 and several layers of composting with filters and light wrap...all wen't fine and rendered fine.

Rob

NicolSD wrote on 2/6/2012, 2:49 PM

Except for one bug I have already mentioned in another thread, it works very well for me. And NewBlue has also updated their titler recently, so I am running fairly smoothly nowadays.

R0cky wrote on 2/6/2012, 3:04 PM

If you care about surround sound, then no. If you want to use the MC AVC encoder with GPU accel, then no. Render at 16 MBps and there is a big green vertical bar in the output if you allow the GPU to be used. CPU only renders do not have it.

Rendering to AVI or MOV container with 6 channel audio (surround) using these codecs:

Sony YUV (AVI)
Cineform (AVI)
DNxHD (MOV)

In Vegas 10 Sony YUV and Cineform AVI work fine with 6 channels. DNxHD MOV does not even though it supports up to 32 channels. Standard Sorenson MOV DOES work with 6 channels.

In Vegas 11 NONE of these work for 6 channels and give an error like "project properties are incompatible with these settings". Same error for DNxHD in V10.

Note: Same project used for all tests. V10 works in the first 2 cases and V11 does not on the identical project.

rocky

NicolSD wrote on 2/6/2012, 4:39 PM

Rocky,

I have never had to use most of the features you are talking about but I know one thing for certain, the MC AVEC encoder with GPU acceleration works perfectly for me.

xberk wrote on 2/6/2012, 5:03 PM

Using 521 on Win 7 64 bit with no problems to report.

cybercom wrote on 2/6/2012, 10:55 PM

Thanks to all the respondents. As I am getting along with a minimum of hassle and no crashes in Build 425 (except if I open a different project without specifically saving the one I'm in first) I think I'll let the sleeping dog lie and wait a while longer before I update..

THX,

< *)###><

Geoff_Wood wrote on 2/7/2012, 1:37 AM

Load up the latest version in Demo mode , suck it and see !

geoff

[r]Evolution wrote on 2/8/2012, 8:50 AM

yes

Gary James wrote on 2/8/2012, 9:34 AM

I've had an on-going problem with all releases of SVP v11. The 32 bit version is less prone to crash than the 64 bit version, but I can absolutely count on both to crash with great regularity.

My last version of SVP was v9. This is 100% rock solid and I've never had any problems using it. I can take a project that works perfectly in v9, import it into v11, and it will crash within a few minutes. And the really amazing thing is that my projects are usually very simple.

Most of my projects are widescreen NTSC slideshows with 1000 or more graphic images of different formats, aspect ratios, and pixel dimensions. I import the clips, arrange them categorically, overlap them, add transition effects, set aspect ratios, apply filers for Brightness/Contrast and Color Correction, and for each image I apply keyframes to create a Pan/Zoom Ken Burns effect. For some low resolution media that generates a herring-bone interference pattern during a Pan / Zoom, I add Motion blur on the video bus track that greatly reduces or eliminates the problem.

When I'm all done with the video track I pick out appropriate audio track media and fit it to the video track.

My problems in v11 happens while I'm setting my image by image adjustments to the Pan/Zoom keyframes and Color Correction, Brightness / Contrast and Motion Blur settings . If I go back and forth between tweaking these settings, and Previewing the video, v11 64 bit will crash after adjusting only 3 or more images. v11 32 bit lasts longer, and I can adjust maybe 20 - 30 events before it crashes. In v9, I can adjust my entire project without any crash!

The problem seems to happen more frequently if I preview the adjustments more frequently. If I just make the adjustments without preview, I can adjust more events before a crash.

As I've said before, your decision to update should be metered with the knowledge that v11 has had the highest rate of bugs reported than any prior version of Vegas. I've owned Vegas since version 3.0 when it was a Sonic Foundry product. And I've never had a hiccup in any upgrade prior to v11. When I upgraded to v11 I was aware of these bug reports, but I decided to upgrade anyway based on two reasons.

1. I could get it at a very low special discount price during the upgrade offer period.
2. This is a product from Sony; a company that I highly respect, and I had faith that Sony would fix the problems.

Because of all of the users who've experienced problems with this release, I can not in good conscience recommend v11 to anyone, if their intention is to purchase the software and use it for a new critical project on a tight schedule. If you want to play with it and get familiar with the new features, that is totally different. I simply can't predict if your v11 installation will be trouble-free like it has been for many people, or you'll be like many others who've found the product too unstable to use.

Remember, if you start off a new project using v11, you can not revert back to an earlier version of Vegas if you later run into problems. Vegas .VEG files are version specific. You can only upgrade to a newer version. You can't revert back.