Processes
Overview
The Processes tab controls the update rates of several core systems within Grid Studio.
These settings define how frequently internal systems update and process data. Adjusting these values can influence both system responsiveness and overall performance.
In most cases, the default values are suitable for typical projects. However, when working with real-time data pipelines, especially tracking systems, these settings can become critical and should match the refresh rates of connected systems.
Main Process Rate
The Main Process Rate defines how often the core system loop of Grid Studio updates.
This update rate is particularly important when working with real-time tracking data that is sent to external systems such as:
real-time rendering engines (e.g. Unreal Engine)
media servers
other real-time processing systems
In these scenarios, it is important that the entire data pipeline uses the same refresh rate. If the tracking system, Grid Studio, and the target system run at different update rates, this may introduce latency, jitter, or inconsistent motion updates.
For example, if tracking data is processed at 30 FPS, the Main Process Rate should typically match this value.
For systems that do not rely on real-time spatial data, the exact value is usually less critical.
GUI Refresh Rate
The GUI Refresh Rate controls how often the user interface updates.
This affects how frequently visual elements in the editor refresh, including:
parameter updates
editor views
monitoring displays
Increasing this value can make the interface appear more responsive, while lower values may reduce CPU load in complex projects.
This setting only affects the editor interface, not the internal processing of data.
Viewport Tick Skip
The Viewport Tick Skip setting controls how often the 3D Viewport updates relative to the main process loop.
Higher values reduce the frequency of viewport redraws, which can improve performance when working with complex scenes or large numbers of objects.
Lower values update the viewport more frequently, resulting in smoother visual feedback but potentially higher system load.
Main Timeline
The Main Timeline setting defines which timeline object should be used for certain context-based timeline operations.
Grid Studio supports multiple timelines within a project. Some interface actions need to know which timeline should be used when performing operations automatically.
For example:
adding a keyframe from a parameter context menu
creating timeline-based actions from interface tools
If no timeline is defined here, these actions may create a new timeline automatically.
Setting a Main Timeline ensures that these interactions use the intended timeline object.
Display Time
The Display Time option defines how time values are displayed in the user interface.
This setting affects only the visual representation of time and does not change how time is internally processed.
Available display formats include:
Timecode with Milliseconds
Timecode with Frames
Timecode with Seconds
Seconds
Frames
These formats control how time is shown in editors such as timelines and other time-based interfaces.
Related Topics
Timeline Working with timeline objects and time-based events.
Tracking Systems Processing real-time tracking data.
Viewport Understanding viewport updates and rendering behavior.
Last updated