[Ridley Walker]

RoRK its this thread:

https://forums.creativecow.net/thread/227/24967

[Ridley Walker]

@Dan;

Could you elaborate on the issue with the original expression and how replacement you graciously provided solves the problem?

[Ridley Walker]

[Michael Chappell] “As a side note, I’ve used this expression in comps that were 2-3 minutes without a problem in the past.
“

Yes, but the Composition you uploaded is longer than 18 minutes. Just discovered that Dan Ebberts solved the problem in the Expressions forum, it seems that the length of the Composition was a factor.

[Ridley Walker]

Its even more interesting. The distance between keyframes also factors in, the keyframe distance is another element in the inertial bounce calculation, this ditance may be returning a result that is makes division using the time factor (the length of the Comp at 0:18:35:14) produce a divide by zero result. Increasing the distance between keyframes or reducing the length of the Composition remove the error.

It seems you’ve revealed a flaw in the expression that only occurs under very specific circumstances.

[Ridley Walker]

Mike;

I took a peek at the project as well. The divide by zero error occurs at this line :

value + v*amp*Math.sin(freq*t*2*Math.PI)/Math.exp(decay*t);

and is related to the length of the Composition. The math involved is beyond me, but time in the expression is calculated on the length of the entire Composition. The Comp you uploaded is over 18 min long, adjust the Composition time to a minute and the expressions work.

I think this question/issue might be better answered by posting a the question in the Expressions Forum
https://forums.creativecow.net/adobe_after_effects_expressions

Perhaps Dan Ebberts will weigh in.

[Ridley Walker]

It works for me in CS6. Have you updated to the current version of CS6? Mine is 11.02.11.

If you are running the current version, try resetting the application preferences to their defaults by holding down Control+Shift+ Alt (Command+Shift+Option) when you launch After Effects.

[Ridley Walker]

Or you could use shape layers with dashed lines round joins and animate the offset.

6396_dots.aep.zip

[Ridley Walker]

The stroke width is a high number and you may have selected Stoke over Fill in the options.

The png you uploaded doesn’t show all the options in the Character panel, drag the bottom of it to reveal more controls.

[Ridley Walker]

You may have allocated too much RAM to After Effects. Cut down the number of cores available to AE, Todd Kopriva’s advice is that 8 cores is optimal.

See: https://forums.creativecow.net/readpost/2/1033810

I’m on a 12 core / 24 thread MacPro with 64GB or RAM, allocated 12 cores to AE with 3GB RAM each, 12 cores free for other apps.

[Ridley Walker]

I’m a Mac user and not certain how you check memory paging on Windows. I’d be looking for the equivalent of Activity Monitor for feedback.

Your RAID should be more than fast enough for your media. If your project uses only vector based files and no video, there isn’t an issue with transcoding or the like.

What happens when you disable Motion Blur for RAM preview?