calfredson
-
Posts
6 -
Joined
-
Last visited
Posts posted by calfredson
-
-
So I am now getting a different error in Watchout:
Parsing error: Bad number: "setInput"
It doesn't seem to be occurring every time I send a value, predominantly when I am sending lots of data in quick succession. Any ideas?
Craig
0 -
This resides more on the Max side of things than the Watchout side, but I kept getting errors in WO when I used the "udpsend" object. For some reason, Max was sending an extra comma a few bytes after the message. It was working, but it bogged down WO considerably with the error message. It turns out that "udpsend" formats all its outgoing messages as OSC, so that might have been where the extra comma was coming from.
Anyway, I switched to using the "mxj net.udp.send" object and all was fine.
0 -
SOLVED!
Thank you Tim. You were almost correct, but led me to the correct solution. The string that finally worked was:
"setInput testin 0.5"
with no internal quotes.
Craig
0 -
Thank you for the reply. I have tried adding a carriage return in all possible forms, but I still get the same error. The program that we are (currently) using to send the UDP data is Max/MSP, so I'm not exactly sure how that program formats carriage returns and hex bits.
Otherwise, is my syntax correct?
0 -
Hello,
I'm trying to control a generic input using a UDP string sent from another computer on the network. Here is the string that I am sending:
setInput “testin” 0.5
The Watchout computer recognizes that there is a command sent, but it returns this error:
Parsing error: 3; Unexpected end of file/line/communication: setInput
Anyone know what I am doing wrong?
Thanks,
Craig
0
Parsing error 3 on UDP input
in WATCHOUT FORUM
Posted
The syntax is correct. I've been using Wireshark extensively to snoop on the UDP packets; it has definitely been a useful tool.
The latest error relating to bad numbers is definitely related to sending too many data packets. I throttled the frequency that the data packets are being sent and the error went away.