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!

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.

Thanks I'll try... and post an issue on github I guess

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?

Excellent, thank you.

The only thing I modified is the range of the probability slider. Noise values come from -1 to 1, so even if the slider is all the way down, we still get random modifications to the sequence. Another way could be using an abs object...

Great patch.

PS. Another change could be summing all the event sliders to correctly map the voltage outcome...

Is there a way to send OSC messages to other apps using MobMuPlat?
I'm working with inScore, an app that receives drawing instructions from Pure Data.

I want to send this OSC message
/ITL/scene/violin1 set gmn [ \meter<"3/8"> a11/8 b g ]
But my guess is that the OSC building is wrong.
Do you have experience with this?
funny thing, if I send
/ITL/scene/violin1 set gmn [a11/8bg]
it works