sigh MPEG render failure... again!

David_Kuznicki wrote on 11/17/2003, 1:33 AM

I remember this popping up a few months ago, but I couldn't find a defintive answer by searching the forums...

When rendering from an .avi to mpeg-2, the render abruptly quits about a minute or two into the render. The error message says only that 'the source of the error could not be determined.'

This is decidedly frustrating. Any thoughts?

David.

Comments

farss wrote on 11/17/2003, 4:32 AM

I've had it happen a few times from memory.
I think once I'd run out of disk space, another time there was soemthing decidedly screwed up in the source file. Never had a situation that didn't right itself with a gentle prod or by a little logical deduction. The error messages aren't very helpful though.

What are you rendering with and how?

You could try a different encoder, usaully pays to have more than one on hand anyway. If they both quit you can be pretty certaini it's the source.

David_Kuznicki wrote on 11/17/2003, 5:46 AM

Unfortunately, I only have one encoder. I almost never burn to MPEG-2, so this problem has probably been lying in wait since I installed Vegas...

I'm just rendering an .avi to an mpeg-2, using whatever default template comes up (I don't remember which one off the top of my head, and I don't have the computer in front of me)...

Running Vegas on my old, reliable (till now!) dinosaur--

PIII 750 MHZ
256 RAM
Vertigo video card
Delta 44
(can't remember the motherboard type!)
Win2K

David.

Bigoj wrote on 11/17/2003, 11:20 AM

It happened to me not long ago with the same error message. But mine was rendering straight from my edited files to mpeg 2, it wasn't from mpeg 1 or any template. What i did was, I created a new vegas file, copied each individual video track, pasted them in the new created file, gave it a different name and rendered. It worked. Try it, if it does work 4 u, lemme know.

David_Kuznicki wrote on 11/17/2003, 11:46 PM

I must have expressed myself badly...

I am rendering from a single .avi file into an MPEG-2 file. I still can't figure out what's causing the failure.

David.

SonyEPM wrote on 11/18/2003, 8:42 AM

Do you have Vegas 4.0d? If not, please download and install the update, then try again.

Other questions:

Was this this avi file generated in Vegas?

Any fx applied?

What mpeg render settings are you using?

lynj wrote on 1/5/2004, 8:45 PM

This exact thing is happening to me, except I'm using my edited file with some parts rendered avi files. Was this ever resolved?

At this rate, I may never get to use DVD Architech!

PeterWright wrote on 1/5/2004, 9:47 PM

Try rendering to a single avi in Vegas, then let DVDA do the MPEG2 render.

farss wrote on 1/6/2004, 12:41 AM

OK,
I can make this happen consistently!

The problem is very easy to reproduce:
PAL clip in standard PAL project.
Select Render As>MainConcept MPEG-2(*.mpg)
Template: Default.

It fails with exactly that error messag every time.
Any other template works perfectly (that I kind find)

I've never changed the default template which may explain why some people simply cannot make this happen (they've changed the default / never use it) and others cannot encode to mpeg-2 at all!

Solution : Use a known template!

Sony needs to look into this, I'd imagine its causing more than a few people major grief.

SonyEPM wrote on 1/6/2004, 7:28 AM

Thanks for the info. Default/untitled aside (yes, there's a bug but the default settings are set by the active project properties and don't generally correspond to any standard MPEG-2 delivery format)....

Can anybody NOT render to one of the named templates (PAL DVD, DVDA PAL wide etc) ? If so, please provide exact repro steps.

JohnS wrote on 1/6/2004, 8:13 AM

I just posted my message entitled "More memory error woes - inching closer to Premiere" prior to reading this set of posts. It sounds like I have the same issue. I too, believe that it is some sort of bug within Vegas. I would love to talk to you, (Sony) about it and tell you exactly what I've done to create the problem. You can call me at (503) 969-0492. It would be much easier than these posts or e-mails.