event
type: Project
license: isc
name: LV2 Event
shortdesc: A port-based real-time generic event interface.
created: 2008-00-00
developer: me
developer: larsl
release:
  revision: 1.12
  created: 2014-08-08
  file-release: lv2-1.10.0.tar.bz2
  blame: me
  changeset:
    item: Minor documentation improvements.
release:
  revision: 1.10
  created: 2013-01-13
  file-release: lv2-1.4.0.tar.bz2
  blame: me
  changeset:
    item: Fix incorrect return type in lv2_event_get().
release:
  revision: 1.8
  created: 2012-10-14
  file-release: lv2-1.2.0.tar.bz2
  blame: me
  changeset:
    item: Make event iterator gracefully handle optional ports.
    item: Remove asserts from event-helper.h.
    item: Use more precise domain and range for EventPort properties.
    item: Use consistent label style.
release:
  revision: 1.6
  created: 2012-04-17
  file-release: lv2-1.0.0.tar.bz2
  blame: me
  changeset:
    item: Fix bug in lv2_event_reserve().
    item: Fix incorrect ranges of some properties.
    item: Merge with unified LV2 package.
release:
  revision: 1.4
  created: 2011-11-21
  file-release: lv2-event-1.4.tar.bz2
  blame: me
  changeset:
    item: Update packaging.
release:
  revision: 1.2
  created: 2011-05-26
  file-release: lv2-event-1.2.tar.bz2
  blame: me
  changeset:
    item: Add build system (for installation).
    item: Convert documentation to HTML and use lv2:documentation.
    item: Use lv2:Specification to be discovered as an extension.
release:
  revision: 1.0
  created: 2010-11-24
  file-release: lv2-event-1.0.tar.gz
  blame: me
  changeset:
    item: Initial release.
documentation: This extension is deprecated. New implementations should use LV2 Atom instead. This extension defines a generic time-stamped event port type, which can be used to create plugins that read and write real-time events, such as MIDI, OSC, or any other type of event payload. The type(s) of event supported by a port is defined in the data file for a plugin, for example: :::turtle <http://example.org/some-plugin> lv2:port [ a ev:EventPort, lv2:InputPort ; lv2:index 0 ; ev:supportsEvent <http://lv2plug.in/ns/ext/midi#MidiEvent> ; lv2:symbol "midi_input" ; lv2:name "MIDI input" ; ] .

EventPort
documentation: Ports of this type will be connected to a struct of type LV2_Event_Buffer, defined in event.h. These ports contain a sequence of generic events (possibly several types mixed in a single stream), the specific types of which are defined by some URI in another LV2 extension.

Event
type: Class
documentation: An ev:EventPort contains an LV2_Event_Buffer which contains a sequence of these events. The binary format of LV2 events is defined by the LV2_Event struct in event.h. Specific event types (such as MIDI or OSC) are defined by extensions, and should be rdfs:subClassOf this class.

TimeStamp
documentation: This defines the meaning of the 'frames' and 'subframes' fields of an LV2_Event (both unsigned 32-bit integers).

FrameStamp
documentation: The default time stamp unit for an LV2 event: the frames field represents audio frames (in the sample rate passed to instantiate), and the subframes field is 1/UINT32_MAX of a frame.

generic
documentation: Indicates that this port does something meaningful for any event type. This is useful for things like event mixers, delays, serialisers, and so on. If this property is set, hosts should consider the port suitable for any type of event. Otherwise, hosts should consider the port 'appropriate' only for the specific event types listed with :supportsEvent. Note that plugins must gracefully handle unknown event types whether or not this property is present.

supportsEvent
documentation: Indicates that this port supports or "understands" a certain event type. For input ports, this means the plugin understands and does something useful with events of this type. For output ports, this means the plugin may generate events of this type. If the plugin never actually generates events of this type, but might pass them through from an input, this property should not be set (use ev:inheritsEvent for that). Plugins with event input ports must always gracefully handle any type of event, even if it does not 'support' it. This property should always be set for event types the plugin understands/generates so hosts can discover plugins appropriate for a given scenario (for example, plugins with a MIDI input). Hosts are not expected to consider event ports suitable for some type of event if the relevant :supportsEvent property is not set, unless the ev:generic property for that port is also set.

inheritsEvent
documentation: Indicates that this output port might pass through events that arrived at some other input port (or generate an event of the same type as events arriving at that input). The host must always check the stamp type of all outputs when connecting an input, but this property should be set whenever it applies.

supportsTimeStamp
documentation: Indicates that this port supports or "understands" a certain time stamp type. Meaningful only for input ports, the host must never connect a port to an event buffer with a time stamp type that isn't supported by the port.

generatesTimeStamp
documentation: Indicates that this port may output a certain time stamp type, regardless of the time stamp type of any input ports. If the port outputs stamps based on what type inputs are connected to, this property should not be set (use the ev:inheritsTimeStamp property for that). Hosts MUST check the time_stamp value of any output port buffers after a call to connect_port on ANY event input port on the plugin. If the plugin changes the stamp_type field of an output event buffer during a call to run(), the plugin must call the stamp_type_changed function provided by the host in the LV2_Event_Feature struct, if it is non-NULL.

inheritsTimeStamp
documentation: Indicates that this port follows the time stamp type of an input port. This property is not necessary, but it should be set for outputs that base their output type on an input port so the host can make more sense of the plugin and provide a more sensible interface.