Skip to content

david-cattermole/mayaMatchMoveSolver

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Maya MatchMove Solver (MM Solver)

A unique and flexible solver toolset for MatchMove (MM) related tasks integrated into Autodesk Maya.

The aim of this project is to provide a solver to aid in complex matchmoving tasks inside Autodesk Maya. This tool is not intended as a one-click-solution - this tool is for advanced techniques that are encountered on a daily-basis in the Film and TV industry.

Documentation

For all tutorials, documentation of Tools, Python API and Maya Plug-In features, take a look at the Documentation Home Page.

The official YouTube channel is mmSolver, it contains video tutorials for mmSolver on a range of topics.

A copy of the documentation is also installed with Maya MatchMove Solver, you can find it by pressing the help button in the Solver UI, or in the module install directory, for example this path:

(On Windows)

C:/Users/<user name>/My Documents/maya/2017/modules/mayaMatchMoveSolver-0.1.0-maya2018-win64/docs/html/index.html

Community

Do you have a question about mmSolver? The mailing list is the perfect place to ask!

There is a Google Group mailing list: maya-matchmove-solver.

The mailing list is a place for user questions and discussions, and will have release announcements of new versions.

If you find a bug, please report it on the GitHub project issues page.

Installation

If you have a 'mayaMatchMoveSolver' archive package and need to install it, follow the instructions in INSTALL.md.

Releases

The following releases are below. The latest bug-fix version should always be used, where possible. Forward compatibility is maintained between point-release versions (v0.1 to v0.2), but major version releases should be considered major and may introduce breaking changes.

Releases Description
v0.5.1 Support for Maya 2025.
v0.5.0 Silhouette Renderer and Improved MM ImagePlane.
v0.4.9 Bug fix for Surface Cluster.
v0.4.8 Add Create Rivet and Surface Cluster tools.
v0.4.7 Bug fix for "Convert to Marker" tool.
v0.4.6 Bug fix for solver and minor features.
v0.4.5 Introduction of MM Renderer and Maya 2024 support.
v0.4.4 Solver, 2D Reprojection and Blender-to-3DE fixes.
v0.4.3 Bug fix for performance.
v0.4.2 Bug fixes and 2D Marker round-tripping.
v0.4.1 Bug fix Basic solver tab.
v0.4.0 Lens distortion, ImagePlane and Camera Solver.
v0.3.16 Maya 2022 support.
v0.3.15 Added Camera Calibration tool and 3DE R7 support.
v0.3.14 Integrated Qt.py and bug fixes.
v0.3.13 New tools, and Maya 2020 support.
v0.3.12 Bug fixes, minor features and updates.
v0.3.11 Bug fixes, and minor tool and UI updates.
v0.3.10 Bug fix release, support for Mesh Rivets.
v0.3.9 User preferences and minor solver changes.
v0.3.8 Bug fix release.
v0.3.7 Performance, stability improvements and bug fixes.
v0.3.6 UI Performance Improvements and bug fixes.
v0.3.5 Fixed bugs.
v0.3.4 Added Attribute Details and fixed bugs.
v0.3.3 Bug fix release.
v0.3.2 Added tools and fixed bugs.
v0.3.1 Added tools and fixed bugs.
v0.3.0 Improved solver, GUI and tools
v0.2.3 Bug fix release
v0.2.2 Bug fix release
v0.2.1 Bug fix release
v0.2.0 Improved solver and tools
v0.1.1 Bug fix release
v0.1.0 Initial release

Building

To build (compile) the plug-in follow the steps in BUILD.md.

License

Maya MatchMove Solver (mmSolver) is licensed under the Lesser GNU Public License v3.0 or LGPL-3.0 for short. This means the project is Free Open Source Software, and will always stay Free Open Source Software: TL;DR.

Please read the LICENSE (text) file for details.

Contributing

If you're interested in contributing to the Maya MatchMove Solver project, please see the conventions and information in DEVELOPER.md.

Bugs or Issues?

All issues are listed in the issues page on the project page. If you have found a bug, please submit an issue and we will try to address it as soon as possible.