Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Speed Changes fixed in 5.02? When reconnecting or media management?

  • Speed Changes fixed in 5.02? When reconnecting or media management?

    Posted by Mike J. on August 3, 2005 at 8:38 pm

    Just really curious if any of you have experienced success with timelines that involved speed changes.

    In 4.5 HD as you know..the footage would play like jumpy super fast after relinking in the intended slow mo clips.

    Did this issue get a resolution in 5?

    Stephen Eckelberry replied 20 years, 7 months ago 6 Members · 7 Replies
  • 7 Replies
  • Ben Insler

    August 3, 2005 at 8:45 pm

    as of Macworld in boston three weeks ago, this had not been fixed in 5.

    Ben Insler
    Editor
    Telemark Films

  • Mike J.

    August 3, 2005 at 8:54 pm

    Really…. I’m sure many people flat out asked that question too.

    Thanks, I guess it’s workarounds then…

  • Johan Skaneby

    August 4, 2005 at 7:00 am

    yes,

    does anyone know af a workaround to this?

  • Annaël Beauchemin

    August 4, 2005 at 6:51 pm

    [johan skaneby] “does anyone know af a workaround to this?”

    Most problems occur when you either use variable speed, or when you modify a speed changed clip on the timeline.

    To reconnect properly, a clip must have only 2 Time Remap keyframes: one EXACTLY on the IN point, another EXACTLY on the OUT point.

    For some reason, FCP sometimes adds keyframes outside of the used portion of the clip. You must delete them. Note that there is often a keyframe very far away from the OUT, this is normal.

    When you move the IN or OUT point of a clip after it has been speed changed, sometimes the time remap keyframe will not follow. You must either move it back exacty on the IN/OUT point, or rebuild the sequence clip to make sure it’s “clean”. For this you select the sequence clip, you hit “f”, you apply the speed change while still in the viewer (command-J) and drop back the clip in the timeline.

    But even then, they might slip a bit or screw up if you add dissolves… I really wish Apple would have corrected those little quirks which makes FCP a bit of an unreliable offline editing software…

  • Paul Provost

    August 5, 2005 at 4:37 am

    little quirks?!?!?! a bit of an unreliable offline editing software?!?!?
    jeez, I cringe every time a client brings in a “homemade” fcp offline for uprez.

  • Annaël Beauchemin

    August 5, 2005 at 7:43 pm

    what I meant is that it is only a few little bugs that jeopardize the entire online-offline workflow. Somethimes it works fine, but everytime I need to inspect the edl carefuly, which takes time…

  • Stephen Eckelberry

    October 2, 2005 at 8:59 pm

    [Le Coyote] “To reconnect properly, a clip must have only 2 Time Remap keyframes: one EXACTLY on the IN point, another EXACTLY on the OUT point.”

    That I will have to try. I have been cutting on FCP since version 1. I have cut countless promos, spots and features and I love it. I’ll put up with all kinds of bugs, but I must say this one has me pulling out what’s left of my hair. This one problem is so bad I seriously think about going back to Avid just for that.

    Here is my workaround: When working with the reconnected material, I first create a scratch timeline. I then go back to the regular timeline and copy the clip in question (that’s just to get its attributes). I then “F” key the clip, and in the viewer set an arbitrary new outpoint (like one second after the in-point), go back to the scratch timeline and insert the clip. I then paste the speed attributes into this new clip. I copy this newly created clip and paste it on a track above the original, and slide the outpoint to match the original.

    I find that the inpoint is usually accurate with these wacky FCP speed goofs.

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