There are two conceptual components to this part.
They will communicate over UDP-based OSC protocol using sockets.
Start with a C implementation of OSC (partial), that is based on TinyOSC that is already a submodule of OpenISS:
https://github.com/mhroth/tinyosc
but embedded into our project.
The purpose to separate skeleton capture and rendering into different computers possibly running Kinect sensors.
One computer will act as a collector and render graphics based on skeleton information from two or more computers.
(a) Using tinyosc, implement issoscsender and issoscreceiver processes with a simple pro- tocol
(b) If skeleton data are available from either libfreenct or libfreenect2 (via OpenNI2 that both have), try capturing real data and sending it over and drawing a skeleton in an OpenGL window. It is OK to re-use an appropriately licensed open source example for this purpose.
(c) OSC protocol messages would look like /player 1 /left-hand /x 1 /y 2 /z 3 etc.
smokhov
commented
6 years ago
There are two conceptual components to this part. They will communicate over UDP-based OSC protocol using sockets. Start with a C implementation of OSC (partial), that is based on TinyOSC that is already a submodule of OpenISS: https://github.com/mhroth/tinyosc but embedded into our project. The purpose to separate skeleton capture and rendering into different computers possibly running Kinect sensors. One computer will act as a collector and render graphics based on skeleton information from two or more computers. (a) Using tinyosc, implement issoscsender and issoscreceiver processes with a simple pro- tocol (b) If skeleton data are available from either libfreenct or libfreenect2 (via OpenNI2 that both have), try capturing real data and sending it over and drawing a skeleton in an OpenGL window. It is OK to re-use an appropriately licensed open source example for this purpose. (c) OSC protocol messages would look like /player 1 /left-hand /x 1 /y 2 /z 3 etc.