Problem with OSC
Dec 6, 2006 at 12:53pm
Problem with OSC
I am having difficulty parsing OSC messages I send with FLOSC in Max. I can print them from udpreceive perfectly, but it seems impossible to use that data that comes directly.
Therefore I tried to use the opensourcecontrol object but when I link the udpreceiver to the opensoundcontrol, no data comes from any of the outputs (checked with print).
Any ideas as to what could cause this problem?
Dec 6, 2006 at 3:43pm
Quote: datadigit wrote on Wed, 06 December 2006 13:53
Check out the cnmat_compatibility subpatcher in the udpreceive help file. The OpenSoundControl object needs the udpreceive to have the CNMAT flag to understand its output. I believe flosc outputs cnmat compatible osc.
I made this some time ago with (a customized version of) flosc. The source of the flash file is downloadable on that page.
Dec 6, 2006 at 9:53pm
On 6-dec-2006, at 16:43, Mattijs Kneppers wrote:
The phrase “CNMAT compatible OSC” is a bit misleading here.
the updrecieve object is capable of parsing OSC packets into max
The OpenSoundControl object is also capable of parsing OSC packets,
Now that otudp is deprecated and replaced by udpreceive, the CNMAT
in fact, “CNMAT flag” is a bit misleading too.
Dec 7, 2006 at 10:16am
Maybe I’m thinking in the wrong directing, focusing on the OSC message here.
This is the Patcher that demonstrates my problem. The Max output I get when sending a OSC packet is this:
*error: number: doesn’t understand “234″
I want to use that number 234, but it is not recognized as Max data.
Dec 7, 2006 at 11:36am
Ah, posting a patch is always good practice.
Could it be that the int is parsed as a symbol so that the numbox doesn’t recognize it? Perhaps in flash you need to add an int explicitly as an int and not as a symbol or string. Have a look at the patch below. This works here. Does it work for you? What does the prepend set output say when you receive the message from flosc?
#P window setfont “Sans Serif” 9.;
Dec 7, 2006 at 8:48pm
Quote: datadigit wrote on Wed, 06 December 2006 04:53
Both of the patches posted in this thread work fine for me. CNMAT’s “printit” object is also a handy way to debug some of these problems, it tells you if a message is a symbol or an int or something else.
It would help to know what platform you are running, etc. I haven’t had any confirmed reports of problems with the Max implementation of OSC, so I start to suspect flosc…
You must be logged in to reply to this topic.