I'd go with Keyable Parameters, mostly as it makes more sense for the
animators (especially those who come from Maya). Marking Sets just seem an
archaic and convoluted solution to me.
On 11 January 2013 10:00, Alok Gandhi <alok.gandhi2...@gmail.com> wrote:
> I find tagging the parameters through user keywords a better options. You
> can then easily script them to select and key through scripts on buttons or
> plugins in menu.
>
> Hope that helps.
>
> Sent from my iPhone
>
> On 2013-01-11, at 2:15 PM, Enrique Caballero <enriquecaball...@gmail.com>
> wrote:
>
> > Hey everyone,
> > I need some advice. I am considering dropping the use of Marking Sets
> in our pipeline.
> >
> > The reason for this is that with Keyable Parameters I don't really see
> much of a point for using Marking Sets anymore.
> >
> > Marking sets also give me the unfortunate side effect of showing
> duplicate Fcurves in the Fcurve editor, one for the master parameter and
> another for the proxy param on the marking set. Also we use DisplayInfo as
> well and that makes 2 proxy parameters and 1 master parameter. Basically
> just a bunch of clutter.
> >
> > I'm giving this a lot of thought before I move on it, and I'm keenly
> interested in what your guy's view is on this.
> >
> > The only current benefit that I can see from marking sets over keyable
> parameters is that marking sets are really easy to find via scripting, i
> just do a search for a Property("MarkingSet")
> >
> > But its not really much more work to find all Keyable parameters.
> >
> > Anyway please tell me your views. I would really appreciate it
> >
> > -Enrique
>
>
