You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After reading the code, I realised the code was writing the type specifiers the values in the wrong order, such that it would not be possible to support multiple values without a significant rewrite of the code.
After reading the code, I realised the code was writing the type specifiers the values in the wrong order, such that it would not be possible to support multiple values without a significant rewrite of the code.
For example, the convertor for float writes the type specifier and then immediately writes the value:
https://github.com/xemantic/xemantic-osc/blob/main/src/commonMain/kotlin/OscApi.kt#L72
But the correct thing to do is to write all the type specifiers first, then write all the values.
One of the messages in the official examples demonstrates this:
Examples are publicly documented along with the spec.
https://opensoundcontrol.stanford.edu/spec-1_0-examples.html#osc-message-examples
The text was updated successfully, but these errors were encountered: