Compare commits
12 Commits
e53507a933
...
29374085f0
Author | SHA1 | Date | |
---|---|---|---|
29374085f0 | |||
40aca6aaab | |||
700b9ca0ce | |||
9a095369d5 | |||
a0f1839d1f | |||
851960bbb8 | |||
|
59168d78c3 | ||
|
aa1906f67d | ||
|
35f9de8dfe | ||
|
a75683eb41 | ||
|
7f2a628c8e | ||
|
b91171b8b4 |
@ -16,7 +16,7 @@
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Using the Draw tool, as for all the automation, allows to create a gradual
|
||||
Using the Draw tool, as for all the automations, allows to create a gradual
|
||||
change from one drawn point to another. A line in the center produces no
|
||||
change to the pitch, while a line above the center will bend the pitch to a
|
||||
higher note and a line going under the middle will bend the pitch to a lower note.
|
||||
|
@ -67,7 +67,7 @@
|
||||
Since the beginning of time (well, sometime early in the 2.X series),
|
||||
Ardour has had the concept of identifying each track and bus with a
|
||||
<dfn>remote control ID</dfn>. This ID uniquely identifies a track or bus
|
||||
so that when messages arrive from elsewhere via MIDI or OSC , we can determine
|
||||
so that when messages arrive from elsewhere via MIDI or OSC, we can determine
|
||||
which track or bus they are intended to control. See
|
||||
<a href="@@controlling-track-ordering">
|
||||
remote control IDs</a> for more information.
|
||||
@ -95,7 +95,7 @@ bindings">
|
||||
|
||||
<h3>Finding out what your MIDI control surface sends</h3>
|
||||
<p>
|
||||
This is the most complex part of the job, but its still not very hard.
|
||||
This is the most complex part of the job, but it's still not very hard.
|
||||
You need to connect the control surface to an application that will show
|
||||
you the information that the device sends each time you modify a knob,
|
||||
slider, button etc. There are a variety of such applications (notably
|
||||
|
@ -2,7 +2,7 @@
|
||||
<p>
|
||||
Generic Midi allows synthesizers and other devices communicate with
|
||||
Ardour. MIDI devices can send commands relating to playback (such as
|
||||
play or stop), performance (such as volume, play, stop, and almost any
|
||||
play or stop), performance (such as volume, play, stop), and almost any
|
||||
other function (such as Edit, or Undo).
|
||||
</p>
|
||||
<p>
|
||||
|
@ -3,7 +3,7 @@
|
||||
<abbr title="Open Sound Control"><dfn>OSC</dfn></abbr> lets synthesizers
|
||||
and other devices communicate with Ardour. OSC devices can send commands
|
||||
relating to playback (such as play or stop), performance (such as volume,
|
||||
play, stop, and almost any other function (such as Edit, or Undo).
|
||||
play, stop), and almost any other function (such as Edit, or Undo).
|
||||
</p>
|
||||
|
||||
<p class="note">
|
||||
|
@ -1,7 +1,7 @@
|
||||
|
||||
<p>
|
||||
The <dfn>Virtual Keyboard</dfn> is a software MIDI instrument, similar to
|
||||
<a href="https://vmpk.sourceforge.io/">VMPK</a> that can be used like an
|
||||
<a href="https://vmpk.sourceforge.io/">VMPK</a> that can be used like a
|
||||
hardware musical keyboard would, to emit MIDI events.
|
||||
</p>
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user