site_archiver@lists.apple.com Delivered-To: Pro-apps-dev@lists.apple.com On Nov 3, 2009, at 8:25 AM, Eberhard Ammelt wrote: Darrin -- Darrin Cardani dcardani@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... our fxplug effect produces quite a lot of intermediate data (about 150 kB per minute video) and needs to keep it somewhere between closing and opening of a FCP project. So far it saves this data into a file in the user space and keeps the file name in a custom parameter. Unfortunately, with this approach one gets into trouble, when the user duplicates an effect instance. Then, both instances share the same data file, and it happens that one effect instance falsely loads the data that was created by the other instance. I'm not aware of a way in fxplug to find out if an effect instance was created by duplication. As an alternative, I'm considering to put the whole data into the custom parameter, but I'm concerned about possible side effects when the FCP project file gets very big. However, according to my tests, opening and saving an FCP project with 1 - 10 MB works quite well. Any suggestions regarding the best strategy for handling big custom data? I don't anticipate that causing any problems. There are other developers who store more data than that in their plugins, and which get saved to disk. It's not ideal, but there are some situations where there's no other way, and this is one of them. This email sent to site_archiver@lists.apple.com