Return-Path: Received: from [208.97.132.177] (HELO homiemail-a12.g.dreamhost.com) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 5228189 for AE-List@media-motion.tv; Wed, 25 Sep 2013 17:35:27 +0200 Received: from homiemail-a12.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a12.g.dreamhost.com (Postfix) with ESMTP id 2B3E9103006D for ; Wed, 25 Sep 2013 08:35:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=aescripts.com; h= mime-version:in-reply-to:references:from:date:message-id:subject :to:content-type; s=aescripts.com; bh=4FZJSwmC4SLEZUKq0TH2tuYkUh M=; b=QgjN+eeotBZdytRBNL988oJH/fECbYjA3ltphr18b7DBL4U18Owkv2ceUS 2CPXNvkUHdK/814n5u3tnEruDhDjOU+HicJblOGANFaCU51nQy8cw2uSnFVX+XNV 5eHrFLLqnekgzAD3kwM1wLiPcP55i0zDlPJGyNeRfb6hFa63A= Received: from mail-vc0-f177.google.com (mail-vc0-f177.google.com [209.85.220.177]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: lists@aescripts.com) by homiemail-a12.g.dreamhost.com (Postfix) with ESMTPSA id 85BCF103006A for ; Wed, 25 Sep 2013 08:35:37 -0700 (PDT) Received: by mail-vc0-f177.google.com with SMTP id hv10so4423346vcb.22 for ; Wed, 25 Sep 2013 08:35:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=Pvnfiec1uoGnBO2kncd94Fh6eCqoqWsI3JLJ909jm0I=; b=M1JTqEFQUaWh0PdLA0AUyY/s5OMgKfC8ZSGReMxFxWshxLp+s1MNszSNsBXwZ8t7fw dwmhOR+8bWBGFmjChn6AbxPGpAGMojqHdjg5LlrCH89w4Dt4V0AbUC8AOB69dzdQxeK0 mRT3mWcVO33cBP6XFpYRN9e2qllraS4qy0oh2yEOmGj+J5zsesvZoaiZ2mtcOfaPWR2D fEbmUmeelv3aDo4PVzux+4gqxZYKjHQV2xYJ645JGNO3lDtlOHghDzv3FWvsPk8Y++uC mHmKkCD0g/DSwCAPPfFcrLbeRW5z8sVXO9M506zeRNlxKM9PbPEPLNf41nlmdcXtqAXF eIOA== X-Received: by 10.58.230.135 with SMTP id sy7mr90292vec.42.1380123336565; Wed, 25 Sep 2013 08:35:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.193.2 with HTTP; Wed, 25 Sep 2013 08:34:56 -0700 (PDT) In-Reply-To: References: From: Lloyd Alvarez Date: Wed, 25 Sep 2013 11:34:56 -0400 Message-ID: Subject: Re: [AE] Inertial bounce expression keeps being disabled randomly... To: After Effects Mail List Content-Type: multipart/alternative; boundary=047d7bdc87be38eaf104e73701de --047d7bdc87be38eaf104e73701de Content-Type: text/plain; charset=ISO-8859-1 What line number are you getting the error on? On Wed, Sep 25, 2013 at 11:30 AM, D wrote: > Looks good. I'll try and persuade these guys to buy that script. Also, > I've just had more expression failures but still get the divide by zero > error when I try to paste your solution above. Is this a bug beyond the > expression? > > > On 25 September 2013 15:40, Lloyd Alvarez wrote: > >> You can use this to batch update all the expressions in your project: >> http://aescripts.com/pt_expressedit/ >> >> >> On Wed, Sep 25, 2013 at 9:46 AM, D wrote: >> >>> Yes, was guessing that. Too many instances to replace with an upcoming >>> deadline though so quick fixing with the aid of your script for now. >>> >>> >>> On 25 September 2013 14:35, Lloyd Alvarez wrote: >>> >>>> The expression will keep failing unless you account for that divide by >>>> zero error. >>>> >>>> >>>> On Wed, Sep 25, 2013 at 9:23 AM, D wrote: >>>> >>>>> Thanks Lloyd. Funnily enough, I just found your script 'Activate >>>>> Disabled Expressions'. I purged all memory then applied the script. >>>>> Emptying the memory seems to allow them back on. Great script. Next time I >>>>> get a mass disablement I'll try your solution. >>>>> >>>>> >>>>> On 25 September 2013 12:35, Lloyd Alvarez wrote: >>>>> >>>>>> As the error suggests, it gets disabled because it tries to divide by >>>>>> zero.. Most probably because you are in negative time due to this: t >>>>>> = time - key(n).time; >>>>>> >>>>>> You can protect against that in several ways but here's a quick >>>>>> cheeky way: >>>>>> >>>>>> amp = .1; >>>>>> >>>>>> freq = 2.0; >>>>>> >>>>>> decay = 12.0; >>>>>> >>>>>> n = 0; >>>>>> >>>>>> if (numKeys > 0){ n = nearestKey(time).index; >>>>>> >>>>>> if (key(n).time > time){ n--; >>>>>> >>>>>> }} if (n == 0){ t = 0; >>>>>> >>>>>> }else{ t = time - key(n).time; >>>>>> >>>>>> } if (n > 0){ v = velocityAtTime(key(n).time - >>>>>> thisComp.frameDuration/10); >>>>>> d= Math.exp(decay*t); >>>>>> if ( d == 0 ) d= 0.0001; >>>>>> >>>>>> value + v*amp*Math.sin(freq*t*2*Math.PI)/d; >>>>>> >>>>>> }else{value} >>>>>> >>>>>> >>>>>> Cheers, >>>>>> Lloyd >>>>>> >>>>>> On Wednesday, September 25, 2013, D wrote: >>>>>> >>>>>>> ...confusingly, the expression will sometimes continue to work on >>>>>>> other layers in the same comp on both position and scale parameters whilst >>>>>>> some get disabled. >>>>>>> >>>>>>> >>>>>>> On 25 September 2013 10:40, D wrote: >>>>>>> >>>>>>>> Hi >>>>>>>> >>>>>>>> The expression I'm using looks like this: >>>>>>>> >>>>>>>> amp = .1; >>>>>>>> >>>>>>>> freq = 2.0; >>>>>>>> >>>>>>>> decay = 12.0; >>>>>>>> >>>>>>>> n = 0; >>>>>>>> >>>>>>>> if (numKeys > 0){ n = nearestKey(time).index; >>>>>>>> >>>>>>>> if (key(n).time > time){ n--; >>>>>>>> >>>>>>>> }} if (n == 0){ t = 0; >>>>>>>> >>>>>>>> }else{ t = time - key(n).time; >>>>>>>> >>>>>>>> } if (n > 0){ v = velocityAtTime(key(n).time - >>>>>>>> thisComp.frameDuration/10); >>>>>>>> >>>>>>>> value + v*amp*Math.sin(freq*t*2*Math.PI)/Math.exp(decay*t); >>>>>>>> >>>>>>>> }else{value} >>>>>>>> >>>>>>>> >>>>>>>> It works most of the time then will randomly get disabled across >>>>>>>> lots of layers and will not allow me to re-enable until I've restarted AE >>>>>>>> (v5.5). This is the error: >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> >>>>>>>> After Effects warning: invalid numeric result (divide by zero?) >>>>>>>> >>>>>>>> Expression disabled. >>>>>>>> >>>>>>>> >>>>>>>> Error occurred at line 10. >>>>>>>> >>>>>>>> Comp: 'XXX' >>>>>>>> >>>>>>>> Layer 17 ('XXX') >>>>>>>> >>>>>>>> Property: 'Scale' >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> >>>>>>>> I have no real knowledge of how expression code works. I cut and >>>>>>>> paste when I use them. The project is 4 minutes long and the expression >>>>>>>> occurs across many comps and typically as the deadline approaches the error >>>>>>>> is now cropping up often. Any help appreciated. >>>>>>>> >>>>>>>> >>>>>>>> Thanks. >>>>>>>> >>>>>>> >>>>>>> >>>>> >>>> >>> >> > --047d7bdc87be38eaf104e73701de Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
What line number are you getting the error on?


