Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy FCP 6 and A-frame broken code. A warning.

  • FCP 6 and A-frame broken code. A warning.

    Posted by Aaron Neitz on November 10, 2007 at 2:57 am

    Just a warning to some of you:

    Our workflow has always been to load our dailies at 24fps. That is, if you make a custom capture preset at 23.98fps, and capture your 30fps dailies on the “A” frame, you get nice tidy 24fps media. No Cinema Tools nonsense needed.

    Timecode would hold up fine, that is every :00 would match up, and it was a very simple matter to get back to the dailies 30fps code for telecine lists or online.

    But FCP 6 doesn’t work. Timecode is all over the place. We’ve got clips that are a full 2 seconds off in the timecode (vesus the burn in).

    Be warned. I’m a little disappointed. It was a great workflow.

    Jeremy Garchow replied 18 years, 10 months ago 2 Members · 5 Replies
  • 5 Replies
  • Jeremy Garchow

    November 10, 2007 at 3:31 am

    Is this using ProRes? Have you tried another codec?

  • Aaron Neitz

    November 10, 2007 at 3:41 am

    DV50 @ standard def. Haven’t tried anything else because we’re already deep in editing (which luckily, it still edits correctly despite rotten timecode). It’ll be a hand typed EDL at the end of the day!

    whoo! it’s friday!

  • Jeremy Garchow

    November 10, 2007 at 4:14 am

    Are you using capture hardware for this?

  • Aaron Neitz

    November 10, 2007 at 4:39 am

    Aja Io. Latest drivers. Tiger and FCP 6.0.1.

    There might be a workaround, but we’ve literally been doing this exact workflow since FCP 4.5, and it’s worked without hiccup. Now it’s broken and I’ve got 3 editors who are ready to go back to FCP 5.

    I understand FCP 6 works great for a lot of things, and perhaps our workflow is a little esoteric, but it worked.

    I’ll try loading Monday with a Kona system, and then a DVCAM-firewire connection. Perhaps with ProRes? But I have a suspicion it relates to that QT timecode issue I was having earlier this week with Combustion.

  • Jeremy Garchow

    November 10, 2007 at 6:59 am

    Mmm, not so sure on that one. The problem is, is that there’s not really been an FCP 6 driver released for the io. The io driver hasn’t been updated for a year and a half. A lot has changed with FCP, QT, OS and everything else since then, for instance, the addition of adding ‘real’ timecode to Quicktime. I would bet that it’s the io in combo with FCP6. This will work with a Kona system as the hardware/drivers are up to date. Did that pref trash work for your easy setups by the way?

    Jeremy

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