midi
type: Project
license: isc
name: LV2 MIDI
shortdesc: A normalised definition of raw MIDI.
maintainer: me
created: 2006-00-00
developer: larsl
developer: me
release:
  revision: 1.10
  created: 2019-02-03
  file-release: lv2-1.16.0.tar.bz2
  blame: me
  changeset:
    item: Fix incorrect range of midi:chunk.
release:
  revision: 1.8
  created: 2012-10-14
  file-release: lv2-1.2.0.tar.bz2
  blame: me
  changeset:
    item: Use consistent label style.
    item: Add midi:binding and midi:channel predicates.
    item: Add midi:HexByte datatype for status bytes and masks.
    item: Remove non-standard midi:Tick message type.
    item: Add C definitions for message types and standard controllers.
    item: Fix definition of SystemExclusive status byte.
release:
  revision: 1.6
  created: 2012-04-17
  file-release: lv2-1.0.0.tar.bz2
  blame: me
  changeset:
    item: Add class definitions for various message types.
    item: Document how to serialise a MidiEvent to a string.
    item: Merge with unified LV2 package.
release:
  revision: 1.4
  created: 2011-11-21
  file-release: lv2-midi-1.4.tar.bz2
  blame: me
  changeset:
    item: Update packaging.
    item: Improve documentation.
release:
  revision: 1.2
  created: 2011-05-26
  file-release: lv2-midi-1.2.tar.bz2
  blame: me
  changeset:
    item: Add build system for installation.
    item: Switch to ISC license.
release:
  revision: 1.0
  created: 2010-10-04
  file-release: lv2-midi-1.0.tar.gz
  blame: me
  changeset:
    item: Initial release.
documentation: This specification defines a data type for a MIDI message, midi:MidiEvent, which is normalised for fast and convenient real-time processing. MIDI is the Musical Instrument Digital Interface, a ubiquitous binary standard for controlling digital music devices. For plugins that process MIDI (or other situations where MIDI is sent via a generic transport) the main type defined here, midi:MidiEvent, can be mapped to an integer and used as the type of an LV2 [Atom](atom.html#Atom) or [Event](event.html#Event). This specification also defines a complete vocabulary for the MIDI standard, except for standard controller numbers. These descriptions are detailed enough to express any MIDI message as properties.

MidiEvent
documentation: A single raw MIDI message (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 midi:MidiEvent is serialised to a string, the format should be xsd:hexBinary, for example: :::turtle [] eg:someEvent "901A01"^^midi:MidiEvent .

statusMask
documentation: This is a status byte with the lower nibble set to zero.