Vegas 11 is CRASH HAPPY

GregO wrote on 3/18/2012, 3:45 AM

Just upgraded from Vegas 9 to 11 because I couldn't even load some new Canon DSLR video on to 9 without it crashing. Other than that... had no problems with 9. Rendered every time ( just about) and I loved it.

(BTW... Desktop uses a 2.67 gigahertz Intel Core i7 920 - 6GB ram - Win 7 - 64bit. With a ATI Radeon HD 4800 GPU)

Anyway... My buddy with the DSLR camera said He upgraded to Vegas Pro 11 and that fixed his problems with editing his DSLR footage. So... since it was a paying project on a tight deadline, I dropped the big bucks to upgrade immediately and have had a massive domino of problems.

First issue: it says that the GPU is not compatible with the GPU accelerator. (Bummer number one... Now I have to drop even more money for new GPU... But still have to get my project done ASAP)

Second issue: Love the new blue titler that comes with 11! BUT... It says my GPU is not compatible with it and may have issues or need new drivers. so I installed the new drivers and at least the new blue titler would now open in Sony Vegas.

Finish the big edit using the great new blue titler affects all over it and then go to render. First time it renders just great, looks great, sounds great. I going to make a few tweaks and try to render again. This time it crashes on me part way through. I try several other times with my client coming the next day to see the final project. Nothing but crash after crash in the middle of rendering.

