Faster speeds do seem to make it worse. If I move the mouse really
slowly, then it doesn't seem to happen. I tried recompiling with
#define DEFPOLLTIME 5 and it still had the same behavior. I guess it
needs a sys_addpollfn. I'll give it a shot and see what I come up with.
.hc
On Sunday, Sep 28, 2003, at 16:39 America/New_York, Olaf Matthes wrote:
Hi Hans-Christoph,
does this error appear at all 'speeds' or is it getting worse the more data you send? I once had a similar problem with netcient dropping / 'manipulating' data when I was sending too fast.
There is a
#define DEFPOLLTIME 20 /* check for input every 20 ms */
in the code which means netclient polls for input every 20 ms using a clock. This should probably be changed to a lower value. Or to make it really perfect, use sys_addpollfn and friends to let Pd poll for input. But I don't have time right now to code this...
The rest of the code is pretty much identical to the netsend / netreceive code. Does it happen as well in case you use these objects?
hope this helps, Olaf
Hans-Christoph Steiner schrieb:
I am using netserver/netclient to send list of info that has been converted to a symbol using [list2symbol]. Somewhere in the process, some of the messages get chopped up at seemingly random points. The examples below only break at spaces, but sometimes it will break in
the middle of the first work (i.e. mo tion).I think the problem is on the [netclient] end because sometimes, one computer will work fine, and the other will chop up the messages. The patches are attached. They use Krzysztof Czaja's [tot] and zexy's [list2symbol].
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
"[W]e have invented the technology to eliminate scarcity, but we are
deliberately throwing it away
to benefit those who profit from scarcity."
-John Gilmore