site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Hey Bjørn, Best Luck! Helena On Oct 14, 2008, at 2:16 PM, Bjørn Holmgren wrote: _______________________________________________ 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/hju%40apple.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... The way the XML import works 1. it makes the whole project, all offline. 2. it reconnects the files if specified to in the XML import dialog or in the <importoptions>. At reconnect time, the durations would get updated, as long as the reconnect succeeds (which might not happen if there is a problem). But if the reconnect failed, or the XML did anything other than making browser clips, then a bogus duration won't work. For example, a sequence referencing items with bogus durations won't work since it happens in step 1 (before reconnect) and it is unclear how to edit things, or even if the source media is long enough. So, the updating of durations is intentional, but only at that one phase of the XML import, which you can guarantee we do by specifying it in the <importoptions>, but you can't guarantee that it succeeds (I've heard reports of specific servers preventing the reconnect from succeeding, for example). You're going to have to make the call about whether to use that hack or not. 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 hju@apple.com This email sent to site_archiver@lists.apple.com