Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro jaggie blues

  • jaggie blues

    Posted by Mary Waitrovich on May 29, 2008 at 5:03 pm

    I was happy to see this thread below on using HDV footage:
    https://forums.creativecow.net/thread/24/879993
    but I am still having a problem.

    I’ve tried setting things up both ways when using HDV footage that is headed for a DVD:
    1) set project as NTSC widescreen
    2) set project as HDV 1080i (how it was shot)

    either way, I render to mpeg2 using the DVDA widescreen video stream template and the footage, which looks beautiful in the Vegas preview window, gets all jaggy on the DVD. (It’s not being rendered twice).
    I can’t see any difference in the result between the two approaches.

    What am I missing here?
    Thanks,
    Mary Waitrovich
    UW-Madison

    Mike Kujbida replied 18 years, 2 months ago 2 Members · 7 Replies
  • 7 Replies
  • Mike Kujbida

    May 29, 2008 at 6:04 pm

    Mary, what bitrate, etc. are you using?

    Did you set your Project Properties to match the source material?

    The easiest way to do this is to open the Properties window (File – Properties) and click the “Match Media Settings” icon (looks like a folder).
    Browse to a folder where you have the source footage for this project, click any one of the AVI files and then click “Open”.
    This will ensure that your Project Properties are correctly set.

  • Mary Waitrovich

    May 29, 2008 at 6:21 pm

    Mike,
    thanks for your response.
    I am using the DVD Architect NTSC Widescreen video stream template under mpeg2 in the render. The bitrate on the template is “variable bit rate” with 9,500,00 as the maximum.

    I thought I had the project properties set to match the sources material, or most of it anyway, which is HDV 1080i. I also followed your directions above, but my files are m2t, not avi, but I assume that also works. I don’t think that resulted in changing the settings from what I had before.

    So, given those answers, any ideas?

    mary

  • Mike Kujbida

    May 29, 2008 at 6:36 pm

    9,500,00 is WAY too high.
    Drop that down to 8,000,000 (recommended maximum by lots of folks here & elsewhere) and try it again.
    BTW, the maximum bitrate for a DVD is 9,800,000 so if you’re rendering at 9,500,000, you have very little room left for your audio.

  • Mary Waitrovich

    May 29, 2008 at 7:02 pm

    Doesn’t it seem odd that the template default is too high? I will certainly try your suggestion.

    I was also wondering if interlacing has anything to do with it. I did turn on “reduce interlace flicker” on the clips, but it didn’t seem to do much. I was wondering if it would be better to do a progressive render, if I’m sure the DVD player supports progressive scan?

    thanks,
    Mary

  • Mike Kujbida

    May 29, 2008 at 7:13 pm

    “Doesn’t it seem odd that the template default is too high?”

    It sure does.
    I don’t ever remember seeing a default bitrate that high.
    I just went through the defaults on my work machine (Vegas 7.0) and didn’t see anything that high for an SD render option.

    “I was wondering if it would be better to do a progressive render”

    Why not? You have nothng to lose.
    Try rendering a minute or two of a problem section, burn it to an RW and see what it looks like.
    The DVD player “should” change it to interlaced if it needs to.

  • Mary Waitrovich

    May 29, 2008 at 8:12 pm

    All the NTSC mpg2 templates in Vegas 8 have maximum bitrates of 9,500,000.

    My test render with the lowered bitrate looks much better.
    This has been a big help to me.
    Thanks much.
    Mary

  • Mike Kujbida

    May 29, 2008 at 9:20 pm

    [Mary Waitrovich] “All the NTSC mpg2 templates in Vegas 8 have maximum bitrates of 9,500,000.”

    Wow!! What was Sony thinking?
    I always use custom settings so I never even look at the defaults.

    “My test render with the lowered bitrate looks much better.”

    Glad to hear that – and to have been of some help 🙂

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy