On Mon, 2012-05-28 at 18:41 +0300, Stefano D'Angelo wrote:
The spec explicitly states: "the plugin instance MUST reset all state
information dependent on the history of the plugin instance except for
any data locations provided by connect_port()"
This text does date from a time when that was the only way to actually
get any data in/out of a plugin, so it might need clarification now with
For live plugins if you're going to stop continually running the plugin,
you must deactivate it, so I can see how a complete and total state
reset here might be undesirable. I'm not sure. A complete
cleanup/re-initialization is always an option for a total reset, though
of course not real-time whatsoever.
> Concrete use case would help.
Linux-audio-dev mailing list