Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy timecode breaks

  • timecode breaks

    Posted by Pol on August 8, 2005 at 11:27 am

    Locating timecode breaks takes forever on fcp 4.5. And it isn’t very accurate. What are the best settings to speed the process up?
    Is it faster in fcp5.0? That would be a reason to upgrade….don’t care about multicam.

    Jerry Hofmann replied 20 years, 9 months ago 2 Members · 3 Replies
  • 3 Replies
  • Jerry Hofmann

    August 8, 2005 at 1:05 pm

    Wasn’t accurate? What do you mean?

    I captured a whole tape the other day in 5.0.2 on Tiger 10.4.2, and didn’t find it inaccurate at all… was faster locating the break I think.

    Jerry

    Apple Certified Trainer

    Author: “Jerry Hofmann on Final Cut Pro 4” Click here

    Dual 2 gig G5, AJA Kona SD, AJA Kona 2, Huge Systems Array UL3D

  • Pol

    August 8, 2005 at 1:17 pm

    It isn’t normal that the system needs 4 min to detect a timecode break. It shouldn’t take longer than 30sec.
    I’m working on FCP for about a year now and this is unacceptable. The log and capture tool is the weakest tool in FCP (and titling is second).
    I can’t see the timecode when capturing, can’t give any description during capture and locating timecode breaks is frustrating slow.

    There’s still alot of work to be done by the fcp team.

  • Jerry Hofmann

    August 9, 2005 at 1:40 pm

    When I captured the tape I’m referring to, it didn’t even take 30 seconds to find the break… I can see TC during capture either on my video monitor or the deck too… Not in FCP, however, I can see it if I setup the system properly… so in answer to your first question, FCP 5 is probably improved a lot here.

    Jerry

    Apple Certified Trainer

    Author: “Jerry Hofmann on Final Cut Pro 4” Click here

    Dual 2 gig G5, AJA Kona SD, AJA Kona 2, Huge Systems Array UL3D

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