Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy FCP and Motion integration issue.

  • FCP and Motion integration issue.

    Posted by Marcus Moore on February 1, 2008 at 5:04 pm

    Starting in 2008 I decided to leave behind my 10 years old workflow and start maximizing the cross program ease of use in FCS 2 by giving up After Effects for Motion. I committed myself on a recent project to use only Motion, Livetype. It went really well, and I’ll be picking up some the FCP Motion book and sourcing some more online tutorials to see just how much more I can do.

    I’m running a G5 Quad with 3.5GB of ram and the NVIDIA Quadro FX 4500. All FCS2 assets up to date.

    Here’s whats going on:

    I’m using “send to motion” to port video files over to work in Motion, so I’ve got the .motn files in my sequence which I then render. Suddenly, I’m finding that my sequences are very slow to update (even after all motn files are rendered), and all thumbnails (video and waveform) are taking a while to refresh. And if I try to move around the sequence too fast, FCP crashes. Is this a bug or are my system setting not set properly? I’m really enjoying working within the Studio, so I hope this problem is fixable.

    When I went into a client’s office to make some final revisions to the same project, the same thing was happening.

    Thanks!

    Marcus Moore replied 18 years, 4 months ago 3 Members · 4 Replies
  • 4 Replies
  • David Bogie

    February 1, 2008 at 7:57 pm

    These symptoms often indicate you’re using your internal drive for media storage. Drive is too full? Drive is too slow.

    bogiesan

    This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

  • Marcus Moore

    February 1, 2008 at 8:05 pm

    In both cases I was editing from a Lacie 500GB drive connected via FW800. The sequence was D1 anamorphic, but contained footage including 720 and 1080 material.

  • Mark Palmos

    February 1, 2008 at 8:23 pm

    Hi Marcus
    When I was on Tiger, Motion integration was pretty stable, though Motion does crash a lot more than the other Studio2 apps in my experience.

    I didnt find it slowed FCP down much, once rendered it was just like a regular clip.

    With Leopard ive had major problems, cannot play back any motion project in FCP for more than about 30 seconds, then get beach ball crash – not responding – and have to kill process.

    I dont know if any of this relates to your issue, but would very much like the integration sorted and made stable.

    Mark.

  • Marcus Moore

    February 1, 2008 at 8:45 pm

    I was dealing with pretty complicated motion comps with lots of 3D layers, so I never tried to play them without rendering. If I zoomed out/in, I had to sit an wait for about 30 seconds for all the video and audio layers to refresh thumbnails/waveforms, like they weren’t being held in cache. Rainbow balls appeared throughout, and sometimes resulted in crashes.

    Perhaps some of this instability will be addressed in 10.5.2.

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