Standard version: 1.4
Gary at Genarts is looking for host that wants to implement to write example/better doc.
Note (by Pierre Jasmin): Gary from Genarts was saying this need to be changed. Not the proper way to do this.
Gary (2015-04-30): Consulting with the team here, I now think the API functions are OK, but need better documentation of what's supposed to be passed where and when. I'll work on an update. Need an interested host partner to implement. (Assimilate has a version but we've identified some issues that could use work.)
Some plug-ins perform heavy processing in response to UI interaction. This is typically some sort of analysis of images to shove into parameters to be used in a later render call. For example, a stabilisation plug-in might analyse all frames of an input clip for motion and write parameter keyframes representing that motion. During render, those values are fetched and used to stabilise the image.
This heavy weight processing can lock up the UI thread on many hosts, and can be distinctly user hostile. A way around this is needed, so that the plug-in can report to the host it is going to lock up processing, or even some way of batching that to a background thread.
This is a suite - Suite don't have the same insertion cycles as the rest.
This suite can be supported by any host that support 1.4 - There is a volunteer (Gary at Genarts) to support that. There has been a variation of this implemented by Assimilate and Genarts but it is an _EXT right now (not in shipping version).