phiol

In this patch I have a pulsating png. using the scale @.

1. is it better on CPU % to use jit.anim.path or jit.anim.drive over MSP to create animations?

2. I've tried a few different combos with jit.anim.path (you'll see in the patch) but w. no success.

I feel jit.anim.path is not efficient ; is there quick way to create the equivalence of what I've done in MSP ?

https://www.dropbox.com/sh/igndylhcwfbc4h4/AAD_ZNxsfXzag3NZZ-zwkVRxa/pulsate%20anim%20vs.%20sig~.zip?dl=0

In this patch I have a pulsating png. using the scale @.
and driving the motion w. MSP. 

1. is it better on CPU % to use jit.anim.path or jit.anim.drive over MSP to create animations?
2. I've tried a few different combos with jit.anim.path (you'll see in the patch) but w. no success.
I feel jit.anim.path is not efficient ; is there quick way to create the equivalence of what I've done in MSP ? 

to-jit-anim-path-or-not-to-jit-anim-path

here's how you would do it with jit.anim.path:

append indicates insert second point with index i.d.(1) / (3 following == rotatexyz 0 0 0)

And final, is it better to use jit.anim.path over MSP like I did in my patch ?

Endless thanks for your hard work in Jitter.

append 0 0 0 0,addscale 0.4 0.4 0.4,append 1 0 0 0,append indicates insert second point with index i.d.(1) / (3 following == rotatexyz 0 0 0)addscale 0.43 0.43 0.43 

Endless thanks for your hard work in Jitter. 

Reading the help document I see that the 1st value following append

time value, 3 position values, 3 scale values and 4 quaternion rotation values

perfect so far so good. So what is this time based on. ms, sec, frames ??

this 1st is directly dependent on the rate right.

I've tested inserting "append 0.2" for my second point and as expected it will go faster

but again this is also relative to the rate $1.

Would it be possible to shed any light on how to calculate the time.

Reading the help document I see that the 1st value following append
is the time value.time value, 3 position values, 3 scale values and 4 quaternion rotation values

perfect so far so good. So what is this time based on. ms, sec, frames ??
this 1st is directly dependent on the rate right. 

I've tested inserting "append 0.2" for my second point and as expected it will go faster
but again this is also relative to the rate $1. 

Would it be possible to shed any light on how to calculate the time.
Or just know what it represents 

the time is in seconds, and is relative to the rate attribute.

Yep I seen that , and a rate of 1 is == ?

Anyways , one more important last one :-)

it better to use jit.anim.path over MSP like I did in my patch ?

Yep I seen that , and a rate of 1 is == ? 

Anyways , one more important last one :-) 

to jit.anim.path Or not to jit.anim.path