Since the last update of VL.IO.OSC to handle array types, a bug has been introduced.
The OSCReceiver can still convert the arguments to a Float32, Vector2, Vector3, Vector4 and Spread<Float32>.
But can’t convert to Spread of “multi-element types” like Spread<Vector2> or Spread<Vector3>.
(Nothing is returned by the OSCReceiver in that case).
This bug does not only concern OSC array ([ffffff]) but also regular set of arguments (ffffff).
Easy to reproduce, simply send a Spread<Float32> and on the OSCReceiver side, plug a IOBox of the mentions types to visualize the issue.
Not sure I understood right.
But to me this doesn’t sound like a bug, more like how you want to interpret the data - so it’s up to the user to do that.
VL.IO.OSC was updated recently, and the only way to have the bug in your VVVV is to update it manually: nuget install vl.io.osc -version 2.0.7
I consider it a bug because before that update, we could plug the OSCReceiver to any type of data, and it would smartly adapt, it’s not the case anymore.
If it was always like this, I wouldn’t have reported it!
But it may break a lot of existing patches if it’s pushed like this.
And ValuesToVectors does fix my issue, but the update could still break a lot of existing patches.
And I do think it was a good thing that the OSCReceiver could adapt itself (make sense in the OSC context).
