Max to vvvv via osc

vvvv beta general
1

hi,
i try to send osc messages from max to vvvv beta11, using [Open Sound Control](Open Sound Control) and upd-write on the max side. in vvvv, UPD gets this kind of messages:

{CODE(ln=>1)}#bundle  loudness ,f Á ÇU#bundle  noisiness ,f >Ǐ²#bundle  pitch ,f B¶G#bundle  ˆlisting ,fffffffffffffffffffffffff Â¥=Âœw•FÚÂoY ÂCò?ÂH½ÂVÏ£ÂRLÂ
+›ÁæÌËÁí³R¾Úå,ÂcÂBð«ÂDª€Â¿ÂYÂWƒÂ0Š­Âe¶NÂ^ClÂsôæ‚v¥ÂO˜¨Â—•F#bundle  loudness ,f Á§$©#bundle  noisiness ,f >Èæ#bundle  pitch ,f Bµé~#bundle  ˆlisting ,fffffffffffffffffffffffff žß(›ƒlÂŽ==ÂrëSÂW9)ÂFþdÂGdÂ#©¬Â\ŸÂηÂú ¿›©Â3€qÂKyøÂG×èÂ
†Â[âaÂ\¦eÂ6gÂ[)ÙÂb ÂkWeÂ}H€ÂUz™P

  • bundle  loudness ,f Á¯ ÷#bundle  noisiness ,f >Ì[#bundle  pitch ,f B¶"k#bundle  ˆlisting ,fffffffffffffffffffffffff šæ’˜í’àåÂ](*#bundle  pitch ,f B¶"k#bundle  ˆlisting ,fffffffffffffffffffffffff šæ’˜í’àåÂ)Œ¨Â>ñzÂ4ú(Âa ÂjŸÂ@aÂôÈÀ ónÂ-œ&Â\ªÂN±ÑÂ{ÂT¤ÞÂdÅNÂ8â§Â^ãûÂgjåÂx7B€áãÂgÊA›œ ^

(saved output to UPDoutput.txt)

can’t decode this with OSCDecoder. has it something to do with the bundled messages issue? thought it should be resolved in beta11? i am a noob.

UDPoutput.txt (816 Bytes)

2

olá!
sorry for not answering and right now, I have no Idea why it’s all so scrambled. Are u sure, that you’re not sending it wrong and vvvv get’s it that way.

Just noticed: You’re using UDP to recieve OSC? Why not use the OSC nodes?

3

halooooorrrrr.

i dont know about the max-side (if you can use something else than udp-write? are there different versions of this node?) but i had the same setup (sending osc: max->vvvv) running recently without any problems.

where did you save the above output from? it doesnt look correct. there are at least ‘/’ (slashes) missing in front of the message names. the garbage is fine. it is the encoded float-data.

@ampop: osc-nodes alone wont help. they only do the encoding/decoding. still you need other nodes to receive data via the network (eg. the udp server)

4

okay sorry, the solution was to add slashes. didn’t think about it because strangely pd accepted the same osc messages without slashes -i guess thats not conform to the OSC standard (if there is one).

5

right. there is a standard specification, that requires slashes.