Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy what’s behind edit natively

  • what’s behind edit natively

    Posted by Bill Willins on April 17, 2011 at 2:45 pm

    Hello . Can you guys help me gain abetter understanding of what exactly is going on within editing software when it is handling files natively , and why should I really care ? In particular I was wondering about AVCHD files in the just announced FCP X , as opposed to the transcode that goes on now. Thank you.

    Shane Ross replied 15 years ago 3 Members · 2 Replies
  • 2 Replies
  • Tom Wolsky

    April 17, 2011 at 3:38 pm

    Editing natively means your processors have to do all the work while you edit. The benefit: less work up front to import the media. Aside from that it’s mainly marketing. You’re still going to have to recompress to something when you output. The downside: less capability available to process other things like effects and multiple tracks of video and audio while you work. At some point native playback is a hinderance because smooth playback is lost and choosing edit points becomes unmanageable.

    All the best,

    Tom

    Class on Demand DVDs “Complete Training for FCP7,” “Basic Training for FCS” and “Final Cut Express Made Easy”
    Author: “Final Cut Pro 5 Editing Essentials” and “Final Cut Express 4 Editing Workshop”

  • Shane Ross

    April 17, 2011 at 5:25 pm

    BTW, there was no mention of editing AVCHD natively in FCP X. They stated that the “transcoding of AVCHD will happen in the background.” Meaning, you will still have to transcode AVCHD. The only native format they mentioned was H.264 from DSLRs.

    Shane

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

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