There are some situations where Mocha standalone will render or track more quickly than the plug-in version. View the Mocha tech/specs chart to see what data formats Mocha supports. Other examples include Apple FCP X, Blackmagic DaVinci Resolve, Autodesk Flame, Assimilate Scratch and any 3D packages where you might use Mocha’s camera solve data. After Effects CS6 is an example of where you would need the standalone version because the plug-in only works in CC. In that time we developed workflows to export tracking and shape data to most VFX or editing software. Mocha was a standalone application for a long time before it was a plug-in. This is something that large facilities find useful. Mocha standalone has a Python scripting engine and can be extended to integrate with asset management pipelines, provide custom tools, etc. Facilities with a finishing artist working in Flame or color grading suites such as Resolve or Baselight often have an assistant station handling the tracking, roto or object removals and Mocha Pro standalone supports these sites well.

If they spend all of their time in Mocha, using the standalone version avoids the facility needing to buy host software seats for these artists.

Some of our customers have a large number of roto artists, who only do roto. Large roto projects or assistant stations.For most Mocha Pro users, the plug-in is the best choice for usability and integration with your host application, below are some situations where you might want to use the standalone application. What Mocha Pro option should I buy, the plug-in or the standalone application? What is the difference between the Mocha plug-in and standalone?Ī.

Mocha davinci resolve