Forum Replies Created

  • David O’brien

    May 4, 2020 at 7:24 pm in reply to: Messaging Automation Question

    I ended up achieving it by generating that index number through a slider on the layer, like this:


    m = marker;
    n = 0;
    moveTime = .2;
    mNumber = m.numKeys;
    indexNumber = effect("index number")("Slider");
    innerMessageHeight = comp("Messages_Comp").layer(index=indexNumber).sourceRectAtTime().height;
    moveAmt = innerMessageHeight;

    if (m.numKeys > 0){
    n = m.nearestKey(time).index;
    if (time < m.key(n).time) n--;
    }
    if (n > 0){
    t = time - m.key(n).time;
    value + [-(n-1)*moveAmt-ease(t,0,moveTime,0,moveAmt)];
    }else
    value

    And, it’s working like I want it to, but for some reason, it’s losing steam (so to say). Every movement after the first is just a little a little short. I can’t quite figure out why.

    Here’s a quick render to show you what I mean:
    https://www.dropbox.com/s/wez3nzb69jdrb7q/convo_comp_issue.mp4?dl=0

    Any thoughts as to why that might be happening?

    Also, again – thank you so much Dan! It’s surreal to be getting your help on this and super appreciated.

  • David O’brien

    May 4, 2020 at 6:56 pm in reply to: Messaging Automation Question

    Thanks, Dan!

    This is definitely working A LOT better. The issue now is that it’s moving the height of index 1 every time, when I need it to move the height of the next index. So, the second marker should move it the height of index 2, the third marker index 3, etc.

    Looking at my code, it makes sense that this will always produce the number 1:

    layer(index+n)

    But, I need to just sub in the number of the marker I’m currently at. Any thoughts?

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