site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Good point on the rowbytes, we'll give that a look. Thanks, Micah On May 2, 2007, at 8:39 PM, Paul Schneider wrote: 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. You can use the TemporalAPI to get the "other" field. - Paul On May 2, 2007, at 9:21 PM, Pierre Jasmin wrote: 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) Thanks, Micah On May 2, 2007, at 9:57 AM, Paul Schneider wrote: This email sent to jasmin@revisionfx.com _______________________________________________ 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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... 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. 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: 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 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. 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: 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. 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 (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/jasmin% 40revisionfx.com _______________________________________________ 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: http://lists.apple.com/mailman/options/pro-apps-dev/pschneider% 40apple.com This email sent to pschneider@apple.com _______________________________________________ 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: http://lists.apple.com/mailman/options/pro-apps-dev/micah% 40redgiantsoftware.com This email sent to micah@redgiantsoftware.com This email sent to site_archiver@lists.apple.com