Matching Vegas/DVfilmaker/TMPGenc and DVDA

PAW wrote on 3/20/2003, 10:50 AM

Hello,

I am trying out DV filmaker with Vegas and using DVDA for the DVD creation.

I have rendered my AC3 file and also rendered an AVI file. The source project is PAL 16:9 and 5.1 surround.

I have passed the AVI file through DV Filmaker (have not used the 24P option - any recommendations?)

I then used TMPGenc to create a constant bitrate mpeg at 8000 (a suggestion said that there was no need to use VBR as the DVD is only 30 minutes long)

When I put the AC3 and the TMPGenc mpeg together in DVDA 1.0a it wants to recompress the video, I tried the option in DVDA to set the bitrate to 8000 but it is still the same.

Any suggestions on where in the process I have created the mismatch, I remeber another post on the forums detailing the bitrate that DVDA expects so that it does not render the project but I can't find it.

Thanks

Comments

RBartlett wrote on 3/21/2003, 1:13 AM

Is the video file a program stream with 1 video and 0 audio tracks?
Did you multiplex the m2v in TMPGEnc, or rename it to .mpg.

Otherwise the fact that you have CBR might be what DVDA is getting upset about from the recompression point of view. Not sure if that is what it is, and it shouldn't ideally, but it just might be that.

PAW wrote on 3/21/2003, 3:54 PM

Thanks for the reply

I created a .mpg with TMPGenc by using the system video only option not the elementary stream

If i use VBR in TMPGenc what settings should I use to match DVDA

RBartlett wrote on 3/22/2003, 3:02 AM

I'd try one of the DVD profiles perhaps with the template described elsewhere on the web (I'll post the link when I'm back on a PC and not this confounded set top internet box).

Have the VBR set to between 4Mbps and 8Mbps or tighter towards 8, and I guess you'd use 2-pass which is why you are not using MainConcept MPEG in the main - right! There are some optimisations for TMPGEnc that I have read about for reducing the time it takes to make the list of encoder hints for motion estimation/prediction. I'll try to enlighten you on this too.

Apart from the chapter point integration from Vegas. I really don't think SoFo have put too many traps in to prevent you using TMPGEnc to create your encoded assets. I haven't yet ventured into this. It does seem that many are trusting in the MainConcept encoder. Possibly because there is a limit to the process quality of DV, but I still think DV looks better with TMPGEnc transcoding than with Vegas Mpeg2. With my type of camera work anyway! If a jobs worth doing etc etc.

I'll be back with the two references if you don't manage to find them on google before I can. It would be nice to have more manual control of importing external media and matching the authored headers to save this risk of encoding - only to get a "must be re-encoded" in DVDA. It is difficult for SoFo to handle all variations. 24P NTSC, 24P PAL sizes would be nice too.

DavidMurray wrote on 3/22/2003, 12:04 PM

This is about different software from those in the subject line, but it's tangentally related in terms of matching for DVDA.

I was playing with a copy of Cyberlink's PowerDirector Pro 2.5 that came free with my Pioneer 105 burner. It has some text generating features that I can't figure out how to reproduce in Vegas (primarily rolling text; ie. the letters roll onto the screen). I created an MPEG II in PDPro and imported it into DVDA. I used the default DVD export settings, which were 6000 Kpbs for video compression and 224 Kbps for audio, constant bit rate.

DVDA accepted the file and burned it to finished DVD with no re-compression.