Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy 23.98 720p with 29.97 NTSC mastering to 720p 59.94

  • 23.98 720p with 29.97 NTSC mastering to 720p 59.94

    Posted by Jay Thomas on January 30, 2008 at 9:30 pm

    I’m cutting a pilot where the majority of the footage was acquired 23.98 720p but we’ll also be incorporating archival 29.97 NTSC sd footage and graphics that will come from a gfx house. The project will need to be mastered at 59.94 720p. I’ve captured all the interview footage (20+ hrs.) at 23.98 and have started the edit in a 23.98 time line. Am I approaching this the right way? Do the GFX need to be rendered 23.98 as well, and will they and the 29.97 footage get strange when automatically removing frames in timeline but then adding back upon output? I have a BMD decklink extreme HD card as well as a Panny AJ-HD1400 deck. Thanx in advance.

    Sean Oneil replied 18 years, 3 months ago 4 Members · 4 Replies
  • 4 Replies
  • Del Chapple

    January 30, 2008 at 10:39 pm

    i’d just Deinterlace the NTSC footage before input into the FCP project(jes deinterlacer works good and its freeware).. who knows which frames final cut will decide to use. this way you can ensure fcp not to pick the frames with a pull down. on the JES Deinterlacer note, JES will remove a pull down with a broken cadence and hopefully bring the NTSC footage back to 23.98 .. That way you can edit in 23.98..
    yes Graphics in 23.98

    del

    you cant hear my inner voice scream… can you..?

  • Aaron Neitz

    January 30, 2008 at 10:41 pm

    The SD footage – is it filmed? that is 24fps with pulldown? or is it 60field video-style footage?

    The thing to do is pulldown removal on the SD footage so it’s 24fps, plop it in the timeline and it’ll look fine.

    graphics at 23.98.

    I don’t know how the BM card does it, but Kona outputs 59.94 from a 23.98 timeline very cleanly.

  • Del Chapple

    January 30, 2008 at 10:48 pm

    “The SD footage – is it filmed? that is 24fps with pulldown? or is it 60field video-style footage?”

    its always both.. 🙂

    del

    you cant hear my inner voice scream… can you..?

  • Sean Oneil

    January 31, 2008 at 2:29 am

    [Jay Thomas] “I’m cutting a pilot where the majority of the footage was acquired 23.98 720p but we’ll also be incorporating archival 29.97 NTSC sd footage and graphics that will come from a gfx house. The project will need to be mastered at 59.94 720p. I’ve captured all the interview footage (20+ hrs.) at 23.98 and have started the edit in a 23.98 time line. Am I approaching this the right way? Do the GFX need to be rendered 23.98 as well, and will they and the 29.97 footage get strange when automatically removing frames in timeline but then adding back upon output? I have a BMD decklink extreme HD card as well as a Panny AJ-HD1400 deck. Thanx in advance”

    Yes you are approaching the right way. Have the graphics rendered at 23.98fps, and edit and master at 23.98. Even though you’re mastering to a 60fps tape format, you don’t want mixed framerates in your program if you can avoid it. It can cause all kinds of problems down the road. You should treat this as if it were a 23.98 tape format you are mastering to. For example, if a DVD or Blu-Ray is made from this master, the authoring house will capture and encode it at 23.98 (unless they’re hacks). But they won’t be able to do this if you have broken cadence or multiple framerates in your program.

    Arron asked if the NTSC footage was originally shot on film or not. You need to know that before you convert it to 23.98p. If it’s film then you do a reverse telecine (using JES) and you’re done. If it’s 30fps video you convert it to 29.97p first (also using JES), then to 23.98p (using Nattress Standards converter, Compressor, or just rendering it in a 23.98 FCP sequence – results will vary among these). It will have a different look, but it should look fine.

    Sean

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