View Full Version : 10 sec Motn file, 22 minute render?


Jem Moore
August 23rd, 2010, 10:57 PM
The title says it all...I created a simple graphic motion file with text that has blur in, blur out and slowly grows, and it's actually less than 10 sec long...when I put it in my sequence and go to render, it takes almost 20 minutes to render. I have a brand new Macbook pro with Intel I7 chipset, 4G of RAM, a 7200rpm hard drive...seems like a really long time to me. Anybody have any ideas? Thanks...

Jordan Hooper
August 24th, 2010, 12:21 AM
A couple things that can really increase render times in Motion is setting render quality to "best" instead of "normal" and having motion blur turned on, especially if you're using a 3rd party plugin. What render settings are you using?

Robert Turchick
August 24th, 2010, 01:39 AM
that can happen...text is a funny thing in motion. seems if you do anything to it other than a simple move, you have time to eat lunch and update your FB page!

BTW, I'm on a MacPro 8-core with 16gig of RAM and that's happened to me on a simple 10 sec lower third!

Now I go to AE CS5 for text which renders faster than I can take a swig of soda! wish Apple would allow motion and FCP to take advantage of the 64-bit processors!

Dave Partington
August 24th, 2010, 01:12 PM
I have found that occasionally Motion will take AGES to render or analyse a clip. Rebooting fixes it every time. No idea what causes it.

Jem Moore
August 25th, 2010, 08:22 PM
I'm actually rendering in the Sequence in FCP, and what's weird is that every time I do another process, the rendering time gets slower, and it seems additive. In any case, something is making FCP notch slower as time goes by, until I have to reboot to get back to normal. Very weird.

James Wong
September 2nd, 2010, 10:46 PM
When I first got my Mac Pro and Final Cut Studio 3, I tried to render a 720p motion graphics clip with simple text that the camera would fly into. But at 59.94fps. It took FOREVER and eventually crashed the system.

For whatever reason, the system would come to a haul and my mouse pointer would jump around erratically when it processed just this .motn project file. Thankfully it hasn't happened... since.

Motion is just really strange that way :( I need to stick with AE instead even for things that I can put together quickly in Motion :(