Skip to content

[DOCS] Clarify MediaPipe graph configuration and task-specific parameters #4075

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
camPetrey wants to merge 2 commits into
base: main
Choose a base branch
from
Open

[DOCS] Clarify MediaPipe graph configuration and task-specific parameters #4075

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6f133b7
[DOCS] Clarify MediaPipe graph configuration
camPetrey Mar 21, 2026
ec98be3
Merge branch 'main' into docs-mediapipe-clarification
camPetrey Mar 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/mediapipe.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -164,7 +164,7 @@ For running multiple graphs in one server instance you must use the `config.json

MediaPipe servables configuration can also be placed in the same json file like the
[models config file](starting_server.md).
Graphs parameters can be defined in section `model_config_list` just like classic models (recommended) or in the section `mediapipe_config_list` which is deprecated now.
Graphs parameters can be defined in the `model_config_list` section just like classic models (recommended), or the `mediapipe_config_list` section which is deprecated and should not be used in new configurations.

Here is an example `config.json` file that defines two MediaPipe graphs. One with custom `graph_path` and one default:
```json
Expand All @@ -187,6 +187,8 @@ Here is an example `config.json` file that defines two MediaPipe graphs. One wit
```
In case the `mediapipe_graph_name_for_default_name` above, ovms will search for the default graph name `graph.pbtxt` in the `mediapipe_graph_name` directory relative to the `config.json` location.

Task specific parameters are not part of the standard model configuration and should not be defined in `model_config_list`. Instead, they are configured inside the MediaPipe graph (`graph.pbtxt`) which is referenced using `graph_path`.

Graphs can also be configured in the `mediapipe_config_list` section.
```json
{
Expand Down