So I'm in the process of extending the poseLibs in Red9 to include
animation data.
We thought hard about whether to use Atom or fbx or some other format, but
we've had issues with Atom in the past and I don't like the way they match
data up. So I'm looking at writing our own format that sits along side the
pose format, using all the same node matching logic etc.
All is well, the key saver is fast even with dense data, but setting those
keys back is still way too slow. Before I look at the api is there any
standard way of passing a list of data and setting the curve in one shot,
rather than doing something like:
for ktime, value, inTan, outTan in keydata:
cmds.setKeyframe(chn, t=ktime, v=value, itt=inTan, ott=outTan)
where keyData = [(0,1,'auto','auto'),(etc etc etc etc)] and setting the key
frames one at a time?
Just wondering if I've missed something obvious or if the only way to get
any more speed is to go to the api? Any pointers guys?
thanks
Mark
-------------------------------------
Mark Jackson
CEO / Technical Director
red9consultancy.com
--
You received this message because you are subscribed to the Google Groups
"Python Programming for Autodesk Maya" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/python_inside_maya/CAGQH2FE_Mxv1LtMVwqZ5E6ZpBr7mN5C%2B4GKUawY9Pjx%3DGMYvew%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
