site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com I'm seeing some issues here that could seriously affect our products. First, we get the current time in the parameterChanged method with: id <FxCustomParameterActionAPI> actionAPI = [_apiManager apiForProtocol:@protocol(FxCustomParameterActionAPI)]; double t = [actionAPI currentTime]; That works in Motion 5 and has always worked before, but in FCP X it seems to always be 0. And we also need access to images outside of renderOutput, specifically in parameterChanged and from on-screen controls (or custom UI in FxPlug 1). I realize this isn't guaranteed by the API but it works in Motion 4 and 5. FCP X seems to return a solid color. I've only tried the bitmap calls here. Stuffing the current OpenGL context into an FxRenderInfo to get a texture seems problematic. Trying to cache a frame from the render calls seems difficult too because of FCP's timeline rendering. I can file a bug but I'm really hoping there are workarounds for this release. _______________________________________________ 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