3 An OSC message is laid out in this form:
6 /path/of/command type parameter
9 The type is there to indicate what the parameter is. This gives
10 the idea that parameter types are quite strict and if the command
11 requires an Integer <em>"i"</em> then the controller had better send it.
12 However, the checking of the parameter type is left to the receiving
16 What this means in practical terms is that the surface can get away
17 with sending the wrong type of parameter. There are some places
18 where that just doesn't make sense. For example, a parameter that
19 is specified as a Float with a range of 0 to 1, could be sent as
20 an Integer, but would only have full scale and minimum value with
21 nothing in between. This is not much use for a fader, though OK for
25 There are a number of OSC controllers based on iOS and Android
26 tablets that only send or receive parameters as floats or text.
27 These controllers should have no problem sending bool or int values
28 as floats. Ardour will interpret the values as required.