OSC Documentation 0.59
©Patrick‐GillesMaillot 14 WINGOSC–V0.59
WINGOSCMessages
Inthefollowingparagraphs,weassumeacommunicationlinkexistsbetweenWINGandaclient
program,andcommunicationtakesplacewithaWINGconsoleataknownIPaddress,usingUDPon
port
2223.
Inthetextshownbelow,thecharacter
‘~’willrepresentaNULLbyte(\0).Patterns‐>WandW‐>
representdatasenttoWINGanddatareceivedfromWINGfollowedbytheactualnumberofbytes
transmittedorreceived,respectively.
RetrievingWINGconsoleinformationcanbecompletedbysendingtheOSCAddressPattern“
/?”
‐>W,4B:/?~~
W‐>,80B:
/?~~,s~~WING,192.168.1.71,PGM,ngc‐full,NO_SERIAL,1.07.2‐40‐g1b1b292b:develop~~~~
Theactualbytesexchangedaredisplayedbelow(OSCisabinaryprotocol)
‐>W,4B:2f3f0000
W‐>,80B:
2f3f00002c73000057494e472c3139322e3136382e312e37312c50474d2c6e67632d66756c6c2c4e4f5f5345524
9414c2c312e30372e322d34302d6731623162323932623a646576656c6f7000000000
ThelinebelowisusingamorecompliantOSCformat,andwillresultinthesameanswer
‐>W,8B:/?~~,~~~
Reading(Get)ParameterandNodedata
TherearetwomainwaystogainaccesstoWINGdata:usingone‐parameter‐at‐a‐timeorusing
“nodes”.
WING“nodes”areagreatwaytoaccessmultipleparametersatatime,andthereforemaximize
communicationbandwidthwiththeconsole.NodesarerepresentedasstringOSCDataTypeandare
zeroterminated(
\0byteendingthestring).
NodesarealsoagoodwaytodiscoverWINGparameters,astheyoffereasyaccesstothefullmapof
theJSONinternaldatastructures.
WeshowbelowWING’sfirstlayerofJSONstructure,andstartingattheroot,retrievedusingOSC.
‐>W,4B:/~~~
W‐>,116B:
/~~~,ssssssssssssssss~~~$stat~~~cfg~$syscfg~io~~ch~~aux~bus~main~~~~mtx~dca~mgrp~~~~fx~~car
ds~~~play~~~~rec~$ctl~~~~
RetrievingaWINGsingleparameterisquiteeasy:YoumustensureyourOSCrequestpointstoaleaf
oftheJSONstructure(i.e.,thereisnomorehierarchydataafterthecurrentone).Thisisthecasefor
thefadervalueofachannelstripforexample,oritsmutestate.ChannelStrip1faderisrepresented
asfollows: