Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro best workflow to BD in Vegas Pro12

  • best workflow to BD in Vegas Pro12

    Posted by Wouter Slagter on November 1, 2012 at 3:49 am

    I try to obtain the most optimal workflow in creating a BD with Vegas Pro 12 and DVD Architect Pro 5.2 for showing on a HD TV.

    Footage is with Sony A77 DSLR, File Format: AVCHD 60i/60p, Recording Setting: 24p 24M (FX)
    In Vegas, my template in Project Properties: HD-1080-24p(1920×1080-23,976 fps)

    After editing, with Render AS, many choices come up.
    1) Sony MXF – HD EX 1920×1080-24p seems to be the 1st choice. I don’t have any experience with MXF, is this really a preferred rendering?
    2) Sony AVC/MVC – BluRay 1920×1080-24p, 16 Mbps. Since my footage is AVCHD, I tend to think this is better, however there is the limitation of max. 16 Mbps.
    3) Main Concept MPEG-2 – BluRay 1920×1080-24p, 25 Mbps Video Stream
    4) Main Concept MPEG-2 – DVD Architect 24p NTSC Widescreen Video Stream. Since I use DVD Architect, this might be an option?
    5) Main Concept AVC/AAC – BluRay 1920×1080-24p 25 Mbps Video Stream

    I could do test rendering with all these settings, but maybe somebody already did and/or knows what the preferred options are.
    Any help greatly appreciated!
    Wouter Slagter

    Jim Greene replied 13 years, 9 months ago 2 Members · 3 Replies
  • 3 Replies
  • Jim Greene

    November 1, 2012 at 7:37 pm

    I have used option 3 & 5, mostly 3. Option 1 will cause DVDA to re-render as this is not BDR, and option 4 is not HD, it is for 720×480 standard definition.

    -Jim.

  • Wouter Slagter

    November 1, 2012 at 11:27 pm

    Thanks Jim,
    Any comments on 2) or 5) ?

    Wouter

  • Jim Greene

    November 4, 2012 at 3:15 pm

    I did comment that I use #5, it’s not really different than #3, just a different codec. I thought you answered your own question with #2 as it is only 16Mbps, but it’s fine also, but why not just use #5 with the higher bitrate.

    -Jim.

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