On Wed, Sep 25, 201= 3 at 11:30 AM, D <dow.hanson@gmail.com> wrote:
Looks good. I'll try an= d persuade these guys to buy that script. Also, I've just had more expr= ession failures but still get the divide by zero error when I try to paste = your solution above. Is this a bug beyond the expression?=A0


On 25 Septemb= er 2013 15:40, Lloyd Alvarez <lists@aescripts.com> wrote:<= br>
You can use this to batch update all the expressions in yo= ur project:=A0http://aescripts.com/pt_expressedit/


On Wed, Sep 25, 2013 at 9:46 AM, D <dow.hanson@gmail.com>= wrote:
Yes, was guessing that. Too many instances to replace with= an upcoming deadline though so quick fixing with the aid of your script fo= r now.=A0


On 25 September 2013 14:35, Lloyd Alvare= z <lists@aescripts.com> wrote:
The expression will keep fa= iling unless you account for that divide by zero error.


On Wed, = Sep 25, 2013 at 9:23 AM, D <dow.hanson@gmail.com> wrote:<= br>
Thanks Lloyd. Funnily enoug= h, I just found your script 'Activate Disabled Expressions'. I purg= ed all memory then applied the script. Emptying the memory seems to allow t= hem back on. Great script. Next time I get a mass disablement I'll try = your solution.


