Re: [PD] non-socket (88)

2019-02-17 Thread michael strohmann
HI, thanks for looking into this! i actually use pd 0.47 on RPi B+ / jessie in any case i found a way to use the suggested workaround with [iemnet/udpsend] i send [disconnect, connect IP PORT( only as when a message is received with [netrecieve -u -b] and i prevent any messages beeing sent

Re: [PD] non-socket (88)

2019-02-17 Thread Lucas Cordiviola
Hi, I've been testing [netsend -u] for a couple of hours on Pd 0.49-0 on windows. I had no trouble if there is no receivers. I used a windows tablet and a linux box for listening. I have switch them off for a while and then re-enter to the LAN. Didn't get any "Socket operation on non-socket

Re: [PD] non-socket (88)

2019-02-17 Thread michael strohmann
ok, thanks for the clarification. i really know next to nothing about network protocols and hoped i could just use the objects and let them do the work (or actually the work of all you developers - THANKS for that!! ) is there a detailed explanation of what is going on under the hood of

Re: [PD] non-socket (88)

2019-02-17 Thread Martin Peach
On Sun, Feb 17, 2019 at 11:16 AM michael strohmann wrote: > but one can issue arbitrary IP addresses, and the obejct will tell you it > established connection. > i guess this is consistend with the UDP protocol > It didn't 'establish a connection', it just opened a socket on the local machine.

Re: [PD] non-socket (88)

2019-02-17 Thread michael strohmann
, 17. Februar 2019 um 11:53 Uhr >> Von: "michael strohmann" >> An: "Christof Ressi" >> Cc: Pd-List >> Betreff: Re: Aw: Re: [PD] non-socket (88) >> >> This non-socket(88) gives me the creeps because it seems to freeze pd >> immedia

Re: [PD] non-socket (88)

2019-02-17 Thread Christof Ressi
Just for the record, do you get the freeze only with [netsend] or also with [iemnet/udpsend] resp. [mrpeach/udpsend]? > Gesendet: Sonntag, 17. Februar 2019 um 11:53 Uhr > Von: "michael strohmann" > An: "Christof Ressi" > Cc: Pd-List > Betreff: Re: Aw: Re

Re: [PD] non-socket (88)

2019-02-17 Thread michael strohmann
for those network issues, can you open an issue on github > for your problem (88)? I have time in march. > >> Gesendet: Sonntag, 17. Februar 2019 um 09:23 Uhr >> Von: "michael strohmann" >> An: "Lucas Cordiviola" >> Cc: "pd-list@lists

Re: [PD] non-socket (88)

2019-02-17 Thread Christof Ressi
etwork issues, can you open an issue on github for your problem (88)? I have time in march. > Gesendet: Sonntag, 17. Februar 2019 um 09:23 Uhr > Von: "michael strohmann" > An: "Lucas Cordiviola" > Cc: "pd-list@lists.iem.at" > Betreff: Re:

Re: [PD] non-socket (88)

2019-02-17 Thread michael strohmann
i am sending OSC messages with [netsend -u -b] there is obviously an issue with [netsend] closing the socket if nobody is listening. which it should not do in UDP mode. https://github.com/pure-data/pure-data/issues/373 but this: netsend:

Re: [PD] non-socket (88)

2019-02-16 Thread Lucas Cordiviola
Did you tried sending every second an empty message [send ( instead of "reopening a connection" ? Mensaje telepatico asistido por maquinas. On 2/16/2019 3:57 PM, michael strohmann wrote: > i finally could caught pd in the act of freezing: > > the console said: > > recv: Connection refused

[PD] non-socket (88)

2019-02-16 Thread michael strohmann
i finally could caught pd in the act of freezing: the console said: recv: Connection refused (111) netsend: Socket operation on non-socket (88) warning: 33 removed from poll list but not found i connect every second to mobile phones that run Lemur to send and receive OSC usually if a phone