On Sun, Jun 13, 2010 at 09:11:24AM -0400, Paul Davis wrote:
> its difficult to see why you wouldn't simply define your own plugin
True. This *will* a separate API, and using it directly will
by far the easiest way, but
1. Given that basic LV2 is almost nothing, *any* extension
more or less corresponds to a complete redeifinition (with
only the run() call being standard). So it's not really
2. 'Embedding' it in LV2 may placate some people, and
save me some flames.
> supporting touch specifically requires 2 things:
(b) is not provided by a basic get/set control port value
interface. How does the LV2 'external GUI' handle this ?
More generally, I don't think you can do automation right
by just monitoring/injecting control port values. Except
maybe when the automation data has a constant rate, e.g.
1/16 FS. In all other cases, it's only the plugin that can
decide in any intelligent way on control points, their
frequency and/or step size, etc. and it's only the plugin
that can interpolate such data in the correct way.
> > I tried to see if/how this works today using Ardour 2.8.9
At least the compressor has other issues as well (didn't test the
O tu, che porte, correndo si ?
E guerra e morte !
Linux-audio-dev mailing list