On 25 Septemb= er 2013 12:35, Lloyd Alvarez <lists@aescripts.com> wrote:<= br>
As the error suggests, it gets disabled because it tries to divide by zero.= . Most probably because you are in negative time due to this:=A0t =3D time - key(n)= .time;

<= /span>
You can protect against that in several ways but here&#= 39;s a quick cheeky way:

amp =3D .1;

freq = =3D 2.0;

decay =3D 12.0;

n= =3D 0;

if (numKeys > 0){ n =3D nearestKey(time).index;

if (key(n).time > time){ n--;

}} if (n =3D=3D 0){ t =3D 0;

}else{ t =3D time - key(n).time;

} if (n > 0){ v =3D velocityAtTime(key(n).time - thisComp.frameDuration/= 10);

d=3D=A0Math.exp(decay*t);
if ( d =3D=3D 0 ) d=3D 0.0001;

=A0value + v*amp*Math.sin(freq*t*2*Math.PI)/d;

}else{value}


Cheers,

<= /span>
Lloyd
=
On Wednesday, September 25, 2013, D wrote:
...confusingly, the expression will sometimes continue to = work on other layers in the same comp on both position and scale parameters= whilst some get disabled.=A0


On 25 September 2013 10:40, D <dow.hanson@gmail.com= > wrote:
Hi

The expression I'm using looks l= ike this:

amp =3D .1;

= freq =3D 2.0;

= decay =3D 12.0;

= n =3D 0;

= if (numKeys > 0){ n =3D nearestKey(time).index;

= if (key(n).time > time){ n--;

= }} if (n =3D=3D 0){ t =3D 0;

= }else{ t =3D time - key(n).time;

= } if (n > 0){ v =3D velocityAtTime(key(n).time - thisComp.frameDuration/= 10);

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

= }else{value}


It works most of the time then will randomly get disabled across lots of la= yers and will not allow me to re-enable until I've restarted AE (v5.5).= This is the error:


--


After Effects warning: invalid numeric result (divide by zero?)

Expressi= on disabled.


Error occurred at line 10.

Comp: 'XXX'

Layer 17 ('XXX')

Property: 'Scale'


--


I have no real knowledge of how expression code works. I cut = and paste when I use them. The project is 4 minutes long and the expression= occurs across many comps and typically as the deadline approaches the erro= r is now cropping up often.=A0Any help appreciated.

=

Thanks.








--047d7bdc87be38eaf104e73701de--