freemocap - Moses Yebei

The Problem

Have you ever tried motion capture and thought, "Wow, this is way too expensive and complicated?" Traditional setups require a small fortune and a PhD in engineering just to get started. FreeMoCap aims to fix that by giving you a low-cost, open-source alternative that doesn’t require a degree in rocket science.

What This Does

FreeMoCap is a motion capture system that runs on both hardware and software you probably already have. The project is split into a few key directories, like freemocap/, which contains the core processes for capturing and processing motion data, and experimental/freemocap-ui/, which houses the React-based UI for interacting with the system.

You can kick things off with freemocap/main.py, which launches the GUI to start your motion capture sessions. If you're feeling adventurous, the experimental/batchprocess/ folder has scripts to handle batch processing of your captured videos, making it easier to analyze multiple recordings without losing your sanity.

Real-World Use

Here’s a quick workflow: After setting up your environment and installing the package using pip install freemocap, you can run your capture session like this:

python -m freemocap

The GUI pops up, guiding you through the capture process, where you can adjust settings directly. Once done, you can dive into the processmotioncapturevideos folder to tweak your data and export it for further analysis. Need to visualize your results? The integration with Blender via exporttoblender.py makes it a breeze to create stunning visuals.

The Bottom Line

FreeMoCap is a solid option if you're looking to dip your toes into motion capture without drowning in costs and complexity. It's got a decent structure and clear documentation, but with only 0 stars, it might lack that warm, fuzzy community support you’d find in more established projects. If you’re a researcher, educator, or hobbyist, give it a shot—but don’t expect the polish of commercial solutions just yet.

What the analyser found

Deployment readiness

3/7

Container image
CI pipeline
Lockfile committed
Test suite
README
License
No committed secrets

Composition

200 files

Python79
TSX29
TypeScript15
YAML14
Shell8
Markdown7

ReactFastAPI

Architecture

Top-level areas of the codebase, sized by module count. Arrows show how many imports cross from one area into another.

graph TD g0["freemocap<br/>148 modules"] g1["experimental<br/>74 modules"] g2["(root)<br/>2 modules"] g1 -->|22| g0

Module dependencies

The 10 most depended-upon modules of 224, from static import analysis. Red outline marks a module in an import cycle.

graph LR n0_enames_file_and_folder_names["file_and_folder_names"] n1_s_and_filenames_path_getters["path_getters"] n2__processing_parameter_models["post_processing_paramete"] n3__models_recording_info_model["recording_info_model"] n4_ties_save_and_load_gui_state["save_and_load_gui_state"] n5_em_logging_configure_logging["configure_logging"] n6_ilities_download_sample_data["download_sample_data"] n7_uff_charuco_board_definition["charuco_board_definition"] n8_ap_utilities_get_video_paths["get_video_paths"] n9__system_logging_queue_logger["queue_logger"] n2__processing_parameter_models --> n3__models_recording_info_model n3__models_recording_info_model --> n0_enames_file_and_folder_names n3__models_recording_info_model --> n1_s_and_filenames_path_getters n3__models_recording_info_model --> n8_ap_utilities_get_video_paths n4_ties_save_and_load_gui_state --> n7_uff_charuco_board_definition n4_ties_save_and_load_gui_state --> n0_enames_file_and_folder_names n4_ties_save_and_load_gui_state --> n1_s_and_filenames_path_getters n5_em_logging_configure_logging --> n1_s_and_filenames_path_getters n1_s_and_filenames_path_getters --> n4_ties_save_and_load_gui_state n1_s_and_filenames_path_getters --> n0_enames_file_and_folder_names n6_ilities_download_sample_data --> n1_s_and_filenames_path_getters classDef cyc stroke:#ef4444,stroke-width:2px; class n0_enames_file_and_folder_names,n1_s_and_filenames_path_getters,n4_ties_save_and_load_gui_state,n5_em_logging_configure_logging cyc;