X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fstep-entry.html;h=b6ab75f5f29f0930f0c9cbb183644c92174c82df;hb=928bc145aca6190278faae96c25031875ccc9396;hp=22d4706ac35b56f913480ff8e9d94a1d33c119af;hpb=7a4c28bd8605e90876ebee619de364ab7001e405;p=ardour-manual diff --git a/include/step-entry.html b/include/step-entry.html index 22d4706..b6ab75f 100644 --- a/include/step-entry.html +++ b/include/step-entry.html @@ -1,22 +1,30 @@

- 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. + Editing MIDI can be a tedious task. Ardour allows using a connected + MIDI device like a music keyboard or pad controller, or use the mouse. + A third option, providing fine-grain control, precision and speed of entry + comes from using a custom note entry dialog.

The step entry dialog is accessed via a right click context menu on the - rec-enable button, because step entry is related to recording - MIDI data. You cannot simultaneously step edit and record MIDI via the - track's MIDI port. + rec-enable button, because step entry is related to recording MIDI + data. Step editing and recording MIDI via the track's MIDI port cannot happen + simultaneously.

- -

The dialog (quite closely modelled on Logic's) contains:

+ +
+ Ardour's Step Entry dialog +
+ Ardour's Step Entry dialog +
+
+ +

+ The dialog (quite closely modelled on Logic's) contains: +

+ +

- 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 that moving back and forth from the keyboard to the mouse is + not necessary even for complex data insertion.

-