[James Peres]

Is there a specific reason you are doing time remap?

I would make expression controls on the main node, and then all nested layers will have their opacities controlled by those controls using expressions.

So “Eyes front open”, “Eyes front inbetween”, “Eyes front closed”, “Eyes front down” would have the following, respectively:


// "Eyes front open":
if ( comp("ellen_head").layer("head_CNTRL").effect("Eye_slider")("Slider") == 1 ) { opacity = 100 } else { opacity = 0 }
// "Eyes front inbetween:
if ( comp("ellen_head").layer("head_CNTRL").effect("Eye_slider")("Slider") == 2 ) { opacity = 100 } else { opacity = 0 }
// "Eyes front closed":
if ( comp("ellen_head").layer("head_CNTRL").effect("Eye_slider")("Slider") == 3 ) { opacity = 100 } else { opacity = 0 }
// "Eyes front down":
if ( comp("ellen_head").layer("head_CNTRL").effect("Eye_slider")("Slider") == 4 ) { opacity = 100 } else { opacity = 0 }

Hold shift while using sliders to make it snap to integers.

And you would do that in every comp that has those features. I do some more complicated layer name parsing sometimes to be able to name the layer with the the control I want it to follow and the expression will read the layer’s name to get the control:

so “eyes_front_open-head_cntrl-eye_slider” could be a layer name and with

L = thisLayer.name.split("-"); // Will split the layer name into three chunks (separated by "-").
// L[0] = eyes_front_open
// L[1] = head_cntrl
// L[2] = eye_slider

if ( comp("ellen_head").layer( L[1] ).effect( L[2] )("Slider") == 4 ) { opacity = 100 } else { opacity = 0 }

I tend to use short names, like “eyes” just become “e”, “head” just becomes “h” and so forth. If you are going to use expressions/scripts, be consistent with names and separators. I tend to use underscores instead of spaces, and hyphens to separate stuff.

–
James

Mac Pro 4,1 Quad Core 2.66

[James Peres]

Makes sense, thanks for the clarification Dan!

–
James

Mac Pro 4,1 Quad Core 2.66

[James Peres]

You can try multiplying your scale by (z + 1.0), so that at when z=0, scale is 100% of it’s value. When z=2, then 200% and so forth. You can then multiply it by a factor to make the scale up not as dramatic.

–
James

Mac Pro 4,1 Quad Core 2.66

[James Peres]

Hi, not sure what you are trying to do exactly, but 10/5 % 1 would be 0.02, so I don’t think it will work the way you want.

Also, I would personally put t=0 before everything, and then put the t=[whatever] in braces, then not put t in brackets. There may be some quick shortcuts I’m not sure about but I just stick to the basic syntax.

–
James

Mac Pro 4,1 Quad Core 2.66

[James Peres]

Hey Dan, could you offer a little explanation as to what was wrong with the original? Just curious, I’m having similar problems but can’t figure out how your solution worked.

Thanks!

–
James

Mac Pro 4,1 Quad Core 2.66

[James Peres]

Oh my god thank you for your reply! That’s a very handy feature! I had asked my coworkers but none of them knew and they are all avid Illustrator users. Thanks again!

–
James

Mac Pro 4,1 Quad Core 2.66

[James Peres]

Hey! Thanks for the reply. I tried smart baker and it doesn’t work: if I use a threshold high enough to remove equal keyframes, it also begins removing animation curve frames. I only want to remove keyframes that are equal.

–
James

Mac Pro 4,1 Quad Core 2.66