Re: Marking Set Vs Keyable Parameters
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 enriquecaball...@gmail.com 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
Re: Marking Set Vs Keyable Parameters
We've been using keyable parameters on Justin's productionhttp://www.justinandtheknightsofvalour.comwithout issues. Of course we had to develop some tools to create/manage 'selection groups' and make life easier for the animation crew, but nothing to fancy to be worried about. On Fri, Jan 11, 2013 at 9:45 AM, 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
Re: Marking Set Vs Keyable Parameters
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
Re: Marking Set Vs Keyable Parameters
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
Re: Marking Set Vs Keyable Parameters
I have given up MarkingSets a while ago and never got a problem with Keyable Parameters. MarkingSets were good in the old time but are now deprecated in my opinion.
Re: Marking Set Vs Keyable Parameters
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 On Sat, Jan 12, 2013 at 9:29 AM, Jeremie Passerin gerem@gmail.comwrote: I have given up MarkingSets a while ago and never got a problem with Keyable Parameters. MarkingSets were good in the old time but are now deprecated in my opinion.
