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 you see them.
14 All MIDI I/O is done via JACK for sample accurate timing and maximal
15 efficiency when communicating with external software synthesizers.
18 Every MIDI track has its own JACK MIDI port for input; it may have an
19 arbitrary combination of audio and MIDI outputs, depending on the signal
20 processing in the track; the full flexibility of JACK connectivity is
21 present for MIDI just as it is for audio.
24 Full automation for MIDI tracks, integrated with the handling of all MIDI
25 CC data for each track.
28 Controllers (CC data) can be set to discrete or continuous modes (the
29 latter will interpolate between control points and send additional
33 There is a Normal and a Percussive mode for note data editing.
36 The <dfn>scroomer</dfn> is a combination scroll/zoom tool for altering
37 the zoom level and range of visible MIDI data.
41 <h2>Notable Differences</h2>
44 Fader (volume) control currently operates on transmitted MIDI data, not by sending CC
48 All note/data editing is per-region. There are no cross-region operations at this
52 By default, copying a MIDI region creates a <dfn>deep link</dfn>—both
53 regions share the same data source, and edits to the contents of
54 one will affect the other. To break this link, select
55 <kbd class="menu">MIDI > Unlink from other copies</kbd> from the region
56 context menu, after which the selected region(s) will have their own copies
57 of <em>only</em> the data that they visually display on screen. You will not
58 be able to trim the region back its original length after an Unlink operation,
59 and the operation cannot be undone.