Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity › Forums › Apple Final Cut Pro Legacy › Capturing 23.98 fps video

  • Capturing 23.98 fps video

    Posted by Pvideoman on July 26, 2007 at 10:05 pm

    Hi Everyone,

    I recently shot a movie on the Cannon XL2 on the 24p setting. I captured my video in Final Cut using the default DV-NTSC 48 kHz and tried to edit on my sequence which was set at DV-NTSC 48 kHz 23.98fps. Everytime I drag a clip to the timeline, I have to render it.

    So I tried editing my capture setting to DV-NTSC 48 kHz 23.98fps, and I no longer had to render. However, when I researched further online, I saw several instances of people saying that it is risky to capture DV at 23.98. The gist I got was that even though the tape is recorded at 23.98, all mini-dv still transfers at 29.97, and if you capture at 23.98 it will start deleting random frames causing it to be unsynched and jumpy.

    My Question: Does anyone know if it is actually risky to capture in Final Cut at 23.98? And if so, does anyone know the effect of capturing footage shot on the 24p XL2 setting at 29.97 and editing on a 29.97 sequence? Does it defeat the entire purpose of shooting on that setting?

    Shane Ross replied 19 years, 1 month ago 4 Members · 7 Replies
  • 7 Replies
  • Sean Oneil

    July 27, 2007 at 1:57 pm

    [pvideoman] “However, when I researched further online, I saw several instances of people saying that it is risky to capture DV at 23.98”

    Applying Advanced Pulldown Removal after the fact can be dangerous. Perhaps that’s what you read about. Doing it during capture should be fine, although perhaps there are issues w/ certain cameras. Just try it out and you’ll know right away if there’s a problem.

    Shooting 24p and editing 60i is not a good idea. It will destroy the pulldown cadence which will cause the final output to have motion artifacts on computer monitors and progressive-scan consumer televisions. Edit 23.98 if you can.

    Sean

  • Pvideoman

    July 30, 2007 at 5:57 pm

    So I discovered that it was shot in normal 24p 2:3. I’ve done some tests capturing in 29.97 and editing in 29.97 then going to DVD Studio Pro and simulating, and the image is jerky with a lot of lines.

    Since it is in 2:3, I should ignore DV-NTSC 48 kHz Advanced (2:3:3:2) Pulldown, right? I believe that to be true, but is there anything wrong with going into my normal DV-NTSC 48kHz capture setting, and adjusting the 29.97 there to 23.98? Or 24?

    Since 29.97 across the board is giving me bad results, and capturing at normal 29.97 and editing at 23.98 would require mountains of render time, I’m not sure what the right course of action should be.

  • Pvideoman

    July 31, 2007 at 4:04 pm

    Is it Possible to make a DVD in DVD Studio Pro that has a 24p timeline and a 30p timeline so I could have one DVD that can have a link to TV viewing and computer viewing?

  • Alphaabetsoup

    August 8, 2007 at 8:01 pm

    I have a similar question: I’m working off 35mm telecined to DVCAM tapes, and was told they were laid out at 23.98 / 4:3 with a 1.78 letterbox – I have set my sequence at 23.98, but so far no amount of tinkering with the capture settings can import the footage so it does not need to be rendered in the timeline. Is the problem with the capture rate or the aspect ratio? help!

    thanks

  • Shane Ross

    August 8, 2007 at 8:15 pm

    No….you need to REVERSE TELECINE the footage. The film was transferred to tapes that run at 29.97fps. If you want to edit at 23.98 you’ll first have to reverse telecine the clips with Cinema Tools, or within FCP itself.

  • Alphaabetsoup

    August 8, 2007 at 8:24 pm

    thank you thank you – so, does that mean i capture at 29.97 first in FCP and then run a batch reverse telecine in cinema tools?

  • Shane Ross

    August 8, 2007 at 8:32 pm

    Yes. And do your tapes have Visible TC on them? That way you can verify that your TC is correct.

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