Hi, (1) Should we ask to the host to create a component that implements the IAVXVisitorManager interface and then use it with a custom IAVXEffectVisitor? Yes, VisitManager is implemented by the host, EffectVisitor by the plug-in. (2) If so, how should I get an instance of the IAVXVisitorManager? Is it through IACFComponentFactory::CreateComponent? In

Hi, An effect context is uniquely created for effect instances between the BeginEffect and EndEffect method calls. You can use this and the effect user data to effectively differentiate between effect instances in the live application. One thing to keep in mind is that the effect context is frequently recreated by the host according to various UX actions

Hi Vlad, Yes, this issue can be seen with Media Composer. The problem is specific to plug-ins that support the IAVXTimeNeighborhood effect. It looks like the Neat plug-in should be able to work without supporting this interface, though using this interface is likely improving render performance. Also, the other conditions that are needed to get the

Hi, Can you please take a look a the AVX2Cirque Sample effect in the SDK and simlarly register the Fade parameter with the same ID. Hope that helps. Thanks, Tim.

Hi Mike, The first two args should not be NULL (i.e. attribute ID and Value). This method should be called multiple times through a the standard setup and use of the plug-in for rendering or moving through the timeline, with various attributes. In the AVX2 samples you will find this method invariably implemented to return an error code to indicate the

Hi Michael, There are a couple of possibilities: a) Use the effect AVXATTR_Effect_ExcludedSignature attribute to flag that the rendered result is uncacheable, until the plug-in is "ready" i.e. return ACF_OK in GetEffectAttribute. Once ready, the effect responds to excludedsignature attribute queries with anything other than ACF_OK. b) Setup

The invalidation of the cache is partially based on the registered parameter set state. So for example, a parameter that reflects the state of the proxy data where the parameter assumes a new value when the cache needs invalidation will result in a render call being made on the plug-in. Perhaps this strategy would work to solve the issue.

Hi Bill, Looks like you're building a 32-bit version of the plug-ins. Please select the x64 version of the compiler target. Also if you're on a recent version of MC (e.g. > v8) please use VS2012, and you'll have to go through the update process with the VS projects. thx Tim.

Thanks for clarifying that. In an interlaced project, during the render request made on the plug-in the image that is passed to the plug-in corresponds to one field and the plug-in is asked to render one field at a time. The field information is available from the AVX Image structure as well. And if the plug-in requires any info about the project dimensions

Hi, Thanks for your interest in MC. I understand that using the IAVXEffectContext interface the developer is getting an image dimension of half frame height in an interlaced project. If that is the case, can you please specify which interface method is being used to get the dimension, is it "GetProjectHeight" or "GetFrameHeight"