Vegas5.b rendering bad mpg files??

earthrisers wrote on 8/6/2004, 3:23 PM
I'm getting fatal errors during the PREPARATION phase of DVDA (DVDA 2a, to be specific), using DVD-A-format mpg and .ac3 files rendered by Vegas5.0b. This is a new one on me... I've successfully done quite a few projects in Vegas4 in the past. The only variable I can think of, is that I recently updated to release 5.0b of Vegas. (Not every rendered project fails... but 2 out of 3 have, over the past 2 days.)
While Preparing the DVD files, DVDA produces this not-helpful message during the preparation of the last object:
-------------
Warning: An error occurred while writing a file.
The reason for the error could not be determined.
-----------
I downloaded a demo version of a competitor's DVD package, and it blows up, too, when trying to handle the files that cause DVD-A to blow up.

This happened on my last TWO projects (each is over an hour long, but the MPG plus AC3 files don't come even close to exceeding the 4+ gigabytes max).
I completely re-rendered the first -project in Vegas, TWICE (a long, long waste of time), and the second render failed again in DVDA but the third render finally worked OK in DVDA.
A project I (thought I had) finished yesterday failed today in DVDA, the same way -- "Prepares" for a few minutes, then blows up.
All 3 of my disks are NTFS format, and each has over 50Gigs of available space.
I'm currently re-rendering my latest project in Vegas, but this SURE IS frustrating!
If I later determine the problem is caused by something other than Vegas, I'll re-post, but right now the 5.0a-5.0b upgrade, followed by file failures, makes me very suspicious.
Ernie

Comments

JasonMurray wrote on 8/6/2004, 6:32 PM
I've been having much the same problem - check out my problems here:

http://mediasoftware.sonypictures.com/forums/ShowMessage.asp?Forum=4&MessageID=305612

In the end, I rendered to AVI and let Encore transcode the thing itself.
Hammer wrote on 8/6/2004, 9:00 PM
I don't use DVDA, but MovieFactory has been choking on MPEGS from 5.0b too. Worked fine with 5.0.
JasonMurray wrote on 8/7/2004, 8:02 AM
Ok, I think we have a problem here then... what can we do? (Do the powers that be at Sony know about this...?)
MyST wrote on 8/7/2004, 8:15 AM
Depends...did you contact tech support about it?
As it says at the top of the forums page, if you require immediate help, contact them directly.
The forums is a roundabout way of letting them know that you've found a possible bug.

Mario
earthrisers wrote on 8/7/2004, 11:37 AM
(I have reported this to Sony tech support.)

I finally got a "good" mpg file from Vegas 5.0b for my current project --- first two renders produced files that killed DVD-A; third try produced files that work OK in DVD-A. (The project has a number of transitions and multiple-track crossfades. So on the 3rd try, I rendered an AVI first, then rendered mpg/ac3 from that--a burdensome workaround. But also I should note that on my previous project I started with an AVI that had NO transitions or effects, and still ran into the bad-mpg problem until the 3rd render.)

BUT WAIT! THERE'S MORE!... when I then BURNED the DVD for my latest project, I got the following results:
(1)Burned in DVD-A 2.a at 2x. Resulting disc plays OK on my computer and in my el-cheapo ($49) US Logic DVD player, but does NOT play on my (relatively) expensive Panasonic DVD player.
(2)Burned in DVD-A 2a at 1x. Results identical to the 2x burn.
(3)Burned in Nero -- the resulting disc plays perfectly in ALL my DVD players.
Kinda kludging together a workflow here...
MUTTLEY wrote on 8/13/2004, 6:42 PM
Well its not just mpg files, getting the same thing here rendering to NTSC DV avi's. Not all the time, pretty much hit or miss. Has anyone tracked this one down ?

Sony Vegas 5.0
Version 5.0b (Build 160)
Exception 0xC0000005 (access violation) READ:0x0 IP:0xE28A3DE
In Module 'FxAUI.dll' at Address 0xE280000 + 0xA3DE
Thread: Engine_RenderFromCookedSlices ID=0x350 Stack=0xA6EE000-0xA6F0000
Registers:
EAX=00000000 CS=001b EIP=0e28a3de EFLGS=00010216
EBX=ff000000 SS=0023 ESP=0a6ee72c EBP=000000ff
ECX=00000000 DS=0023 ESI=000002d0 FS=003b
EDX=7fd70048 ES=0023 EDI=0000004d GS=0000
Bytes at CS:EIP:
0E28A3DE: 8B 30 8B 39 83 C0 04 83 .0.9....
0E28A3E6: C1 04 89 84 24 84 00 00 ......
Stack Dump:
0A6EE72C: 000001E0
0A6EE730: 000002D0
0A6EE734: 000002D0
0A6EE738: 00000000
0A6EE73C: FF000000
0A6EE740: 000001E0
0A6EE744: 5B5A0048 5B5A0000 + 48
0A6EE748: 00000006
0A6EE74C: 00000000
0A6EE750: 0A6EEAEC 0A5F0000 + FEAEC
0A6EE754: 00000000
0A6EE758: 5B5A0048 5B5A0000 + 48
0A6EE75C: 00000000
0A6EE760: 000002D0
0A6EE764: 55555555 510E0000 + 4475555
0A6EE768: 3FE55555 35690000 + A7C5555
> 0A6EE7CC: 0E37E0D8 0E280000 + FE0D8 (FxAUI.dll)
0A6EE7D0: 00000000
0A6EE7D4: 00000000
0A6EE7D8: 00000001
0A6EE7DC: 7FD70048 7FD70000 + 48
> 0A6EE8E8: 0E37B36B 0E280000 + FB36B (FxAUI.dll)
0A6EE8EC: 00000000
> 0A6EE8F0: 0E2872B1 0E280000 + 72B1 (FxAUI.dll)
0A6EE8F4: 0A6EEA64 0A5F0000 + FEA64
> 0A6EE8F8: 0E148498 0E140000 + 8498 (StepTime.dll)
0A6EE8FC: 0E3F1680 0E3F0000 + 1680
0A6EE900: 0A6EEA64 0A5F0000 + FEA64
0A6EE904: 00000001
0A6EE908: 0E17A378 0E170000 + A378
> 0A6EE97C: 008E9AC4 00400000 + 4E9AC4 (vegas50.exe)
0A6EE980: 00140000 00140000 + 0
0A6EE984: 0A6EE784 0A5F0000 + FE784
0A6EE988: 00000000
0A6EE98C: 0A6EEBC4 0A5F0000 + FEBC4
> 0A6EE990: 77FA88F0 77F50000 + 588F0 (ntdll.dll)
> 0A6EE9A0: 77F589F2 77F50000 + 89F2 (ntdll.dll)
> 0A6EE9AC: 77F58A3A 77F50000 + 8A3A (ntdll.dll)
> 0A6EE9E0: 77FA88F0 77F50000 + 588F0 (ntdll.dll)
> 0A6EEA04: 77F58A3A 77F50000 + 8A3A (ntdll.dll)
> 0A6EEA1C: 01228EA0 01000000 + 228EA0 (vegas50k.dll)
- - -
0A6EFFF0: 00000000
0A6EFFF4: 004FB140 00400000 + FB140 (vegas50.exe)
0A6EFFF8: 007D90D0 00400000 + 3D90D0 (vegas50.exe)
0A6EFFFC: 00000000

- Ray

www.undergroundplanet.com

Express wrote on 8/14/2004, 10:39 PM
I'm doing similar things, but FWIW, I have not seen the errors.
I'm using Vegas 5b, working on a large project, using about 10 different mpg files. There are about 20 menu's in the DVDA project.

I have no errors creating DVD's, but I am doing it a bit differently.

How I create the files.

I create DVD NTSC compatible files - but keep the audio stream with the mpg files (I let DVDA encode the audio).
The MPG files are all VBR, most are two pass, all are set to 31 on the quality scale.
Rates vary from from 5K to 8K at the high end, and from 4K to 7.5K average.
Some of the more complex files were rendered to AVI's before the MPG's were created from those AVI files.

I have been just using the burned version from DVDA with no trouble, but I hand intended to make a NERO version to check against - perhaps I'll do that for sure.

For reference,
I am using Windows XP PRO SP1
AMD XP 2000+
768 MB mem
I have 850GB of disk (6 internal drives), but only a couple hundred free, over several drives - and I've got the project spread around on various drives.

Guess I'm lucky - I've been working on this project for several months, and the discs go to duplication on Monday.

Chris
db wrote on 8/16/2004, 11:46 AM
i recently rendered a little over 75hrs of mpeg2/ac3's at a constant 2Mbs in Vegas .. then burned 3 1/2 to 4 1/2 hrs on each DVD using DVDA with extensive scene selection menu's -

the only problem i see is from panasonic DVD stand alone player/recorders - have 2 friends with them and they will NOT play 80% of the clips on these DVD's .. after a little test i found the panasonic recorders ( stand alone DVD ) have problems with bit rates under 2.2Mbs

so what is the common factor here with these rendering MPEG errors ?
AMD cpu ? via chip set ? are we all using Vegas 5b build 160 , DVDA 2 build 121
earthrisers wrote on 8/16/2004, 12:36 PM
2 cents' worth more about Panasonic players -- I also discovered that they (at least the RV32, the model I have) can't play DVDs that are burned on the new 4x media I had started to use (Prodisc). Even if I burn the DVDs at 2x, the Panasonic can't play them. My Sony player, and an el-cheapo off-brand player we have, can both play them OK.

I'm sticking with older, 1x-2x blank media, because my clients might have Panasonic players, and I can't risk sending stuff they can't play--the Panasonic CAN play DVDs burned on the older media. (My Panasonic does have the latest firmware upgrade, BTW.)