Return-Path: Received: from omr6.networksolutionsemail.com ([205.178.146.56] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 4830864 for AE-List@media-motion.tv; Fri, 31 Aug 2012 00:21:22 +0200 Received: from cm-omr4 (mail.networksolutionsemail.com [205.178.146.50]) by omr6.networksolutionsemail.com (8.14.4/8.14.4) with ESMTP id q7UMMDIL005611 for ; Thu, 30 Aug 2012 18:22:13 -0400 Authentication-Results: cm-omr4 smtp.user=chris@chriszwar.com; auth=pass (PLAIN) X-Authenticated-UID: chris@chriszwar.com Received: from [122.150.240.225] ([122.150.240.225:49904] helo=[192.168.0.2]) by cm-omr4 (envelope-from ) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 17/18-26650-397EF305; Thu, 30 Aug 2012 18:22:13 -0400 From: Chris Zwar Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/alternative; boundary=Apple-Mail-1-838426420 Subject: Re: [AE] building a dynamic node-like effect in AE Date: Fri, 31 Aug 2012 08:22:10 +1000 In-Reply-To: To: "After Effects Mail List" References: Message-Id: X-Mailer: Apple Mail (2.1084) --Apple-Mail-1-838426420 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 31/08/2012, at 4:11 AM, Teddy Gage wrote: > The second issue I'm now having is that even though "this.inPoint" is = supposed to start at the layer's inpoint, I still have to scrub the = layer back in time to find out where it is actually starting the = transition. Is there another pointer besides this.inPoint? I tried = thisLayer.inPoint and it was still starting the transition back at the = zero mark, even if the layer didn't start being visible until 30 seconds = in. This could be because I split the layers (they are stills) and it's = looking at the origin in point and not the actual in point in the = composition. does that make any sense? Hi, Just to give you something different to think about, I usually build = these sort of automated expressions to work in numbers of frames. I = tend to think of 25 - 50 frame transitions rather than 1 or 2 second = transitions. This code sets up a few basic variables that I use: // in seconds // start=3DthisLayer.inPoint; end=3DthisLayer.outPoint; dur=3Dend-start; count=3Dtime-start; //in frames // fps =3D 1 / thisComp.frameDuration; start=3Dstart*fps; end=3Dend*fps; dur=3Ddur*fps; count=3Dcount*fps; count=3Dclamp(count,0,dur); // optional // [count] If you want a variable that counts the number of frames into the layer = it is, you need to subtract the layer's in-point from the composition = time. This might be the hint you're after. -Chris= --Apple-Mail-1-838426420 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii The second issue I'm now having is = that even though "this.inPoint" is supposed to start at the layer's = inpoint, I still have to scrub the layer back in time to find out where = it is actually starting the transition. Is there another pointer besides = this.inPoint? I tried thisLayer.inPoint and it was still starting the = transition back at the zero mark, even if the layer didn't start being = visible until 30 seconds in. This could be because I split the layers = (they are stills) and it's looking at the origin in point and not the = actual in point in the composition. does that make any = sense?

Hi,

Just = to give you something different to think about, I usually build these = sort of automated expressions to work in numbers of frames. I tend = to think of 25 - 50 frame transitions rather than 1 or 2 second = transitions. This code sets up a few basic variables that I = use:

// in seconds //

start=3DthisLayer.inPoint;

dur=3Dend-start;

count=3Dtime-start;

//in frames //

fps =3D 1 / thisComp.frameDuration;

start=3Dstart*fps;

end=3Dend*fps;

dur=3Ddur*fps;

count=3Dcount*fps;

count=3Dclamp(count,0,dur); // optional //

[count]

If you want a variable that counts the = number of frames into the layer it is, you need to subtract the layer's = in-point from the composition time. This might be the hint you're = after.

-Chris

= --Apple-Mail-1-838426420--