Skip to main content
The Studio tab inside the Moverse Hub allows you to adjust various capturing parameters like camera encoding, the capturing session with respect to your local GPU hardware allocation, enable remote control and customize each different Moverse Capture Studio launch.

​
Configuration & Launch Sequence

1

Configuration Layout

Upon switching to the Studio tab () in the primary sidebar, or clicking “My Studio” in the Explore post-login screen, the following interface is presented. Properties are arranged across three primary categories: Camera Tuning (left), Session settings (middle), and Performance Tuning (right).
Moverse Hub Application Control Center

The Moverse Hub Studio tab interface.

2

Adjust Studio Session Configuration

Configure the parameters below to optimize the studio’s runtime behavior for your available hardware and capture session context:

​
Camera Tuning

​
Slider (Low to High)
default:"Medium"
Adjusts the raw data stream coding quality to match the data throughput limits of your local network.
​
Toggle (50Hz | 60Hz)
default:"50Hz"
Matches camera electronic shutters with local AC power grids to eliminate lighting flicker.
​
Dropdown Menu
default:"16:9"
Adjusts the camera viewport clipping and image dimensions.
​
Boolean (Toggle)
default:"False"
Disables parallel device connection. Use this exclusively to mitigate peak power spike issues for switches that may not handle them properly.

​
Capture Session

​
Fidelity Slider
default:"High Fidelity"
Uses more advanced models to improve quality, selectable performance profiles:
  • Highest Fidelity (Refer to image_3ddda2.png): Delivers the best quality using maximum GPU resources. Optimized for 1-2 actors with finger models; targets high-end hardware setups like the ~RTX 4090/5080.
  • High Fidelity (Refer to image_3ddd9a.png): Balanced quality against compute cost. Ideal for tracking 2-3 actors with fingers on standard ~RTX 3090/4080 systems.
  • Efficient (Refer to image_3ddd7e.png): Scales down compute cost to support higher actor counts or lower end compute hardware (~RTX 3060/4070).
  • Very Efficient (Refer to image_3ddd63.png): Minimal compute resources required. Used to run up to 4 actors with fingers.
​
Toggle (Single | Multi)
default:"Single"
Switching the toggle to Multi (shown in image_3ddd1e.png) to capture 2, 3, or 4 actors.
Increasing your actor count requires more GPU resources.
​
Boolean (Toggle)
default:"False"
When toggled on, configures the launched studio capture session to allow for remote control. Enabling this (as shown in image_3dda18.png) will offer a selection of network interfaces to use, along with an IP address and port element to configure if necessary.
​
Boolean (Toggle)
default:"False"
Enables a higher level of diagnostic log data. Used when troubleshooting to send logs to our support team.

​
Performance Tuning

​
Selector (Default | Low | Very Low)
default:"Default"
Experimental Configures the studio for low latency streaming. Low and Very Low are trade-offs between throughput and quality to deliver highly responsive outputs for real-time embodiment or interaction.
​
Boolean (Toggle)
default:"False"
Experimental Configures the studio for higher FPS camera streaming.
3

Launch Moverse Capture Studio

Verify your configuration matches your capturing context. Click Start a new capture session to launch the Moverse Capture Studio and start the capturing session.
Looking for Precise Hardware Benchmarks?For more information regarding tuning capturing sessions against GPU hardware and actor counts, see our NVIDIA GPU Support Guide.

​
Process Dependencies

Do Not Close Moverse Hub:The Moverse Capture Studio application runs as a dependent child process of the parent Moverse Hub. Closing or killing the Moverse Hub window will immediately terminate your live studio tracking stream session. The Hub launcher application must remain open in the background for the duration of your session.