Re: Invalidating render files in FCP
Re: Invalidating render files in FCP
- Subject: Re: Invalidating render files in FCP
- From: Paul Schneider <email@hidden>
- Date: Tue, 12 May 2009 13:42:08 -0500
Hi Eberhard,
In general, FCP will not respond to parameter changes if the parameter
isn't visible in the effect viewer. This makes it difficult to
invalidate one plugin instance from the controls of another, which
sounds like what you're trying to do.
It would be better if we listened to parameter changes from all extant
plugin instances. But I'm not sure if that would completely solve your
problem. If the user has just opened a big project, and there are
instances of your plugin applied to segments that haven't been viewed
or rendered since the project was opened (but were rendered
previously), then we might not have instantiated your FxPlug instance
for those segments.
I can't think of a way around this issue. Please file a bug at bugreport.apple.com
requesting a way to achieve what you want.
Thanks,
- Paul
On May 12, 2009, at 12:51 PM, Eberhard Ammelt wrote:
Hello,
we use global settings for our FxPlug effects and need to invalidate
the affected render files in FCP when changing global settings.
To get this working, I change certain custom/standard parameter
values for all effects. This works for an effect if its parameter
panel is visible, but it doesn't work if the effect's parameters are
hidden.
Is there another way to invalidate the render cache for an effect?
Thanks,
Eberhard Ammelt - Pixlock
_______________________________________________
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
_______________________________________________
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