site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Hi list, Greg. _______________________________________________ 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've found a problem using NSXMLDocumentTidyXML to clean up XML for FCP. My altered sequence XML ends up being a bit messy, so I've passed it through NSXMLDocumentTidyXML and then NSXMLNodePrettyPrint to give me good looking easily foldable XML code. This has never been a problem with my PAL DV footage, which has a <codecname>Apple DV - PAL</ codecname> codec with code <codectypecode>dvcp</codectypecode>. However my first try with NTSC footage caused FCP to warn that there is a codec missing and the sequence refused to open. This is followed by an "out of memory" error message. The codec was <codecname>Apple DV - NTSC</codecname> with code <codectypecode>dvc </codectypecode>. Note the space in the codectype. After NSXMLDocumentTidyXML the trailing space had been stripped from the 4 letter codectypecode, so FCP would no longer recognize the sequence's codec. If I just give FCP my un-tidied XML it's happy. I don't think this is a bug with NSXMLDocumentTidyXML since it's no doubt meant to tidy that extra space. Since I've already got a work- around, this is more of a heads-up for other XML users on the list. This email sent to site_archiver@lists.apple.com