From 994a8b17a2501d95e485e12dea0eb6f408df6b0d Mon Sep 17 00:00:00 2001
From: David Robillard
An LV2 plugin library is suitable for dynamic loading (e.g. via
-dlopen()
) and provides one or more plugin descriptors via the
+dlopen()
) and provides one or more plugin descriptors via the
lv2_descriptor()
function. These can be instantiated to create
plugin instances
, which can be run directly on data or connected
together to perform advanced signal processing tasks.
type
. The macro LV2_ATOM_FROM_EVENT is provided in this header
- for this purpose.
+ host MAY marshal an LV2_Event to an LV2_Atom by simply pointing to the
+ offset of type
. The macro LV2_ATOM_FROM_EVENT is provided in
+ this header for this purpose.
*/
typedef struct {
diff --git a/ext/contexts.lv2/contexts.ttl b/ext/contexts.lv2/contexts.ttl
index 85245b1..3fb4358 100644
--- a/ext/contexts.lv2/contexts.ttl
+++ b/ext/contexts.lv2/contexts.ttl
@@ -99,8 +99,7 @@ ctx:MessageContext a ctx:Context , lv2:Feature ;
A non-realtime context for plugin control via message passing. This context
has a run method which takes a bitset of flags for parameters specifying which
input and output ports are valid before and after the run method has executed,
-respectively (see LV2_Contexts_MessageContext).
+respectively (see LV2_Contexts_MessageContext
).
""" .
ctx:IdleContext a ctx:Context , lv2:Feature ;
@@ -112,10 +111,9 @@ This context never has any ports.
ctx:RequestRunFeature a lv2:Feature ;
lv2:documentation """
A feature allowing the plugin to request the execution of a particular context
-at an arbitrary time. To support this feature, the host MUST pass an LV2_Feature to instantiate
with
-data
pointing to a LV2_Contexts_Request_Run_Feature.
+at an arbitrary time. To support this feature, the host MUST pass an
+LV2_Feature to instantiate
with data
pointing to a
+LV2_Contexts_Request_Run_Feature.
The plugin MAY call request_run
with the given
data
from any non-realtime context to demand soon-as-possible execution
diff --git a/ext/reference.lv2/reference.ttl b/ext/reference.lv2/reference.ttl
index 8c8281f..e928e06 100644
--- a/ext/reference.lv2/reference.ttl
+++ b/ext/reference.lv2/reference.ttl
@@ -51,7 +51,7 @@ reference:Reference a rdfs:Class ;
Reference to a Blob. The actual contents of a Reference are opaque and host specific, and must not be copied, serialized, or otherwise interpreted by a plugin, except via functions provided by the host in -LV2_Blob_Support.
+LV2_Blob_Support.A Reference is a special case of Atom with type = 0
.
"Null" is the unique Atom with type = 0
and
@@ -62,21 +62,19 @@ reference:blobSupport a lv2:Feature ;
rdfs:label "Blob support" ;
lv2:documentation """
Support for dynamically allocated blobs. If a host supports this feature, it
-MUST pass a LV2_Feature with
-URI
http://lv2plug.in/ns/ext/atom#blobSupport
-and data
pointing to a LV2_Blob_Support.
+MUST pass a LV2_Feature with URI
+http://lv2plug.in/ns/ext/atom#blobSupport and data
pointing to a
+LV2_Blob_Support.
""" .
reference:Blob a rdfs:Class ;
rdfs:label "Blob" ;
lv2:documentation """
-
Base class for all dynamically allocated blobs. An LV2_Blob ia an opaque pointer to host -data. The type and data of a blob can be accessed via host-provided -functions in LV2_Blob_Support. -The type of a blob can be any URI that describes a data format. Blobs are -always allocated by the host, and unlike atoms are not necessarily POD.
+