Jay Carr
Forum Replies Created
-
I can’t really speak to a comparison test or anything like that. But lets clear up one quick misconception. As of right now (and I really hope this changes) there is no round tripping between FCPX and Motion. In fact there was another thread written a just yesterday where a guy was trying to figure out how to round trip and it sounds like an absolute pain. You basically end up exporting back and forth.
So…yeah. Until they fix that, I wouldn’t worry about it too much.
(FYI– I basically use Motion as a stand alone, that’s why I have a pretty cavalier attitude about this particular topic…)
-
You’re welcome, glad to be of service :-).
-
If you use the 3D transform tool, and then open up the HUD (F7), at the bottom of that menu is a drop down that let’s you adjust what perspective you are rotating relative to. Does that help?
-
Well, if there’s anyone I trust to know… Is there any sort of way to emulate the effect that you know of? I mean, aside from sequentially animating every single one of the objects manually…
-
Not only does it stand alone, but it does it pretty stinking well. The only thing I really used FCP for was keying, and with the new Key filter in Motion 5 I hardly need FCP for my current projects. Plus the share options have been beefed up, so you can do a quality job outputting now…
-
I respect your point of view, but I think something needs to be made clear before comments like this become a bit to prevalent. I’ve seen them on the FCPX threads, I’d hate to see them here too,
Motion 5 was a total and complete re-write of Motion, not just a skinning job. They were switching frameworks from the old Carbon standard (used in OS9 and before) to the much newer and much better Cocoa frameworks (OSX and beyond, including iOS). They had to re-write tens of thousands of lines of code just to bring Motion 5 up to the same standard as Motion 4.
Frankly, I would have been more than pleased if they had simply given me the exact same program in Cocoa. Why? Because re-writing 7 years worth of code is a ridiculous task to ask of anyone. But not only did Apple completely re-write everything, they added a few new features that really needed to be addressed. Things like 64-bit processing and GCD compliance. Which will do far more for most of our workflows than we will ever actually appreciate.
And no, they didn’t get to all of them, but they will. Just give it some time.
All I’m saying is I hope people will try to realize the humungous amount of work that went into simply making this program on par with the previous version. Trust me, this isn’t a simple skinning job, it’s a complete re-write. So bear that in mind when you’re evaluating it.
-
Though someone else did mention, it does kind of mess up your round trip from FCP to Motion4. Well, at least if you’re broke like me and can’t get FCPX just yet. If you do have FCP7, and you sent to Motion, it goes to Motion 5. There’s no way to change this last I heard.
-
If I’m honest, I would have paid $50 just for the the fact that it’s 64-bit and uses GCD. Everything else is pure icing at that point, frankly. Really looking forward to working with rigging too…
btw, Mark, how long have you had the new Motion? I only have to ask because you got those instructional videos up so stinking fast… ;-).
-
Fingers and toes crossed.
-
That’s what I was afraid of… When is this new version of Motion coming out anyway? Hopefully they’ve fixed this.