Open your recording in Blender
FreeMoCap can export a processed recording straight into Blender: a full 3D scene with a skeleton mesh, the camera positions from your calibration, and lighting already set up.
Blender export currently works with MediaPipe mocap data only. RTMPose 3D data doesn't have a working Blender export yet.
Before you start
You'll need:
- Blender installed. FreeMoCap detects it automatically, or you can point it at your Blender install manually.
- A processed recording, meaning the mocap pipeline has already run
and produced the required
.npyfiles in that recording'soutput_data/folder (see Find and read your output). You can't export a recording that hasn't been processed yet.
Nothing else to install: the Blender addon that builds the scene is handled automatically. It's injected into Blender at export time rather than installed into Blender's own preferences, so there's no separate addon-install step to do yourself.
Exporting
From the recording you want to export, click Export to Blender.
FreeMoCap detects your Blender install, runs the export, and writes a
.blend file into that recording's folder. You can have it open
automatically in Blender's GUI when it's done, or open the .blend file
yourself later.
What actually ends up in the scene
| Element | Comes from |
|---|---|
| Skeleton mesh | Body keypoints, connected into a skeleton |
| Hand meshes | Left and right hand keypoints |
| Face mesh | Face keypoints |
| Center of mass | The whole-body center of mass trajectory |
| Camera frustums | Your calibration, showing where each camera actually was |
| Ground plane | Your calibration's ground-plane alignment (Z = 0) |
| Lighting | A default three-point lighting setup |
If something goes wrong
"Blender not detected." Install Blender from blender.org, or set the path to your install manually.
Export fails, citing missing files. The recording hasn't been fully
processed yet, not every required .npy file exists. Run the mocap
processing pipeline on it first.
The addon fails to load. It's injected at export time rather than
installed into Blender's preferences, so this usually means the
freemocap_blender_addon package itself isn't available in your Python
environment, not a Blender-side problem.