A1R

OSC

Send and receive OSC to integrate A1R with other gear.

Pro+ A1R speaks OSC both ways:

The OSC panel — send to gear (Tracks) and receive remote control.
The OSC panel — send to gear (Tracks) and receive remote control. phone

The OSC panel — send to gear (Tracks) and receive remote control.

Sending OSC: the +OSC track

  1. Add a track named +OSC to your Arrangement.
  2. Drop clips on it wherever you want a message fired. The clip name is the raw OSC message, address first, then arguments separated by spaces — e.g. /light/scene 4 or /video/play intro.mp4.
  3. Set the target IP and port in the OSC settings, and switch OSC out on.

As the playhead crosses each clip during playback, its message is sent. Use the Test button in the settings to fire a test message and confirm the target device is receiving.

Receiving OSC: OSC Remote

In the OSC settings popup, turn on the OSC Remote toggle and choose a UDP listen port. The Random button picks a safe uncommon port for you (ports must be ≥1024). Any device on the network can then send the commands below to the A1R computer's IP on that port.

Command reference (input)

AddressArgumentsWhat it does
/global/playStart playback (also accepts /global/startPlaying, /global/continuePlaying).
/global/pausePause.
/global/stopStop.
/global/playPauseToggle play / pause (also /global/playStop).
/global/tempobpmSet the tempo.
/global/tempo/adjustdeltaNudge the tempo by a relative amount (e.g. -2).
/global/startRecordingArm arrangement record and start playing.
/global/stopRecordingStop recording.
/global/toggleRecordingToggle recording.
/global/quantizationvalueSet launch quantization (e.g. none, 1, 2, 1/4).
/setlist/jumpToSongn | name | RANDOMJump to song number n (1-based) or by name.
/setlist/jumpBySongs±nJump forward / back by n songs.
/setlist/jumpToSectionn | nameJump to section number n (1-based) or by name.
/setlist/jumpBySections±nJump forward / back by n sections.
/setlist/jumpToTimebeatsSeek to a beat position on the timeline.
/setlist/setLocatorsFromClipsRun Auto Locator.
/setlist/toggleStopToggle "Stop After Song" for the current song.
/settings/jumpModemanual | quantized | otherSet the jump mode.
/settings/autoJumpToNextSong0/1Turn the Engine (auto-advance) on or off.
/mixer/<slot>/volume0–1Set a mixer slot's fader (slot 0 = MAIN).
/mixer/<slot>/mute0/1 | toggleMute / unmute a slot.
/mixer/<slot>/solo0/1 | toggleSolo / unsolo a slot.
/mixer/<slot>/fadeTolevel [speed]Fade a slot's volume to a level over time.
/click/mute · /click/solo0/1 | toggleMute / solo the click track.
/midi/send/noteOn|noteOff|cc|pc|rawoutput, channel, num, value…Send MIDI out through A1R (e.g. /midi/send/cc 1 1 20 127).

Feedback: /subscribe

A1R pushes live status to any controller that subscribes. Send /subscribe <ip> <port> (or just /subscribe — the sender's address is used) and A1R starts sending updates whenever a value changes, plus a /heartbeat roughly every 2 seconds so your controller can detect a lost connection. Send /unsubscribe to stop.

Feedback addressValue
/global/isPlaying · /global/isPaused0/1 transport state.
/global/tempoCurrent BPM.
/global/timeSignatureNumerator, denominator.
/global/beatsPositionPlayhead position in beats.
/global/humanPosition · /global/currentMeasureBar and beat-in-bar.
/setlist/activeSongName · activeSongIndex · activeSongColor · activeSongDescriptionCurrent song info.
/setlist/activeSongDuration · activeSongProgress · remainingTimeInSongSong timing (progress is 0–1).
/setlist/activeSectionName · activeSectionProgress · nextSectionNameCurrent / next section.
/setlist/songs · songCount · songColors · songDurationsThe full setlist (in Sort order).
/setlist/sections · sectionCountSections of the active song.
/setlist/nextSongName · remainingTimeInSetWhat's next, and time left in the whole set.
/network/ip · /network/hostSent once on subscribe — the A1R machine's IP and hostname.
/mixer/<slot>/volume · muted · soloedLive mixer state per slot.
/heartbeatKeep-alive ping (~every 2 s).
The command set follows the same conventions as popular setlist controllers, so most existing TouchOSC / Companion templates need little more than an IP and port change.