OSC Documentation 0.59

©Patrick‐GillesMaillot 15 WINGOSC–V0.59

Or“ch”/”1”/”fdr”,whichtranslatestoOSCAddressPattern/ch/1/fdr:
‐>W,12B:/ch/1/fdr~~~
W‐>,32B:/ch/1/fdr~~~,sff~~~~‐oo~[0.0000][‐144.0000]

Intheexampleabove,thedata
[0.0000][‐144.0000]areasciiinterpretationsoftwo32bitsbig‐endian
floatdatavalues,eachrepresentedon4bytesasbinary.Thebinarydataactuallyreceivedisasshown
below,andinordertoeasethereadingofnumericalinformationinthisdocument,weusereadable
valuesinbracketsratherthantheactualbinarydata.Thecolorhighlightsaretheretohelpdistinguish
dataelements.
W‐>,32B:2f63682f312f6664720000002c736666000000002d6f6f0000000000c3100000

DependingontheOSCAddressPattern,WINGreturns'
,s'forstringsorenums,',sff'(ascii,rawpos,
floatvalue)forfloats,'
,sfi'(ascii,rawpos,intvalue)forints.Intheexampleabove,faderpositionisa
floatandWINGreturnstheasciirepresentation,theraw
[0.0..1.0]dataandtheactualfloatvaluein
dB.
Similarly,requestingthemutestateofchannelstrip1wouldreturn:
‐>W,12B:/ch/1/mute~~
W‐>,32B:/ch/1/mute~~,sfi~~~~1~~~[1.0000][1]
W‐>,32B:2f63682f312f6d75746500002c73666900000000310000003f80000000000001

ItshouldbenotedthatWINGwillacceptbothOSCpathorthenativehashdataforrepresenting
nodesorparameters;Indeed,allnodesandparametersintheconsoleareassignedabinaryaddress(a
hash)asexplainedinthechapteronnativeinterfacetotheconsole.Forexample,thechannel1mute
commandabovecanbesentasOSCAddressPatterns
/ch/1/mute~~asshown,or/#f50f69f8~~,and
wouldreturnthesamedataasshownabove.
0xf50f69f8isthehashforcommand“Channel1mute”.
ThefullsetofWINGhashvaluescanbediscoveredbyrecursivelytraversingtheJSONtreeofWING
nodes/commands,usingthenativebinaryinterfaceorOSCprotocol,butitisgenerallymore
convenienttousethemorestandardOSCnodenotation,ratherthanhexadecimalhashvaluesto
addresstheconsolefeatures.

ReceivingOSCdataonaspecificport
SomeOSCprogramswillrequestthatdataisreturnedonaspecificportratherthanbeingsentbackto
theportusedbytherequestingclientforsendingdata.Inordertoenablethiscapability,WINGOSC
includesanoptional,specialnotationforallOSCcommands:
AnyOSCcommandcanbeprefixedwiththe
/%<port>,with<port>intheform“12345”toenable
receivingtheexpectedanswerontothespecifiedportnumber.Forexample,theOSCrequest:
‐>W,20B:/%10027/ch/1/mute~~~

WillreceivetheexpectedreplyfromWINGonport10027,asshownbelow,usingasnifferprogramon
saidport.TheIPdoesnotchange.