So then I tried to render it in other formats the next morning (original crashes in Windows media video format) turns out it won't even start to render in other formats. So then I had the bright idea to load Vegas and the new blue titler and my production onto my new laptop to at least have the project rendered once my client arrives (now 2 hours away).
(It's an HP Pavilion dv7-6163cl. Intel Core i7-2670QM Processor 2.20 GHz - With 8GB DDR3 SDRAM. Radeon (tm) hd 6770m GPU.)
Just got it a few months ago... So This thing SHOULD be just screaming along without any problem! Right?

Nope!!! I load up Sony Vegas and open it up. Then I load the new blue titler program and now Sony Vegas crashes immediately when I try to open Vegas and won't even open any project at all. A warning comes up again saying that I may need updated drivers or to upgrade to a newer GPU. Seriously? A newer GPU than December? (Can you tell I'm a little P.O.'d about now?) So I update all the drivers on the laptop… And still Sony Vegas still won't even run when the new blue titler is installed.

So back to the old computer. I have to render it until it crashes... See where the video ended... Render it from there until it crashes... And do that four times to complete the whole 6 1/2 min. video. I patched back together at least to play for the client.

The request a few tweaks which should just take minutes to fix... But NO!!! Crash! Crash! Crash... It renders 19%… Than 37%… Then 8%… Than 64% before crashing. I keep trying and once in a while get a full render... But when I listen back to it… It has all kinds of weird sound anomalies in the middle of the project that randomly show up in some renders and not on others. So… After hours and hours and hours wasted… I finally get one good render to send to the client.

Sorry to vent all of the details... But I'm at my wits end and have no idea what to do for my laptop.

I'm guessing I need a new GPU for my desktop... But… Will that really fix the problem? Obviously I have a new GPU in my laptop and it doesn't like that.

Any suggestions???

Back to post

Comments

MTuggy wrote on 3/29/2012, 4:54 PM

It would be interesting to see if it truly is a small number of users - my sense from the forum is that it is a large number of users since a fair percent of us regulars are having the same issue.

I tried the same advice (reinstalling under a new user) - absolutely no effect- and why would it? The problem is with the GPU accelerated plugins causing a vegas11. exe error - seems its a issue deep in the code that causes the problem.

If just feels like taking a car in with an oil leak and having the mechanic tell you to fix the brakes to solve the problem.

MT

Spectralis wrote on 3/29/2012, 11:24 PM

I think the flaw in the argument that the problem is with the users system is that most of us have been using Vegas for years on our systems without too much trouble. I've used three versions of VP on my current system and only VP11 crashes when using plugins.

When I had problems with PaintShopPro X4 not installing and Painter 12 crashing Corel support claimed it must be my system. Despite following all their advice including installing as a new user their products still didn't work. I've used PSP for years and had the previous two versions installed and working on this system. Needless to say I won't ever buy any Corel products again.

I have Adobe CS5 Production Suite installed which works flawlessly. I've just bought CS5.5 with the free upgrade to CS6 because I trust their products will work. Long may that continue.

VidMus wrote on 3/29/2012, 11:57 PM

I am going to try to explain this in a totally different way in hopes that I do not get yelled at this time.

On my system and in my case the problems were mostly a combination of earlier versions of Vegas 11 64 bit, Nvidia drivers when I went to an Nvidia card and my system.

Note: I had regular but not too often crashes with earlier versions of Vegas.

Now I do not get any crashes at all. I have not had any crashes while doing quite a number of big projects.

I do not use the New Blue or other plug-ins like it. I do not need those and my not using them is probably a big reason why I do not have crashes.

Still, if one does get crashes with third party plug-ins or anything third party then those companies are 100% responsible for making their products work with Vegas. SCS is not.

I sincerely wish I could give you all an answer as to why my system works and others do not!

I would not be surprised if even a minor change of something would put my system on the crash side of things. I know one thing for sure, it is not broken and I am definitely not going to change a thing! And that includes Windows and other software updates!

So when the update questions pop-up, I will just say no.

OVP2Go wrote on 3/30/2012, 1:12 AM

I to am really disappointed with Vegas Pro 11 as the software crashes all the time. I have found that the problem mostly lies within the VideoFX module. As long as I do not use any of the plugins I can complete my work. Not really how the program should work. Take a look at the crash log and tell me if any of you see any similarities:

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: vegas110.exe
Problem Signature 02: 11.0.0.595
Problem Signature 03: 4f47704d
Problem Signature 04: Sony.MediaSoftware.VideoEffectsUI
Problem Signature 05: 11.0.0.595
Problem Signature 06: 4f476fe3
Problem Signature 07: 570
Problem Signature 08: d
Problem Signature 09: System.NullReferenceException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

biggles wrote on 3/30/2012, 1:31 AM

Just another thought on the stats relating to VP11: I wonder how many users are like me, that is have purchased the upgrade but not yet installed due to nervousness induced by many threads like this one!

I must also own up to having purchased the '10' upgrade but sitting on that one too after reading some of the threads relating to issues with that version as well. Memo to self: don't get sucked in by the cheaper upgrade deals in future!

~Wayne

2knowone2 wrote on 3/30/2012, 10:06 AM

AMEN to that!!! Most people just give up. And not everyone is willing to take the time to complain! I think it's much larger than Sony wants to admit! Which is the problem! They're in DENIAL!!! LOL!

MusicTECH wrote on 3/30/2012, 10:48 AM

I couldn't even finish a project last night due to overwhelming crashes and other strange happenings with Vegas 11 (64 bit).

I have one weird crash where I was rendering the audio only for 10 sections of a project (so, trying to make ten audio files). Even turning off all the video tracks and just rendering the audio, after every render completed, any type of click anywhere within Vegas would cause the whole program to stop responding. So, I had to force close the program each time after rendering the audio, and load it all up again just to render the next section. Just using a few VST audio plugins (all 64 bit, so no bridging happening).

For the video side of things I was using some noise reduction on one media clip with a Boris Continuum Complete plugin, and then some simple contrast & saturation processing with the New Blue FX and simple titles with the New Blue Titler. I had to turn off the GPU acceleration to make it through the ten segments of video rendering without crashing every time.

But, then the strange part happened when I tried to go back and prepare the individual sections of the concert for rendering to video for the web. I wanted to create a separate small project for each song, so that I could then cue them all up in one big batch transcoder process using Vegasaur. As I trimmed each section and split them into new projects, I started getting really weird looking video. I had two cameras rolling during the concert (plus some separate fancam footage), and I had put some video FX on the two cameras' media to match them up a bit. I used the project media screen and added the effects as "media FX" instead of putting them on a video track since I first did the editing with the multicamera editing, so I didn't have each camera on its own video track after that.

Once I started separating the project for each song and creating multiple projects, somehow the Video FX inserts on the media got duplicated several times... i.e., there would be several instances of each video FX on the video insert, so each effect was getting stacked on top of itself several times. No matter how many times I reset the effects to just one of each, if I closed the project and went back to it or any other project, it would happen again.... so, I couldn't even render those or finish it up. I couldn't figure out how to stop it from doing that. Eventually, I went back to Vegas 10 and just loaded up the MPEG-2 renders and audio tracks for each song into a fresh empty project, with no plugins or anything, and just transcoded from there.... I know I'm losing quality since I'm going from the already compressed MPEG-2 (for DVD) files to more compressed web files, but I couldn't work with the project in Vegas 11 anymore without having stacked video FX on top of each other.

I'd still like to use the NewBlue Video FX and titler in Vegas 10. Doesn't anybody know how to activate these with Vegas 10? The activation screen comes up and I can enter my serial number, but the activate buttons never become active.

I simply can't use Vegas 11 at all right now.

Ros wrote on 3/30/2012, 11:39 AM

This morning I decided to turn off the GPU Acceleration in Vegas preferences. So far so good, no crashes, it feels like Vegas 10e which has been very solid for me. Did some moderate compositing with OFX and titles.
I also had jerky previews when running 2 Vegas sessions side by side with GPU on. With GPU off, previews are fine so far....

I haven't done much work with Vegas 11, only once in a while taking a dive and see how it behaves and I usually fall back to V10, lately only because of severals crashes.
I was hoping that 595 would fix the crashes but I still get few of them.

On the render part, I can't complain, it works fine but didn't render any long projects yet.

EDIT: so I did get my fisrt crash with GPU off......

Rob

BurrMan wrote on 3/31/2012, 6:46 PM

I experienced the issues with 64 bit Vegas and re-producable crashing.

I did some research and here's what i found personally.

I can re-produce crashes by adding an effect and setting it, then closing it, and editing it a second time. Crash. (Sometimes, and more rarely, a 3rd edit is needed)

The faulting module crashing becomes .net framework related, (as pointed in other posts in this thread) and deeper digging leads to an error created in using the newer .net stuff with older com wrapped code (Any plugin's/effects just carried over and not re-written for the new architecture) for the dialogues. This is true for me with native sony effects also, with no new blue.

So far, trying suggestions in the thread here, with preferences of mem/gpu/cpu, dont produce anything reliable...

The only reliable fix i have, and dont get any crashes when working this way, is never edit effects more than once per session. If I need to do that, then a save and close, then re-open the project, allows me to continue. If I do this, then I dont get crashes editing my projects.

Needless to say, this is not a fix for me, or any type of workaround, it just allows me to get my work done, without "wasting" work by crashing after an edit.

I think the issue is in the code of legacy connections, and needs to be fixed by having all the dialogues reviewed and brought up to date with the framework in use currently to develope the app...

2 cents.

Ros wrote on 3/31/2012, 8:03 PM

BurrMan, I wasn't able to reproduce your crashes GPU On or Off.

In my case, a crash happens unexpectedly, making it impossible to reproduce, sometimes just moving the mouse around.

It "seems" that when I save often, it is less prone to crash, but sometimes I forget to save and then it crashes....reminding me to save...

Rob

BurrMan wrote on 4/5/2012, 9:48 PM

Well, just an update... After reading the posts regarding my instability and looking at solutions provided and discussed, i un-installed the 64 bit version and loaded the 32 bit, and the crash happy has been resolved. I wont continue discussion if I recieve "an occasional" crash or issue, and would certainly love the opportunity to use the resources of my $10,000 workstation, but for the moment, it is not a requirement of my workflow. I'll look at future editions or updates to see if it resolves out for me. Thanks for the response RoS.

Suvin111 wrote on 4/13/2012, 10:49 AM

Just curious - when a thread like this goes "quiet" - does that me people have found solutuions - or that they have given up and gone a different direction?
a) quit video editing all together
b) switched to FCP
c) switched to Avid
d) switched to Adobe Premiere or Adobe Production Suite
e) switched to other
f) decided to live with the VP11 instability

