[Wick Van den belt]

Hi Adam, yes that is pretty much correct. So for just two text layers this is easy, as the anchor point for text 1 is on the bottom and for text2 the anchor point is on the top of that text layer. (So for big or small text size, they both scale of and the gap between them stays the same…)

The issue is with the third text layer; I am trying to have that move along with the text layer 2 bottom position, which varies depending on the length of the text. -So the third text should ideally react to the bottom of text two, but I have tried endlessly to create expressions but I can’t get it to work.

Most likely because the scale on the text layers makes the sourceRectAtTime expression fails to get the exact position? Which is weird, as I do manage to get a null linked to the exact position of the bottom of text two, but it just won’t work for text layer three.

[Wick Van den belt]

thank you for your helpful comment thus far! I am investigating it further based on that!

I need to keep tabs on what I am writing as I am not a programmer, so I kinda need the comments to keep track of the script. But thanks for your compliment 🙂

Also, I have possibly found a new way to improve the image precomp duplication by looking at the number of actual numbered comps in the template. That seems to be a way that would improve functionality for potentially handling more precomps in the future.

Thus far it’s a fun project to get my hands dirty on, and I feel I am getting quite close to make it do exactly what I need it to do. Exciting 🙂

[Wick Van den belt]

That was it!
Thanks so much, you’re really THE expression guru 🙂

WickieMedia.net

[Wick Van den belt]

That was awesome, thanks for the quick help Dan!
I found a solution for my other question based on your input and another topic here on CC.
(A topic where you gave the perfect solution as well, as you always seem to do!) Thanks a bunch!!

Wick.

WickieMedia.net

[Wick Van den belt]

Hi Graham, I have been trying so many things but over-written all that I’ve used in the process..

I guess the right way would be to either First get the velocity or speed of the Y-position, or an actual increase in Y position and map that to an increase in the value that the expression is added to with a Clamp.

thisComp.layer(“BUG”).transform.yPosition.velocity;
linear(velocity, 0, 10, 0, -10);

I am really new to expressions so I’m really not sure what would be the right one here.
I tried tweaking the squash and stretch expression from motionscript.com but also with a lot of tweaking that didn’t gave me the results I was looking for… I think that some else-if ideas and definitely some easing would really help sell the effect.. and well, in the worst case I end up keyframing it after all :))

Any ideas here would be greatly appreciated!

Cheers,

Wick

WickieMedia.net

[Wick Van den belt]

Worked like a charm!

Thanks a lot!

WickieMedia.net

[Wick Van den belt]

Hi Danny,
thanks a lot for your quick reply!

-That was exactly the answer that I was hoping for!

This means I should be able to do my animations and video-shots in 25 fps, and edit the whole film in that framerate and simply convert the final (preferably uncompressed?) render.

And a 4% speed change over a 60 minutes film wouldn’t be too bad I suppose!

I am curious to find out how the typography/animations will look like when using this workflow, So I might perform a few small test-renders.

And I suppose that I’ll have to be very precise with shooting and animating and keeping that final crop in mind when I’m going to convert it to NTSC for DVD.

Thanks a lot!
I might post my experiences on this workflow in a later stage. (It might help out someone else in the future.)

Cheers,

Wick.