Re: Understanding FCP and NTSC - add on
Re: Understanding FCP and NTSC - add on
- Subject: Re: Understanding FCP and NTSC - add on
- From: Eryk Vershen <email@hidden>
- Date: Thu, 10 Jul 2008 11:53:53 -0700
Andreas,
I took at look at this.
Here's the problem. When you alter the editing timebase (away from
NTSC) in FCP, the timecode in the UI is updated, but something
internally is not set correctly. When you export that sequence the old
timecode (i.e. drop-frame) is exported in the XML. When FCP reimports
that XML it changes the timecode to NDF and uses the frame number to
make new timecode values.
If you create a sequence at 60 (using a preset) the problem never occurs
If you change the timecode to NDF before altering the editing timebase
the problem does not occur.
The problem only occurs when you are using DF timecode and you switch
the editing timebase from 29.97 to 30 or from 59.94 to 60
I've put a bug in about this.
-eryk
On Jul 10, 2008, at 10:24 AM, Andreas Kiel wrote:
Forgot this
the proect that you sent does indeed contain a sequence that
behaves the way you describe: You can't change it from dropframe to
DF in the sequence settings, but the exported XML has is be
dropframe anyways, and incorrectly so.
Maybe I misunderstood your comment, but if I create a project which
is not NTSC then there can't be a DF timecode. In so far the FCP
behaviour is totally correct!
The weird thing is that the original exported FCP XMLs say it's not
NTSC but DF timecode, which is not possible at all. Re-importing
this virgin FCP XML does make a NTSC DF sequence out of it.
Regards
Andreas
_______________________________________________
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
_______________________________________________
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