BinaryCafe wrote on 4/13/2012, 3:04 PM

My answer:
d) switched to Adobe Premiere or Adobe Production Suite

I took the plunge and am now a proud owner/user of Adobe Master Collection Suite.

Editing is fun/crash-free again.

johnmeyer wrote on 4/13/2012, 3:19 PM

I suspect that, by far, the most common answer is one that is not on your list:

g) Continue to use an earlier version of Vegas

This is certainly what I would recommend to everyone. Vegas 11 is borked, and even Vegas 10 is suspect (IMHO). What's more, the last several versions of Vegas have provided only a small, targeted list of enhancements. This list was succinctly listed by "riredale" near the end of one of the half dozen "crash" threads that are still currently active:

Why does Vegas 11 Crash so much?

Obviously, each release had more new features than what he listed, but I think he did a good job of summarizing the main "story" of each release.

I can still use 7.0d for absolutely everything (I transcode AVCHD, or I use 8.0c for AVCHD). Since the motion stabilization provided with Vegas is kindergarten-grade stuff (i.e., too de-featured to be useful), I use either my Deshaker scripts or the 2.0 version of the Mercalli plugin. I use Excalibur for multi-cam. I don't do 3D, so I don't need any of that (and never will).

I do use the amazing Elastique plugin, but I just export the audio, when I'm finished with the project, process it with Elastique, and then re-import the audio. I would have used the newer titlers (Protype) but, of course, it was (and is) impossible to use. I do plan to try the newer titler when I need to do some really good titles or lower thirds. So, that might get me to use the newer stuff.

