Return-Path: Received: from mail-iy0-f169.google.com ([209.85.210.169] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 4831949 for AE-List@media-motion.tv; Fri, 31 Aug 2012 23:43:45 +0200 Received: by iagk10 with SMTP id k10so5669525iag.28 for ; Fri, 31 Aug 2012 14:44:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=79qZRHnTzWUMiswPLU2XNSTJIrdgDBAxX6k/Ea5WlJI=; b=CiI1ERoyPxTdt86Az8nztcw5gPtaa4yCSgcRVFsPN/cDxM+wbqjXs1fGVJEgAf93i3 t/i3hEGrrl/Ua0HO/nh9Bnbp8Rlvmng0hNuFwBURU3+Ktgtu2eYQ/QjObJG43LJByeAC b0RvtjCBG1fQn7IoeT1Og7b4rHhBGkyAXuTfmTZnTEB0sP5KAPoQpgTPmnKlpHe+89d6 WpXD6xxpR+LEb+t1NUxr3gv4sbN02+em77bQ1xbhF6r+HjbJ8ftCMF1AohN54TQYSPL0 iFn53mTz4WtjxsqYJJaoFwdoQwmkXOPqeGlDo81RDIYNqWZJQnrJcF2v3oYT3zro+Oyv vZww== MIME-Version: 1.0 Received: by 10.50.158.169 with SMTP id wv9mr4451672igb.25.1346449477759; Fri, 31 Aug 2012 14:44:37 -0700 (PDT) Received: by 10.64.165.167 with HTTP; Fri, 31 Aug 2012 14:44:37 -0700 (PDT) Received: by 10.64.165.167 with HTTP; Fri, 31 Aug 2012 14:44:37 -0700 (PDT) In-Reply-To: References: Date: Fri, 31 Aug 2012 14:44:37 -0700 Message-ID: Subject: Re: [AE] building a dynamic node-like effect in AE From: Darby Edelen To: After Effects Mail List Content-Type: multipart/alternative; boundary=14dae93404bdd4711104c896b20c --14dae93404bdd4711104c896b20c Content-Type: text/plain; charset=ISO-8859-1 Getting here a bit late but it seems like a good opportunity to mention that you can place adjustment layers in a precomp and then nest that precomp (with transformations collapsed) inside additional comps. This gives you centralized access to the effects. On Aug 31, 2012 7:04 PM, "Teddy Gage" wrote: > > Ah I went the lazy man's route and just re-cut the layers to start at their original in-point. But that makes a lot of sense as to why the transition didn't occur at the "visual layer in-point." And should be extremely useful in the future. Then, because ft-Instance won't link to expressions I used an animation preset of the instanced effect (still referencing the master effect) and dropped it on all the layers. But then I still couldn't change the transition length for all of them at once, because that info was just a number embedded in the transition expression. so I made a slider control, linked that to transition length, and now all the effect-preset-instanced expressions could be changed from that one variable slider. I DARE the client to ask me to change the page peel length again! > > sorry for the email flood guys. too much coffee this morning. > > On Thu, Aug 30, 2012 at 6:22 PM, Chris Zwar wrote: >> >> 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=thisLayer.inPoint; >> end=thisLayer.outPoint; >> dur=end-start; >> count=time-start; >> >> //in frames // >> fps = 1 / thisComp.frameDuration; >> start=start*fps; >> end=end*fps; >> dur=dur*fps; >> count=count*fps; >> count=clamp(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 > > > > > -- > Animator & Editor > www.teddygage.com > Brooklyn > --14dae93404bdd4711104c896b20c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Getting here a bit late but it seems like a good opportunity to mention = that you can place adjustment layers in a precomp and then nest that precom= p (with transformations collapsed) inside additional comps. This gives you = centralized access to the effects.

On Aug 31, 2012 7:04 PM, "Teddy Gage" <teddygage@gmail.com> wrote:
>
> Ah I went the lazy man's route and just re-cut the layers to start= at their original in-point. But that makes a lot of sense as to why the tr= ansition didn't occur at the "visual layer in-point." And sho= uld be extremely useful in the future. Then, because ft-Instance won't = link to expressions I used an animation preset of the instanced effect (sti= ll referencing the master effect) and dropped it on all the layers. But the= n I still couldn't change the transition length for all of them at once= , because that info was just a number embedded in the transition expression= . so I made a slider control, linked that to transition length, and now all= the effect-preset-instanced expressions could be changed from that one var= iable slider. I DARE the client to ask me to change the page peel length ag= ain!
>
> sorry for the email flood guys. too much coffee this morning.=A0
>
> On Thu, Aug 30, 2012 at 6:22 PM, Chris Zwar <chris@chriszwar.com> wrote:
>>
>> 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 star= ting the transition. Is there another pointer besides this.inPoint? I tried= thisLayer.inPoint and it was still starting the transition back at the zer= o mark, even if the layer didn't start being visible until 30 seconds i= n. 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 compositi= on. does that make any sense?
>>
>>
>> Hi,
>>
>> Just to give you something different to think about, I usually bui= ld these sort of automated expressions to work in numbers of frames. =A0I t= end to think of 25 - 50 frame transitions rather than 1 or 2 second transit= ions. =A0This 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 l= ayer it is, you need to subtract the layer's in-point from the composit= ion time. =A0This might be the hint you're after.
>>
>>
>> -Chris
>
>
>
>
> --
> Animator & Editor
> www.teddygage.com
> Brooklyn
>

--14dae93404bdd4711104c896b20c--