3 Ardour's handling of <dfn>MIDI editing</dfn> differs from most other DAWs
7 <h2>Key features of Ardour MIDI handling</h2>
10 All editing is done in-place, in-window. There is no separate piano roll
11 window or pane. Edit notes right where they appear.
14 MIDI, just like audio, exists in regions. MIDI regions behave like audio
15 regions: they can be moved, trimmed, copied (cloned), or deleted. Ardour
16 allows either editing MIDI (or audio) regions, or MIDI region content (the
17 notes), but never both at the same time. The <kbd class="menu">e</kbd> key
18 (by default) toggles between region level and note level editing
21 Editing note information in Ardour occurs in only a single region. There is
22 no way currently to edit in note data for multiple regions at the same time,
23 so for example notes cannot be selected in several regions and then all
24 deleted, nor can they be copied-and-pasted from one region to another.
25 Region(s), though, can be copy-pasted just as with audio.
28 All MIDI I/O is done via JACK for sample accurate timing and maximal
29 efficiency when communicating with external software synthesizers.
32 Every MIDI track has its own JACK MIDI port for input; it may have an
33 arbitrary combination of audio and MIDI outputs, depending on the signal
34 processing in the track; the full flexibility of JACK connectivity is
35 present for MIDI just as it is for audio.
38 Full automation for MIDI tracks, integrated with the handling of all MIDI
39 CC data for each track.
42 Controllers (CC data) can be set to discrete or continuous modes (the
43 latter will interpolate between control points and send additional
47 There is a Normal and a Percussive mode for note data editing.
50 The <dfn>scroomer</dfn> is a combination scroll/zoom tool for altering
51 the zoom level and range of visible MIDI data.
55 <h2>Notable Differences</h2>
58 Fader (volume) control currently operates on transmitted MIDI data, not by
62 All note/data editing is per-region. There are no cross-region operations at
66 By default, copying a MIDI region creates a <dfn>deep link</dfn>—both
67 regions share the same data source, and edits to the contents of one will
68 affect the other. Breaking this link is done by selecting <kbd
69 class="menu">MIDI > Unlink from other copies</kbd> from the region
70 context menu, after which the selected region(s) will have their own copies
71 of <em>only</em> the data that they visually display on screen. The region
72 will no longer be trimmable back to its original length after an Unlink
73 operation, and the operation cannot be undone.