| Pete,
That’s interesting. I’ll take a look at your project when I get it. (I’m still catching up from being out the past 2 days. Sorry for any delay.)
Does the problem only happen in FCP, or does it also happen in Motion?
Darrin
On Oct 21, 2015, at 9:45 AM, Peter Litwinowicz < email@hidden> wrote:
Darrin,
Thanks for getting back to me.
I believe it IS size related. For the plug-in in question, we write data for the plugin…, creating a NSMutableArray of NSDIctionary items. One dictionary for each frame. 8 items in each dictionary. I can write about 18k frames (it varies) before FCP fails to restore the custom data upon reload (upon reload, my NSCoding of the array of dictionary items has 0 items returned to me).
If I create a dictionary for each frame of 16 items, I can write roughly 1/2 as many frames of data.
And the person who had the problem before wrote to me and said they had problems with 5 or 10 mb, not 50. And they said they worked around the problem by cutting up their data into chunks (probably, like us, they had a customer who couldn't wait for a fix), which is also how I solved the problem yesterday. Big pain. But the fact that I could get it to work by cutting down the data size tells me there is an FCP bug somewhere.
Also why do you put a smiley face next to 50Mb? That's not really unreasonable amount for a big stash of analysis for a sequence.
I will send you a project, footage and details for how to reproduce. Now you have two companies reporting this! Pete
No, there shouldn’t be any sort of limit. (I have a vague recollection of at least one vendor storing something like 50MB in their custom data.) If you want to send me a simple test app, I can look into what’s happening on our end.
Darrin On Oct 19, 2015, at 8:52 PM, Peter Litwinowicz < email@hidden> wrote:
Hey all, but particularly Darrin ;-),
We are having a problem with one of our plugins that reads/writes custom data. We have an NSMutableArray wrapped so that it is properly read/written with NSCoding.
When the number of elements gets above a certain amount (about 20k elements, of NSDictionary items that have about 8 double floats… not the most efficient way of doing it, but we are following the SimplePaint example in the SDK., more or less).
Once the number of elements in the array gets above a certain amount, it seems that upon re-read of the project that the array read back has zero elements.
Does this ring a bell with anyone? Is there a data size limit for custom data?
Pete
|