Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy FCP Codec Question

  • FCP Codec Question

    Posted by Ken Hyde on June 15, 2011 at 10:36 pm

    Hi everybody…editing in FCP, I exported a file for a client using the “Export to Quicktime” option. On the settings, I used “Current Settings.” The client now needs to know which Codec I used. How do I determine what my current settings were and thus the Codec? Sorry for the newbie question. Any help would be greatly appreciated.

    Chris Borjis replied 14 years, 11 months ago 12 Members · 24 Replies
  • 24 Replies
  • Shane Ross

    June 15, 2011 at 10:55 pm

    IN the project, go to the SEQUENCE menu and choose SETTINGS.

    Shane

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

  • Brendan Maghran

    June 15, 2011 at 10:59 pm

    Or, just open up the exported quicktime file and hit Command+i. It will tell you the codec in the little window that pops up.

  • Michael Gissing

    June 15, 2011 at 11:37 pm

    Hate to be rude Ken but how can you be editing a sequence without already knowing what your codec is?

    Basic workflow practice means you really must know what your source and sequences codecs are. All editing systems work best when the right match is made between camera codecs and sequence settings

  • Chris Borjis

    June 16, 2011 at 12:09 am

    oddly enough I’ve seen a few fcp users, using mismatched codec to sequence settings.

    they make edits then re-render the timeline every time they have to for smooth playback….they don’t realize thats not the right way to do it.

  • David Roth weiss

    June 16, 2011 at 12:13 am

    [Michael Gissing] “Hate to be rude Ken but how can you be editing a sequence without already knowing what your codec is? “

    There was a guy yesterday working on a feature film entirely edited at the wrong frame rate by a director who:

    a) claimed to have used FCP since ver. 1

    b) said he never did anything but, “just start editing.”

    David Roth Weiss
    Director/Editor/Colorist
    David Weiss Productions, Inc.
    Los Angeles
    https://www.drwfilms.com

    POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

    Creative COW contributing editor and a forum host of the Business & Marketing and Apple Final Cut Pro forums.

  • Michael Gissing

    June 16, 2011 at 12:24 am

    [David Roth Weiss] “b) said he never did anything but, “just start editing.””

    Scary.

  • Bret Williams

    June 16, 2011 at 2:34 am

    At least this guy admitted he’s a newbie. But also admits he has clients. Scarier.

  • Matthew Bradshaw

    June 16, 2011 at 12:42 pm

    How do you guys know he isn’t a great editor who just happens not to be as into the geeky side of things as you? I have worked with many talented “preditors” who would really rather not spend their time nerding about with codecs when they can get somebody else cheaper (me) to sort it out for them.
    Matt.

  • Randy Davis

    June 16, 2011 at 12:55 pm

    I have to say that this forum is great when information is given freely and without attitude. We are all at different levels of expertise and really appreciate connecting with those whose knowledge exceeds ours and enjoy supporting those who are newer to the wacky biz of editing as well. Thanks everyone! -RD

  • Alexander Kallas

    June 16, 2011 at 1:15 pm

    [Michael Gissing] “Hate to be rude Ken but how can you be editing a sequence without already knowing what your codec is?

    Basic workflow practice means you really must know what your source and sequences codecs are. All editing systems work best when the right match is made between camera codecs and sequence settings”

    ……..but FCP will ask to automatically set the matching codecs for the imported media without revealing them, and this is probably what Ken did.
    As Shane pointed out Ken just failed to look back at what FCP had set.

    Cheers
    Alexander

Page 1 of 3

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