I have a problem with incoming OSC data from OSChook.
When sending accelerometer OSC from phone, I get two simultaneous messages in Pure Data
oscparse: unknown tag 'h' (104)
print: list oschook -0.002295 0.006195 0.983895 0 0
Any hints?
OSChook error. oscparse: unknown tag 'h' (104)
I have a problem with incoming OSC data from OSChook.
When sending accelerometer OSC from phone, I get two simultaneous messages in Pure Data
oscparse: unknown tag 'h' (104)
print: list oschook -0.002295 0.006195 0.983895 0 0
Any hints?
@patricio.tics You probably need to ask the app developer.
I have used this one in the past without issues...... https://apkcombo.com/kontrolleur/processing.test.kontrolleur/
... but it was a while ago so.....?
Or you could try using the MrPeach library instead of the vanilla osc objects..... it is generally more user friendly..
Here is a patch for routing the kontrolleur app data using MrPeach...... which could be useful anyway with [oscparse]....... kontrolleur.zip
5-point touch
Acceleration
Magnetism
Orientation
David.
Per https://opensoundcontrol.stanford.edu/spec-1_0.html , 'h' is the type tag for 64 bit big-endian two’s complement integer. Probably [oscparse] simply doesn't implement it.
... in which case, try mrpeach. (Though, come to think of it, what would Pd do with a 64-bit integer? It can't be squished down into a 32-bit float. Even a 64-bit float would be able to keep only 53 bits' worth of precision, or 54 if you count the sign bit. So it would be helpful to know what data the app is sending in this format.)
hjh
Thanks I'll try... and post an issue on github I guess
Well, with the mrpeach library I get this error
unpackOSC: PrintTypeTaggedArgs: [A 64-bit int] not implemented
ddw_music is right...
The data OSChook is sending is accelerometer information. I'm guessing now to work with another app. It's a shame, OSChook is super powerful.
SOLVED.
In the OSChook v2.1.2 there is an advanced setting that combines the OSC messages in one (in order to save some latency). I don't know the depth of this, but I guess the 64 int combines several messages into one.
So the solution is NOT sending combined OSC messages from OSChook.
I hope this is useful to others.
Thanks!
Oops! Looks like something went wrong!