Re: Understanding FCP and NTSC - add on
Re: Understanding FCP and NTSC - add on
- Subject: Re: Understanding FCP and NTSC - add on
- From: Andreas Kiel <email@hidden>
- Date: Thu, 10 Jul 2008 19:04:38 +0200
Thanks again Rainer for diving into that.
I think I got it a bit more circled.
After again trashing the prefs on both of my machines and NOT opening
all the test files and projects the behaviour came back to normal,
after some time when again adding many projects and sequences ("fresh
from the given setup") the "odd" behaviour did return.
So it seems it has to do with the amount of open project files and
sequences and the kind of them. Maybe it's worth a note that none of
the sequences did refer to any actual file.
It seems that there is a bug somewhere with that in FCP which is hard
to reproduce if you are "not in this state", but if, it will happen -
still don't know how to get into this state. The good thing is that
this is likewise very seldom happening as normal people would not run
FCP with this this crazy mixture of projects and the amount of. And I
learned how to create a workaround if it happens. So for my part it's
solved, but what remains is this feeling in the stomach.
Maybe it's related to a bug I filed that when you open a big amount
of projects and a real big amount of sequences and close all projects
all the sequences stay open.
Thanks again
Andreas
On 10.07.2008, at 15:05, Rainer Standke wrote:
Hi Andreas,
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.
I then created a new sequence with the same parameters as yours,
and that can be set to have NDF or DF timecode, and it seems to
export correctly. This leads me to believe that your sequence may
be corrupt or something like that. You might want to try creating
your sequence from scratch again.
FYI, I am on 10.5.3, Intel, FCP 6.03 and QuickTime 7.4.5.
Rainer
On Jul 10, 2008, at 5:36 , Andreas Kiel wrote:
Just to proof me a fool.
I spent some more time on these (in my opinion) odd things about
FCP's NTSC and timecode handling.
So I was wrong with the 60 NDF non NTSC - it's not always DF, I've
to do some more tests to figure out when and why.
To make me look not too bad.
Here something somebody may check and possibly will give some
feedback.
I attached a real simple FCP project which is non NTSC, 30 FPS and
therefore timecode should be NDF.
It includes a sequence containing a slug and some markers.
If I export as XML and then re-import all timing is screwed up.
The earlier stuff I did was for creating empty sequences so I
"only looked in theory" for this NTSC/NDF oddities without any
actual footage.
So the way I described in the earlier post is not really correct,
as it seems that at least for a round trip of an XML some stuff
has to be exchanged in the original XML.
I really would appreciate if somebody could do the same test and
let me know about the result.
Maybe it's my setup - hmh
Thanks Andreas
<30p project.zip>
_______________________________________________
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