Render crashes anyone?

kairosmatt wrote on 5/13/2009, 7:43 AM
Of course the new vegas comes out when I'm on vacation for 2 whole weeks, and can't access the project that was consistently chocking Vegas 8. Its killing me, gotta know...

Has anyone who has had render issues been able to try those Vegas 8 projects in Vegas 9 with a) no problems b) same problems c) new problems?

I've read a few bugs on the forum, but was wondering if some of our specific older problems have been fixed.

kairosmatt

Comments

cliff_622 wrote on 5/13/2009, 9:21 AM
V9 demo crashed on a massive AVCHD/HDV surround sound project. (6, 30 min video tracks and 17 audio tracks) Tried 3 times with only one thread. = crash.

I upgraded installed Windows 7 64bit, Vegas 9 64bit demo and opened same project with same PC hardware. Rendered sucessfully with 4 threads on!

I couldnt believe it,...3 gigs of physical RAM on a full 64bit platform and I was able to render ALL quad cores for the first time in in a very long time!

Wahoo,..I'm sooo happy.

BTW, we need to be very carefull about blaming rendering issues on Vegas. Some people have a heart attack if they think anybody hints that Vegas doesnt render properly under certain circumstances. You will even get attacked and called nasty names too for doing it! LOL! (shhhhh)
blink3times wrote on 5/13/2009, 9:37 AM
I'm glad it worked for you cliff!

But really... that last little part.... a bit unnecessary don't you think?
michaelshive wrote on 5/13/2009, 9:48 AM
"BTW, we need to be very carefull about blaming rendering issues on Vegas".

It is this kind of blind loyalty that I just can't understand! Who else would we blame? Vegas worked fine up until version 7, then with 8 crashes became shockingly normal. We should be careful about blaming anyone except the company who makes the product.
cliff_622 wrote on 5/13/2009, 11:24 AM
"But really... that last little part.... a bit unnecessary don't you think?"

it may or may not be "unnecessary"....regardless, it's still quite "true".

CT : - )

cliff_622 wrote on 5/13/2009, 11:36 AM
"....with 8 crashes became shockingly normal."

I agree with this statement, but there are those here that believe they are rare and only any happen to a small number of us.

To me, Vegas 8 is an almost PERFECT product. The rendering issues are the ONLY significant and glaring problem that has ever plagued it.

As far as "complaining" about it, I see it this way;

Really tough steel is forged in fire. It's the heat and hammering that make it so super strong. In this process, WE are that heat and hammering. I'm sure that our "complaining" has shed light on areas that need to be stregenthened and Vegas HAS improved over the years.

We just got to finally nail down this rendering thing once and for all. (Even if it means changing the hardware requirement specs of the software)

CT
kairosmatt wrote on 5/13/2009, 1:48 PM
Render issues definitely need to be nailed down. On my end, it was definitely Vegas, tried it on three different systems with exact same crashes.

Does anyone else with previous problems have any experience with Vegas 9?
Gidi wrote on 5/13/2009, 2:36 PM
kairosmatt,

since changing to Vista/64 and V9/64 all my previous crashes with V8.x are history. I was close to throwing out the whole thing but gave it a last chance.

It was worth to do so :-)

MUTTLEY wrote on 5/13/2009, 2:57 PM

I actually had one a couple hours ago. Where it was midway through the render and Approximate time left said 00:00:00 thought the Elapsed time kept ticking away without going anywhere. In the past I've had this with vids that had images that were too big but this was just straight video. And whenever this has happened "Cancel" doesnt really work, have to use ctrl+alt+delete and program manager to close it.

- Ray
Some of my stuff on Vimeo
Me On Twitter
michaelshive wrote on 5/13/2009, 7:12 PM
"To me, Vegas 8 is an almost PERFECT product. The rendering issues are the ONLY significant and glaring problem that has ever plagued it."

I almost agree. I proselytized for years about the joys of Vegas and even got several people to switch to Vegas...until 8 came out. Now I don't recommend it all to anyone anymore because of the rendering / crashing issues introduced in 8. In fact, I rarely use Vegas anymore simply b/c I can't commit to a project using Vegas when I'm not sure if it will render out at the end. I was burned several times on several different machines with this exact issue and now I'm primarily using Final Cut, not because I think it is a better NLE (although it's pretty darn good), but because I know I can get something rendered out and delivered when I'm done. If Vegas could fix that issue, I'd be back in a heartbeat.
blink3times wrote on 5/13/2009, 7:31 PM
"I actually had one a couple hours ago."

Ray,
Are you running 32 or 64?
farss wrote on 5/13/2009, 7:49 PM
The salvation and a huge step forward would be if we got out of this "what happens in Vegas stays in Vegas" rut.
If things do go belly up or you can't get something done in Vegas that you need to get done being able to bounce the project to another NLE would be your lifeboat. This is why we so desperately need AAF and/or EDL export to get sorted. No sane person is going to commit a high budget project to Vegas without that lifeboat.

Bob.
jabloomf1230 wrote on 5/13/2009, 8:06 PM
LOL, Bob. Unfortunately, Premiere is pretty leaky lifeboat also. :-)
MUTTLEY wrote on 5/13/2009, 8:39 PM

