Sketch 1:
The idea for this visualization is that you have a skeleton shown at Frame 1, and its major joints are labeled with dots. So in order to prevent showing many skeletons at various frames, you instead plot the joint position at a frame and connect it to the joint position at the previous frame to create a kind of continuous line of motion. This hopefully makes it easier to see which body parts move the most, and which stay stagnant. Of course, my drawing is super bad and I did it by random, so we'll actually have to load a motion into it to see how it looks. Another idea was that if you were to hover over any part of the group of lines, you could see what the skeleton looks like at that particular frame. Perhaps, if it scales well, you can also choose to view it from the front/back, which could present a very different view.
Sketch 2:
This sketch is mainly for the skeleton (ie, what to display at a given frame). The idea was to place arrows indicating direction of movement at each of the major joints, and the direction would be determined by the difference in position between this frame and the next frame. Problem: the arrows might appear visually cluttered though, so they would have to be thin and lightly colored. There are various ways to display the arrows (length, shape, opacity, width) so that they don't appear as intrusive. Maybe the skeleton could take a back seat and let the arrows be the focus.
Sketch 3:
This is just your typical frame-by-frame display of motion. Standard.
Sketch 4:
Sketch 5:
Now this one is more of an overlay of skeletons at each frame (or intervals of frames). Each skeleton would be translucent so you can see which body parts stay in the same place (indicated by a darker color), or which body parts move around more (indicated by lighter colors). The idea is to make this look like a slowed down motion clip, where you see traces of the frames before. Onion skinning, is that the term?
Sketch 6:
This is another way of displaying the skeleton per frame. Instead of seeing the skeleton as a whole, maybe someone would like to focus on a specific body part, say the legs. For each frame displayed, we could either show just the legs (resulting in a really weird torso-less body), or we can show the whole skeleton with with the rest of the body in a light color, and the legs in a dark color. This allows you to focus on the body part that concerns you. For example, if you're searching for motion capture data of an Irish dancer, then you probably would want to see movements of the legs and not the upper body, since the upper body stays still most of the time anyways.
So for next week, my plans are to:
- Iterate on these sketches
- Start sketching the website (results page) layout
- Look at the asf/amc parser code that Joe will hopefully send me!
3 comments:
I think that the 1st, 3rd, and 4th ones are the most interesting (in my opinion). For the 1st and 3rd, you would be most able to understand the full motion (and the focus of the motion) at a glance. Although, for the 1st one, you would need to have some basic understanding of the splines (at least this is what it looks like to me... the splines from MotionBuilder). Which may be great in some instances... but may not be incredibly user friendly? The 3rd one I guess is what the norm currently is? Not sure... but it gives you a lot of information about the motion at a glance which is nice. The 4th one is really cool, because it gives you the focus on the motion (i.e. which limbs) and would be great for things like when you want to use different motions for frame blending, but I wonder if it would really help you figure out what the motion actually is? For instance, looking at that... would you be able to tell something is a squat? Or would a run look any different than a walk? Also, would things like the hands always be darkest as they follow the line of motion and/or have minor changes even when standing still?
You might want to look at some of the (many) schemes for multi-dimensional data display, especially with parametric glyphs. Check Tufte books or "Visualization of data" by R Daniel Meyer and Dianne Cook. Or see me... NB
http://www.sciencedirect.com/science/article/B6VRV-3YS8JMH-K/2/42552ea01f0b59c52b9151a8a38c3399
Post a Comment