Re: note on problem reports
Re: note on problem reports
- Subject: Re: note on problem reports
- From: Steve Christensen <email@hidden>
- Date: Mon, 21 Jul 2008 13:41:37 -0700
On Jul 21, 2008, at 9:46 AM, Kristian Harms wrote: Den 21. juli. 2008 kl. 16.14 skrev Steve Christensen:
What are you doing to determine the length of the clip?
For the simple plugin I made to verify this problem in a minimalist way, I'm simply doing:
id timingAPI = [_apiManager apiForProtocol:@protocol(FxTimingAPI)]; if (!timingAPI) return NO; const double duration = [timingAPI durationForEffect: self]; const double progress = renderInfo.frame/duration;
We have both seen issues with the timingAPI, as you'll remember, but I haven't seen any of that as I was making this debug plugin.
I was asking because I haven't seen cases where the duration was changing for a particular plugin instance. (Other instances of the plugin most definitely do! :) )
If you're not seeing the same behavior in your test plugin, is it possible that the -properties, -variesOverTime and -frameSetup:... methods are returning different values than in your other plugin?
steve
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden