[Peter Zeet]

Hiya!
I’m curious if it’s possible to update this expression using the new sourceRectAtTime().width so we can get rid of the copy path as position to null?
I’m thinking about a ball following the end trim as on a video player, but making it work no matter the path’s width (and not using the position null trick)?

[Peter Zeet]

Oh, many thanks!! worked perfectly!

[Peter Zeet]

mmm I should have explained better:
the scene is something like an assembly line, and the animated shape layer would be a chain (with a product at the bottom). So the basic animation is the null at the top going from left to right of the screen, with some holds in the middle of the screen. The bottom null would drive the overlaping animation of that chain when the Up null makes the hold.(And going down to find a paint bucket and then up again) Then the animation continues to the right.
So this is repeated like 50 times. The way the scene is done I can’t precompose anything (plus the client needs the scene this way), so I was faking it with the inPoint thing, so I just make the sequence once on each null.
Maybe there is a workaround to drive the bottom of the chain triggered by each shape layer’s inPoint?

(this is one of these cases where I could have it done by hand and finished it time ago instead of trying to speed the proccess via expressions, but now I can’t stop until I figure out how to do it via expressions! arg

anyway, if you think it’s a waste of resources, I’ll have to do it by hand

thanks again!

[Peter Zeet]

works like a charm! thanks!!!

[Peter Zeet]

amaaazing! thanks!!!

[Peter Zeet]

actually.. do you think it’s possible to tweak the function to make the letters fade out randomly and not all the word together?

[Peter Zeet]

awesome! thanks!
I was thinking in a random fade out per character, but it works too!

[Peter Zeet]

awesome!!

uhm… do you think is it possible to fade it out before reaching the outPoint?

thanks!!!

[Peter Zeet]

I think it works! Thanks!!

[Peter Zeet]

über awesome, thanks!