Re: Invalidating custom data based on clip
Re: Invalidating custom data based on clip
- Subject: Re: Invalidating custom data based on clip
- From: Ben Syverson <email@hidden>
- Date: Mon, 28 Nov 2011 13:22:30 -0600
Darrin,
If the dragging bug could be fixed, then finishInitialSetup seems like it could work. But after filing that enhancement request, it seems the larger issue is that an FxPlug has no way to know that its input has changed since the last time it was run.
My request asks for an "inputUUID" in FxRenderInfo. The UUID would stay the same across invocations and hosts, as long as the input remained identical. That way you could cache data for that particular input. But as soon as *anything* about the underlying clip is changed (for example, an earlier effect is tweaked), it would generate a new UUID to alert our FxPlug about a change in the input.
That makes it pretty flexible, agnostic to the type of information the FxPlug is caching, and hopefully simple to implement!
In the meantime, a combination of finishInitialSetup and Pete's hacky checkbox idea (thanks Pete!) should be enough.
Thanks!
Ben
On Nov 28, 2011, at 13:11, Darrin Cardani wrote:
> Ben,
> Some here suggested that maybe using -finishInitialSetup could work. It's called once when a plug-in is added, but not after deserialization. It's called when a plug-in is copy/pasted elsewhere. It looks like it's not currently called when a plug-in is dragged from one piece of footage to another, but that's probably a bug. Let me know if it that might be workable.
>
> Darrin
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden