On Mon, Mar 25, 2002 at 02:09:20 +0100, Stefan Kost wrote: > Additionally it introduces processing overhead, as parameters usually don't change >that much.
Agreed, there are definatly some parameters that can't/shouldn't be interpolated. > Ideas : > 1.) What about if the host takes care about avoiding cracks due to parameter >changes. Right after a parameter change, > it could call the plugin twice and then x-fade the outputs. Not all plugins can be xfaded to produce meaningful results, not to mention it doubles the cpu use, and you need two instances of the plugin, with the same state. The host can't reasonably do the parameter edge filtering, as it doesn't know what the appropriate scheme is. Sure, you could code up all the common schemes (and thier parameters) and express them as port metadata, but that seems uneccesarily complicated. - Steve
