And now the mesh tracker is pretty exciting, albiet a little harder to use than planar tracking data.įor me, if I had to call out one hurdle with Mocha for roto, it would be how Mocha translates its roto spline shape’s points to Flame. A few improvements have really stood out to me over the years: The ability to export the gmask tracer instead of just the traditional gmask was a big leap, and along with that improvement came the ability to include a roto shape’s keyframe data you create in Mocha. I learned Mocha as a Flame Assistant, providing roto and tracking data to Flame artists daily, so when I became a Flame Artist it was a no brainer to continue to take advantage of it. Same scenario - if it’s a simple roto it’s always better to be able to see things in context within Flame, but as soon as it’s a roto that will take more than something like 20 minutes, the quality of life of using Mocha (at least for me with my background) makes it a lot more enjoyable and efficient. I’ve never used Mocha’s matchmove features, but for all things complex roto I’m also absolutely jumping into Mocha. ![]() I’m only using Flame’s planar tracker if the track I’m doing is incredibly simple and almost impossible to fail otherwise I’m jumping into Mocha. ![]() ![]() As soon as I have a shot that Flame’s planar tracker flies off the rails, Mocha will generally be able to handle it much better. I’m a big Mocha planar tracker user and find it to always ALWAYS work better when compared to Flame’s planar tracker.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |