Re: More questions: resolution and time with Motion templates in FCP
Re: More questions: resolution and time with Motion templates in FCP
- Subject: Re: More questions: resolution and time with Motion templates in FCP
- From: Darrin Cardani <email@hidden>
- Date: Wed, 27 Jul 2011 09:58:26 -0700
On Jul 26, 2011, at 12:52 PM, Peter Litwinowicz wrote: I said: Note, we are considering changing this and giving you FCPX times in the future. We're trying to work out how difficult it will be to do that (more difficult than you'd think), and how badly that will mess up currently shipping plug-ins.
What would be helpful if you can't give us FCPX times, is to give us an FCP X time-step (like in AE) of the amount of time to the next time to render, adjusted of course for the duration differences. Then when I need frame N of the input, I can simply multiply by this time-step before I request an input frame.
Of course the time-step value to the next time to render doesn't allow for the accounting of differing frame rates. So a bit more thought would be needed for this solution.
I'm trying to reconcile what you're asking for vs. what we were giving you in Motion 4/FCP 7. Rather than add new API at this point, I'd like to make things work in such a way that you can simply recompile your old code and just have it work. How were you figuring out the time-step value previously?
Darrin
|
_______________________________________________
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