Hi Russell, thank you very much. Both apps work fine, TouchOSC is easy to program, stable and reliable. GyrOSC works as well but the sensors are very sensitive even with the smoother at max.I was thinking of using it for motion captures the range of the Kinect and Orbbec sensors is very limited.
If anything I was the one being rude. I should have explained what the link was and told you that the bottom of the article discussed AirServer instead of just lobbing a link at you with no additional information.
A little late to the party, but I recently worked with John Toenjes of The Laboratory for Audience Interactive Technologies using their Mosho app to send audio, video, trigger vibrate, flash screen, etc. to audience cell phones, pretty similar to @eight 's app. They were super helpful, their documentation was straight forward, and cues were easy to tweak. While it wasn't quite as successful as I would have liked, it had more to do with not fully explaining to the audience how to interact with the app, rather than the app itself. Overall, it was a great first experiment...
Thank you so much for your reply. Look forward to whenever it does get integrated and totally get that it might be awhile. I have work arounds for now.
Unfortunately, the Syphon NDI apps don't do NDI HX. Currently the syphon apps only do regular NDI which works great for iPhones but not the new HX hardware that NewTek has put out.I might try to bug them and see if they will add. Sienna has added it to their NDI monitor at my request so who knows.
In case anyone is interested, I have tested and am using both the NewTek spark and their NDI PTZ camera. Both work great. Currently running over 250 ft of ethernet cable. No issues. Worked pretty much right out of the box. Very low latency (at least for me). Helping me move beyond my various analog to digital convertors. And the PTZ camera is really great quality. Expensive but can imagine using it in performance a lot.
@gapworks I had some "improvements" with the situation:
If I use the incremental version of the position it works fine, even from Isadora, and the commandes appears to be in the good order as in:
"GET /service/galileo/position?pan=" **P1** "&tilt=" **P2** " HTTP/1.1\r\nHost: 192.168.0.28\r\n\r\n"
But still no change for the absolute positioning (which is the feature I would like to use...)
So to me I would really think there's something with the airbeam version or the Motrr SDK version they are using
I have Airbeam v 2.1.4 (build5)
Since it seems to work properly for you @Marci , I'm curious to know which version you're using