On Fri, 2012-06-01 at 22:56 +0000, Fons Adriaensen wrote:
> Isn't the LV2 way to do this via features (i.e. the plugin
Yes, this callback is in a feature struct. Essentially "feature" just
means "thing provided by the host".
Restrictions would also be features, but nevermind that. Regardless of
restrictions, plugins need to know the actual situation (for example,
right now I need to know max, and have no restrictions). It decomposes
Not mentioning any of that was no mistake; I am attempting to farm
precisely one piece of information: whether or not the above callback
can adequately express any reasonable block length situation; i.e.
whether or not any plugin could know "yes, I can run" or "no, my
requirements to run are not met".
There is no point confusing the thread with restrictions since that part
follows directly from the above.
Also, I said something stupid about constant size earlier. Of course,
constant can be expressed with min == max.
 Poor choice in terminology here, it turns out
 I know this stupid list and how to extract useful information from
it and ignore the rest ;)
Linux-audio-dev mailing list