Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy DVCPro HD 720p24 Firewire capture – dropping frames

  • DVCPro HD 720p24 Firewire capture – dropping frames

    Posted by Andrea Klipp on September 4, 2008 at 9:49 pm

    We are working with a project that was shot on Varicam at 720p 24. We are using a AJ-HD1400 to capture. Our Easy Set up is DVCPRO HD 720p 24. When we have captured via firewire the timecode was effected. When we cursored through the clip frame by frame the timecode would jump 2 or 3 frames, and create timecodes like 10.24.10.47.

    We are running FCP 6.0.2 on an G5 tower. I have tossed the preferences – tried the capture again, and still the same result. Has anyone else seen this behavior before, and know a work around?

    Andrea Klipp replied 17 years, 12 months ago 3 Members · 6 Replies
  • 6 Replies
  • Shane Ross

    September 4, 2008 at 9:54 pm

    Nothing to worry about…this is normal. DVCPRO HD tape records 60 frames per second. IF you have the camera set to 720p24, then it flags the footage as 24 frames…so when FCP captures it, the redundant frames are not captured and you are left with 24 fps footage running at 23.98.

    Shane

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

  • Jeremy Garchow

    September 4, 2008 at 10:09 pm

    What Shane says, and if you need all of the frames, you can capture at the 59.94 setting and capture continuous timecode. BUt like SHane says, this is normal when capturing 24p and removing the redundant frames. What’s your output and why are you concerned?

    Jeremy

  • Andrea Klipp

    September 4, 2008 at 11:02 pm

    Thanks for your responses. The other thing that is happening is the material is out of sync. I also tried capturing with the Kona 3 – DVCPRo HD Varicam 720p24 – and it captured it properly, and the TCs didn’t jump 2 and 3 frames. As well I didn’t have TCs of 10.20.15.47 – once the frame hit 29 – the next frame was 00. It would drop the odd frame, but not 2 or 3 – for example when I loaded with firewire it would go from 10.20.15.10 to 10.20.15.13 in the next frame. The Kona capture went from 10.20.15.10 to 10.20.15.11 to 10.20.15.12.

    I do have access to the Kona 3 – and can continue loading with it – but there are 15 tapes that I load via firewire that I think I may have to reload – so that the material is in sync.

  • Shane Ross

    September 4, 2008 at 11:14 pm

    Firewire capture will capture with the audio out of sync…correct. Audio will lead video by about 2 to 8 frames. Yes, this is annoying. So I too use the Kona 3 to capture DVCPRO HD vai HD SDI. And yes, then the TC only goes up to 29…and again, the redundant frames are removed. Same thing, just different TC numbers. Dunno why it only goes to 29 when you use the Kona…wondered about that.

    If you don’t want to reload the firewire captures, all you need to do is figure out how far off-sync you are, and when you cut the footage into the timeline, shift the audio that many frames.

    Shane

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

  • Jeremy Garchow

    September 4, 2008 at 11:17 pm

    How far out of sync?

    Okay. The Kona card uses 30 frame based tc (which is what is recorded to tape) essentially each tc frame number has two frames to it as the Varicam records 60 frames (but it uses 30 frame based tc, ugh). SO the Kona sets its capture frame base to 30. FCP uses 60. You can change the tc rate in the browser.

    Again, what is your output and why are you concerned about this? It will help us help you.

    Jeremy

  • Andrea Klipp

    September 4, 2008 at 11:43 pm

    Thanks! I think I’ll stick with the Kona 3 -and to be safe reload. There are multiple editors working on the project – so it’s best to have it all be the same – as slipping and sliding may throw some of them off. 🙂

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