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 Miller <email@hidden>
- Date: Wed, 02 May 2007 17:40:37 -0500
Peter Litwinowicz wrote:
Earlier I said;
Well, there you are. It does start breaking down. Which is why AE always
provides full frames, just time-sampled at the frame rate of fields, when
appropriate. AE converts EVERYTHING to frames and works from there, and then
60i footage gets processed as 60p... Then these issues go away (with the
problem that it is sometimes almost impossible to identify what was original
interlaed material). Inefficient for a realtime editing app, of course.
Note the Premiere Pro actually hands us full-res frames always. And it is
an editing app... So it *can* be done in an editing app.
Full-size frames are nice.
I must admit I've been very spoiled by the way AE/Premiere does it.
--
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