Skip to content

OSC

OSC

Overview

The OSC device enables OnlyView to send and receive OSC (Open Sound Control) messages over UDP networks. OSC is a network protocol for communication between computers, sound synthesizers, and other multimedia devices that is optimized for modern networking technology.

Category: Communication Device
Hardware Requirements: Network interface connected to OSC network
Software Requirements: None (protocol handled internally)
Compatibility: OSC 1.0 specification

Setup and Configuration

Network Configuration

Output Configuration: - Send to everybody (broadcast): Broadcasts OSC messages to all devices on the selected network interface - Broadcast Interface: Select the network interface to use for broadcast messages - Send to a specific IP: Sends OSC messages directly to a specified IP address - Receiver IP: Target IP address for unicast messages

Port Configuration: - Output Port: UDP port number for sending OSC messages (default: 7000) - Input Port: UDP port number for receiving OSC messages (default: 7001)

Built-in OSC Commands

OnlyView responds to several built-in OSC message formats: - /ov/quickkey/[id] 1: Execute a QuickKey by ID number - /ov/timeline/[id]/grandmaster [0-100]: Set timeline grandmaster level (0-100%)

Actions

Available Actions

Emit Message: Send a custom OSC message with specified path and value. - Parameters: OSC Path, Data Type (Integer/Float/String), Value - Usage: Send custom OSC messages to external applications or devices

Timeline Integration

OSC actions can be triggered from Command Cues on any timeline: 1. Add a Command Cue to a timeline layer 2. Set the cue's device action to "Emit Message" 3. Configure the OSC path and value parameters 4. The OSC message will be sent when the timeline playhead reaches the cue

ActionGraph Nodes

OSC Input

Purpose: Receives OSC messages from the network and outputs the contained values. - Inputs: Device (OSC device selection) - Outputs: Value (Float or Vec3 depending on received message type) - Properties: - Device: Select the OSC device to monitor - OSC Path: The OSC address pattern to listen for (e.g., /osc/1/fader1)

This node listens for incoming OSC messages matching the specified path and forwards the received values to connected nodes. It only supports simple messages:

  • One numer OR three numbers, nothing else
  • No multi-message OSC bundles. Some software like TouchDesigner or Millumin only send bundles; use OSC Full Input instead.

OSC Full Input

Purpose: Advanced OSC input node that dynamically creates outputs based on the received message structure. - Inputs: Device (OSC device selection) - Outputs: Dynamic outputs created based on received OSC message structure - Properties: - Device: Select the OSC device to monitor - OSC Path: The OSC address pattern to listen for

This node automatically adapts its output structure based on the complexity of incoming OSC messages, creating multiple outputs for multi-parameter messages. Click "Update outputs"; and on the next message, the node will have output slots that match the message's parameters.

Note that the parameters of OSC messages are not names, so Onlyview can't give meaningful names to these output slots. Instead, the slots are named according to the type of the parameter ("i" for an integer parameter, etc)

OSC Output

Purpose: Sends OSC messages to the network with various data types. - Inputs: Integer, Float, Vec3, Quaternion, Color, String - Outputs: None - Properties: - Device: Select the OSC device for sending - OSC Path: The destination OSC address (e.g., /mixer/channel/1/volume) - Send Event: Trigger to send the message

Connect data from other nodes to the input slots, configure the OSC path, and trigger the Send Event to transmit the message. You only need to connect one slot; if you connect more, several messages will be sent.

TUIO Output

Purpose: Specialized OSC output for TUIO (Tangible User Interface Objects) tracking data. - Inputs: Trackings (tracking data from tracking devices) - Outputs: None
- Properties: - Device: Select the OSC device for sending - TUIO Configuration: Settings for TUIO message format

This node converts tracking data from devices like OptiTrack or BlackTrax into standardized TUIO messages for multi-touch and tangible interface applications.