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: Paul Schneider <email@hidden>
- Date: Wed, 2 May 2007 13:37:47 -0400
What is confusing is if I am working in a sequence that is 720x480
DV (interlaced), and my track has a 720x540 PROGRESSIVE movie clip
on it (which FCP happily SCALES to fit the 720x480 sequence size),
my plugin gets as INPUT a 720x240 FIELD.
Unfortunately, I think it's more confusing than that. We do scale
all inputs to the sequence size during RT preview. But, you will get
a full-size input when you hit Cmd-R to render.
The idea here is that you get speed during preview and quality during
render. It's easier to justify if your still image is 2K than if
it's just a few pixels bigger than the sequence. But it does
complicate things more for developers.
On May 2, 2007, at 1:31 PM, Paul Miller wrote:
Peter Litwinowicz 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.
Not confusing at all. If the source is progressive, you get
progressive frames. If the source is interlaced you get fields.
What’s confusing about that? What’s more confusing to me is that
the input is somehow tied to the output settings. I find it more
confusing that I have to worry to use my output settings to
somehow retrieve my input. And I worry also that when you tie
input to output settings then you also get into the problems that
FCP and Motion has that you can’t retrieve all 120 frames of a
120fps sequence when you are sitting within a 30p or 60 sequence.
Of course, let’s address one issue at a time.
What is confusing is if I am working in a sequence that is 720x480
DV (interlaced), and my track has a 720x540 PROGRESSIVE movie clip
on it (which FCP happily SCALES to fit the 720x480 sequence size),
my plugin gets as INPUT a 720x240 FIELD.
But if I request a frame via the temporal API (using the RenderInfo
that was passed in to me - you know, the one that tells me what
field I am on and such), I get back a 720x540 FRAME.
This might make sense to you, but it looks like a bug to me.
--
Paul Miller | email@hidden | www.fxtech.com | Got Tivo?
_______________________________________________
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