wiggle and rendering?

[Bartek Skorupa]

wiggle itself won’t cost you anything.

wiggle is a pure math. Math is easy for the computer.

“154795421.466845 * 12433.2464 / 0.00054745 – 12” is impossible to compute by human’s brain, but for computer it’s a piece of cake.

However if your wiggle causes anything that increases rendering time, i.e – motion blur, or anything similiar – well… it will cost you.

But pure wiggle? No way.

Let me put it this way: We have 100 frames animation of solid standing still.
What will be rendered longer: The composition that has 100 position keyframes set to the same value, or the one without any keyframe?

Answer: The time of rendering will be the same.

What if you put “wiggle(0,0);”?

Nothing.

So let’s put “wiggle(120,50);”

Any difference? NONE.

Unless you activate motion blur of-course.

Calculation of the value of the cartaint parameter caused by wiggle is done before anything time consuming happens. Wiggle only set’s the value. It doesn’t do anything else.

Bartek Skorupa
Warszawa, Poland