MotionBuilder Pipeline
PythonPySide
The MotionBuilder pipeline evolved constantly to fit the current and future needs of the motion capture pipeline. Initially, the UI was purely the native UI elements from MotionBuilder.
To allow for a more customizable and nicer UI, all the interfaces were transposed to PySide inserted in a dockable native UI tool.
The pipeline has access to the upstream data of the Mocap Shoot Interface and the Client Selection Website, that it uses to automate a lot of integration and exportation tasks, minimizing manual intervention.
From asset preparation to final exports, manual processes have been condensed into easy to use UIs with buttons taking care of repetitive and error-prone manipulations.
This includes managing the real-time devices during the shoot, managing environment position for the motion capture shoot and for the export to engine,
pairing assets with range of motions, and more.
The integration process that required manual preparation of assets per take has been automated to file selection that processes them all and leaves them ready for retargeting touch ups.
Integration went from taking 5 to 15 minutes per file to 1 to 3 minutes processing time per batch of multiple files.
The files export process for delivery automatically separates the takes by client selection parts with the appropriate assets.
Throughout the pipeline, the status and assignee of tasks in Flow PTR (ShotGrid) is updated automatically when possible. For any manual step, like retargeting and animating, a UI is available with
direct access to the relevent tasks for the currently opened file, increasing the ease of keeping tasks up to date.