site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Hi Rainer, Good luck and see you hopefully next month. Andreas On 13.01.2008, at 07:39, Rainer Standke wrote: Hello all, Could anyone shed some light on this, please? Thanks, Andreas Kiel Spherico Nelkenstr. 25 D-76135 Karlsruhe Tel.: +49 (0)721 183 9753 eFax: +1 650 897 8094 eMail: kiel@spherico.com http://spherico.com/filmtools -- workflow tools for FCP P Please don't print this e-mail unless you really need to. _______________________________________________ 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... I think you should not worry about this. It's sometimes difficult to understand why and I don't have an explanation for these thing- but maybe some thoughts. So finally it depends on whether you want to read or write XMLs. There are a lot of ways you can write informations an XML which are not necessarily needed as they will be either inherited from the parent or replaced(ignored) during import. If you read XMLs you can use this "redundant" stuff to verify or just ignore - it depends on your app. I haven't made too many thoughts about "clip" and "clipitem" but "clip" behaves as same as "sequence" (this came up earlier here on the list). Even if it looks a bit strange you can merge "clip/sequence" reading into one handler in your code - this can save a lot of code and time. Here an issue when this may look different: "Live Type". "Live Type" clips are always NTSC 30 wherever you use them. This is odd - I think - but it may explain why this stuff is necessary. Also for future expansion it might be interesting to keep these things divided while keeping the XML structure the same. You may search the FCP XML PDF for the "how and why" inherit things and just do some "trial and error" about what is really needed. P.S. & O.T. Still got no idea why all node names in a FCP XML are "lower letters" except "mediaSource" which is mixed - not a problem but interesting. looking at FCP XMLs, there is a rate (as in: frame rate) given for the 'parent item' (either a clip or a sequence), and then there is a rate for each clipitem (as in: parent item/media/video/track/ clipitem). I can see how it is a good thing that one can mix clipitems with different rates, but I am wondering about the redundant(?) parent item's rate. In clips, isn't the clip's rate *always* the same as the video track's rate? And in sequences, isn't the sequence's rate *always* the same as the video track's? Rainer _______________________________________________ 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/andreas.kiel% 40spherico.com This email sent to andreas.kiel@spherico.com This email sent to site_archiver@lists.apple.com