UDP receiver problems. MAX MSP

Replies to This Discussion

Permalink Reply by Ron Shvartsman on November 17, 2011 at 12:50pm

I have one suggestion off the top of my head:

 

Whenever I have sent packets of info out of MaxMSP, into anything, I used a different component than udpsend, because it caused me some grief. I cannot remember what the other component was called, but I believe it was a jitter component. I will try to find out what it was. Also, don't be afraid to call Cycling '74 (makers of MaxMSP) they are pretty friendly guys and willing to help.

Permalink Reply by Katherine Treppendahl on November 18, 2011 at 8:32am

Thanks for the reply, and if you remember the component let me know.  I'm a novice with MSP, and, you're right, contacting the company might be a good idea.  

Permalink Reply by Ron Shvartsman on November 19, 2011 at 4:08pm

I found the component I used. It is called:

 

mxj net.udp.send @port 7000

 

The port number is up to you. I was unable to determine exactly where in Max it was because my trial has expired. The only way I was able to see it was by opening Max in runtime mode. Also, I could not find anything on this in the Cycling 74 documentation, http://cycling74.com/docs/max5/vignettes/intro/docintro.html. However, I did find some information on different networking components here, http://cycling74.com/2006/10/23/networking-max-talking-to-max/, and here, http://www.maxobjects.com/?v=objects&initiale=N&id_platform=0. In addition, here is another grasshopper thread discussing how udpsend does not send proper packets or lists of information to grasshopper, but the above mentioned component does. :

http://www.grasshopper3d.com/forum/topics/2985220:Topic:17818?comme...

 

Luis, you are also in this thread. By the way, hello old friend. Hope this helps.

Permalink Reply by Luis Fraguada on November 18, 2011 at 7:40am

Hello Katherine,

You might have a slightly older version of gHowl that had some mistakes in the description of the inputs.

The 999 switch is to receive OSC packets, which are slightly formatted UDP packets.  You want to keep it at 0.

 

Best,

Luis

Permalink Reply by Katherine Treppendahl on November 18, 2011 at 8:36am

Thanks, Luis.  I guess this means that my issues are with MaxMSP and not with ghowl.  When I keep it on zero I'm getting odd messages (like the float,f??~? that you can see in the image) and not the data numbers that I thought I was sending.  I'll need to work on the patch I'm using in MSP.   

Permalink Reply by Luis Fraguada on November 19, 2011 at 10:34am

Katherine, can you try converting the numbers into a string (text) variable before you send from MaxMsp.  See if that helps...

 

Permalink Reply by Katherine Treppendahl on November 25, 2011 at 9:28am

I got it to work.  That mxj object solved all the problems.  Thank you both for all your help!  A friend and I are going to use sound data (pitch and noisiness and brightness) to drive a remote controlled car.  Pretty silly, but I think we can now get all our data and our objects to communicate with each other.  

Permalink Reply by Luis Fraguada on November 25, 2011 at 12:22pm

Right on!  Looking forward to see how that thing moves...

Permalink Reply by joncor on July 19, 2014 at 11:25am

Hi people!

I'm having the same issue as katherine, when i receive udp messages in grasshopper there are like: float,f??~? and similar. I never get the numbers I want. I know the problem is in grasshopper because in other software is receiving ok.

Please any help with this?¿?

Permalink Reply by Luis Fraguada on July 26, 2014 at 11:58am

Try to format the data as text before sending it through to GH.  See if that helps.