site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=WLOGSStWYD8zj4UdN8ar2viAjoSp0eHNaVc7/Vww+7wC1QtcAfSz8AcKfrXL/Iz+; h=Received:Cc:Message-Id:From:To:In-Reply-To:Content-Type:Mime-Version:Subject:Date:References:X-Mailer:X-ELNK-Trace:X-Originating-IP; Patrick On Apr 24, 2009, at 11:43 AM, Darrin Cardani wrote: Thanks! Darrin _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... This email sent to site_archiver@lists.apple.com While I can think of all kinds of fun things one could do with access to this data (smoothing, etc), what I really need in FxPlug support is a library of routines that provide the functionality available in FxScript. I realize this is something that big time developers probably don't need, but to the "casual" developer such as myself - I just don't have the resources to write a huge library containing blur routines/keying routines/blend mode routines/etc... In fact, I really see no reason that there couldn't be a FxScript to FxPlug compiler... That would aid migration ENORMOUSLY. I understand that you're largely geared to supporting the big developers, but thought I'd put my 2¢ in... It was great to see several of you at NAB this week! I hope you all had a great time and made a lot of money. :) In talking with 3rd party developers about the future of the FxPlug API, one thing that came up repeatedly was the need for an API that allows access to the app's keyframe data. [snip] tion. I'm hoping we'll be able to implement it, but first we have to design it and discuss it. :) smime.p7s