site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Hi all, Does anybody have thoughts about this? Helena?:) Thanks and kind regards Andreas _______________________________________________ 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 used the Apple generator example to create text tracks for quite a long time. This way you create one "master" generator with an "effect id = 'xxx'" and only write the changes into the XML for the "childs". This works fine and has the advantage that you can change "master" settings in a second, which will be applied to all following generators. I and my customers (which I had been in contact with) in the last time only worked on smaller (amount of title) projects, but now some bigger came up with 1000 titles and way more. And here we got an issue: the XML import takes a real (I mean real) long time. That wasn't the case with elder versions of FCP, though I can't proof when this started. Using the "non optimized way" which means writing the full generator each time reduces the import time by factor 10, 20 or more. The disadvantage is that you can't do global changes any more in that kind of speed as with the "optimized way", means that you cannot - even as an "know nothing about XML user" - open the XML in TextEditor and change one entry in the "master" and all children will follow. Same as with an app that would do it for you. creating the XML and file size isn't an issue though. This email sent to site_archiver@lists.apple.com