GVA1994

We're trying to send strings from Unity to Max. We're using these objects in Unity for sending UDP packets: https://forum.unity.com/threads/simple-udp-implementation-send-read-via-mono-c.15900/

We are able to receive in Max through udpreceive, however we're getting errors as Max tries to convert what's incoming into a message: "OSC Bad message name String: DataAfterAlignedString: Unreasonably long string Dropping entire message"

If we add a symbol argument to udpreceive to prevent Max from trying to convert the incoming data, the data we receive seems to be different from what we are sending (see attached images). First image shows what we are receiving in Max, second image shows what we are sending in both ASCII and Hex (monitored through plug-in outside of Max).

Ideally we would just like to send the strings over. Any help is appreciated!

afbeelding.png

Hi,

We're trying to send strings from Unity to Max. We're using these objects in Unity for sending UDP packets: https://forum.unity.com/threads/simple-udp-implementation-send-read-via-mono-c.15900/
We are able to receive in Max through udpreceive, however we're getting errors as Max tries to convert what's incoming into a message: "OSC Bad message name String: DataAfterAlignedString: Unreasonably long string Dropping entire message"

If we add a symbol argument to udpreceive to prevent Max from trying to convert the incoming data, the data we receive seems to be different from what we are sending (see attached images). First image shows what we are receiving in Max, second image shows what we are sending in both ASCII and Hex (monitored through plug-in outside of Max). 

Hi,

We're trying to send strings from Unity to Max. We're using these objects in Unity for sending UDP packets: https://forum.unity.com/thr

problems-receiving-strings-through-udpreceive

Sorry hate to bump it but would love some help.

Thanks for the reply. We just have a udpreceive object attached to a print object. Inside Unity we send the data. Made a quick vid showing it.

2018-10-09 11-18-33.mp4

Thanks for the reply. We just have a udpreceive object attached to a print object. Inside Unity we send the data. Made a quick vid showing it. 

Looks like you are sending OSC from Unity try the OSC object from CNMAT

Update: I'm not getting it working. If I set udpreceive to output full package, OSC-route is complaining the message pattern isn't correct and OpenSoundControl says the string is too long. If I set udpreceive to output normally (no full package) it's always saying the string is unreasonably long and doesn't output anything. Any thoughts? Thanks again.

2018-10-09 12-27-52.mp4

Update: I'm not getting it working. If I set udpreceive to output full package, OSC-route is complaining the message pattern isn't correct and OpenSoundControl says the string is too long. If I set udpreceive to output normally (no full package) it's always saying the string is unreasonably long and doesn't output anything.  Any thoughts? Thanks again.

What if you append / to the message from unity, like it says in the console?? 

What if you append  /  to the message from unity, like it says in the console?? 


Hmmm dunno then maybe something from the unity side then.

I strongly suspect that you're getting bad OSC from Unity. On OSX, I'd use Osculator to check. I don't know of a PC equivalent.

In the last video, you're sending OSC-route a fullpacket message. It wants OSC-formatted Max messages, like "/my/osc 123". OSC-route won't help this problem.

I don't think anything is coming out of the OpenSoundControl object? Your video was a bit quick. I think that error about string length is still being generated by the udpreceive object. Do you get a bang, out of the left outlet of OpenSoundControl.

In the last video, you're sending OSC-route a fullpacket message. It wants OSC-formatted Max messages, like "/my/osc 123".  OSC-route won't help this problem.

I don't think anything is coming out of the OpenSoundControl object? Your video was a bit quick. I think that error about string length is still being generated by the udpreceive object.  Do you get a bang, out of the left outlet of OpenSoundControl.

OpenSoundControl does bang when receiving full packet from udpreceive. We're going to look into what Unity's sending. Thanks for now everyone, it's much appreciated.

EDIT: I added "/n" to the end of the string in Unity, now I don't get any errors when connecting udpreceive to OpenSoundControl (and OpenSoundControl still outputs a bang from left outlet when sending to udpreceive). However nothing is printed when connecting print object to middle outlet of OSC.

OpenSoundControl does bang when receiving full packet from udpreceive. We're going to look into what Unity's sending. Thanks for now everyone, it's much appreciated. 

this old ass thread helped me fix my errors /n.

Problems receiving strings through UDPreceive