Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Log & Transfer Timecode issue Part 2

  • Log & Transfer Timecode issue Part 2

    Posted by Matt Gerard on April 29, 2011 at 4:22 pm

    OK, Still having issues with timecode getting messed up when ingesting P2, and avchd footage from the KiPro Mini. This is more for documentation than anything else, but feel free to weigh in on anything that I haven’t tried-

    Summary of issue- When using Log & Transfer in FCP to ingest either P2 or SD card footage from our HPX2000 and AF100 respectively, there are clips that show up in the bin that have timecode reset to 00:00:00:00. Seems to average about 1 out of 10 clips that this happens to.

    Things that don’t seem to matter or work-
    • Compression type (DVCPROHD, ACVINTRA, PH1080, etc…)
    • clip length
    • audio channels or compression
    • ingest from card, archived disk image or archived folder structure
    • OSX user (created new user, still happens)
    • repairing permissions on source and destination drives
    • Create new project and ingest into that. Still happens.

    Things that seem to work (sometimes)
    • Make media offline and re ingest those clips. This usually works, but only after the 3rd (or 17th) time of deleting media and re ingesting.
    • Save project, close FCP trash prefs, empty trash. The results of this action is weird. About 50% of the time I’ll open the project and the TC will be correct. Other 50% of the time it will still be wrong and have to go with the 1st option of re-ingesting.

    In troubleshooting, I’ll find that about half the time, the actual QT movie will have the correct TC, but FCP isn’t reading it. If I find this happening with a particular clip, I’ll trash prefs and restart FCP and the TC will be read properly. The other half of the time the QT movie won’t have the correct TC. Then I’ll have to resort to re ingesting.

    My boss is having this same issue on his macpro as well. All software updates are current. It seems to be an issue on ingest.

    I will be posting more on this issue as I move forward. Happy to hear from anyone else that is having this issue. So far seems to be a rogue issue and I need to find the little gnome thats running around our office and beat it about the head and neck with a 2×4 with a nail sticking from it.

    Cheers-

    Matt

    Its more fun to ride a slow motorcycle fast than a fast motorcycle slow…

    Matt Gerard replied 14 years, 12 months ago 2 Members · 3 Replies
  • 3 Replies
  • Kevin Francis

    May 17, 2011 at 4:47 pm

    Matt-

    I’ve been having the same issues with both P2 and AVCHD timecode and have been frustrated that more people haven’t reported this. I guess most people don’t even care about timecode any more! I’ll try some of your suggestions, but again, can’t believe a mature product is having problems like this and not many seem to care or notice.

    Kevin

  • Matt Gerard

    May 18, 2011 at 2:26 pm

    Nope. I’ve reported it to Apple as a bug. Not sure what is going on. I’ll keep posting if I find anything, but I don’t think that this is an issue that can be fixed quickly.

    I saw your post on the apple forums as well, I’m more likely to post here than there.

    Matt

    Its more fun to ride a slow motorcycle fast than a fast motorcycle slow…

  • Matt Gerard

    May 18, 2011 at 4:57 pm

    More info-

    Cam is set to rec run DF TC. This all shows properly in the L&T window before ingesting.

    I’ve tried importing as ProRes (all flavors) and the AVCIntra as both ProRes and Native, and it still does it.

    I’m trying again, and some clips get the TC reset to all zeros, and some clips have the TC set to random times, like 21:24:14;28, then the next clip is zeros, then the next clip has the correct TC.

    Thanks for the ideas, still looking around….

    Matt

    Its more fun to ride a slow motorcycle fast than a fast motorcycle slow…

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