site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2 On Sep 20, 2011, at 11:20 AM, Paul Miller wrote: We've fixed a number of bugs. Here are the ones I think most concern FxPlug developers: - frame times in FCPX now work like they did in FCP 7 - Image sizes should be more sensible now, including when using the temporal API and parameter APIs - This one's a little tricky because there remain some issues we haven't addressed, but basically, images are passed to plug-ins at their actual size, even in FCP templates. So if your Final Cut Effect is 1920x1080, but the user applies it to footage that is 1280x720, your input and output frames (and those from the temporal API) will be 1280x720. However, there still appears to be an issue where we're setting the texture coords of FxTextures to be 2 pixels wider than the images. But we aren't rescaling anything to the full template size anymore - Programmatically changed values should now be properly saved in FCPX - [-FxCustomParameterActionAPI currentTime] should work properly now, even during non-render times (i.e. in parameterChanged) _______________________________________________ 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... On 9/20/2011 4:13 PM, Darrin Cardani wrote: Saw the update announcement (thanks for the heads-up!) and was wondering if any of the FxPlug bugs we've been reporting have been addressed. I think those are the biggest ones. Have any insight on bug # 10001565? I note there hasn't been any input on it at all, but it is seriously impacting several of our plugins that have custom (external) UIs. This email sent to site_archiver@lists.apple.com