On May 4, 2015, at 9:16 AM, Lyndon Hill <lyndon@tiliam.com> wrote:
Hi Darrin,
But I believe that many other developers have been successfully using -startTimeForEffect: and -durationForEffect: in the meantime.
That doesn’t work for me: I need to know the start frame number relative to the clip the filter is being applied to. -startTimeForEffect gives the frame number relative to the timeline.
My filter needs to calculate some weighty frame analysis for all frames in the clip. If I know the start and end frames I can re-use analysis that covers frames in that range whenever trim is changed. Without knowing start and end frames my filter will have to recompute everything each time the clip is trimmed. The user experience will be like running in mud.
In that case, please file a bug with a very clear description of what you’re trying to do, what’s missing or working correctly, and what you think it should work like. Looking through the current set of bugs for FxPlug, I see one (which I filed in 2014) about something that appears to be related to this issue. I see no bugs originating between October 2009 (when the linked discussion happened) and October 2010 about it (after I asked the poster to file a bug about it), nor do I find any others searching for just key words like “in point”, “FxTimingAPI” etc. that were filed by 3rd parties about this issue. So if you don’t file them, they won’t get fixed. (I have received some filed recently about changes between 10.1.4 and 10.2, so thanks for those!) Darrin _______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com