Closed mzed closed 5 years ago
I understand this now, thanks to John. Wekinator doesn't like doubles, which is what I'm getting from o.pack. Unfortunately, o.downcast isn't part of the Windows release.
hey @mzed I think o.downcast should be in the windows release, but in the /dev folder which isn't automatically added to the package search path. do you see it there?
I think probably we could move o.downcast out of the dev folder in the near future. If I remember correctly, we recently added a blob type to deal with sub bundles. but probably there are some other pending type handling questions.
Super. I pulled it from /dev.
Messages created using o.pack -> o.downcast
are understood by Wekinator. OSC 1.0, ftw.
I just ran into a funny inconsistency when trying to use o.pack.
I think this is related to #2
Here’s a patch:
Using [o.pack /foo] creates a different OSC packet than sending “/foo 6.66” directly to udpsend. udpreceive doesn’t understand the message, although I can get it if udpreceive is in full packet mode.
More serious for me, Wekinator doesn’t understand the o.pack OSC message, either.