OSC Documentation

Hi there,

I was wondering if there was any documentation for the OSC addresses used by Onyx. I am able to control the “known” addresses but I am wondering if I can control the extra 10 playbacks that are to the right of the main playbacks over OSC as well. Can’t find it in the TouchOSC editor. I’m also wondering if I can control the faders that are present on the M-Play. Again, it would be nice to have a full documentation of how OSC can be used inside Onyx.

Thanks for the help!

1 Like

Hi,
This is the OSC documentation about the M-Series software. I guess a lot must be the same :wink:

OSC

All OSC addresses start with ‘Mx’.

There are 7 categories:

- LED buttons

- LCD buttons

- faders

- belts

- scroll wheels

- playback

- configuration

LED/LCD buttons, faders, belts and scroll wheels have an identifier in their path.

This identifier is mapped to a real physical control element on the desk.

The console layout with the identifiers can be found in the iPad and iPhone Martin-Mx-series_V1.10.touchosc file.

You can edit this file with the TouchOSC Editor from Hexler.

iPad and iPhone touchOSC layout (under M-series -> OSC remote access):

http://www.martin.com/controllersupport/

TouchOSC Editor:

http://www.hexler.net/software/touchosc

------------------------------------------------------------------

LED Button

/Mx/button/

/Mx/button//led

buttonId: required identifier

led: indicates the led status (optional)

example: /Mx/button/5511

/Mx/button/5511/led

/Mx/button/4201

Button action (OSC client to console)

Path:/Mx/button/

Value: 0 (up), 1 (down)

LedState (console to OSC client)

Path:/Mx/button//led

Value: 0 (off), 1 (on)

LedColor (console to OSC client)

Path:/Mx/button//led/color

Value: blue (on, off), red (blink)

------------------------------------------------------------------

LCD Button

/Mx/button/

buttonId: required identifier

example: /Mx/button/6101

/Mx/button/6102

Button action (OSC client to console)

Path:/Mx/button/

Value: 0 (up), 1 (down)

BackgroundColor (console to OSC client)

Path:/Mx/button//color

Value: green, red, blue, orange, gray, blue, purple, yellow

Text (console to OSC client)

Path:/Mx/button//text/

Value: string that represents the name

TextColor (console to OSC client)

Path:/Mx/button//text/color

Value: green, red, blue, orange, gray, blue, purple, yellow

------------------------------------------------------------------

Fader

/Mx/fader/

faderId: required identifier

example: /Mx/fader/4203

/Mx/fader/2202

Value (both directions)

Path:/Mx/fader/

Value: integer (0 - 255)

------------------------------------------------------------------

Belt

/Mx/belt/

/Mx/belt//channelValue

/Mx/belt//channelName

beltId: required identifier

example: /Mx/belt/6112

/Mx/belt/6112/channelValue

/Mx/belt/6112/channelName

Value (OSC client to console)

Path:/Mx/belt/

Value: integer (> 0: up, <= 0: down)

Name (console to OSC client)

Path:/Mx/belt//channelName

Value: string that represents the name

Text Value (console to OSC client)

Path:/Mx/belt//channelValue

Value: string that represents the value (DMX or percentage)

ProgrammerMode (console to OSC client)

Path:/Mx/belt//color

Value: gray (none), orange (inactive), red (active)

EffectMode (console to OSC client)

Path:/Mx/belt//channelValue/color

Value: gray (none), orange (inactive/active)

Linking (console to OSC client)

Path:/Mx/belt//channelName/color

Value: gray (off), yellow (on)

------------------------------------------------------------------

Scroll wheel

/Mx/scroll//

wheelId: required identifier

direction: up, down, left, right

example: /Mx/scroll/4110/up

/Mx/scroll/4110/down

Button action (OSC client to console)

Path:/Mx/scroll//

Value: 0 (up), 1 (down)

------------------------------------------------------------------

Playback actions

/Mx/playback/page//

action: go, pause, release, select

example: /Mx/playback/page1/1/go

/Mx/playback/page5/20/pause

/Mx/playback/page9/3/release

NOTE: No playback feedback information is send from the console to the OSC client.

This will be added at a later moment.

------------------------------------------------------------------

Configuration

Current devicespace (console to OSC client)

Path:/Mx/configuration/deviceSpace

Value: devicespace

Devicespace down (OSC client to console)

Path:/Mx/configuration/deviceSpace/down

Value: 0 (up), 1 (down)

Devicespace up (OSC client to console)

Path:/Mx/configuration/deviceSpace/up

Value: 0 (up), 1 (down)

Refresh all console elements (OSC client to console)

Path:/Mx/configuration/deviceSpace/refresh

Value: 0 (up), 1 (down)

1 Like