My Vegas 12 became rock stable - here's what I did

ritsmer wrote on 5/8/2013, 9:34 AM

After a long history of Vegas 12 hangs, will-not-even-start etc. etc. installing and uninstalling of Nvidia drivers and Vegas 12 also made my oh-so-stable Vegas 11 32 bit (B700) hang.
Now none of my Vegas 11 versions nor Vegas 12 would start anymore. Even the good old Nvidia driver 296.10 did not help.

In order to fall-back to my most reliable Vegas 11 32 bit I uninstalled and re-installed that version - and since that Vegas 11 works perfectly again... but even more strange: also Vegas 12 has begun to start without hanging - and also to work well.
By now I have used V12 for nearly a full week without any (repeat: without ANY) hiccup.

So: if anybody has an unstable Vegas 12 it might help to un-and-re-install your Vegas 11 32 bit - at least that did it for me.

(Rumor says that the different Vegas versions share some common DLLs etc and that the elder ones from Vegas 11 32 bit seem to be much more stable than the newer ones - and in some cases re-installing Vegas 11 might replace weaker DLL's by more reliable ones - for the current PC hardware- and software environment, that is)

That said: working with a Vegas 12 - as it obviously was intended to be from its makers - is really a great and most positive experience.

Comments

engr wrote on 5/8/2013, 3:37 PM

Got to give it a go!

Tom Pauncz wrote on 5/8/2013, 4:17 PM

Me too...
Tom

R0cky wrote on 5/8/2013, 5:20 PM

What worked for me was just replacing the black magic external monitor dll with one from an early build of V12.

That alone was magic.

rocky

Laurence wrote on 5/9/2013, 11:15 PM

You know, my Vegas 12 installation has been amazingly stable the past week or so, and I have done absolutely nothing to cause this. Maybe one of the automatic Windows updates fixed something that was broken.

wwaag wrote on 5/10/2013, 12:19 AM

Here's another hypothesis. My system has been remarkably stable after removing and reinstalling MS dot.net and then NOT permitting any automatic updates-in fact, no MS updates. Since most updates are for security reasons, I'm not too concerned since my "editing" machine is not my "internet" machine.

Or perhaps, it's the "luck of the Irish" since St Paddy's day!

Whatever the reason, V12 563 is working well.

wwaag

Laurence wrote on 5/10/2013, 12:28 AM

Spoke too soon. I just had three crashes in a row merely trying to start Vegas. :-(

Grazie wrote on 5/10/2013, 1:52 AM

Laurence
[b][/b]

Is there a way one of our IT savvy Gurus here could debug just where and how these intermittent crashes occur?

G

Laurence wrote on 5/10/2013, 7:25 AM

The crashes during startup is a relatively new problem (about three weeks). It doesn't actually crash, it just stops loading partway through. I have to call up the task manager and kill the process tree, then try launching Vegas again.

ForumAdmin wrote on 5/10/2013, 10:09 AM

Hi Laurence, if Vegas dies or hangs on startup, the most likely cause is a conflict with something else running concurrently. When you open up Task Manager's processes list, what else do you see running? Are there many processes running that don't need to be? My advice would be to cull the list down to the essentials. In order to identify the conflict, you'll need to go through one by one, killing a process then launching Vegas each time until it starts up. (Look at the process description to determine whether it's an essential process or not.) This can be tedious if you have a lot of extra processes running, but probably worthwhile in the long run.

Since you mentioned that the problem started about three weeks ago, try this: open up Control Panel > Uninstall a Program. Sort the list by Install date, then figure out what was installed three weeks ago. That might also provide a clue.

Let us know what you find out.

Best,
Paddy
SCS

ritsmer wrote on 5/10/2013, 3:46 PM

It doesn't actually crash, it just stops loading partway through

Yup - precisely that issue is one that I have seen here for Vegas 12 too - right after the message "initializing VST.. something" or at the end of start-up - just before it should show the User Interface - and so I couldn't use it at all - BUT it got corrected 100% when I un- and re-installed Vegas 11..

... Now, after some days with a totally stable Vegas 12 I was very happy and believed that I could walk on the water - and I decided to try my NewBlue Titler Pro 2.0 today...
Vegas 12 immediately crashed, and I tried to un- and reinstall the Titler Pro 2.0 - and now I get crazy white interlaced-lines all over when I render a project which rendered 100% Ok until then...
...to morrow I have to invest more time to get back to where I was before I re-installed that Titler... ...annoying. Really.

PS: I use CPU rendering only.

Grazie wrote on 5/10/2013, 4:06 PM

NBTP is a Partner product. SONY and NewBlue need to be all over this.

G

ritsmer wrote on 5/10/2013, 4:11 PM

I know - but still strange that NBTP2.0 can make Vegas 12 go totally bananas.
I tell you: when I re-installed that NBTP2.0 it was like throwing a match into a gunpowder barrel: Wham -Vegas 12 crashed - stopped working - made interlace-lines - bang.
Really a surprise, it was.

I just tried to re-render another project without NBTP2.0 - a project that rendered well this morning - but I'm still getting these &¤#! interlace-lines in the rendered output.

To morrow I'm gonna clean out here - and MBTP2.0 will be banned from my main machine. I will install it on an old laptop and render the texts there before using them on my main machine.

ritsmer wrote on 5/10/2013, 4:37 PM

I really could not go to bed with a totally smashed up editing system on my main machine so I decided to continue and uninstalled that NewBlue Titler Pro 2.0.

Then I rendered the project from this morning - and - Phew: that did it, now it renders without them&%¤# interlaced lines again.

Strange that just the sole presence of NBTP2.0 could make Vegas go totally bananas - even when the Titler WAS NOT USED in the project.
Very strange indeed.

.

NormanPCN wrote on 5/10/2013, 8:34 PM

If something hangs, i.e. not responsive, Sony has a diag tool that supposedly gives them info to help diagnose the issue.

https://www.custcenter.com/app/answers/detail/a_id/2826

The dump file from this is attached to a support incident.

wilvan wrote on 5/11/2013, 12:41 AM

NewBlue has some really nice and easy to use products but they cause vegas to crash . ( not all the time but enough to get frustrated )

Each few weeks an update of their applications made me go nuts and not being able to follow anymore.

I gave up on these newblue plugins and removed them all since vegas is a way too nice and fast working software without them. ( I even didn't want to figure out how come , just removed them )

Think in general there is still some work to be done in the ofx plugin capability of sony vegas ( BCC , genarts ,..)

Just my experience on both workstations

Grazie wrote on 5/11/2013, 1:01 AM

. . .and again . . I feel like an annoying "dripping-tap" . . .

SONY and NewBlue need to be crawling all over this. They both need to come here and supply updates as to how this is being being resolved.

Vegas is a fine NLE. NewBlue produce fine software. I'm not having a pop at their intentions, but we can't go on, and on, and on, like a demented Lab-Rat chasing our collective tail on this.

Cheers

Grazie

VidMus wrote on 5/11/2013, 3:51 AM

The version of NewBlue Titler Pro that came with Vegas was installed on my previous system. I also had occasional crashes.

I never installed it on my current system. No crashes at all!

I do not need it anyway, so that is not a problem for me.

jetdv wrote on 5/11/2013, 8:56 AM

Two things to note:

1. Just installing Titler Pro will not cause any changes to interlacing.

2. If you are having Titler Pro issues, please contact NewBlue so we can work out the few remaining issues. Titler Pro is very stable on my system and we are working with people who contact us that are having issues.

ritsmer wrote on 5/11/2013, 2:58 PM

Update:

I submitted a support ticket to NewBlue - and first thing next morning there was an answer. Very positive indeed.
A new version of the NB Titler 2.0 was released just 3 days ago - and after installing it the above issues were solved.

@Jetdv: Of course simply installing the titler will hardly cause interlace-lines.
But the media on the timeline that got the interlaced-lines issue immediately after I installed and used a former version of the Titler were simple jpg's with NB Essentials II Lens Correction applied.
So maybe using that earlier version of the Titler *might have* influenced some common Titler/Lens Correction parts (if any - or something else) and might have caused these interlaced lines.
Whatever: after installing the last version of the Titler the interlaced lines issue is now solved here - and that is what matters.
I have mailed these results this to NBs support too.