[Devel] Requiring hosts to pre-initialize outputs, and plugins to always write

David Robillard d at drobilla.net
Sun Feb 12 10:23:37 PST 2012

On Sat, 2012-02-11 at 22:52 -0500, David Robillard wrote:
> 1) All variable-sized atom types (like LV2_Atom_Sequence) must have a
> separate 'capacity' field to handle cases like this where they are used
> as outputs.  Pros: like the current code for event ports, no
> initialization required, plugins can not write anything and data is
> valid.  Cons: The actual data type has been bloated with a field that
> only makes sense when that type is used for writing.

Consequence of this I hadn't thought of: it means in-place processing
for such ports is impossible, so, because of our hard definition, any
plugin with (variable-sized) atom ports is lv2:inPlaceBroken.


More information about the Devel mailing list