Re: Wrapping FxPlugs in .moef
Re: Wrapping FxPlugs in .moef
- Subject: Re: Wrapping FxPlugs in .moef
- From: Nathan Weston <email@hidden>
- Date: Tue, 19 Jul 2011 09:29:08 -0400
On 7/18/2011 1:37 PM, Darrin Cardani wrote:
And we can't get the duration appropriately?
You currently get the duration of the effect source (the drop zone the
effect is applied to in most cases). Since the frame timings you get are
relative to that duration, you can calculate some things like the
percentage through the clip. (Though apparently, there is some round-off
error that we need to address.) I don't know if this will work for your
plug-ins or not, as I don't know how you're using and calculating those
sorts of things. I urge you to try out how it works and let us know if
there's a more effective way we could be doing things. And again, the
quicker you tell us, the better.
Any way to get the frame rate of the underlying footage? And Duration?
Not currently. I believe that has always been the case, though, hasn't it?
Is there any way to get accurate clock time from all of this? Normally
you can divide frames by FPS to get a time in seconds. But suppose I
have a moef that's 10 seconds long and I apply it on a 1-second clip.
Motion will fudge all the timing numbers so keyframes and relative
position in the clip basically work out right, but if I try to calculate
absolute times, it will appear to my effect as though 10 seconds have
elapsed, instead of 1.
If the effect relies on clock time, everything is going to move 10x
faster than it should. There are lots of effects that work this way --
flicker, camera shake, simulated clouds, etc. This could be a
show-stopper problem for a lot of people.
- Nathan
_______________________________________________
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