OSC Commands

MadMapper allows you to map any OSC address to any parameter using the Controls dialog found under the Edit menu. However, all parameters also have predefined addresses, allowing you to directly send OSC messages to those addresses to change parameters. Using predefined addresses means you bypass any input range, output range, or filtering settings within MadMapper.

You can find predefined OSC addresses using the following methods:

OSC Query Support

MadMapper fully supports the OSC Query protocol. OSC Query acts as a dynamic network directory, allowing software to expose its entire OSC address space to the local network.

Because of this, you do not have to memorize or manually type out predefined addresses. You can use OSC Query-compatible software—such as the OSC Query Browser, Chataigne, or another copy of MadMapper on another computer—to automatically discover MadMapper on your network. These external applications can actively browse MadMapper's available parameters, view current values, and instantly link commands to control MadMapper from outside sources.

OSC Routing & Preferences

To enable OSC Query, define your incoming and outgoing OSC network ports, or toggle network discovery, navigate to the Preferences > OSC / MIDI tab. It is crucial to ensure your external controllers and MadMapper are communicating over the correct ports (typically Port 8000 for incoming OSC data).

 

OSC Channels List

Understanding the basic data types is essential when sending OSC commands to MadMapper. Depending on the parameter, you will need to send a specific type of value:

Below is the consolidated list of MadMapper's internal OSC addresses.

Application

System & Session

View & Interface

Preview Controls

Media Management

Master

Levels & Speed

Global BPM

Engine & Output Freezes

Master Color Control

Output Cursors & Overlays

Media

Note: Replace [media_name] with the exact name of the file in your media bin (e.g., My_Video or Lines). Generative materials and shaders will expose their own unique parameters under their media name.

General Selection

Specific Media Actions

Material/Generator Specific Parameters

Modules

Outputs

Note: Replace [1-X] with the specific hardware output or buffer number you are targeting (e.g., Video-Output-1).

Video Outputs & Buffers

Laser Outputs & Buffers

DMX Outputs

Timelines & Conductor

Global Timeline Actions

Timeline Editor

Master Conductor Controls

Conductor Markers

Conductor Montage Parameters

Column Execution

Cue Matrix (Grid Execution) Note: Replace [1-16] with your Column/Cell number, and [1-32] with your Row number. You can also use col_current to target the currently active column.

(Scenes use the identical structure to cues, mapped as scene_row_1)

 

Note on Grid Exclusivity & Transitions: MadMapper enforces grid exclusivity per row. If you start a new Scene, Cue, or Timeline on a specific row (e.g., Row 1), any currently playing Timeline on that identical row will be automatically stopped.

However, if your newly triggered Timeline has a Fade Time (transition duration) set:

  • Audio & Montage Crossfades: Any audio or montage tracks running in the "killed" Timeline will gracefully fade out over the transition duration of the newly started Timeline.

  • For example, if you trigger a Timeline with a 3-second fade time on a row where an audio clip is already playing, MadMapper will automatically execute a 3-second crossfade (fading out the old audio while fading in the new).

  • Continuous Playback: The previously running Timeline will actually continue its playback internally strictly for the duration of that transition fade, ensuring a seamless visual blend for any active montage tracks.

 

 

Page Content