site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com _______________________________________________ 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 am developing an application that searches through a folder on the network containing many thousands of clips, and generates a FCP XML with the search results. The problem is that I have no easy and fast way of determining the duration of the found clips (mdls does not work; no spotlight index). The manual for the XML interchange format indicates that duration is mandatory in the XML, and testing confirms that it is. The good news is that FCP seems to ignore the duration encoded in the XML, so I can write an arbitrary value on all clips, and FCP get the real duration from the source files. My question is: Is this behaviour intentional, or can I expect it to change at any time, thereby breaking my app? This is how I encode the clips: <clip id="asdf"> <name>asdf</name> <duration>25</duration> <rate> <ntsc>FALSE</ntsc> <timebase>25</timebase> </rate> <file id="asdf 2"> <name>asdf</name> <pathurl>file://localhost/Volumes/disk/dir/asdf</pathurl> </file> </clip> This email sent to site_archiver@lists.apple.com