site_archiver@lists.apple.com Delivered-To: Pro-apps-dev@lists.apple.com Darrin On Jul 2, 2009, at 7:29 AM, Paul Schneider wrote: Hi Eberhard, - Paul On Jul 2, 2009, at 9:01 AM, Eberhard Ammelt wrote: Hello, Is there anything I'm missing, or is there a workaround for this? Thanks, Eberhard Ammelt - Pixlock _______________________________________________ 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/pschneider%40apple.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/dcardani%40apple.com -- Darrin Cardani dcardani@apple.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... Or better yet, can you reproduce it with any of the filters in the "Time" category? Things like Echo, WideTime, etc.? That isn't something we're aware of; the FxTemporalImageAPI should work all the time in Final Cut. Can you make a sample plug-in that demonstrates this problem? I'm experiencing a problem when reading frames at arbitrary times in FCP (6.0.6). My fxplugin filter reads many frames sequentially using the FxTemporalImageAPI method "getInputBitmap:" in the "renderOutput:" section. This works in principal, but there seems to occur some confusion in FCP when events from the user interface are processed while reading frames: When I e.g. click somewhere into FCP's windows, only wrong images are read during the rest of the reading procedure. It looks like FCP returns only the current frame then. I've tried to distribute the frame reading procedure over many calls of "renderOutput:". This helps to continue reading the correct frames again, but doesn't fix the problem from the ground. This email sent to pschneider@apple.com This email sent to dcardani@apple.com This email sent to site_archiver@lists.apple.com