Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy EX1 – Using native GOP with FCP and performance

  • EX1 – Using native GOP with FCP and performance

    Posted by Olly Lawer on January 18, 2009 at 11:18 am

    Hi,

    I have heard it suggested on forums that presently FCP has a preference to convert HDV to prores and that if you want to work with GOP, the files have to be converted to prores in compressor for the workflow?

    How does FCP handle native GOP as a workflow rather then converting to prores? I have a Macbook 2.2GHz Intel Core 2 Duo with 4GB ram and am worried that my system will not be fast enough to work with this material?

    Also, if I work with native GOP and set the render to prores 442, will this have any effect on the performance on FCP (bearing in mind the speed of my machine)?

    Thanks

    Rafael Amador replied 17 years, 3 months ago 4 Members · 8 Replies
  • 8 Replies
  • Rafael Amador

    January 18, 2009 at 12:38 pm

    An Intraframe codec like the Proress will always be more easily managed that a GOP based one, but I don’t think you will have problems with your MBP unless you try to work with few layers. Only in this case I may see recommendable to capture to other codec.
    Rafael

    http://www.nagavideo.com

  • Elijah Lynn

    January 18, 2009 at 12:41 pm

    I am working with Native HDV and rendering with ProPres 422. I am seeing some sluggishness but am unsure as to why. I am running an 8 core with fast enough drives and 10 GB Ram.

    Everything I have read suggests that it is common practice to capture native HDV and render with ProRes. Hopefully my HDV + ProRes work flow gets some Pep!

  • Elijah Lynn

    January 18, 2009 at 12:47 pm

    Oh, btw, there is also a sequence preset in FCP for this exact same setup. It basically makes a HDV 1080 60i sequence but changes the render codec to ProRes (interlaced upper field first).

  • Rafael Amador

    January 18, 2009 at 1:32 pm

    I think that option is interesting for people that work in an XDCAM or HDV environment, so they start in XDCAM/HDV and they end up in the same format.
    You can drop the EX-1 footage in any sequence and will work without problems. So you can set your sequence according with your delivery format and cut the EX-1/HDV footage over there.
    I don’t deny that there are advantages when you capture EX-1/HDV to ProRess through a good video card. The Chroma filtering applied when going from 420/8b to 422/10b is worth the process.
    You can get a close effect in FC with the Nattress filters and a long process for a MBP.
    rafael

    http://www.nagavideo.com

  • Rob Grauert

    January 18, 2009 at 4:35 pm

    What is meant when someone says, “I am working with Native HDV and rendering with ProPres 422.” Do they mean they render to ProRess422 when they’re done with their project?

    Robert J. Grauert, Jr.

  • Rafael Amador

    January 19, 2009 at 2:03 am

    Hi Robert,
    There is an option available when working with HDV or XDCAM that allows edit in an HDV or XDCAM sequence but the renders are done in ProRess. However when you export the sequence you keep the original codec.
    Rafael

    http://www.nagavideo.com

  • Olly Lawer

    January 19, 2009 at 7:58 pm

    Hi,

    Thanks for your replies.

    I am hearing some worrying reports that the FCP doesn’t produce a very good quality output for SD (this is from a Sony Vegas 8 user). Does anyone know of any reports like this?

  • Rafael Amador

    January 22, 2009 at 3:41 pm

    Hi Olly,
    yesterday I’ve been in SONY in Bangkok to get the firmware update for the EX-1.
    A SONY’s guy told me that were still been some problems in AVID but he said nothing about Vegas (their own product).
    I’m working with the EX-1 in FC since last february and I’m 100% happy with the picture quality and the workflow.
    rafael

    http://www.nagavideo.com

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