Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Yet another noob question

  • Yet another noob question

    Posted by Heather Walters on December 19, 2009 at 8:04 am

    A quick thanks to all who have helped me on this forum!
    I have a project that will be shown on broadcast TV this week and the station’s production dept wants my commercial in full d1, mpeg2.

    I initially rendered the raw footage as a 4.8Mbs HD 24p wmv(this was for another project), then used that footage for this project, where I added some graphics and moving text, then rendered at 720p intermediate 24fps avi, with the TechSmith Screen Capture Codec. I took this avi and added some 3d motion and then rendered it for broadcast. I chose mpeg2 DVD NTSC 720×480 29.97 fps with 16:9 aspect ratio and I checked the box for no letterboxing (per the station’s requirements). Words cannot describe how shitty the output was. It’s understandably fuzzy at such a low resolution, but it’s unbelievably pixelated, full of artifacts, and it’s got nice, jaggedy mousetoothing (is that merely because I’m on the computer and this will resolve on a TV?).
    Right now I’m assuming that I need to take my original video footage and render that out as an avi instead of a wmv, then just use that, along with my graphics and 3d motion to render the broadcast mpeg2. Is this correct?
    As for the mousetoothing, can I just render this as 24fps or do I need to telecine? And will I still see mousetoothing on my computer but not on a TV?

    Any help would be greatly appreciated as I need to have this puppy ready for upload sometime Monday.

    Heather Walters replied 16 years, 5 months ago 2 Members · 4 Replies
  • 4 Replies
  • John Rofrano

    December 19, 2009 at 5:42 pm

    > <>Right now I’m assuming that I need to take my original video footage and render that out as an avi instead of a wmv, then just use that, along with my graphics and 3d motion to render the broadcast mpeg2. Is this correct?

    You assume correctly. WMV is a highly compressed delivery format that should be avoid as source at all costs. If you want quality, you should always start with your source footage. No need to render as AVI, just render as MPEG2 directly from Vegas.

    > As for the mousetoothing, can I just render this as 24fps or do I need to telecine? And will I still see mousetoothing on my computer but not on a TV?

    This is called “interlacing” and it will not be seen on a TV. Never judge TV footage on a PC as PC’s are not interlaced devices.

    ~jr

    http://www.johnrofrano.com
    http://www.vasst.com

  • Heather Walters

    December 20, 2009 at 2:04 am

    Ok, thanks! So I should change it to 29.97 fps when I render then? And one more question: My boss wants me to do the project settings in the original size of the video (1920×1080 24p). Should I keep the high project settings or set the project to match my final output (720×480)?

  • John Rofrano

    December 20, 2009 at 2:43 pm

    > Ok, thanks! So I should change it to 29.97 fps when I render then?

    NTSC TV is 29.97. It doesn’t matter what you shot the footage in, you need to deliver it in 29.97 for broadcast. Your final render settings should be 29.97 regardless of your project settings.

    > And one more question: My boss wants me to do the project settings in the original size of the video (1920×1080 24p). Should I keep the high project settings or set the project to match my final output (720×480)?

    You should keep the high (HD) project settings so that anything you add like generated media will also be HD. This also gives you the option to create an HD version later should you need it. I would always work in HD and render to whatever delivery formats that you need but keep the project HD.

    ~jr

    http://www.johnrofrano.com
    http://www.vasst.com

  • Heather Walters

    December 20, 2009 at 8:09 pm

    Right. Thank you!

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