Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Capture Problems, yet again.

  • Capture Problems, yet again.

    Posted by Ashley James on July 18, 2006 at 8:27 pm

    Hi guys. I’m doing a music special with five cameras, all synced with the same TC. Some of the backstage was shot with a DVX 100B. Over the weekend I experienced a huge problem when in the Log and Capture function. I tried to bring in anamorphic XDCAM via SDI through my Kona LS but everything that was captured was squeezed into 4×3 frame. That issue was resolved by upgrading from 5.0 to 5.1 (I then upgraded to 5.1.1. Thank you Walter and Jeremy and Rob at Advanced Systems Group in Oakland, CA

    Now when I try to capture, both from my XDCAM deck via SDI and with my Pana DVX 100B via firewire, I get a prompt that there is a timecode break and FCP stops capturing. There is no break in timecode and the problem is random, never in the same place. I can only capture about three minutes before FCP punks out.

    I read the post about user prefs and deselected Abort Capture on dropped frames / On time code break. I think I then chose “Warn After Capture” This worked and I’m able to capture what I want, but at the end of the capture I get the “you had a timecode break. Relog and recapture” warning. This appears to be a FCP issue. Since I’m experiencing the same problem with both SDI and Firewire DV I believe that eliminates the AJA LS, the XDCAM 1500 deck and my DVX as hardware problems. The situation scares me as I’m offlining in DV and will export/import an edit list and recapture in DV50 Anamorphic.

    Any suggestions as to the cause and solution to the phantom “timecode break” prompt?

    Ashley James

    A.James

    Ron James replied 19 years, 9 months ago 3 Members · 4 Replies
  • 4 Replies
  • Vladislav

    July 18, 2006 at 9:10 pm

    I just had the same problem with capturing DV and experienced the same Time Code Break errors and I know for sure there are no TC breaks. I tried two different decks, same thing. The only way I was able to capture this footage is by turning the Device Control off and pressing play on the deck and going Capture Now. I can’t explain it, but that’s what happened, I’m wondering if the new updates causing this. Any one else tried to Capture something lately via Firewire and experianced the same problem?

  • Ron James

    July 19, 2006 at 3:08 am

    I haven’t used the dropped frames report in years. And I haven’t had a dropped frame in years. It’s waaaay too sensitive. I’m not sure what it’s looking at exactly, but I’ve had it go off every minute or so for no apparent reason, so I finally turned it off and never looked back. I watch 90% of my material when I capture, too, so I’d probably catch any problems. I think FCP can even search for dropped frames after the fact, if you’re at all worried.

  • Ashley James

    July 19, 2006 at 6:37 am

    I’m told it could be a quicktime problem and that I should re-install or upgrade quicktime.

    Any other suggestions?

    A.James

  • Ron James

    July 23, 2006 at 2:38 pm

    I find it’s been a constant problem irregardless of system or quicktime version.

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