With the release of version 25.01 SPAT Revolution introduces an exciting feature: the support of Relative OSC messages. This innovative functionality offers the capability to adjust parameter values dynamically, without needing to know the current value.
Absolute vs. Relative OSC messages
Traditionally, OSC messages require users to specify the desired value for a parameter. This approach is ideal for scenarios like setting precise trajectory values. For example, to set a parameter to a specific value, we historically used an Absolute OSC message:
/room/1/gain/ -10
In contrast, Relative OSC messages allow users to define an offset rather than a specific value. This means you can adjust parameters incrementally, such as increasing room gain by +3dB or decreasing source distance by -2m. This flexibility is amplified when you don’t have bidirectional integration, as the parameter current value is unknown, and can simplify the interaction with SPAT Revolution.
How Relative OSC messages work
Relative OSC messages follow the same structure as standard OSC messages, with the addition of a path keyword. For instance, to offset the room gain by +3db, you would use:
/room/1/relative/gain 3
This consistency ensures that the OSC path structure remains unchanged, allowing users to utilize wildcards to target multiple objects or add interpolation timing. For example, to offset the distance of all sources by 2 meters over 5 seconds, you would use:
/source/*/relative/dist 2.0 5.0
Getting started with Relative OSC messages
To assist you in leveraging this new feature, we provide a QLab5 template with examples of Relative OSC messages. This resource will guide you through your initial steps and help you explore the full potential of Relative OSC.
You can find all available controls in the updated OSC table, which includes all available OSC commands in SPAT Revolution.
We encourage you to try out this new feature and share your template and use cases with us!
