-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
limit for OSC message #6
Comments
Just in case I update the sketch test for the big message:
|
I was looking for the same issue (not for sender but for receiver) and I figured out that you need
to increase the data size, for example, to 5,000. Note that data includes osc address and other metadata (?) so you can send a bit less than 5,000 characters in this case. |
Thx @micuat for the trick, now I can push to the limit of the datagram, 1842 for the classic array type like int, float, String... |
For those that might run into Index Out Of Bounds errors when trying to parse incoming messages. The reason could be that the type is one that needs a larger datagram size. I ran into it when trying to parse messages from the Moss OSC controller script for Bitwig, probably caused by the The fix above posted by @micuat solves that error in oscP5 |
Hello,
I try to send message, but I found a different limit for each type of argument.
That's depend of my computer or it's a limit of the OSC ? It(s possible to increase this limit ?
Or don't stop Processing and just limit the the size of the package must be sent and print a warning to inform the user ?
and thx for your work.
Processing 3.3.4 OS Sierra Osc 2.0.4
String limit 1524 java.lang.ArrayIndexOutOfBoundsException
Array float limit 1842 Could not send datagram java.net.SocketException: Message too long
Array int limit 306 java.lang.ArrayIndexOutOfBoundsException
Boolean limit 9207 Could not send datagram java.net.SocketException: Message too long
Here the little sketch I code to find the limit.
The text was updated successfully, but these errors were encountered: