site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com I mentioned this and filed bugs (one for this, and one for the [actionAPI currentTime] always returns 0 in FCP X bug), but I'm sure it's affected others. The timeline rendering makes workarounds difficult, i.e. you can't just cache a frame from the last renderOutput call. You might able to do your processing from parameterChanged in renderOutput (if the output data is small and the process is fairly fast), and store a map of render time to output data that you can access during parameterChanged. For the currentTime bug, the best workaround seems to be storing the time passed to an OSC. I haven't thought of a general workaround for this bug, so hopefully it will be fixed in the next release. On Aug 8, 2011, at 8:42 AM, Paul Miller wrote:
So my problem with getInputBitmap during parameterChanged last week was because I was using the wrong FxPlug SDK. It's all working properly in Motion.
However, I created a template and brought it into FCPX and when I click my button and get the input image (this is not from an image well), it's giving me the drop source arrow icon (at a large size) instead. I remember something along these lines from weeks ago, but I couldn't dig it up. Is there a workaround for this? _______________________________________________ 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/garrick%40digitalanarchy...
This email sent to garrick@digitalanarchy.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