OSC Address Reference

Complete reference for JamWide’s bidirectional OSC server. All addresses are under the /JamWide/ namespace.

Defaults

Controllable Parameters

These addresses accept incoming OSC messages (float argument) and send feedback when values change.

Master

Metronome

Local Channels (1-4)

Replace {n} with channel number 1 through 4.

Note: Channel numbering is 1-based in OSC (channels 1-4), matching what you see in the UI.

Session Telemetry (Read-Only)

These addresses are send-only. JamWide broadcasts them when values change. Incoming messages to these addresses are ignored.

VU Meters (Read-Only)

VU meters are broadcast every 100ms regardless of whether values have changed. Range is 0 to 1.

Master

Local Channels (1-4)

Volume Mapping

JamWide uses two volume namespaces:

Normalized (default): /volume addresses use a 0-1 range that maps to the APVTS parameter range of 0-2 (linear gain). This means:

• 0.0 = silence (-inf dB)
• 0.5 = unity gain (0 dB)
• 1.0 = +6 dB (maximum)

dB: /volume/db addresses use decibels directly:

• -100 dB = silence
• 0 dB = unity gain
• +6 dB = maximum

For TouchOSC faders, use the normalized namespace with range 0-1. The dB namespace is useful for precise control or display purposes.

Pan Mapping

All pan addresses use a 0-1 range:

• 0.0 = hard left
• 0.5 = center
• 1.0 = hard right

This applies to both local channel pan and metronome pan, so your TouchOSC layout can use the same knob range for all pan controls.

Echo Suppression

JamWide uses echo suppression to prevent feedback loops between the plugin and the control surface. When a value is received via OSC, it is marked as “OSC-sourced” and skipped on the next outgoing send tick. This means:

• Move a fader in TouchOSC: JamWide updates but does not echo the value back
• Move a fader in JamWide: TouchOSC receives the update
• No oscillation between the two

The suppression window is one timer tick (100ms), which is imperceptible.

Bundle Mode

All outgoing OSC messages are grouped into a single OSC bundle per 100ms tick. This provides:

• Atomic updates (all values in a tick arrive together)
• Fewer UDP packets (one bundle instead of many individual messages)
• Lower network overhead

Error Handling

• Unknown addresses are silently ignored
• Invalid argument types (not float or int) are silently ignored
• Out-of-range values are clamped to the parameter’s valid range
• Port bind failures are shown in the config dialog and turn the status dot red

Configuration

Click the grey/green/red OSC dot in the connection bar footer to open the config dialog:

Settings persist across DAW save/load cycles. Fields remain editable when OSC is disabled, so you can configure ports before enabling.

Remote Users (1-16)

Replace {idx} with a 1-based index. Slot 1 = first connected user, slot 2 = second, etc. When users leave, subsequent indices shift down. The roster name broadcast tells the control surface who is in each slot.

Group Bus Control

Sub-Channel Control

Replace {n} with a sequential 1-based channel index (NOT the sparse NINJAM bit index). /ch/1 is the user’s first channel, /ch/2 is the second, etc.

Remote VU Meters (Read-Only)

Template note: The shipped TouchOSC template omits remote VU meters intentionally for layout density reasons. The OSC server still broadcasts them.

Roster Broadcast (Read-Only)

Sent when users join or leave the session. Empty string for unused slots.

Video Control

Video

Display modes: Grid (default, all participants in the companion page) and popout (per-user separate windows via /video/popout/{idx}). There is no dedicated “mode switch” OSC address. Grid mode is always active in the main companion; popouts are additive per-user windows. This satisfies VID-11 “switch display modes” – the user switches from grid-only to grid+popout by triggering popouts.

Session Control

Connect/Disconnect via OSC

Connect validation: Host is required. Port defaults to 2049 if omitted. IPv6 addresses must be in brackets (e.g. "[::1]:2049"). Maximum string length is 256 characters.

TouchOSC Setup Guide

Quick Start

1. Download JamWide’s TouchOSC template: assets/JamWide.tosc
2. Import the .tosc file into TouchOSC (File > Open)
3. Configure the OSC connection (see below)
4. Switch to Play mode and start controlling

Connection Setup

In JamWide (click the OSC dot in the footer):

In TouchOSC (Connections > OSC > Connection 1):

Finding your IP:

• macOS: ifconfig en0 | grep "inet " or System Settings > Network
• Windows: ipconfig in Command Prompt
• iPad/iPhone: Settings > Wi-Fi > tap your network > IP Address

Template Contents

The shipped template (JamWide.tosc) targets iPad landscape (1024x768) and includes:

The OSC server supports 16 remote user slots. The template shows 8 (covers most sessions). You can extend it in the TouchOSC editor if needed.

Troubleshooting

• Nothing happens when moving faders: Check that both ports match between JamWide and TouchOSC. The Send Port in TouchOSC must equal the Receive Port in JamWide (default: 9000).
• Faders don’t update in TouchOSC: Check JamWide’s Send IP points to your TouchOSC device’s IP.
• OSC dot is red: Port is in use by another application. Try different ports (e.g. 9002/9003).
• Feedback oscillation: Should not happen (echo suppression is built-in). If it does, check that you don’t have two OSC sources sending to the same port.