Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Version 6 Time Code bug?

  • Version 6 Time Code bug?

    Posted by Barbara Ballow on May 19, 2008 at 11:55 pm

    I wrote in earlier about a work around for footage captured with no timecode. Now I hear from another editor that losing timecode and reel numbers is a known problem with FCP 6. Is this true?
    Is there a workaround for that? I’ve decided to recapture my
    70 hours of material because I think timecode and reel numbers are kind of important in a long format show. I’d like to make sure it gets done correctly this time. Thanks!

    Mark Maness replied 17 years, 10 months ago 11 Members · 25 Replies
  • 25 Replies
  • Walter Biscardi

    May 20, 2008 at 12:00 am

    We’re not experiencing anything like that capturing DVCPro HD, BetaSP, DigiBeta, HDV, DV and DVCAM.

    Walter Biscardi, Jr.
    Biscardi Creative Media
    HD and SD Production for Broadcast and Independent Productions.

    STOP STARING AND START GRADING WITH APPLE COLOR Apple Color Training DVD available now!
    Read my Blog!
    View Walter Biscardi's profile on LinkedIn

  • Shane Ross

    May 20, 2008 at 12:17 am

    Never experienced anything like that. FCP or QT does not just lose TC. This points to someone capturing with UNCONTROLLED DEVICE. That never captures TC.

    Shane

    GETTING ORGANIZED WITH FINAL CUT PRO DVD now for sale!
    http://www.LFHD.net
    Read my blog!

  • Chris Borjis

    May 20, 2008 at 12:20 am

    What Shane Said.

  • Tom Matthies

    May 20, 2008 at 1:53 am

    Did someone accidentally turn off the timecode columns in your bin by chance? I’ve never heard of FCP “loosing” timecode after the clip was captured.
    Weird…
    Tom

  • Rafael Amador

    May 20, 2008 at 1:54 am

    [Barbara Ballow] ” I hear from another editor that losing timecode and reel numbers is a known problem with FCP 6″
    Absurd.

    Mac OX 10.5.2-FC 6.02-QT 7.4.1
    G5 2x2Gh 4GbRAM-BlackMagic Extreme
    PMBP 17″Core2Duo 4GbRAM-AJA ioHD
    JVC DTV-17″
    SONY EX-1 . SONY PD170
    ..and always a big mess on top of the table.

  • Jeremy Garchow

    May 20, 2008 at 2:05 am

    It’s been a long time since I have seen this.

    I could never really track it down, but it had to do with df and ndf timecode and bringing in footage over firewire. FCP expects df tc over firewire as many consumer dv cameras default to df timecode and only professional cameras allow ndf in dv.

    On this particular project in which I was restoring the timecode for some reason had been reported as df, but the tape was ndf (or maybe it was the other way around). Once the footage was captured the reel name would disappear and all the timecode information would be set to a media start point of 00:00:00:00.

    Check to make sure your timecode matches from your tape and what’s logged. Then changing your device control to firewire ndf can sometimes solve it.

    I have to look it up, but I know it’s documented on the cow somewhere.

    Jeremy

  • Barbara Ballow

    May 20, 2008 at 11:58 am

    Jeremy, if you can find the information I would really appreciate it. I want to make sure the assistant editor (yes they do still exist) who loaded the material initially understands how this happened and why it is a potential problem.
    I’d like to be more helpful than “well you screwed up, so someone else has to do this all over again”. Thanks!

  • Mark Maness

    May 20, 2008 at 2:32 pm

    To add to what Jeremy spoke about… This is a real possibility.

    Also, with DV camcorders (and HDV), timecode needs to be properly set in the camera’s menus for you to get accurate timecode.

    Let me give you an example. When we purchased our Sony HVR-Z1U camcorders, the timecode was set to automatic. Not thinking anything of this several shows were taped. After getting the tapes in the edit suite, we found that FCP was giving us timecode errors when we captured the footage. Come to find out… the Z1U’s were recording timecode in NDF and DF at odd intervals. So… we went into the camera’s setup menus and set all of the Z1U’s to DF. Since that time, we’ve had no timecode errors.

    Can you tell us what tape deck you are using and how it is hooked up to your computer?

    _______________________________

    Wayne Carey
    Schazam Productions
    http://www.schazamproductions.com
    https://blogs.creativecow.net/waynecarey

  • Jamie Pickell

    May 20, 2008 at 3:12 pm

    I had this problem when I upgraded from ver. 5 to 5.1 and I have a Kona 2 coming in off of DBeta and DVCam decks. I could log and capture clips, but once they were captured, the timecode would reset to zero and the reel # would reset to 001. I solved it by trashing preferences and never saw the problem again. I am currently running 6.02.

    Jamie
    OS 10.4.11
    Dual 2.5 G5
    Kona 2
    XRaid
    FCP 6.02

  • Barbara Ballow

    May 20, 2008 at 3:30 pm

    Unfortunately, this material was captured prior to my being hired to edit. It was done at a facility in Spain. The assistant e-mailed me and told me the deck was a Sony HVR/M25E deck, but I have no idea how the system was setup. The material seems to be fine (except for this problem). Also, under capture in the bin each clip says “not yet”. What does that mean? I’ve been in the AVID world for over a year, so I am getting back up to speed
    on these issues which are unique to FCP. Thanks for the help.

Page 1 of 3

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