-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Blob size unpack_from with wrong unit #72
Comments
When parsing the blob, why do you use an integer (>%iQ) instead of a char (>%cQ)? From osc.parser:
The specification says:
I think the line where the data is unpacked should be something like:
|
Seems like a bug indeed, i didn’t put a lot of attention in the project since i don’t need it currently, but i’ll try to have a look at it, of course, if someone else has time before that, PR welcome. |
Modify blob parser and test_blob to address issue #72.
Describe the bug
I am sending an OSC message containing a single blob of data:
/destn/1\x00\x00\x00\x00,b\x00\x00\x00\x00\x00\x08...
[28 bytes] /destn/1 b [8]0123456789ABCDEF
I am getting this result for both OSC data send from C and using Dart.
To Reproduce
Code example showing the issue is the example code from the readme:
Here the sending portion in C using tinyosc compiled with
gcc *.c -Werror -std=c99 -O0 -g -o sendosc
Note: main.c from tinyosc has to be removed or the content be replaced with below:Expected behavior
Read the correct size of the blob and get a binary array same way it was written.
The same message works without any issue using e.g. python-osc.
blob = b'\x01#Eg\x89\xab\xcd\xef'
Logs/output
Platform (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: