You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
with -k mode you say it should stick the user number on the joint name (eg l_knee1), but I just get no user number. It works fine in normal mode (ie l_knee 1 f f f), but with -k nothing. Here's what I can see using Max to read messages when 2 users are being tracked:
OSX 10.6.8, OSCeleton 1.2.1
Thanks for amazing tool, but...
with -k mode you say it should stick the user number on the joint name (eg l_knee1), but I just get no user number. It works fine in normal mode (ie l_knee 1 f f f), but with -k nothing. Here's what I can see using Max to read messages when 2 users are being tracked:
print: /joint head 0.249929 0.207312
print: /joint neck 0.213173 0.286689
print: /joint l_shoulder 0.258474 0.294912
print: /joint l_elbow 0.327878 0.28873
print: /joint l_hand 0.245192 0.200382
print: /joint r_shoulder 0.167873 0.278466
print: /joint r_elbow 0.167873 0.412705
print: /joint r_hand 0.167871 0.546943
print: /joint torso 0.218675 0.384076
print: /joint l_hip 0.253753 0.486832
print: /joint l_knee 0.277243 0.688107
print: /joint l_foot 0.302533 0.882304
print: /joint r_hip 0.1946 0.476095
print: /joint r_knee 0.205924 0.678929
print: /joint head 0.809788 0.305879
print: /joint neck 0.769984 0.401978
print: /joint l_shoulder 0.828214 0.437232
print: /joint l_elbow 0.879691 0.522959
print: /joint l_hand 0.899683 0.549603
print: /joint r_shoulder 0.711754 0.366723
print: /joint r_elbow 0.616282 0.404154
print: /joint r_hand 0.643541 0.477619
print: /joint torso 0.730598 0.503658
print: /joint l_hip 0.729555 0.628553
print: /joint l_knee 0.729555 0.872458
print: /joint l_foot 0.729544 1.106983
print: /joint r_hip 0.652869 0.582124
print: /joint r_knee 0.652962 0.806677
print: /joint r_foot 0.629579 1.027292
Cheers,
Luke
(getting round it with Max router and normal OSC mode to another port for now)
The text was updated successfully, but these errors were encountered: