Why don’t you just use locrotscale all the time as apposed to using loc and locrot?
Well, for instance, you might need one really long, smooth movement along a line, but with a bunch of little rotations. It’d be a lot easier to just have two keys for the start and end of the actual movement, and then key the rotations as necessary, especially if you’re planning on moving the keys around a lot. Or you might just have an elbow joint, so you’d never need to use Loc or Scale, and having these IPOs active would only clutter things up.
it depends on the situation
but it creates IPO’s for data that you may not need - this makes your file bigger than it needs to be and there is more IPO’s to work with
Sometimes I want to animate the location then adjust the rotation later. If you record a LocRot in this situation, you have no ability to freely adjust the rotation because you have created an IPO that will override the numeric or graphical inputs for an object. Your rotation will always “snap” back to what the IPO value is.
yeah that is a pain in the arse
it would probably screw up if you have a driven channel too
eg - if you are using another object to drive the rotation (or scale or whatever) and there is a IPO curve already for the rotation - you may find it gets double transformation or none at all
but I haven’t tested this