LV2 MIDI

A series of contiguous bytes (usually one) in a message.

A hexadecimal byte, which is a xsd:hexBinary value <= FF

A single raw MIDI message (i.e. a sequence of bytes).

This is equivalent to a standard MIDI messages, except with the following restrictions to simplify handling:

• Running status is not allowed, every message must have its own status byte.
• Note On messages with velocity 0 are not allowed. These messages are equivalent to Note Off in standard MIDI streams, but here only proper Note Off messages are allowed.
• "Realtime messages" (status bytes 0xF8 to 0xFF) are allowed, but may not occur inside other messages like they can in standard MIDI streams.
• All messages are complete valid MIDI messages. This means, for example, that only the first byte in each event (the status byte) may have the eighth bit set, that Note On and Note Off events are always 3 bytes long, etc. Where messages are communicated, the writer is responsible for writing valid messages, and the reader may assume that all events are valid.

If a MidiEvent is serialised to a string, the format should be xsd:hexBinary, e.g. (in Turtle notation):

[] eg:someEvent "901A01"^^MidiEvent .

The value of a pitch bender (-8192 to 8192).

The MIDI event to bind a parameter to. This describes which MIDI events should be used to control a port, parameter, or other object. The binding should be a MidiEvent but the property that represents the control value may be omitted. For example, to bind to the value of controller 17:

eg:port midi:binding [
    a midi:Controller ;
    midi:controllerNumber 17
] .

The 0-based index of a byte which is part of this chunk.

The channel number of a MIDI message.

A chunk of a MIDI message.

The numeric ID of a controller (0 to 127).

The value of a controller (0 to 127).

The numeric ID of a note (0 to 127).

Key pressure (0 to 127).

The numeric ID of a program (0 to 127).

The property this chunk represents.

The numeric ID of a song (0 to 127).

Song position in MIDI beats (16th notes) (-8192 to 8192).

The exact status byte for a message of this type.

The status byte for a message of this type on channel 1, i.e. a status byte with the lower nibble set to zero.

The velocity of a note message (0 to 127).