You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @DomNomNom, my apologies for the very slow response. Thank you so much for the simplified test case for this issue, it makes a huge difference in trying to triage issues like this.
Since it's been a while, did you ever come up with a workaround or fix?
It seems like the bug you've found is legit, though so far I'm puzzled by it. It looks like the output you're receiving is reading the zero padding and the four-byte size of the binary blob, so there's an incorrect offset somewhere.
But, playing with your example, it appears that the bug is not in the low-level OSC API, where all the low-level packing/unpacking happens:
So you might be able to work around the issue by receiving raw OSC data and reading it yourself, I'm not sure. I'll need to look into this further and expand the unit tests to including sending and receiving binary data over multiple transports.
Hi, I was sending icons over websocket OSC and some of them got corrupted.
It seemed like larger ones were fine but smaller ones have trouble.
I've made a minimal example that shows the problem clearly:
want:
got:
The text was updated successfully, but these errors were encountered: