While marking sets kinda suck, some times you need parameters to be flagged
as keyable for technical reasons, but not necessarily something that gets
aggressively/artistically keyed.

If nothing in your current pipe/workflow requires that, at this point in
time I'd just drop marking sets for keyable if the artists can get used to
it, and rely on custom sets of proxies but not named marking sets for when
you need aggregation.

I would discourage though name based functionality for aggregation, it's
usually a recipe for either disaster, or unnecessarily long parameter names
and animator rage in the AE. CPSets offer metadata like aggregation
options, when this kind of option is available relying on names should
laways be a last ditch kind of measure IMO.

On Sat, Jan 12, 2013 at 4:33 PM, Enrique Caballero <
[email protected]> wrote:

> Awesome this is what i was thinking as well, I got a bit set in my ways
> and it just struck me recently that they aren't that useful anymore.  I'll
> have to adapt some of our animation tools but i think the decision is made
> now, no more marking sets. just keyable parameters.
>
> thanks guys, i feel alot more comfortable now
>
>

Reply via email to