I was fortunate because I was able to contain the misery with Vegas 11 to one project. It cost me almost three full extra days to do what should have been a two-hour project. I briefly worked with SCS, submitting bug reports and talking to their team. They asked me to be a part of their bug fixing team (they are definitely trying to fix V11), but I declined (it would not be helpful to discuss my reasons).

I definitely hope they can eventually make Vegas a professional editing platform, although to do that, they must do more than just fix the bugs, but that's a discussion for another thread.

Grazie wrote on 4/13/2012, 4:58 PM

My "earlier version", John's g) , is VP10e.

I'm still plugging away at 595, to see what I can get away with.

Not to have John on the BETA or ALPHA bug chasing Testing Team is a real loss for all of us. I'd really like to know why he declined.

G

CorTed wrote on 4/13/2012, 9:42 PM

Unfortunately, it appears I must be adding myself to this list...

I have been trying to render a project for the last 4 hours, trying to install previous versions of the NVIDIA drivers for my GTX570, I keep getting error boxes telling me the app crashed as it did not have enough resources.... (12G RAM i7 processor go figure).
I think the New Blue FX along with GPU acceleration seems to bring loads of problems I do not need.
How do we get a stable Vegas 11??
John, with all due respect, I do not want to have to go back to 7e

edit: I went back and disabled GPU accelaration, and it is now getting past the first New Blue FX.......(was unable to ever do before)

Grazie wrote on 4/13/2012, 11:27 PM

I went back and disabled GPU accelaration, and it is now getting past the first New Blue FX.......(was unable to ever do before)

That's got to inform SCS on them chasing the issues?

G

JimboWHO wrote on 4/14/2012, 7:40 PM

