These accelerometers do have some drift, but I would be surprised if it is to the extreme that you have described. I have used them for extended periods (over 6 hours continuous) with negligible issues with drift, however I would not say there is no drift. They appear to be much better than the accelerometers I have been using since 2011. The way I am using them currently does not require accurate tracking of position over time or distance. I am using numerical decay and smoothing that responds to the force of directional movements, rotation and orientation of the device. These are like exaggerations of directional movement that are always trying to decay back to the raw reading of the accelerometer data. The numerical data is filtered and passed to numerous 3D player assets that flock and swarm synchronized with rotation and direction of the performers hand movements. The spatial representation of these swarms as projections tracking over physical distances is not going to be achieved with the accelerometer data. There are a couple of other options for spatial tracking, one is a camera vision system that tracks IR LEDS mounted on the device (reducing the battery duration significantly), the other is Bluetooth triangulation (there appears to be a Bluetooth beacon on the NodeMCU) however, the programming task of implementing the Bluetooth option is out of my reach.
@mwasser NDI.Cloud sounds very interesting. Thank-you for the information. The mobile app, does have noticeable delay over my current wireless (1300Mbps), but is still useable for some situations. Worth knowing its an option.
I don´t have anymore access to that specific Optoma, but good to know about the RESYNC on the remote. I have another one at my disposal, so next time I run into the a similar problem, I will definitely try that one.
Yes the Matrox software can create a bunch of question marks
@mark Obviously if you had a 6 seconds fade out and 0 second fade in, Scene 2 would immediately make Scene 1 invisible, though the sound would take 6 seconds to fade out. That was your goal in the original post, yes?
Gladly. There are more features I am happy to add if people start to use this. My focus was on trying to pass the osc data as json ( hoping to make an easier system ). So the straight osc addresses haven't been tested much, and don't yet include the hand open/closed state. Hopefully it's useful to some. ☺