Anyone else haveing issues where Motion 5 performs worse than Motion 4?

I love AE, but in previous versions of Motion, I could just spend more time being creative and less time dealing with the software's issues. Now that's plaguing Motion. I know they'll correct (at some point). AS for FCPX, I absolutely love it. First week after release and I was so much more productive with it; only on small test projects of course. I like the updates. I look forward to this new platform going forward. It has so much potential that I am pretty sure the likes of Adobe and Avid will copy.

It's still not ready for prime time, but I've found a place for it for some projects, so I'll grow with it. FCP 7 still is my workhorse, but I am incresingly shifting to X. It's just so much more powerful.

...as I wait for my Motion reinstall to finish...

Here we go again. Motion has become practically inresponsive. I don't care about feature updates anymore. I just want this thing to work.

I don't know what's caused it, but it's slow. It takes a long time for it to respond to my clicks. Actually every time I do something I click in the finder and click back to motion as that seems to help it along for another click or two. I checked my console - I am getting uncrecognized button errors, plugin loading erros, and this persistent com.apple.peruser call (something to do with Akamai) among others.

I haven't updated anything, I am opening the same projects over and over. At some point things just go bad. I mouse over parameters and they light up as if to follow my mouse ointer. Then some parameters just keep flashing repeatedly.

This is so disappointing.

Compariitvely I have to say that anything Lion related has been a major headache compared to Snow Leopard. Not that Lion is always in problem mode. But I can't remember the last time I've had a MacOS with so many problems with the apps as well.

Time for Motion install #8.

BTW, FCPX on another station just failed as well.

It is ridiculous that motion problems haven't been sorted out with the updates yet.

I turned on motion blur to render a 15 second sequence that uses only still images, left it over night and came back to only 1% rendered and 250 hours to go. So I gave up again and rendered without motion blur.

This may sound crazy, but I just started thinking about Quicktime X and 7 and how the may or may not interact with different apps, or rather how apps get to their resources.

In short, I've been starting Motion first when I start my computer. I load a blank project, close it and then edit (keeping the app open) in FCP 7 (for this current project). Motion doesn't seem to be having any issues. We'll see how it goes. There's so many things taht are in transition and I think that Qucktime (both versions) are at least in part, some of the problem.