Article View: adobe.after.effects
Article #58Re: Particle Playground in RAM preview
From: Mylenium
Date: Mon, 30 Mar 2009 06:52
Date: Mon, 30 Mar 2009 06:52
11 lines
1760 bytes
1760 bytes
desirable??? it's essential!! so, what do you mean by "technically nothing
needs to be fixed"
Not really. Working with relative units has disadvantages, too (think of the million people whose brain will explode when suddenly they have to set positions or item sizes in fractions of percent...). And technically nothing needs to be fixed - the current behavior is correct in terms of the underlying math and predictable by the user, the only real problem is that Adobe does a pretty poor job of communicating it to the user. If you get my meaning - you will want to work at reduced resolutions all the time to speed up interactivity, but you usually do not want it to make your work less predictable. They are still two different things, though. One could also argue that the flaw is simply in the effect/ plug-in. By all means, within the ranks of the AE API (as I understand it), it could just as well request the full resolution buffer, but then again, I don't know enough of that nor do I know anything about the licensing stuff that futzing with the code may touch upon, as apparently the effect originated outside Adobe a long time ago...
Mylenium
Technical Details
Message-ID:
<59b86bb5.7@webcrossing.la2eafNXanI>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!newshub.sdsu.edu!webcrossingReferences:
<59b86bb5.-1@webcrossing.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Thread: 105699,2e7b39a7c3a277c6 X-Google-Attributes: gid105699,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit From: Mylenium@adobeforums.com Path: arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!newshub.sdsu.edu!webcrossing Newsgroups: adobe.after.effects Subject: Re: Particle Playground in RAM preview Message-ID: <59b86bb5.7@webcrossing.la2eafNXanI> Date: Sun, 29 Mar 2009 23:52:28 -0700 References: <59b86bb5.-1@webcrossing.la2eafNXanI> Lines: 21 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit