Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy 29.97 edit to 23.98 timeline in FCP

  • Brent Bye

    April 4, 2008 at 5:33 pm

    Luckily, everything rendered out of After Effects is at an actual frame rate of 23.976 (comps were built as such as well)

    QuickTime however does not display the frame rate of the clip as such. Opening the AE project reveals 23.976 comps and the renders are labeled as 23.976 when imported into AE. Opening the same clips in FCP or Quicktime, the frame rate is displayed as 23.98

  • Jeremy Garchow

    April 4, 2008 at 5:52 pm

    It’s 2008. FCP4 was released circa April 2003? So that’s 5 years. Not to get in an argument or anything, it’s just not a new feature. The DVX100 came out in 2002 I believe.

    Jeremy

  • Brent Bye

    April 4, 2008 at 6:02 pm

    Hello Dave,
    Thank you for the detailed post. My bad for using incorrect terms such as “conform” when I perhaps should have said “convert” or other terminology.

    I do understand the 3:2 pulldown process and as stated in the third paragraph of the first thread here, I have run all of my original footage through Cinema Tools and removed the pulldown effectively giving me all 23.98 footage ready for a 23.98 timeline.

    Problem is, all of the edits were done years ago. I have a dozen projects all of which were edited back in the days before “Advanced Pulldown Removal” injest options of the modern FCP versions. I would really prefer to not have to completely re-edit nearly four hours worth of projects.

    My biggest issue is trying to figure out the most reliable method for converting the 29.97 edit into a 23.98 edit so I can simply reconnect to my pulldown footage.

    Thanks for all the suggestions so far…

  • Brent Bye

    April 4, 2008 at 6:08 pm

    Right you are Jeremy,

    Those are the dates, and that is the exact time when all this work was done.

    The day the DVX-100 came out, I got it and began to shoot and edit. Prior to all of the Final Cut Pro integration and ability to import using the “Advance Pulldown Removal”.

    Yes, it would have been super awesome back then to have been able to injest and edit at a native progressive 23.98 timeline…it just wasn’t possible until they updated FCP.

    In the meantime, I was a busy little bee up until the point when I could import 24Pa footage into FCP.

    Now I’m just trying to figure out how to make those old archive edits and footage all nice and progressive in a 23.98 timeline.

    All these years later it seems like some delayed karma getting me back for being an eager early adopter of a camera in 2002…

  • Matthew Nelson

    April 4, 2008 at 6:30 pm

    Here’s a thought.

    If exporting a reference QT from your 29.97 sequences will pass through the source clips cadence metadata then CT can read this data and reverse the advanced 3:2 while adjusting for the cadence breaks. You will know it worked, if CT gives you a simple reverse telecine interface see pg 212 in the CT manual. Make sure Check for cadence discontinuity is checked.

    If you get the detailed interface, see pg 130 in the CT manual, then you are out of luck.

    Matt

  • Brent Bye

    April 4, 2008 at 6:39 pm

    Sounds like an interesting experiment.
    Do you think QT will have a problem detecting cadence in the reference movie because of the switch in cadence during editing? Also, many of the timelines are a mix of about 95% 24Pa footage and some 24P and even 60i footage. I wonder what that would do to cadence detection?

  • Matthew Nelson

    April 4, 2008 at 7:14 pm

    If the cadence metadata is passed through CT will use that to reverse making adjustments to cadence as dictated by the metadata (the Check Cadence Discontinuity setting). As for what will happen to the 60i footage only testing will tell. Again this whole thing is a big if. Let us know if it works.

    Matt

Page 2 of 2

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