<p dir="ltr">You can also try disis_netsend/receive which is nearly identical to Pd's netsend/receive, except that it provides additional features including UDP broadcast, msg queueing etc., including a different way for dispatching received messages that has (at least on pd-l2ork) solved freezing gui issues.</p>
<div class="gmail_quote">On Mar 1, 2013 7:16 AM, "Roman Haefeli" <<a href="mailto:reduzent@gmail.com">reduzent@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Fre, 2013-03-01 at 08:53 +0100, IOhannes m zmölnig wrote:<br>
> On 02/28/2013 17:33, Matthias Blau wrote:<br>
> >><br>
> >> checkout iemnet's [udpclient].<br>
> >><br>
> ><br>
> > already have tried that - without success. I only get<br>
> > "udpclient:status: sent 4", nothing else.<br>
> ><br>
> > If I understand it correctly, udpclient listens on the specified port as<br>
> > well, so if the remote udp server gets the request, say on port 6667 and<br>
> > answers on another port (e.g., 60303), how can udpclient receive this<br>
> > answer?<br>
><br>
> because you are misunderstanding how udpclient works.<br>
> each network connection (UDP or TCP/IP) consists of two ports, a sending<br>
> port and a receiving port. the receiving port (on the server side) is<br>
> usually fixed, it's the port you connect to.<br>
> but on the sending side (the client) you also open a port, which is<br>
> normally chosen randomly from all the currently available ports on the<br>
> system.<br>
> this port can be used to get data back from server to client.<br>
><br>
> [udpsend] will silently discard all data on the sender port, but<br>
> [udpclient] will not.<br>
><br>
><br>
> ><br>
> > Just to make sure we are talking about the same version: I am on<br>
> > pd-extended 0.43.1 (20120430) under Ubuntu 12.04 64bit.<br>
> ><br>
><br>
> dunno, i have neither.<br>
> but you can test whether [udpclient] works as expected by doing the<br>
> following:<br>
> - run a simple udp-server from the commandline (the following uses<br>
> netcat to Listen on Udp Port 7777)<br>
> $ nc -u -l -p 7777<br>
> - start Pd (in another terminal), load iemnet, and do<br>
> [connect localhost 7777(<br>
> |<br>
> [udpclient]<br>
> |<br>
> [print foo]<br>
><br>
> then send something (e.g. "64 64 10") via [udpclient].<br>
> you should see whatever you sent appear on the console running netcat, e.g.:<br>
> @@<br>
><br>
> now, in the very console running netcat type something "e.g. "foo") and<br>
> hit return. Pd should print something like "102 111 111 10".<br>
><br>
><br>
> if the iemnet bundled with PdX is broken, you can install the debian<br>
> packages, by simply running<br>
> $ sudo aptitude install pd-iemnet<br>
<br>
Why are you assuming it is broken in Pd-extended?<br>
<br>
Actually, it seems to have glitches. With above setup, right after<br>
connecting [udpclient] to the netcat server, you cannot send anything<br>
from netcat to the client. Only after sending at least one packet from<br>
[udpclient], it flushes all messages it has received from the server<br>
since the connection. From this point in time, the communication works<br>
instantly both ways.<br>
<br>
This is on Linux (Ubuntu 12.04) with most recent iemnet and Pd compiled<br>
from source, but also with Pd-0.43.3-extended.<br>
<br>
When using netcat as UDP client, I can start sending packets from the<br>
server immediately.<br>
<br>
Roman<br>
<br>
<br>
_______________________________________________<br>
<a href="mailto:Pd-list@iem.at">Pd-list@iem.at</a> mailing list<br>
UNSUBSCRIBE and account-management -> <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br>
</blockquote></div>