Trying to resurrect some old pd-extended scripts that use "udpreceive" , "unpackOSC" and "routeOSC" and run them in 0.49.1. Whats the process for converting? I can see the OSC stream so I know the data is there.
Thanks,
Tom
OSC problems running pd-extended scripts in 0.49.1
Trying to resurrect some old pd-extended scripts that use "udpreceive" , "unpackOSC" and "routeOSC" and run them in 0.49.1. Whats the process for converting? I can see the OSC stream so I know the data is there.
Thanks,
Tom
@onewheeltom I made these to replace mrPeach objects as I transferred some very heavy patches to Vanilla....... MrPeach Vanilla.zip
The [routeOSC] is not a direct replacement, as it needs to be followed by a standard [route] object.
I tried making a dynamically created [routeOSC] by starting with a very large number of outlets and throwing away any that were unused, but it was not worth the effort.
I have done some pretty thorough testing, but there is always room for weirdness with OSC.
The mrPeach objects took care of different OSC formats automatically. The Vanilla objects need some tweeking unfortunately. You will need to know the format of the data (float symbol integer) and specify it in order to properly send a blob using [oscformat]
Another thing to look out for is how messages are routed after reception. [oscparse] chucks out any float in the message header as a symbol..... so it cannot be routed..... but otherwise it is a direct replacement for [unpackOSC] except that the slashes are stripped from the header.
Here is a solution for "float as symbol"........ vanilla osc.zip
I didn't make a [udpreceive] abstraction as I had never used it..... always using [dumpOSC]
David.
Oops! Looks like something went wrong!