I'm using V9 32 Bit though I'm on Vista 64, can't use V9 64 till Magic Bullet is usable with it.

- Ray
Some of my stuff on Vimeo
Me On Twitter
blink3times wrote on 5/13/2009, 9:11 PM
I don't know if you noted my work around for V8 crashing and I don't know what media type you're using, but I did note that the OI plugins in V9 are STILL not flagged as "greater than 2gig memory size"

I've just automatically changed my plugins over and all works fine The work around works for avchd, HDV... and just about anything else that uses the M2TSplug.dll file.

For more info you can look here:

http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=648054
Harold Brown wrote on 5/13/2009, 9:12 PM
I am unable to render using MainConcept AVC/AAC (MP4) 1280x720. Vegas crashes the second the render starts. Using SD 640x480 settings it works.
farss wrote on 5/13/2009, 9:32 PM
I've not had any problems with it so far, in fact it's saved my bacon several times when Vegas failed badly.
That's kind of irrelevant though, Premiere isn't the only show in town, there's a whole world of other options and at escalating pricepoints, some that cost as much per hour to rent as Vegas costs to buy.
You want to take your project to some overpriced overpimped post house for a final polish and the first thing they'll want it your EDL. Vegas is about the only NLE that stops you going there. Same on the audio side, you're stuck in Vegas.
This isn't some hyperthetical problem either. A while back I was called on to help another local Vegas user. He was getting grief from a major client because their TVCs looked like "home movies" and well he wasn't using one of the Big A NLEs. The resolution should have been dead simple. Hand the tapes and EDL over to the local overpimped overpriced post house and compare the results.
Bacause that wasn't possible they lost the next job. Needless to say the results were just as bad, you don't spend money on lighting and you get what you paid for. Still the client wasted money and the Vegas user lost money.

Bob.
quoka wrote on 5/13/2009, 9:54 PM
I've got to add my two-pennies worth to Bob's comments -
We use Vegas for full Broadcast output for national TV.

Flaky AAF, No EDL and lack of full support for Decklink are the only things stopping this app from being a fully professional NLE.

We have a stream of clients coming in watching us work on Vegas and they are incredibly impressed with its speed and ease of use, but every time they talk about interchangeable files with other facilites I have to put my tail between my legs and tell them it doesn't have industry standard interchangeable formats. These clients are in and out of other facilities using Avid/FCP/Flame/Pro-Tools/Fairlight,Premiere etc. and just expect us to be able to 'exchange' with these.
I have no intention of jumping ship, but you would think that for Sony to have its name in front of Vegas they would address these points.
kairosmatt wrote on 5/14/2009, 11:55 AM
Good EDL support would be a great solution wouldn't it?

SCS wouldn't have to address ever customer's crash, as many of us have another NLE that could save the project.

Like Michael said its hard to commit a longer project to Vegas if you know you are going to have issues with it and can't get it out. Its heartening to hear that there have been some improvements with V9.

Can't wait to test my nightmare render project. Will report back on that in a couple o' weeks.

kairosmatt
LReavis wrote on 5/14/2009, 12:43 PM
I don't understand why anyone can't get a final render out of Vegas 8 by the usual work-around of chopping the timeline into short segments (by putting a marker at every 2-minute interval), rendering each using a batch-render script to produce Cineform .AVIs (such as the batch render script that is included in Veggie Toolkit), then putting all the .AVIs on the timeline and rendering that with most any codec that works in Vegas (except for some .MP4 codecs, perhaps).

Admittedly, Vegas still will crash on every 5th or 6th render unless the timeline is free from tasks that push Vegas, and sometimes even a 2-min. segment is too large and must be cut in half or even thirds; so this solution does require extra human time in addition to extra machine time, and there is a slight generational loss due to the intermediate Cineform AVIs. Bummer . . .

But, as an ex user of Premiere and others, I definitely prefer Vegas even though only a few of my projects can be rendered on either my Q6600 or my old P4 machines by simply invoking "render as ..." AFIK, the only time this doesn't work is when a huge .JPG or other image file brings Vegas to its knees.

Otherwise, is there anyone for whom this work-around DOESN'T work?
kairosmatt wrote on 5/15/2009, 7:23 AM
Well, that work around is not really a solution.

With my project, it required a reboot after every render, otherwise it would crash. Batch rendering did not work.

This required a long night of babysitting. Several in fact.

I was hoping that V9 fixed many of our rendering issues...can't test that project yet, but I will!

kairosmatt
Harold Brown wrote on 5/15/2009, 3:36 PM
Was unable to render using MainConcept AVC/AAC (MP4) 1280x720. Vegas crashes the second the render starts. I was looking at it today with a fresh perspective and noticed I had checked Two-Pass render. I unchecked it and now it is working. So it was the 2 pass render that was causing the error.
LJA wrote on 5/16/2009, 8:47 AM
Just tried it here. Works fine (Vista 32).