Hello,
Thank you for writing Osculator! It is an awesome tool.
I do believe I found a strange bug in the way that Osculator processes blob messages.
I am generating OSC messages from a command line tool I wrote in C using the liblo. I use Osculator for the occasional sanity check.
For whatever reason, when a blob has a size that is cleanly divisible by 4, I get...
"OSC Error 9911 in /my/namespace: Invalid message received"
...in yellow at the bottom of the screen.
If the blob size is modulo 4 equal to 1,2, or 3, then all is fine and I see my messages without any errors.
Interestingly enough, if I send the exact same stream to a Processing app using the OscP5 library, I get the exact opposite. The blobs with a size that is a multiple of 4 are just fine... and a blob with size % 4 == 2 throws an exception in Processing.
Very strange. Can you elaborate on the 9911 error and what might be happening with the 4-byte boundary check?
Many thanks,
John
Thank you for writing Osculator! It is an awesome tool.
I do believe I found a strange bug in the way that Osculator processes blob messages.
I am generating OSC messages from a command line tool I wrote in C using the liblo. I use Osculator for the occasional sanity check.
For whatever reason, when a blob has a size that is cleanly divisible by 4, I get...
"OSC Error 9911 in /my/namespace: Invalid message received"
...in yellow at the bottom of the screen.
If the blob size is modulo 4 equal to 1,2, or 3, then all is fine and I see my messages without any errors.
Interestingly enough, if I send the exact same stream to a Processing app using the OscP5 library, I get the exact opposite. The blobs with a size that is a multiple of 4 are just fine... and a blob with size % 4 == 2 throws an exception in Processing.
Very strange. Can you elaborate on the 9911 error and what might be happening with the 4-byte boundary check?
Many thanks,
John
Comment