Rendering to .avi vs MPEG2

[Brad Higerd]

That is correct. I am rendering to an .avi and letting MyDVD (free with the HP 200e) do the rest. Of the 1 hour and 30 minutes I wait for each DVD, about 1 hour and 20 minutes is spent "transcoding" the data. True burn times are very fast (as noted in cnet.com's tests.

I went into this without much advise as to how to make quality DVDs, and I am very pleased with the results so far. I bought an HP 200e burner, and every disk I have burned (about 30+) has worked. The only problem (so far) is that my dad's nearly 4 year old DVD home player could not play the disk I sent him (however his Mac could). With that noted, we have been able to play our disks on every other home player we have tried as well as Macs and PCs. I personally believe the DVD+R is worth the extra expense.

I hope this helps.

[Alex Dunn]

Clarification, Sonic does convert it, but it doesn't do it well. I've spent the last 12 hours trying every possible combination of ways to get a good avi to mpeg2 covnersion with Sonic and was not happy with the results.

[Brad Higerd]

Alex,

I'm not sure what problems you are having, but I am very pleased with the results Sonic's MyDVD has produced from an .avi file. The time could have been shorter, but the resulting video and audio has been every bit as good as the original .avi file at three times the size.

As far as setup goes, I have done nothing to reconfigure MyDVD. The software is the latest release. The only changes I have made is in updating the driver software for the HP 200e DVD burner. According to some reviews, poorer quality DVDs from earlier software versions has been corrected. I never tried with the older release software.

How does your original .avi file look, and what are the properties of the file?

I'm learning as I go, but let me know if you think I might be able to help.

Brad

[Brad Higerd]

Alex,

I reread your earlier posts in this thread, and I read that your Vegas to .avi to Sonic DVDs were "perfect". Using any other method we both appear to be having the same results. I am not sure why, but I will do a little research with some of my more tech conscious contacts and let you know what I find. My suspicion is that MPEG2 lacks complete standardization.

Brad

[Rob Lohman]

To all who think they have rendering times. An hour, or an hour
and half is nothing in mpeg2 encoding!! Keep in mind that for
testing you DO NOT have to encode a whole movie. With TMPGEnc
for example you can set the range of frames it will process. You
can tell it to encode from frame 4000 to frame 5800 (for example)
to get 1 minute of footage for NTSC. You can judge settings and
filesizes from this.

I've done encodes that take 5 - 18 hours to complete. But I do
have gorgeous images as well. In my mind this is no problem. I
try out the main settings and then have it render a movie over-
night. It is mostly finished when I wake up again. If I think it didn't
do such a good job afterall (this can happen when you are doing
VBR encoding!) then I change some settings and render again
the next night.

Wat is a few hours on your movie to which you have already
given much much much more hours to make in the first place?

[Brad Higerd]

Rob,

What is VBR encoding?

Brad

[David Hurdon]

Brad

VBR is variable bit rate, as opposed to CBR, which is constant bit rate. VBR encoding "reads" the material in the first pass to determine where high motion scenes will require higher data rates for good results and where relatively inactive scenes can be given lower data rates without degradation. The intent is to create optimum file sizes of good quality. If for example, you use 8 mbps as a CBR everything gets the same treatment and the file size reflect that. If you set minimum 2 mbps max 8, you should get equal quality at smaller size - so more material per disk.

[Alex Dunn]

I clearly have much more to learn, I thought NTSC DVD had to be a CBR of 6000.
Here's what I'm seeing, if anyone can help me fix it let me know:
The picture is sharp in places, but pixelized in others, especially if the subject is wearing a black suit or anything that is one color the image has blurred pixels (I can't sell that).
Also, even having shot in Frame Mode and set at Frame-based, high action shots have streaked scan lines. Like if someone waves at the camera, their fingers are blurred by the scan lines being out of sync. Other than that my MPEG's are great (sound, transitions, titles, etc.). Any ideas?

[David Hurdon]

Alex, I'm curious about why you shoot in frame mode, and is it 30 or 15 fps (ie Canon vs Sony)? My impression is that frame mode is useful for stills and multimedia-targeted material, but not for NTSC which is of course interlaced.
I don't know this for a fact but having seen the results of overly high compression on files created for dial-up progressive download or streaming, I wonder if the constant bit rate you're using isn't too much compression for solid colours which are normally easy for an encoder to do with low bit rate.
Regarding the motion artifacts on a hand waving you might experiment with a higher bit rate to see what happens. Or recreate the action in a short clip shot in interlaced mode versus frame mode and see what that looks like at the same CBR you used before. I hope someone else has other/better suggestions.

[Alex Dunn]

Those are good suggestions. To answer your question, it's Canon 30fps and I did that because it improved upon the results of shooting it interlaced (60 interlaced fps). The Canon 30fps gives it a cool film look. I don't think that's the problem though, more likely I need to adjust my compression as you suggested. Will do.

[Rob Lohman]

Alex,

What MPEG2 encoding software where you using for this specific
example? DVD only has a maximum bitrate (9.8 mbps including
sound and titles etc.). I usually do VBR with a Minimal of 2000,
Average 5000 and max 7000 or something in that area. This way
it allocates all the bits and bytes more efficiently. This should help
with your blacks. But if you put a picture up showing the problems
with the black areas we can better suggest what you might do
to remove those "problems"

[Alex Dunn]

I ran multiple tests over the weekend with VBR at several different maximums and still got shotty results.
I'm using Ulead's encoder which uses a MPEG.Now codec (from MainConcepts). The MSPro6.5 comes with a Ligos codec, but the MPEG.Now is a "patch" which is encouraged on the Ulead site, so it's all I have right now.
Can anyone tell me if I'd have better luck with the DVStorm2 with the StormEncoder hardware encoder?

[Rob Lohman]

I do not know those products myself, so it is hard to judge them.
If you have the time, try the demo from www.tmpgenc.net
and see what kind of results you get from that one on both CBR
and VBR.

Thats the best thing I can think of to see what is causing the
problem.

If you have a way to put it online you can shoot me an e-mail
and I'll have a look at the original source and your encoded mpeg
and let you know!

[Stuart Kupinsky]

Just an FYI, the new Premiere 6.5 edits and exports in mpeg-2 (and if you use the dv500 dvd, there's hardware acceleration to boot).

[Adam Wakely]

These settings have it dead on!! (see bottom of thread)
My customers have never been so happy!
But MOST important....I'm happy!!!
The quality looks pretty much like the original footage!


TMPGE
http://dvd-hq.info/Compression.html