3 Ardour's handling of MIDI and how it allows the editing of MIDI data differs
4 in key ways from most other DAWs and MIDI sequencers. Also, unlike its
5 handling of audio data, the editing of MIDI data in Ardour is necessarily
6 <em>destructive</em> by nature.
9 <h2>Key features of Ardour MIDI editing</h2>
13 All editing is done in-place, in-window; there is no separate piano roll
14 window or pane. Notes are edited right where they appear.
17 Editing note information in Ardour occurs in only a single region. There is
18 no way currently to edit note data for multiple regions at the same time;
19 so, for example, notes cannot be selected in several regions and then all
20 deleted, nor can they be copied and pasted from one region to another.
21 Regions, however, <em>can</em> be copied and pasted just as with audio.
24 When using jackd as the audio server for Ardour, all MIDI I/O is done
25 via JACK for sample accurate timing and maximal efficiency when communicating
26 with external software synthesizers. Otherwise, Ardour connects to midi
27 via the existing OS MIDI system.
30 Every MIDI track has its own MIDI port for input; it may have an
31 arbitrary combination of audio and MIDI outputs, depending on the signal
32 processing in the track.
35 Full automation for MIDI tracks, integrated with the handling of all MIDI
36 CC data for each track.
39 Controllers (CC data) can be set to discrete or continuous modes (the
40 latter will interpolate between control points and send additional
44 There is a Normal and a Percussive mode for note data editing.
47 The vertical dimension of the region window is controlled by a
48 <dfn>scroomer</dfn> widget, which is a combination scroll/zoom tool for
49 altering the zoom level and range of visible MIDI data.