---
<p>
- Sometimes you will want to edit MIDI data directly from a connected
- MIDI device like a music keyboard or pad controller. Sometimes you will
- want to use the mouse. Sometimes you'll want the fine-grain control,
- precision and speed of entry that comes from using a custom note entry
- dialog.
+ Sometimes editing MIDI data directly from a connected MIDI device like a musical
+ keyboard or pad controller is desired; sometimes using the mouse is. Sometimes
+ the fine-grained control, precision and speed of entry that comes from using a
+ custom note entry dialog is; the <dfn>Step Entry</dfn> dialog aims to be the
+ latter.
</p>
+
<p>
- The step entry dialog is accessed via a right click context menu on the
- rec-enable button, because step entry is related to <em>recording</em>
- MIDI data. You cannot simultaneously step edit and record MIDI via the
- track's MIDI port.
+ The step entry dialog is accessed via a right click context menu on the
+ rec-enable button, because step entry is related to <em>recording</em> MIDI
+ data—step editing and recording MIDI via the track's MIDI port cannot be
+ done simultaneously.
</p>
-<img src="/files/a3/a3_step_entry.png" />
-<p>The dialog (quite closely modelled on Logic's) contains:</p>
+
+<p class="center"><img src="/images/a3_step_entry.png" /></p>
+
+<p>The dialog (closely modeled after Logic's) contains:</p>
+
<ul>
<li>
Chord entry switch (successive notes are stacked in a chord until
<li>Buttons to add bank or program change events</li>
<li>a full 10 octave virtual keyboard</li>
</ul>
+
<p>
- More or less all actions in the step entry dialog can be driven
- directly from the keyboard, so you do not need to keep moving back
- and forth from keyboard to mouse to do complex data insertion.
+ More or less all actions in the step entry dialog can be driven directly from
+ the keyboard, so moving back and forth from keyboard to mouse to do complex data
+ insertion is unnecessary.
</p>
+