site_archiver@lists.apple.com Delivered-To: Pro-apps-dev@lists.apple.com Hello Darrin, the problem seems to be related to caching of textures. The plugin uses a contiguous range of texture frames and keeps the recently used ones retained so mostly only one frame needs to be read from the timeline per "renderOutput:" call. Is it wrong to retain textures beyond the scope of "renderOutput:"? Eberhard
Eberhard, That's something that should work correctly. My only guess would be either to make sure you're actually sending different time values (within the valid range for the clip) for each frame. If that's happening correctly, it could be a bug in FCP (though I'd think someone would have run into this sooner if it were).
Darrin
On Nov 19, 2010, at 6:08 AM, Eberhard Ammelt wrote:
Hello,
I'm trying to read a contiguous range of textures from the timeline in FCP (7.0.2) using "getInputTexture:". All the returned textures seem to contain just the current image though the texture ids are different. Am I missing anything?
Thanks, Eberhard _______________________________________________ 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
This email sent to dcardani@apple.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... This email sent to site_archiver@lists.apple.com