[Scott G]

So the jackinabox pops up, and bounces with decay to a halt. but then imagine it went back into it’s box, it should have a small anticaptory bounce before going back down. i actually don’t think this is possible with the one expression on the one layer, as the beginning motion and the end motion are two different things, one a decaying spring, the other an anticipatory pseudo-squash-stretch motion. it’s not simply playing the first move in reverse…

any clues here guys? dan?

[Scott G]

heh, thanks, i would have checked jj gifford and dan’s site later on, i’m just swamped at the moment. perhaps this should be added to that sticky list of common questions, i searched for “bounce” and got a million responses (they were all drop-and-bounce though, not jackinthebox).

cheers,
scott.

[Scott G]

heh, thanks, i would have checked jj gifford and dan’s site later on, i’m just swamped at the moment. perhaps this should be added to that sticky list of common questions, i searched for “bounce” and got a million responses (they were all drop-and-bounce though, not jackinthebox).

cheers,
scott.

[Scott G]

i’m working on this at the moment, here’s where i am so far – blur works on z distance. it’s easy enough to change this for camera position, just subtractt the position of the layer from the position of the layer, and multiply by -1 if it’s a negative value.

you need a null object with a slider effect on it. name the slider “Divider”

positionz = position[2];
divider = thisComp.layer(“Slider”).effect(“Divider”)(“Slider”);
multiplier = -1;
blur = positionz/divider;
if (blur < 0) { blur = blur*multiplier } else { blur } blur; the problem i'm having at the moment is figuring out what to do if the camera rotates. i need to calculate distance from the front of the camera, is the direction that the camera is facing, rather than simply relying on z-space calculations. z is fine if all you're doing is flying in and out, but what if you turn 90 degrees? nothing will look right. never was perfect at maths, and not sure how the rotation (or orientation) of the camera factors in?

[Scott G]

i’m working on this at the moment, here’s where i am so far – blur works on z distance. it’s easy enough to change this for camera position, just subtractt the position of the layer from the position of the layer, and multiply by -1 if it’s a negative value.

you need a null object with a slider effect on it. name the slider “Divider”

positionz = position[2];
divider = thisComp.layer(“Slider”).effect(“Divider”)(“Slider”);
multiplier = -1;
blur = positionz/divider;
if (blur < 0) { blur = blur*multiplier } else { blur } blur; the problem i'm having at the moment is figuring out what to do if the camera rotates. i need to calculate distance from the front of the camera, is the direction that the camera is facing, rather than simply relying on z-space calculations. z is fine if all you're doing is flying in and out, but what if you turn 90 degrees? nothing will look right. never was perfect at maths, and not sure how the rotation (or orientation) of the camera factors in?

[Scott G]

Okay, thanks so much for the explanation. 🙂

[Scott G]

Thanks for the explanation, Mylenium! So if I understand correctly, if I applied a 3pixel fast blur 3 times, would this be the same as a 3 pixel box blur with an iteration of 3?
Why don’t they have an iterations slider for fast blur then?

Hmm perhaps I am perhaps still slightly confused.

Regards,
Scott.

[Scott G]

thanks, that’s exactly what i was after. i came across the date() code last night, but then wasn’t sure if i could use IF statements in expressions. i know i could use them in scripts but i didn’t think expressions could contain such things.

now that i know, well, it opens up a world of possibilities!

and much more elegant that simply using multiple instances of the effect and masking. :p

[Scott G]

thanks, that’s exactly what i was after. i came across the date() code last night, but then wasn’t sure if i could use IF statements in expressions. i know i could use them in scripts but i didn’t think expressions could contain such things.

now that i know, well, it opens up a world of possibilities!

and much more elegant that simply using multiple instances of the effect and masking. :p

[Scott G]

another issue i’m coming up against is when i try to use nucleo to do a ram preview. the popup message comes up, then it starts rendering. the “est remain” starts counting down…
then, a short way into the rendering process, the entire screen starts flickering madly. i can just make out in the flickering that the counter is still counting down, till it gets to “est remain: 1sec”. then it stays on 1 sec for about 15 seconds. then then flickering stops, and the “est remain” jumps back from 1sec to 40 secs, or something else, and rendering continues from where the flickering started.

also, once the ram preview is complete, the popup message windows seem to stop playback when they popup (just like switching out of afx would stop playback).

these two things are incredibly annoying. is there anything i can do about this?

also, nucleo feels the need to tell me continually that i have other applications running. of course i have other apps running! i’m trying to design here! is there any way to turn off this annoying popup?