[Sam Mattson]

Note that you can also switch your frame blending on or toggle it to pixel motion (the little film icon in your switches/modes). This won’t give you quite as good of results as Twixtor will, but in many cases it works for what you’re doing.

[Sam Mattson]

I know I’m a little late to the game on this one, but if you’re aware something is going to take a long time to render, always render to frames. That way if it crashes, you can fix the problem and start the render again where it left off. Then media encode from the frames. You’ll save yourself a ton of time doing it this way.
As for what was causing your render to take so long, were you trimming your layers? AE will spend the time rendering a layer even if it’s covered up or off stage. If you hadn’t trimmed anything through your entire comp it’s now rendering everything through your whole timeline.
Other things can cause slow render times also (particles, lots of copies of something, large file sizes, using PDFS, etc). The best thing to do is to attempt to scrub your timeline in that area until your output slows down, then stop in that area and start turning off layers or effects until you find the culprit. Then perhaps you can create a proxy, downres, or find another way of creating the effect…or just realize that part is going to take a while and render it overnight or something.

[Sam Mattson]

Exactly what I was looking for. Thanks.

[Sam Mattson]

Same here! Also found this searching for an answer, also using DUIK. It’s even glitchy when keyframing manually (no slider).

[Sam Mattson]

I have severely underutilized this effect. It’s damn close to what I’m looking for and with a little warp effect on top will do just what I want. Thanks!

[Sam Mattson]

Thanks Dave, I’ll be animating the mask path. Thought there had to be an easier way. 🙂

[Sam Mattson]

I had coded that too, but I was hoping to find the initial position without looking at time, as the nulls I’ll be moving are on a character rig. Oh well, I guess I’ll hand enter the initial values.

[Sam Mattson]

On other words, I know I can write it like this:

variance = 640-thisComp.layer("Null 2").transform.position[1];
xPos=transform.position[0]+variance;
yPos=transform.position[1];
[xPos, yPos]

But I’d like to not have to type the manual value of “640” in if I applied this script to something else with a different Y value.