Content-Type: text/plain; charset="UTF-8"
On Sat, 2012-10-20 at 11:44 +0000, Fons Adriaensen wrote:
By "zero latency" here I mean zero latency, synchronous, and strictly
hard real-time safe, i.e. no buffering and no threads whatsoever.
Also note I did not say fixed. This plugin requires a power of 2 buffer
size, not a fixed one. That is a separate feature (which also exists in
LV2 1.2.0 but there is no corresponding test plugin yet).
What I really meant was: it inherently requires restrictions, period
(perhaps not those exact ones). This is a new feature.
> Thirdly, for the use case of reverbs, the whole latency issue is
The whole point of this plugin is to expose convolution at a low level
in a simple well-behaved plugin with no threads. This is obviously
desirable in some cases. It is more about being synchronous than
anything about time.
If that is not what you want, either do all the funny business at a
level above the plugin, or use a different plugin. We are not claiming
this plugin in its current form is the best way to do convolution in a
plugin in all cases.
Of course, as mentioned, the real point here is to announce a test
plugin for block length restrictions, so host authors can work on it.
Perhaps we will come to the conclusion that slightly different ones are
best in this case (e.g. any multiple of the minimum which happens to be
a power of 2), but any plugin that operates in this way will definitely
require some kind of restriction(s). Currently we have fixed, bounded,
and power of 2 (and any combination thereof), which is good enough until
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----