Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy XDCAM Compressing – Conforming MPEG-2 Video LONG RENDER?

  • XDCAM Compressing – Conforming MPEG-2 Video LONG RENDER?

    Posted by Christopher Targia on June 25, 2010 at 2:38 pm

    So I received XDCAM HD422 1080p30 (50 MB/s) Footage, and I need to green screen it. After compositing the rendering is taking MUCH much longer then footage I composite in DVCProHD Compressing. It doesn’t even say writing video while I am rendering. It says “Conforming MPEG-2 Video” What does this mean and why is the rendering time literally taking 2-3x as long as similar footage in DVCProHD take?

    MacPro Octo Core Intel Xenon 2.8Ghz 6GB 800MHz DDR2 Ram
    FCP 7.0

    Jason Moss replied 15 years, 10 months ago 5 Members · 9 Replies
  • 9 Replies
  • Mark Maness

    June 25, 2010 at 2:46 pm

    That’s simple…. And yes, it will take longer to render than DVCProHD.

    XDCAM HD is a form of Long-GOP video, whereas, DVCProHD is I-Frame video. Long-GOP is the method that is traditionally used in HDV and XDCAM HD has borrowed this for its primary method of video. Thus, in order to be seen, the video has to conform itself to Long-GOP. Its very scientific and lengthy to explain. Do a search on the web for Long-GOP and you’ll see for yourself.

    Usually, the conforming only comes when you have to output your timeline. Can you tell me what is your sequence settings that you are using?

    _______________________________

    Wayne Carey
    Schazam Productions
    https://web.mac.com/schazamproductions
    schazamproductions@mac.com

  • Rafael Amador

    June 25, 2010 at 3:46 pm

    ..so change your sequence codec to Prores.
    rafael

    http://www.nagavideo.com

  • Christopher Targia

    June 25, 2010 at 4:22 pm

    I imported the footage into a sequence and just auto adjusted it to the footage, so the sequence settings are :

    Frame Size 1920 x 1080 Aspect HDTV 1080i Square

    Compressor XDCAM HD422 1080p30(50mb/s)

    MacPro Octo Core Intel Xenon 2.8Ghz 6GB 800MHz DDR2 Ram
    FCP 7.0

  • Christopher Targia

    June 25, 2010 at 4:24 pm

    I changed the settings in the sequence to ProRes 422 and hit render, the estimated time was the same, if not longer.

    MacPro Octo Core Intel Xenon 2.8Ghz 6GB 800MHz DDR2 Ram
    FCP 7.0

  • Rafael Amador

    June 25, 2010 at 4:26 pm

    Great.
    So now change the sequence codec to Prores and start editing. Everything will go faster.
    rafael

    http://www.nagavideo.com

  • Shane Ross

    June 25, 2010 at 4:45 pm

    OR…go to the USER PREFS, click on the RENDER CONTROL tab and change the CODEC to PRORES.

    Shane

    GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
    Read my blog, Little Frog in High Def

  • Christopher Targia

    June 25, 2010 at 5:18 pm

    I did both those things, Changes sequence to ProRes and Render Control to ProRes, I am still getting 2 hours to render a 15 min clip with Primate RT Key and some minor color correction. I know primate takes longer then Chroma Keyer but never this long.

    MacPro Octo Core Intel Xenon 2.8Ghz 6GB 800MHz DDR2 Ram
    FCP 7.0

  • Rafael Amador

    June 26, 2010 at 5:41 am

    You should start by updating your FC. 7.0, no good.
    Then a bit of maintenance (permissions, caches, directories).
    rafael

    http://www.nagavideo.com

  • Jason Moss

    June 28, 2010 at 9:05 pm

    Christopher,

    We have been editing large amounts of XDCAM50 at our facility for the past 2 years, and the render times are exactly what you are getting for keying green screen with the Primatte Keyer. It is due to the XDCAM codec being long GOP instead of i-Frame with DVCProHD. In our workflow, we went from DVCProHD to XDCAM50, and were shocked at the difference in overall render times (roughly 4 to 5x slower). Best of luck with your project; sounds like your setup is correct.

    Jason

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