Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Neo-HD vs. Neo-HDV for HD broadcast

  • Neo-HD vs. Neo-HDV for HD broadcast

    Posted by Dale Spetz on July 3, 2007 at 12:34 am

    With the goal of creating the best quality 1920×1080 footage for eventual HD broadcast, from HDV source footage, is Neo-HD necessarily the better than Neo-HDV?

    Or, can I obtain the same end results by capturing the HDV footage with Neo-HDV? Editing the now uncompressed 1440×1080 episodes in Vegas7. Then, rendering the final output project via the Cineform 1920 HD v2.5 codec (built into Vegas7).

    Will the final HD product be the same as if I had edited the project with the Neo-HD 1920×1080 uncompressed files?

    Both courses bring me to an output of 1920×1080, but does one course inherently create superior results? Is it advisable to spend the extra for the Neo-HD, over the Neo-HDV?

    I am trying to better understand codecs. Thanks!

    10 replied 18 years, 10 months ago 3 Members · 2 Replies
  • 2 Replies
  • Seth Estrada

    July 6, 2007 at 1:08 am

    First off you need to know that Vegas 7 does not support 10-bit media, only 8-bit, so the extra money you’re spending “ain’t worth 2-bits” Though capturing ‘full raster HD’ instead of 1440×1080 does add more information to your media… but not enough to justify the extra $350 unless you’re also getting the extra color information (the 10-bit color depth) That’s my ‘2-bits’
    -seth

    p.s. Vegas 8 should have support for 10-bit uncompressed media, but that’s not for several months still.

    “Oh be wise, what can I say more?”

  • 10 Create COW Profile Image

    10

    July 7, 2007 at 5:01 pm

    Well, except I need the 1920 x 1080 output size. I think that the only Vegas output option for this is the “HD 1080 60i YUV” uncompressed setting–which creates a huge file. Neo-HDV, I think, limits me to 1440pix.

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