hi all can anybody explain me [netreceive] message i send to [netreceive] message like 1 33, 2 77, 3 23, .........,15 89, ; every 100 ms
in the console i get EOF on socket 22 EOF on socket 22 EOF on socket 22 EOF on socket 22
and sometimes EOF on socket 23 EOF on socket 24 EOF on socket 22
and this is not good any idea?
best regards
nico wrote:
hi all can anybody explain me [netreceive] message i send to [netreceive] message like 1 33, 2 77, 3 23, .........,15 89, ; every 100 ms
in the console i get EOF on socket 22 EOF on socket 22 EOF on socket 22 EOF on socket 22
and sometimes EOF on socket 23 EOF on socket 24 EOF on socket 22
and this is not good
what do you mean by "this is not good" ?
any idea?
it looks like you are trying to much data at once via the network.
probably you might get better results if you try to send all the data in one single message [1 33 2 77 3 23 .... 15 89( and repack this list to small sub-lists on the receiver-side.
mfg.a.dr IOhannes
hi
and this is not good
what do you mean by "this is not good" ?
it breaks my sender side
any idea?
it looks like you are trying to much data at once via the network.
do you know the limitation?
probably you might get better results if you try to send all the data in one single message [1 33 2 77 3 23 .... 15 89( and repack this list to small sub-lists on the receiver-side.
ok will try
mfg.a.dr IOhannes
it looks like you are trying to much data at once via the network.
probably you might get better results if you try to send all the data in one single message [1 33 2 77 3 23 .... 15 89( and repack this list to small sub-lists on the receiver-side.
in fact, i send all the list in one message [1 23, 4 67, 3 88, ......(
mfg.a.dr IOhannes
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
nico wrote:
it looks like you are trying to much data at once via the network.
probably you might get better results if you try to send all the data in one single message [1 33 2 77 3 23 .... 15 89( and repack this list to small sub-lists on the receiver-side.
in fact, i send all the list in one message [1 23, 4 67, 3 88, ......(
in fact, this is one _message-box_ containing several _messages_ (separated by commas ",")
e.g. [1, 2( is the same as
[t b b] | | [2( [1(
mfga.sd.r IOhannes
in fact, it was a problem from tcl [socket] as [netreceive] need to get EOF to process data, i have to open and close connection each time i send data. and [socket] from tcl is as speed to handle 0,1s open/close
i believe.... thanks nico
nico wrote:
it looks like you are trying to much data at once via the network.
probably you might get better results if you try to send all the data in one single message [1 33 2 77 3 23 .... 15 89( and repack this list to small sub-lists on the receiver-side.
in fact, i send all the list in one message [1 23, 4 67, 3 88, ......(
in fact, this is one _message-box_ containing several _messages_ (separated by commas ",")
e.g. [1, 2( is the same as
[t b b] | | [2( [1(
mfga.sd.r IOhannes
On Thu, Aug 18, 2005 at 08:11:32PM +0200, nico wrote:
in fact, it was a problem from tcl [socket] as [netreceive] need to get EOF to process data, i have to open and close connection each time i send data. and [socket] from tcl is as speed to handle 0,1s open/close
you know about ";"s and their meaning in pd messages, right? its just that i dont see any below..and you shouldnt need to open and close the socket every time you send a message...
i believe.... thanks nico
nico wrote:
it looks like you are trying to much data at once via the network.
probably you might get better results if you try to send all the data in one single message [1 33 2 77 3 23 .... 15 89( and repack this list to small sub-lists on the receiver-side.
in fact, i send all the list in one message [1 23, 4 67, 3 88, ......(
in fact, this is one _message-box_ containing several _messages_ (separated by commas ",")
e.g. [1, 2( is the same as
[t b b] | | [2( [1(
mfga.sd.r IOhannes
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
here's my proc proc pd_send {all} { set to_pd [socket 127.0.0.1 40000] puts $to_pd $all flush $to_pd }
proc vu {x} { pd_send "$x ;" } there's the ";" in vu if i don't close $to_pd , i get a message like netreceive : accept failed
with close $to_pd if i ask for pd_send every 0.1s, it fail every 0.2s ,it's ok
i would like to sequence every 0.1s but......
in fact, it was a problem from tcl [socket] as [netreceive] need to get EOF to process data, i have to open and close connection each time i send data. and [socket] from tcl is as speed to handle 0,1s open/close
you know about ";"s and their meaning in pd messages, right? its just that i dont see any below..and you shouldnt need to open and close the socket every time you send a message...
i believe.... thanks nico
nico wrote:
it looks like you are trying to much data at once via the network.
probably you might get better results if you try to send all the data in one single message [1 33 2 77 3 23 .... 15 89( and repack this list to small sub-lists on the receiver-side.
in fact, i send all the list in one message [1 23, 4 67, 3 88, ......(
in fact, this is one _message-box_ containing several _messages_ (separated by commas ",")
e.g. [1, 2( is the same as
[t b b] | | [2( [1(
mfga.sd.r IOhannes
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Thu, 18 Aug 2005, nico wrote:
here's my proc proc pd_send {all} { set to_pd [socket 127.0.0.1 40000] puts $to_pd $all flush $to_pd } proc vu {x} { pd_send "$x ;" } there's the ";" in vu if i don't close $to_pd , i get a message like netreceive : accept failed with close $to_pd if i ask for pd_send every 0.1s, it fail every 0.2s ,it's ok
Change it to:
set to_pd [socket 127.0.0.1 40000] proc pd_send {all} { global to_pd puts $to_pd $all flush $to_pd } proc vu {x} { pd_send "$x;" }
Because the way you do it with one open per message and no close, you are using waaaaay too many sockets at once, which is causing a denial-of-service attack on [netreceive].
Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju Freelance Digital Arts Engineer, Montréal QC Canada
i'm tooooooo stuppid
if you come to Paris, don't forget to call me to drink champagne many thanks
On Thu, 18 Aug 2005, nico wrote:
here's my proc proc pd_send {all} { set to_pd [socket 127.0.0.1 40000] puts $to_pd $all flush $to_pd } proc vu {x} { pd_send "$x ;" } there's the ";" in vu if i don't close $to_pd , i get a message like netreceive : accept failed with close $to_pd if i ask for pd_send every 0.1s, it fail every 0.2s ,it's ok
Change it to:
set to_pd [socket 127.0.0.1 40000] proc pd_send {all} { global to_pd puts $to_pd $all flush $to_pd } proc vu {x} { pd_send "$x;" }
Because the way you do it with one open per message and no close, you are using waaaaay too many sockets at once, which is causing a denial-of-service attack on [netreceive].
Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju Freelance Digital Arts Engineer, Montréal QC Canada
On Thu, 18 Aug 2005, nico wrote:
in fact, it was a problem from tcl [socket] as [netreceive] need to get EOF to process data, i have to open and close connection each time i send data. and [socket] from tcl is as speed to handle 0,1s open/close
after you do a puts $fd "13 21;" you may eed to do flush $fd
this is required so that the data always get sent. Else it only gets sent when the output-buffer is full (usually 4096 bytes).
Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju Freelance Digital Arts Engineer, Montréal QC Canada
hi i've flushed the output with no success.
by sending packet every 0.2s , i don't have problem but it's not genial.... Le 18 août 05, à 21:40, Mathieu Bouchard a écrit :
On Thu, 18 Aug 2005, nico wrote:
in fact, it was a problem from tcl [socket] as [netreceive] need to get EOF to process data, i have to open and close connection each time i send data. and [socket] from tcl is as speed to handle 0,1s open/close
after you do a puts $fd "13 21;" you may eed to do flush $fd
this is required so that the data always get sent. Else it only gets sent when the output-buffer is full (usually 4096 bytes).
Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju Freelance Digital Arts Engineer, Montréal QC Canada
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-
IOhannes m zmoelnig -
ix＠replic.net -
Mathieu Bouchard -
nico