We have tons of scripts that utilise marking sets to key certain
parameters in one go and / or move animation of a bunch of marking sets'
parameters into actions and stuff like that. Of course our staff *could*
modify the setups and hence break the system, but they are told not to
do so and that's how it works.
So it's not about locking away stuff, we rather like the marking sets as
a convenient system to tag certain parameters in advance, thus
streamlining the animation workflow and make results 100% reproducable.
That wouldn't work with an animated-parameters-filter-only workflow.
Helen Bucknall wrote:
Ya, in Max you can easily filter for animated params. What I'm
suggesting is that marking sets and animated parameters are just made
to be one and the same.
No fuss no muss.
I mean if it's just a question of people from different teams not
tooling around with parameters they shouldn't be touching I don't see
how marking sets can help. They can always just add the parameter to
the marking set anyway if they are so anarchic as to touch things they
shouldn't.
André Adam wrote:
'Cause I can *see* the marking sets' parameters while the keyable
parameters are hidden. Before I move our setups to the alternative
system, I want the keyable parameters to be clearly exposed through
the explorer *with top-level access*. Our whole animation pipeline
depends on that transparency...
-André
Helen Bucknall wrote:
OK I'll bite, since so far this has been a pretty lame death match.
More like a group grope.
Why can't keying a param and setting a marking set be one and the
same?? You know if I'm keying sompthin I'm adding it to my marking
set and if I'm not keying it I'm not marking it?
8 years of 3DsMax and nearly 2 years of Xsi and I can't for the life
of me see why anyone would want to keep the whole marking set
bullsheet.
There, I said it.
Scott McGinley wrote:
Rob,
if you run the plugin from Christian Rittener over all you rigs you
can sync up your keyable parameters with your marking sets, doesn't
take long at all. i've done that were i'm working right now.
Hasn't cause any problems yet. perhaps it would be nice to have a
built in functionality to sync up the two different keying
techniques but it doesn't seam to be that huge of a deal.
http://www.softimage.com/community/xsi/discuss/archives/xsi.archive.0512/msg00613.htm
*/Robert Moodie <robertm(at)hybride.com>/* wrote:
> One thing in this area that we will be doing is putting a text
indicator
> in the UI that will make it evident what is the current keying
mode.
> Presently, this is only verifiable in the Animation menu.
Text indicators is a good idea.
> What oversight do you mean..
Luc, I'm not moaning. If you guys saw it coming then my
apologies. We
typically don't animate with every kine param keyed but that might
just be
us.
I was going through a bunch of anim shots for export to
lighting and
thinking it was coming from the animators - and obviously only in
certain
cases. I had a eureka moment when I figured out what was causing
it and just
wanted to pass the info on.
home time
a demain
_rob
----- Original Message -----
From: "Luc-Eric Rousseau"
To:
Sent: Thursday, July 20, 2006 5:53 PM
Subject: RE: ex-Maya Animators vs QWERTY tools and Alt interaction
model vs
XSI - Death Match
>
> One thing in this area that we will be doing is putting a text
indicator
> in the UI that will make it evident what is the current keying
mode.
> Presently, this is only verifiable in the Animation menu.
>
>> From: Robert Moodie
>>
>> Absolutely.
>> I'll ask Warner Bros to hold off for a couple of weeks while
>> I fix all the
>> rigs.
>>
>> On a more serious note, has anyone from the UI team seen this?
>> I remember some discussions about Keyable params and workflow
>> a while ago,
>> this behaviour appears to be an oversight
>>
>> _rob
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
