Re: FCP6 TemporalImageAPI - returning an image different from main input
Re: FCP6 TemporalImageAPI - returning an image different from main input
- Subject: Re: FCP6 TemporalImageAPI - returning an image different from main input
- From: Micah Sharp <email@hidden>
- Date: Thu, 3 May 2007 08:43:56 -0700
Yeah, that is what I meant. Not during render, but using the
temporal API. Good to know, because that is what we do and it seems
to work well.
Good point on the rowbytes, we'll give that a look.
Thanks,
Micah
On May 2, 2007, at 8:39 PM, Paul Schneider wrote:
If we are getting fields back from the temporal API, but we want
a full interlaced frame, is the following a valid way for us to
re-create the interlaced frame:
1) Get 720x240 field buffer at time n
2) Get 720x240 field buffer at time n + .5
3) Combine the two fields (field order correct of course)
Yes, that should let you reconstitute a full interlaced frame.
No unless you cache the first field result as a full frame
internally as you will be called twice, the second time at frameNum.5
You can use the TemporalAPI to get the "other" field.
If you are working with FxBitmaps, and you are running in FCP, you
might notice that the two fields point to the same memory, and we
have done clever tricks with rowbytes to make it appear that you
are only looking at a single field. You can probably use this
technique to access the full frame more efficiently than using the
temporalAPI and manually combining frames. I wouldn't expect FCP
to change its behavior in this regard anytime soon.
- Paul
On May 2, 2007, at 9:21 PM, Pierre Jasmin wrote:
Micah Sharp wrote:
If we are getting fields back from the temporal API, but we want
a full interlaced frame, is the following a valid way for us to
re-create the interlaced frame:
1) Get 720x240 field buffer at time n
2) Get 720x240 field buffer at time n + .5
3) Combine the two fields (field order correct of course)
No unless you cache the first field result as a full frame
internally as you will be called twice, the second time at frameNum.5
We do need actual fields in our plugin and not something that is
line doubled.
And Paul is right that media does get scaled automatically, which
is nasty, but I thought after much searching I found a way to
turn that off. Yet another manual entry for us I think.
Thanks,
Micah
On May 2, 2007, at 9:57 AM, Paul Schneider wrote:
Right now, FCP's implementation of the temporalAPI will always
give you the native format of the media. In other words, if you
use the temporalAPI on a progressive clip, you'll get a full
frame back, even if you are in an interlaced timeline. This is
arguably confusing, since it's not the same as the input image
that we pass to filters (input images are in the timeline
format, not the media format). I think Paul Miller has a good
point here.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40revisionfx.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40redgiantsoftware.com
This email sent to email@hidden
_______________________________________________
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