Actually, having keys at every frame doesn't really guarantee the smoothness of movement at all: if the source of the bvh data was jerky or had spikes in the function curves, then you would have popping and weirdness just the same. The best bvh data comes from a good mocap system and in that case, yes, you'll most likely have keys at every frame. Something to consider about bvh, though, is that in many studios doing mocap, they still have animators go over the data, analyzing the function curves from it and reducing it to keyframes because the mathematical calculation of curves is actually much smoother than having keys at every frame.  So while it's totally true that a lot of bvh packages you might buy are going to be smooth and yet have keys at every frame, it's not necessarily a phenomen inherrent to bvh in itself. An animated Pose file is totally capable of exactly the same smoothness of motion, regardless of whether it's using keys at every frame or not: it's all about the quality of the origin of the data, whether that origin is mocap, hand animation or a combination of both. For the record, often times when I release an animated Pose I will go ahead and "bake" the animation by selecting all my frames for all parts in the keyframe window and setting them all to be keyframes. This essentially takes whatever position the function curve is in at each frame and keys that so the hand animated, f-curve based movement is there, but it's "baked" in to garauntee that the movement won't be effected by poses applied before or after the particular clip. I've long been an advocate of Poser for animation and still think that it has a really solid little toolkit that can be used to do far better work than the app gets credit for. -Les