This is how I declared my parameter: gParamHost->paramDefine(paramSet, kOfxParamTypeDouble2D, param, &propSet); gPropHost->propSetString(propSet, kOfxParamPropScriptName, 0, param); gPropHost->propSetString(propSet, kOfxParamPropHint, 0, name); gPropHost->propSetString(propSet, kOfxPropLabel, 0, name); gPropHost->propSetString(propSet, kOfxParamPropDoubleType, 0, kOfxParamDoubleTypeNormalisedXYAbsolute); gPropHost->propSetDouble(propSet, kOfxParamPropDefault, 0, 0.08 * id); gPropHost->propSetDouble(propSet, kOfxParamPropDefault, 1, 0.5); gPropHost->propSetString(propSet, kOfxParamPropCacheInvalidation, 0, kOfxParamInvalidateAll); gPropHost->propSetInt(propSet, kOfxParamPropEvaluateOnChange, 0, 0); gPropHost->propSetInt(propSet, kOfxParamPropSecret, 0, 0);
I am wondering if the "kOfxParamPropEvaluateOnChange" set as 0 is preventing the cache invalidation from happening? ----- Original Message ----- From: Mike Wong <smm...@cityu.edu.hk> Date: Wednesday, March 30, 2011 11:04 pm Subject: Re: [Nuke-dev] Cache invalidation from OFX To: Nuke plug-in development discussion <nuke-dev@support.thefoundry.co.uk> > Hello, > > thanks for the response. > > > > I am working on an OFX plug-in on Nuke which requires sequential > > > rendering and I would like to find a way such that the plug-in may > > > > invalidate the cache to maintain continuity or re-render if > > necessary > > > (e.g. the user drags the timemark in Nuke). > > > > > Have you declared the plugin property > > kOfxImageEffectInstancePropSequentialRender? > > Yes, I declared it but I guess nuke doesn't support it yet ? I made a > query via the OFX API about > kOfxImageEffectInstancePropSequentialRender, the result is 0. > > > If you modify the time position of a parameter key and your > parameter > > is > > declared with kOfxParamPropCacheInvalidation=kOfxParamInvalidateAll, > > > your cache will be invalidated. > > Yes, I declared this property for the parameter the same way and when > I try to add/remove/modify value and/or time of a keyframe of the > parameter, no single bit of cache in Nuke is invalidated ..... > > Mike > _______________________________________________ > Nuke-dev mailing list > Nuke-dev@support.thefoundry.co.uk > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev _______________________________________________ Nuke-dev mailing list Nuke-dev@support.thefoundry.co.uk http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
