Hmmm. the easy way sounds to me like it would have some latency issues.
So let me ask some stupid questions until I catch up with the reality of the second method.
Wrap a python interface around your C code.
Could you give me a simple example to illustrate this sort of thing.
Load the python module from within Blender.
So I would be compiling my own module in C and calling it like I might call the Math or Draw module?
I have had a couple of false starts in my understanding of calling outside modules. Where sould I be reading/studying to round out that area of my python ability???
With the first method, it would be offline, ie you record your mocap data, then load it into Blender. I would try this way first, you should be able to reuse all the Blender-python bits.
I think that there are some broad implications for the scripts, but I am out of my depth in moving this along in any kind of timley fashion.
I will let you in on part of what what I am doing tho.
I am building two new machine tools in my studio this year.
The first is a tracker that has a cutter that I can push around manually in the X&Y axis’ and has a motion control assy that positions the cutter in Z, for carving the soundboards for the string Basses and archtop guitars that I build.
The second is a much more ambitious project that will the my third generation of 3 axis CNC profiler, designed specifically for shaping stone for sculpture. I can do Blender models and meshes in most machinable materials now, but it is a cumbersom processthat needs LOTS of manual input from Maya and Surfcam. If I can work out the passing of these values through the port (serial, USB I dunno) I can machine directly from Blender/Python, and thats why I am here.