Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Determining Sequence Settings for Best Performance

  • Determining Sequence Settings for Best Performance

    Posted by Bill Vincent on March 9, 2010 at 4:28 pm

    I know there are other threads related to this, but I couldn’t find a specific answer to this, so my apologies if this has been addressed before.

    I am using ProRes422 files created from 7D (H264) footage and HDV footage (Canon A1s). The 7D footage is 1920×1080, and the HDV footage is 1440×1080. For the purposes of best editing performance and fastest renders, should my sequence settings be set to match the 1920 footage or the 1440 footage? When you mix them on the timeline either one or the other is not in it’s full rendered state. Maybe I should just match the sequence to whatever format I have the most footage in?

    OR, should I not worry about which format is most appropriate for fast editing/rendering and set the sequence settings based on my final output size requirements? (I don’t really have a “requirement” for size output, although 1920×1080 seems more common than 1440×1080.

    Thanks in advance for any/all suggestions…

    Bill

    Rafael Amador replied 16 years, 2 months ago 3 Members · 2 Replies
  • 2 Replies
  • Nicole Haddock

    March 9, 2010 at 8:02 pm

    Well, how’s this for a non-answer: It depends.
    How much footage is type A versus type B?
    What machine/drives are you editing on?
    Where is it going to end up?

    Generally, I let the answers of 1 and 3 guide the sequence settings the most, and if I’m cutting on a laptop, that will way in heavily on #2 as well. So start from the end and work your way backwards.

  • Rafael Amador

    March 10, 2010 at 3:14 pm

    Unless you have to deliver in 1440 (HDV, DVCProHD), go to 1920 that is the standard for HD.
    Rafael

    http://www.nagavideo.com

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