site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Hey gang, Cheers, Greg. _______________________________________________ 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... All generators, including motion templates, when dragged to the browser have no XML representation since they aren't clips, but instead, short-cuts to an effect. That makes perfect sense. And FCP is smart enough to know that if it is dragged into the Browser, and you select the generator, it won't let the user export it (Export XML is grayed out). Unfortunately if the user selects the clip's container (its bin, or the whole project) then the export is allowed to happen with the "empty" XML for the generator. I understand the difference, but to most users it wouldn't make sense. I've rewritten our help doc with explicit instructions on adding a Motion Template through the Viewer. What would you expect the XML to be? Perhaps a new kind of bin entity much like an effect definition on a clip? As long as it had enough information in the XML to recreate the generator item on import, that'd be perfect! This email sent to site_archiver@lists.apple.com