Forum Replies Created

Viewing 1 - 10 of 140 posts
  • Navarro Parker

    April 13, 2017 at 1:42 am

    Whew, glad to know I’m not losing my mind. Is this an upcoming fix or is it out in the wild?

    (A quick check of my CC updater says my AE is current)

  • Navarro Parker

    February 8, 2017 at 11:49 pm

    Yup! That did the trick! Thank you, Dan!

  • Navarro Parker

    February 1, 2017 at 2:16 am

    Hey Dan!

    I just applied this to an auto-traced mask and it didn’t remove any keyframes. Are mask KFs something different?

  • Navarro Parker

    September 23, 2016 at 10:43 pm

    Of all the dumb things… #@*! Yes, that must have been it. Good eyes! I blame Google Docs.

  • Navarro Parker

    August 12, 2016 at 9:07 pm

    Good ol’ to.World?? With a matrix definer?? Man, I feel dumb.

    But thank you for your quick reply! 🙂

  • Navarro Parker

    January 28, 2016 at 8:02 pm

    Thank you!

    Is there a way for this to respect the timing of my existing two keyframes (0 & 100)?

  • Navarro Parker

    January 21, 2016 at 8:24 pm

    You’re right, it isn’t a speed demon (on ten layers in a 1000 frame comp)!

    But it works great! Compare the difference in value graphs. Completely eliminates the bouncy wiggle!

  • Navarro Parker

    January 21, 2016 at 3:40 am

    Here’s a screenshot of the value graph that shows the bouncy quality

  • Navarro Parker

    January 21, 2016 at 3:20 am

    Hi Dan!

    I’ve revisited this expression today. And I’ve noticed a funky situation. I’m using a low freq (.25) and I get this weird “bounce” when the wiggle reaches the maximum value. It doesn’t gracefully flow from a low value to a high value to a low value.

    It reaches the maximum and then immediately bounces backward like it hits a wall. I’d describe it as “triangle” interpolation.

    I’m using an octave of 1 in hopes to get the most flowy, gentle wiggle.

    Any ideas how to smooth this expression out so there’s more of a gentle sine-y interpolation between min and max values?

  • Navarro Parker

    January 12, 2016 at 9:48 pm

    This expression does not work with CC2015.

    Even if I just use it by itself with two keyframes, AE is giving me an error: “Invalid numeric results (divide by zero?)”

    Any ideas?

Viewing 1 - 10 of 140 posts

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy