Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy VRR/Cadence Pulldown Errors

  • VRR/Cadence Pulldown Errors

    Posted by James Vancouver on March 26, 2006 at 8:09 am

    Hey – Though I’m seeing some old posts on this, I don’t yet see a solution, so I’m hoping perhaps someone has found one to this problem? I’m currently logging clips and experiencing the “Cadence Error” problem. Strange thing is, I’m re-creating a short film scene by scene from an editor who used these exact tapes before me (albeit 2 years ago – could the tapes have deteriorated?) Because these errors are popping up in the middle of takes, I can only assume the previous editor did not experience these errors otherwise he would not have been able to capture the clip…now I’m trying to capture the same clips, from the same tapes, and I’m getting these errors. I don’t know what to do. I thought it was a setting thing as I’m relatively new at this, but sounds like it is a timecode thing or defect in the tape itself? Is there a way around it other then capturing around the cadence error (VERY time consuming to figure out its exact spot).

    I’m hoping you have an answer…

    J

    James Vancouver replied 20 years, 1 month ago 2 Members · 2 Replies
  • 2 Replies
  • Daryl K davis

    March 26, 2006 at 4:40 pm

    Are you attempting to do reverse-pulldown and experience the cadence error? Did you capture each clip on the A-frame?

  • James Vancouver

    March 26, 2006 at 11:27 pm

    Hmm – I’m not certain what you mean. That’s my inexperience showing. I have not been trying to reverse pulldown as far as I know. I have been capturing numerous clips over several tapes in exactly the same way – no issues. I firmly believe that there’s issues with the source tapes – blips on the tape for some reason are here now, and weren’t here two years ago when it was first edited.

    I’m not sure what the A-Frame thing is you’re speaking about.

    Thanks for replying…
    J

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