I just wrote about this in another forum so I hope you don't mind the 'cut and paste': :)
If you haven't used iPi Studio before, 'supervised' tracking (i.e., error correction) is pretty straightforward. When you see an error occur you can do any of the following to fix it:
1. Go to a good frame and track backward through the error. This is the easiest trick and often it works the best. If it doesn't work...
2. ...position the mis-tracked limb to the middle of the frame range around the error (iPi Studio supports IK and FK), click Refit Pose and then track backward and forward from that frame to correct the surrounding frames. (Be careful not to track through the corrected frame.) Or...
3. ...if Refit Pose fails, just position the limb manually (do not click Refit Pose) and track backward and forward to correct the surrounding frames. Or...
4. ...Reposition the mis-tracked limb and hit Refit Pose, step through manually (< and > keys), and repeat as necessary through the error.
Once you get the rhythm for it, the process goes very quickly. When you're done it's a good idea to 'bump' the Trajectory Filtering slider to smooth the transition between fixes. In the very worst cases you may need to manually matchmove through the error but I've never had to do that. Honestly, if the footage is THAT bad, it's much easier to just record the motion again.
My typical workflow is to allow iPi Studio to process an entire Take from T-Pose to end frame by itself (unsupervised), and when it's done I'll play through the Take and fix any errors I might see. Typically, if there are errors in a Take, they can all be corrected in a few minutes.
When you're all done, you will need to run Configurable Jitter Removal. The 'raw' data can be very jittery if you don't apply at least a little CJR. CJR is run in a layer on top of the mocap data so it's non-destructive. This means, if you feel you've used too aggressive a setting, you can simply dial it down and run it again. Also, using CJR is not cumulative and you can run it as often as you like without worrying about permanently over-smoothing the motion.
Typically, I dial in the strongest CJR setting for the legs, a little less for the torso, and the least amount for the arms. If you wish, you can vary the settings at different points in the Take but I usually run one setting for the entire Take unless it's a special situation. If you use varying CJR settings in a Take, you need to 'bump' Trajectory Filtering to smooth out the transitions when you're done, otherwise you may notice a 'twitch' at the frames where you changed CJR settings.
And then there is Trajectory Filtering. This is another feature that can 'smooth' your motion data. TF is applied on-the-fly so you can change its strength at anytime. Be careful not to use too strong a setting because it can make your motions look too soft and lifeless. I usually set it at 1 or 2, and only go higher if there is a severe problem with the data.
For me, most of my iPi tracks produce very few errors if any. This is because I plan my shots in advance by creating an animatic, and I capture the exact motions I need on a shot by shot basis. This keeps my Takes fairly short and easier to track. 'Happy Box' is a very good example. I haven't posted my animatic online but
you can see the original storyboard at my website. The animatic version of the board served as a guide when I recorded the motions and it helped me capture motions for 3 characters for 17 shots in about an hour. Because this shoot had been carefully planned, tracking and error correcting the entire show took me about two evenings.
A more difficult case is the motion my daughter and I captured last Sunday right before dinner time. You can see the results here:
Mocap Test with Small Child (1 m)This example was the trickiest to track because the motions were very fast and 'poppy' but also because the iPi 'Actor' isn't really proportioned to track a small child. There were more errors generated in this track than usual but using the techniques described above, they were all corrected in about an hour. In spite of these challenges, iPi Studio was still able to produce accurate motion capture results quickly. (Tracking was done after dinner of course.) :)
Hope this info is helpful.
G.
