MIDI 2.0 Overview

• MIDI 2.0 protocol for MIDI In Devices and MIDI Out Devices.
• Per-note controllers and per-note pitch bend.
  MIDI 1.0 data from an MPE keyboard is converted to per-note controls. The MultitrackStudio Instruments, Sampler, and Matrix Sampler support some per-note controls. Per-note controls are sent to AU/CLAP/VST plugins using the best available method (MIDI 2.0 protocol, Note Expressions, or MPE).
• MIDI Clip File (.midi2):
  • Import via Add Track → Import Audio/MIDI File.
  • Export via Song → Export → Export MIDI Tracks.
  • A MIDI track editor can export the selected part to a MIDI Clip File.
  Imported files can use either the MIDI 1.0 or MIDI 2.0 protocol. Exported files always use the MIDI 2.0 protocol.
• MIDI-CI Property Exchange for MIDI Out Devices. Can retrieve program names, control names, and MIDI channel names. Uses ProgramList, ChCtrlList, and Korg's X-ParameterList.
  See External MIDI Instruments and MIDI-CI
• Orchestral Articulation Profile for CLAP plugins. Fully supported except for the note-off attribute. The profile is included in exported MIDI Clip Files.
  See Orchestral Articulations
• In general, all MIDI 2.0 protocol Channel Voice message types are supported, except for Assignable Per-Note Controller. All assigned Registered Per-Note Controllers are supported, except for #3. Note-on attributes are used for articulations. Only Registered Controllers (RPNs) used by supported profiles are supported.

Note: on Windows, any features related to MIDI devices currently aren't available. See Windows MIDI Services.