[LV2] LV2 event ports running out of space

Jeremy Salwen jeremysalwen at gmail.com
Thu Aug 30 15:07:19 PDT 2012

Thinking about it more, it seems to be something that needs an extension.
A plugin should be able to stop processing partway through a chunk and say
"Hey, I ran out of space for events, here's how many frames I finished".
Ideally it would just be the return value of the *run* function (think of
an fwrite like interface), but obviously we can't make an incompatible
change like that.  Probably just a tagged port like the way latency
reporting works.  It can be an optional feature, and if a host doesn't
support it, it just loses events, but it still works.  What do you think?


On Sun, Aug 26, 2012 at 7:02 PM, Jeremy Salwen <jeremysalwen at gmail.com>wrote:

> I can find in the documentation that atom output ports are supposed to be
> connected to an atom:Chunk, so the plugin knows how much space it has to
> write output events.  However, I can't find anything about how the host or
> plugin should behave if the space given is not enough to write all the
> events.  How can the host tell if the plugin should have a bigger buffer
> size?
> Also, where does the plugin write the atom:Sequence?  directly over the
> atom:chunk or after the atom:chunk header?
> Jeremy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lv2plug.in/pipermail/devel-lv2plug.in/attachments/20120830/060b7846/attachment-0001.htm>

More information about the Devel mailing list