"Just curious - when a thread like this goes "quiet" - does that me people have found solutuions - or that they have given up and gone a different direction?
a) quit video editing all together
b) switched to FCP
c) switched to Avid
d) switched to Adobe Premiere or Adobe Production Suite
e) switched to other
f) decided to live with the VP11 instability"

ANSWER: C

TheRhino wrote on 4/14/2012, 8:32 PM

ANSWER:

G) Switched back to 9e

LoTN wrote on 4/15/2012, 12:55 AM

e) switched to other

g) kept some work done with v8c

Suvin111 wrote on 4/15/2012, 4:33 PM

Yes - that's what I did too. I really miss the speed and easy of use of Vegas - I go all the way back to Screen Blast.
I check back from time to time to see if SCS has responded to my issues - but so far they have been no help at all.

Oh, I switched to VP at version 10 - so I would have to go back to Movie Studio to get away from the instability issues. Decided I wanted to go forward with this, so I moved on to Adobe Production Suite 5.5
Thanks to all who responded!!

pat s wrote on 4/15/2012, 5:56 PM

I finally figured out what was causing Vegas Pro 11 to constantly crash on my PC. It's been rock solid now for over a week, during my last week of my trial period! I'm an IT person and by no means a video pro; I'm using this for my son's hockey team banquet video, which has turned into a complex project. I am somewhat new to Sony Vegas Pro, but have played around with it in the past. I have a high-end 6 Core PC, 8G RAM, with a pretty good GPU capable ATI video card. I updated all the drivers and NOTHING fixed my constant crashes. I even uninstalled my ATI driver and used the default VGA driver with the same results, so I knew it wasn't the ATI driver.

The problem for me was a conflict with my Bamboo Tablet driver. I uninstalled all my Bamboo products, and now everything works great! I re-installed it and it started crashing again immediately. Unbelievable. After 3 weeks of fighting this thing. I was able to replicate this problem over and over again not only on my PC, but also on a virtual machine. (This is software that simulates PC hardware and lets you create a "virtual" Windows 7 computer, making it great for testing.)

Here is one of the many ways I can easily re-create the crash while I have the Bamboo Tablet driver installed:

1. Open a new project. (I left everything default from a fresh install of Vegas Pro)
2. From the Media Generators tab, select "Drop Split" from the Titles & Text section and insert it on the timeline, and close the settings. (Leave the defaults)
3. Open and close the "Generated Media" settings for that event on the timeline about 3 times and Vegas crashes every single time. (I click on the little film strip icon on the event.)

I was working off of the 30 day eval with the constant crashes, but I bought it anyway because it was running clean in my virtual machine. (I didn't have the Bamboo Driver installed there, which is why it didn't crash.) I wanted to reply to this thread last week, but I couldn't until my purchased serial number arrived.

I don't need my tablet to get me through this project, but eventually I will need to work with Sony and/or Bamboo to find fix so that they can coexist. This is a lot of cash to spend on something I will only use occasionally, and I want to make sure it works! (Unfortunately, Movie Studio didn't give me enough tracks for my project. so I had to go to the Pro version...sad!)

One other note, I have not installed the NewBlueFX Titler Pro yet, but I wonder if this would fix problems people are having with that as well. I noticed a lot of people blaming the new titler for the crashes.

ushere wrote on 4/15/2012, 7:04 PM

have bamboo, can't replicate.

pat s wrote on 4/15/2012, 9:49 PM

@ushere Do you know what version of Wacom driver you have? Go to Control Panel, Device Manager, then open the Human Interface Devices. Double-click on Wacom Virtual Hid Driver, then click on the Driver tab. Mine is version 2.9.2.4.

I found that I don't even need to uninstall it. I just disable it and then Vegas works all day. I've been editing and rendering for almost 8 hours straight with no crashes today. As soon as I enabled the driver and restarted Vegas, it crashed within a few clicks. And I can follow the sequence I described earlier to replicate it again. Very strange...

I'm on 64bit Windows 7 by the way.

1 2 3 4 … 5

of 5