site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com -Rolf Hi Rolf Regards Andreas On 05.02.2006, at 11:45, Rolf Howarth wrote: Ok, here's another question then. -Rolf -- Rolf Howarth Square Box Systems Ltd Stratford-upon-Avon UK. http://www.squarebox.co.uk _______________________________________________ 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/kiel%40spherico.com -- Rolf Howarth Square Box Systems Ltd Stratford-upon-Avon UK. http://www.squarebox.co.uk _______________________________________________ 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... Thanks for confirming that. Yes, we already insert a comment in the XML file that we export, but that doesn't help us much as we're unlikely to be re-loading these files into our app. Currently we artificially extend the duration of exported clips so they have the expected duration when imported into Final Cut Pro, but I don't know if that's a sensible strategy or not. We don't do any correction on import. That means if we import a Final Cut XML file we display it the same way as it was when it was exported, but not the same way as it would be if you import it into Final Cut Pro. At 1:11 pm +0100 6/2/06, Kiel wrote: I saw that error as well. For own usage I fix that internally and do insert a comment at the beginning of the XML, which tells me who did create it - my app (or Automatic Duck, as Wes includes a comment as well) or another one - in case there is no comment. I think it's a good idea for any developer to insert a comment at the root level of the XML. With the next releases of some of my apps I also will put an extra XML into the comment, which will allow others to parse version changes and handling of some nodes. This doesn't help really much in case Apple or other other companies you don't know about will fix or create bugs, but at least it keeps people who read your comments informed about what you are doing. To make it even more complicated be aware there are 3 versions of XML V1 out which are not really compatible "up-down" with the versions of FCP 4.1 thru 5.x When FCP imports an XML file describing subclips, it ignores the clip's stated duration but calculates it based on the file's duration and startoffset and endoffset. However, there seems to be a bug in FCP 5.0.4 and the processing of endoffset is out by one, so the subclip's duration (and Media End) is one frame too short after it's imported. You can see this by importing a subclip, exporting it and importing it again. Each time it gets shorter by one frame, which I take it to mean it's unequivocally a bug in Final Cut Pro, and not my understanding of the XML format :-) Has anyone else seen this? If so, how do you handle it? Do you process subclips the same (broken) way as Final Cut, to try to be compatible, or do it correctly and put up with durations being out by one frame compared to FCP? Obviously the danger with trying to correct for FCP's behaviour is that Apple might fix it in a future update. This email sent to kiel@spherico.com This email sent to site_archiver@lists.apple.com