Hi there,
Just getting OSCulator fired up and am super impressed - great work Camille! I got OSCulator and a Wiimote to start incorporating the controls into a MAX patch, and I'm wondering if you could give me a bit of advice with regards to the message.
Does the yaw work from the point of view of "dead reckoning" to try to establish a value for the wiimote's orientation? Obviously pitch and roll have gravity as a pretty strong indicator and as such their values remain pretty constant, whereas the yaw message seems to gradually drift back towards the center of its range after giving the wiimote a little spin.
I take it that there's nothing inside the wiimote which would know its orientation with regards to my computer (and its bluetooth ariel) and that the yaw values are independent of the IR inputs too?
In essence my question is whether anyone has noticed any broad rules or guidelines for using yaw input with regards to its absolute yaw value in real space, for example whether anyone has been able to achieve consistent results through the whole of the yaw input range, or whether people have found that it's a less precise input.
My ideal aim is to be able to consistently receive absolute values for the pitch, roll, and yaw of the wiimote, but I'm sure that if this is impossible that I'll be able to tailor my patch in MAX to suit. I'm just hoping for a few words from the wise and experienced out there who might have dealt with a similar situation.
Thanks!
Comment