[LV2] plugin bypass

[Fons Adriaensen]

On Tue, May 06, 2014 at 09:50:07PM +0200, Robin Gareus wrote:
 
> A host supporting 'bypassFeature' must always add any plugin which does
> have a port tagged 'bypass' in bypassed mode and un-bypass it after the
> first process callback. That will allow for clickless insertion of the
> plugin. (same for removal, first bypass, then remove.)

This could be problematic as the first process callback could be
too short to allow the plugin to do a clean transition, defeating
the original purpose.

Ideally the plugin should indicate to the host if it is in bypass
mode or not. So when a plugin is to be removed, the host puts in
bypass, waits until the plugin confirms this, and then removes it.

Ciao,

-- 
FA

A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)