Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums AJA Video Systems Timecode Drift

  • Jason Levy

    December 10, 2008 at 5:48 pm

    We’re having the same problem but trying to mastser to a Panasonic AJ HD1400..

    jason

  • Jeremy Garchow

    December 13, 2008 at 7:15 pm

    [jason levy] “We’re having the same problem but trying to mastser to a Panasonic AJ HD1400.. “

    What have you tried?

  • Jason Levy

    December 13, 2008 at 9:28 pm

    Well, we’ve tried a number of things and now the timecode is no longer drifting but when we assemble from 09:58:40;00 (with a picture start of 10 hours) the 2 pop and picture start is off by 2 frames (though the initial insert is accurate). Also we cannot insert accurately… Sorry not to be more specific. The editor knows the details and I’ll ask him Monday.

    So it’s getting closer.

    What I don’t get is why the timecode counts 60 frames for each second on the sequence but 30 frames for each second on the deck. Is that normal?

    jason

  • Rob Neilson

    December 14, 2008 at 10:17 am

    Sorry for the delay.
    I was working in NDF – it felt like that sort of problem to me too, but unfortunately it wasn’t that simple. I never really figured out what the problem was, but I did manage to find a workaround.
    Once I realized that the exported movies were out too, I decided that it must have had something to do with the frame rate. So, I exported the reels again using QT conversion, at 24 fps (23.98 wasn’t an option). Thankfully, this movie was frame accurate, so I imported it back into FCP, put it on a 23.98 timeline and output to tape via the Kona card. I did several tests on each HDSR reel and they seemed to be frame accurate. I haven’t heard anything bad from Technicolor yet, so I’m hoping everything’s been resolved.

  • Jeremy Garchow

    December 14, 2008 at 5:49 pm

    [jason levy] “Is that normal? “

    Yep. 60p material is based on 30 fps tc. Its’ weird and I don’t get it. I believe it probably has to do with dragging that ole NTSC legacy around. Basically, two frames get assigned one tc number.

    [jason levy] “Well, we’ve tried a number of things and now the timecode is no longer drifting but when we assemble from 09:58:40;00 (with a picture start of 10 hours) the 2 pop and picture start is off by 2 frames (though the initial insert is accurate).”

    Are you sure your timeline is setup properly? Meaning are you sure that your b&t aren’t 2 frames long? Are you sure that you might be accounting or not accounting for df tc in both FCP and the deck?

    ALso, have you calibrated the timing of your deck to your Kona? I can tell you how to do this, but actually the FCP manual has a pretty decent description on doing so.

  • Jason Levy

    December 14, 2008 at 8:33 pm

    [Jeremy Garchow] “ALso, have you calibrated the timing of your deck to your Kona? I can tell you how to do this, but actually the FCP manual has a pretty decent description on doing so.”

    Hmm. Can you refer me to the manual page? Thanks Jeremy.

    Jason

  • Jason Levy

    December 15, 2008 at 5:31 pm

    We are now able to insert accurately.

    When you right click on the timecode display on the sequence it gives you some options including HH:MM:SS:FF and 60@30. We found it set to the latter by default but we changed it to the former and suddenly the inserts are accurate. We must set the in by clicking on the “in” button not entering the numeric inpoint on the keypad.

    I don’t totally understand why this works but the 60 to 30 conversion definately required the right tweaks to work correctly.

    Thanks for your help Jeremy.

    jason

  • Jeremy Garchow

    December 15, 2008 at 5:47 pm

    Of course, that makes sense. FCP allows you to view SPMTE tc or view the frames as 60 discreet fps. You can do this on a clip by clip basis as well. It was probably a matter of FCP not knowing where to insert on the correct frame.

    Good sleuthing.

    Jeremy

Page 2 of 2

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