3 MIDI (or Musical Instrument Digital Interface) is a method of representing
4 musical concepts in a form suitable for use in computers. MIDI defines 16
5 different <dfn>channels</dfn>, along which messages are passed to instruments
6 or synthesizers that understand the MIDI protocol; notes are played by
7 sending appropriately crafted <dfn>NoteOn</dfn> messages that are followed
8 by <dfn>NoteOff</dfn> messages. MIDI channels can be manipulated with
9 special <dfn>controller</dfn> messages to alter the pitch of instruments, or
10 their volume or timbre, and they can also tell the instrument or synthesizer
11 what sound to play using <dfn>Program Change</dfn> and <dfn>Bank Select</dfn>
16 Typically Program Change and Bank Select messages are collectively referred to by the singular term <dfn>Patch Change</dfn>.
19 <h2>Key features of Ardour MIDI handling</h2>
23 MIDI, just like audio, exists in regions. MIDI regions behave like audio
24 regions: they can be moved, trimmed, copied (cloned), or deleted. Ardour
25 allows either editing MIDI (or audio) regions, or MIDI region content (the
26 notes), but never both at the same time. The <kbd>e</kbd> key
27 (by default) sets <a href="@@toolbox#edit-internal">Internal Edit</a> Mode,
28 which allows the editing of MIDI data in a given region.
31 All MIDI I/O is done either by ALSA or JACK (depending on which backend was chosen when starting Ardour), for sample accurate timing and maximal efficiency when communicating with external software synthesizers.
34 Every MIDI track has its own JACK MIDI port for input; it may have an
35 arbitrary combination of audio and MIDI outputs, depending on the signal
36 processing in the track; the full flexibility of JACK connectivity is
37 present for MIDI just as it is for audio.
40 Full automation for MIDI tracks, integrated with the handling of all MIDI
41 <abbr title="Continuous Controller">CC</abbr> data for each track.
44 Controllers (CC data) can be set to discrete or continuous modes; the
45 latter will linearly interpolate between control points and send additional
50 <h2>Notable differences compared to other DAWs and sequencers</h2>
54 Fader (volume) control currently operates on transmitted MIDI data, not by
58 All note/data editing is per-region. There are no cross-region operations at
62 By default, copying a MIDI region creates a <dfn>deep link</dfn>—both
63 regions share the same data source, and edits to the contents of one will
64 affect the other. Breaking this link is done by selecting <kbd
65 class="menu">MIDI > Unlink from other copies</kbd> from the region
66 context menu, after which the selected region(s) will have their own copies
67 of <em>only</em> the data that they visually display on screen. The region
68 will no longer be trimmable back to its original length after an Unlink
69 operation, and the operation cannot be undone.