X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=_manual%2F15_editing-and-arranging%2F12_edit-midi.html;h=00b36df3006751233802eba670e1b320d7858a6d;hb=b19b09025d678f35bc882f17e73718009509b4ae;hp=4996e032c769daf2e1af680a4bf201d4207cf275;hpb=85e48bfa703786066ab5b0fbff8fa4a98da036e7;p=ardour-manual
diff --git a/_manual/15_editing-and-arranging/12_edit-midi.html b/_manual/15_editing-and-arranging/12_edit-midi.html
index 4996e03..00b36df 100644
--- a/_manual/15_editing-and-arranging/12_edit-midi.html
+++ b/_manual/15_editing-and-arranging/12_edit-midi.html
@@ -3,47 +3,65 @@ layout: default
title: Edit MIDI
---
+
+ Ardour's handling of MIDI editing differs from most other DAWs
+ and MIDI sequencers.
+
-
-
-Ardour's handling of MIDI editing differs from most other DAWs and MIDI sequencers.
-Key features of Ardour MIDI handling
+Key features of Ardour MIDI handling
-- All editing is done in-place, in-window. There is no separate piano roll window or pane. Edit notes right where you see them.
-
-- All MIDI I/O is done via JACK for sample accurate timing and maximal efficiency when communicating with external software synthesizers
-
-- Every MIDI track has its own JACK MIDI port for input; it may have an arbitrary combination of audio and MIDI outputs, depending on the signal processing in the track; the full flexibility of JACK connectivity is present for MIDI just as it is for audio.
-
-- Full automation for MIDI tracks, integrated with the handling of all MIDI CC data for each track
-
-- Controllers (CC data) can be set to discrete or continuous modes (the latter will interpolate between control points and send additional data)
-
-- Normal or Percussive mode for note data editing
-
-- The "scroomer" (a combination scroll/zoom tool) for altering the zoom level and range of visible MIDI data
-
+ -
+ All editing is done in-place, in-window. There is no separate piano roll
+ window or pane. Edit notes right where you see them.
+
+ -
+ All MIDI I/O is done via JACK for sample accurate timing and maximal
+ efficiency when communicating with external software synthesizers.
+
+ -
+ Every MIDI track has its own JACK MIDI port for input; it may have an
+ arbitrary combination of audio and MIDI outputs, depending on the signal
+ processing in the track; the full flexibility of JACK connectivity is
+ present for MIDI just as it is for audio.
+
+ -
+ Full automation for MIDI tracks, integrated with the handling of all MIDI
+ CC data for each track.
+
+ -
+ Controllers (CC data) can be set to discrete or continuous modes (the
+ latter will interpolate between control points and send additional
+ data).
+
+ -
+ There is a Normal and a Percussive mode for note data editing.
+
+ -
+ The scroomer is a combination scroll/zoom tool for altering
+ the zoom level and range of visible MIDI data.
+
-Notable Differences
+
+Notable Differences
-- As mentioned above, all editing is done in-place
-
-- Fader (volume) control currently operates on transmitted MIDI data, not by sending CC #7
-
-- All note/data editing is per-region. There are no cross-region operations at this time
-
-- By default, copying a MIDI region creates a "deep link" or "cloned copy" - both regions share the same data source, and edits to the contents of one will affect the other. To break this link, select
MIDI > Unlink from other copies from the region context menu, after which the selected region(s) will have their own copies of only the data that they visually display on screen. You will not be able to trim the region back its "original" length after an Unlink operation, and the operation cannot be undone.
-
+ -
+ Fader (volume) control currently operates on transmitted MIDI data, not by sending CC
+ #7.
+
+ -
+ All note/data editing is per-region. There are no cross-region operations at this
+ time.
+
+ -
+ By default, copying a MIDI region creates a deep link
+ — both regions share the same data source, and edits to the contents of
+ one will affect the other. To break this link, select
+ from the region
+ context menu, after which the selected region(s) will have their own copies
+ of only the data that they visually display on screen. You will not
+ be able to trim the region back its original length after an Unlink operation,
+ and the operation cannot be undone.
+
-
-
-
-
-
-
-
-
-
-
{% children %}