Vegas 11 is CRASH HAPPY

Comments

MTuggy wrote on 5/1/2012, 1:56 PM
I'll test this out too. If we find it works, we need to post this as a fix. I'll report back this evening.

Mike
tdsilk wrote on 5/1/2012, 3:54 PM
@Royce1

I think you're on to something. I previously upgraded from Vista to Win7 and since running Vegas 64 bit on Win7 64bit continuus crashes doing minor things (i.e. opening files). When I was running Vegas Pro 11 on Vista 64 it was pretty stable. I will try your suggestion to see if it helps.

Thanks!
AtomicGreymon wrote on 5/1/2012, 5:43 PM
Interesting. I upgraded to V11 from V8, but haven't used it very much yet (haven't noted much instability on my current Vista setup when I have used it, however). I was planning to install it on my new Ivy Bridge 3770K build, which of course will be running Windows 7; good to know compatibility mode will at least enable it to function properly if I find it crashes on Windows 7.

Not having any experience with Windows' compatibility modes, will Vegas still benefit from features like GPU/CUDA acceleration when run in that mode?

Hopefully Sony steps up and resolves V11's instability issues relatively quickly. Based on the forums, at least, they have quite a few unhappy customers. I myself will finally be upgrading my Adobe Master Collection CS3, and I've already pre-ordered the boxed CS6 upgrade at a local Adobe dealer. I'm not really doing it because I want an alternative editor to Vegas (not yet, anyway), but because CS6 will be my last chance to upgrade from CS3 and stay in the loop on new upgrade eligibilities. Also, I'm really looking forward to take a crack at the newer versions of Photoshop and Illustrator, and to see what's new in Encore (Blu-Ray authoring in DVD Architect is sadly lacking) and After Effects.

Although I only use Premiere Pro infrequently at the moment, if it comes to pass that V11's issues aren't resolved before it's time for V12, this will probably be the last version of Vegas I own. While Adobe is a bit more of a memory hog (at least CS3 is; I've heard there have been improvements since then), my new system will have 32GB of DDR3-1600 RAM and a 240GB SATA3 solid state drive as the boot and primary install disk. I really can't imagine anything running slow under those conditions.
pat s wrote on 5/1/2012, 8:23 PM
@Royce1

No luck on any of the Windows Compatibility mode for me, but my situation may be different than yours. My system is very stable as long as I disable my Wacom driver, and I don't use NewBlueFX Titler Pro. Same results with all the different compatibility modes. The Titler Pro plugin crashes instantly when I drag it down to a track. Everything else works great with the Wacom driver disabled.

Here is something unrelated that I discovered while testing the different compatibility modes. If I disable my 2nd display using the ATI/AMD Catalyst panel, I can use the NewBlueFX plugin just fine. (That's a 1st for me...I finally saw the registration screen!) While Vegas is open, I can extend my display to the 2nd monitor and everything continues to work. (Go figure) At least I have a work-around for this plugin too now. It seems stable so far...

BTW, I just upgraded all of my Catalyst drivers today to no avail. My ATI display adapter version is 8.961.0.0 dated 4/5/2012 if anyone is interested. Also GPU enabled/disabled has no effect.

Suvin111 wrote on 5/6/2012, 6:39 PM
Does anyone in this thread have a reaction to the latest release - 683?
ushere wrote on 5/6/2012, 6:56 PM
dl'ed and installed. so far so good - but i haven't begun pushing it yet. i too would like to hear from anyone doing heavy lifting with it as well.

i'm so paranoid about the media replacement bug that i've just installed cs6 - mind you, i've been trawling the adobe / dvinfo forums and not all is rosy over there either.

just gimme an rm450 and two vtrs - the worst that ever happened was the odd tape drop out ;-)
wombat wrote on 5/6/2012, 7:30 PM
downloading and will try it soon.

However I am having no crashing at all with the previous release, just a few bugs, and some memory hangups after closing V11 after long sessions.

Win7 x64, AMD cpu and graphics.
GPU rendering working, but a bit slower that cpu, so don't use it for rendering.
rs170a wrote on 5/6/2012, 7:34 PM
just gimme an rm450 and two vtrs - the worst that ever happened was the odd tape drop out ;-)

You forgot about dropouts and tape jams due to humidity :O

Mike
ushere wrote on 5/6/2012, 8:50 PM
not where i was editing mike - middle east and australia aren't particularly known for their humidity (well, unless you're at the top end of aus).!

mind you, everything was realtime, including preroll, spooling, duping, etc ;-(

rs170a wrote on 5/6/2012, 9:11 PM
Leslie, our summers here can get up to 100 F. with close to 100% humidity and the AC system in the college I work at can't keep up.
We used to keep a humidity gauge in the edit suites and when it went above 75, we simply refused to edit (constant head plugs).
Computers and tapeless cameras are a real life-saver for me.

mike
pat s wrote on 5/6/2012, 9:14 PM
@Suvin111 - I haven't noticed any difference with 683. My Wacom problem is still there as well as the Titler Pro while using 2 displays problem.

It's stable with the Wacom driver disabled and if I make sure that the Titler Pro dialog box doesn't open on my secondary monitor. (I can open it on my primary and drag it to the other monitor without crashing...so that's what I do as a work-around.)

Sony did tell me that they are working on a Wacom fix for a future release. I have not opened a support ticket on the NewBlue Titler problem yet.

For me, this software was very expensive, especially since I'm only doing this as a hobby and it's for personal use. While I do have work-arounds, and I really like working with Vegas 11, I would like to believe that Sony will come through and fix these issues before moving on to 12. The thought of having to upgrade every major release scares me little!