Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy encoding in DVCproHD

  • encoding in DVCproHD

    Posted by Jason Dutcher on November 15, 2006 at 9:54 pm

    Ok, I went witht he easy set up settings for DVCpro HD and now I am a bit confused looking at the material. Please assist me in understanding.

    I have HDACM footage recorded @ 10bit 4.2.2 encoded thru a Kona 3
    When I look at the footage details in the FCP bin, it is showing me 1280×1080 frame size. When I look at the original digitized QT file it is also showing 1280×1080 but then plays at a normal size of 1888×1062. Where does that come from? Also, I think the default for the easy setup DVVpco HD was 8bit? Can I do 10 bit DVCpro? In the capture preset area, what should my settings be? Why is the video at 1280 and not 1920?
    One more thing please – If I do edit in DVCproHD and then export out to HDcam tape will I need to convert the timeline or anything before I print to tape? Thanks!

    Izoneguy replied 19 years, 6 months ago 3 Members · 2 Replies
  • 2 Replies
  • Kent Kajino

    November 15, 2006 at 11:06 pm

    Seems like DVCPROHD is limited to 8-bit, and its native resolution is 1280×1080. Pixel aspect ratio of 1.5 is what makes the codec play at 1920. If you want to keep your uncompressed files, maybe you can just recompress the files into DVCPROHD, and cut in DVCPROHD, then reconnect back to the uncompressed media before outputing to HDCAM tape. DVCPROHD is 1/10 of the size of uncomressed, yet I couldn’t distinguish between them when they showed me a comparison shot at the post house. Only then, I knew that DVCPROHD was good enough for me.

  • Izoneguy

    November 16, 2006 at 12:24 am

    On most video shots you cannot see much difference….
    You will see some banding on smooth gradients,
    graphics for example….otherwise DVCPRO HD
    delivers for most projects.

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