[Scot Walker]

Motion isn’t immune to limitations of what computers can do. Obviously, the more behaviors you use, the slower it gets.

That’s why there is RAM preview.

I’ve been using Motion for a project recently and it does slow down, especially when you have the timeline open (like on a second monitor). For some scenes I have, it’s real time. For others, it isn’t. For the scenes I have that won’t animate in real time, I end up doing what I do in AE — I render RAM previews.

Like I said, it helps if you don’t have your timeline open. That seems to slow it down when you have projects with a lot of layers, etc.

[Scot Walker]

That’s not optimal, but it will work.

Thanks!

[Scot Walker]

Maybe a combo of a particle generator combined with a blur wipe off?

[Scot Walker]

Does it lose sync with a RAM preview?

[Scot Walker]

No problem. Thanks for the response anyway! 🙂

Greg, I’ll try that Image Mask method. That sounds very cool.

Thank you!

[Scot Walker]

OK, I figured it out and I’ll explain it here in case someone else has the same question:

Don’t select the photo/movie and apply a mask to it. Instead, select the layer the photo/movie is in and then apply the mask to that. If you do it this way, you can then animate and do whatever you want with behaviors and the photo/movie. They are now independent.

Gee, it only took me a couple of hours to figure that one out. Doh!

I’m guessing I need to get a better book than the Motion manual. 🙂

[Scot Walker]

OK.

Thanks