site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com In my opinion it is very important to be able to get to the source file of the effect source, at the very least when and if the effect is sitting directly on footage. The same goes for timing info relative to the effect and to the footage item. Rainer On Jul 18, 2011, at 11:03, Darrin Cardani wrote:
On Jul 18, 2011, at 9:37 AM, Paul Miller wrote:
Even if we added that, users still want to be able to create Motion templates with your plug-ins, so they need to work properly in that case, anyway.
The Motion templates are nifty and all, but when applying them in FCPX, they should at least report correct information about the clips they are applied to.
Maybe I'm missing something/not thinking different enough, but this seems like a really really bizarre design choice.
I don't recall every nuance of the design decisions off the top of my head, but keep in mind that your plug-in may not be applied directly to footage. The effect source could be inside a group, with the filter applied to the group, or it could be that the effect source is the source for an emitter or replicator, and the effect is applied to the emitter or replicator instead. This complicates things a little bit.
Darrin -- Darrin Cardani dcardani@apple.com
_______________________________________________ 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/lists%40standke.com
This email sent to lists@standke.com
_______________________________________________ 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