Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OSC packets #2

Closed
ofZach opened this issue Jan 26, 2015 · 1 comment
Closed

OSC packets #2

ofZach opened this issue Jan 26, 2015 · 1 comment

Comments

@ofZach
Copy link

ofZach commented Jan 26, 2015

is there a reason to send an osc packet for each joint? I'm wondering if batching joints would be more efficient? (for example, sending a full skeleton or full frame scene, etc)

@microcosm
Copy link
Owner

Essentially the data you want to communicate for each skeleton is a key (bodyId) to a set of key/value pairs, i.e:

{
    bodyId => {
            { jointId => [f, f, f] },
            { jointId => [f, f, f] },
            etc...
    }
}

The best way to fit that to the OSC specification with it's ID => list of keyless values seems to be to munge the bodyId and jointId into the address and then add the values.

Whether you can then group multiple OscMessages together into a single OscPacket I don't know - I don't know the spec / implementations well enough. Would have to dig around in here:
https://bitbucket.org/rugcode/rug.osc/src/6f12d2e4d4f6/Rug.Osc/?at=master

Does ofxOSC allow for that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants