site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 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. Okay thanks for the clarification. _______________________________________________ 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 8/8/2011 12:23 PM, Garrick Meeker wrote: I haven't thought of a general workaround for this bug, so hopefully it will be fixed in the next release. I also hit the "custom data not getting saved" bug, which pretty much kills about 6 of my more advanced filters. Hopefully we'll see an updated version of FCPX with all of these fixes this year so we can support it. As it is now it would be a support nightmare for us. This email sent to site_archiver@lists.apple.com