Text changes.
This commit is contained in:
parent
803dd48b6e
commit
b56cd35b80
|
@ -601,8 +601,6 @@ CC1[16]{0} CC1 CC2'
|
|||
|
||||
Using similar rules, you can extract almost any part of an input value, down to every single bit if needed (see the end of the next section for an example).
|
||||
|
||||
As you can see, mod translations in combination with discrete value lists are fairly powerful and let you implement pretty much any desired mapping with ease. There are some limitations, though. In particular, the reversal of the `CC1[1] C0` translation in the previous section, i.e., *extracting* the note number from a note input, is rather tedious (it involves writing down rules for each and every single note). Also, there's no direct way to combine different kinds of translations of the same input, or to consolidate the values of multiple input messages into a single output message. (The macro facility in the following section helps with the former, but not with the latter problem.)
|
||||
|
||||
## Macro Translations
|
||||
|
||||
There are some situations in which it is hard or even impossible to construct a translation in a single step, but it may become much easier if we can recursively invoke other translations. midizap allows you to do this by "calling" the mod translation for a MIDI message on the right-hand side of a translation. This is done by prefixing the message to be expanded with the `$` character:
|
||||
|
|
14
midizap.1
14
midizap.1
|
@ -1613,20 +1613,6 @@ CC1[16]{0}\ CC1\ CC2\[aq]
|
|||
Using similar rules, you can extract almost any part of an input value,
|
||||
down to every single bit if needed (see the end of the next section for
|
||||
an example).
|
||||
.PP
|
||||
As you can see, mod translations in combination with discrete value
|
||||
lists are fairly powerful and let you implement pretty much any desired
|
||||
mapping with ease.
|
||||
There are some limitations, though.
|
||||
In particular, the reversal of the \f[C]CC1[1]\ C0\f[] translation in
|
||||
the previous section, i.e., \f[I]extracting\f[] the note number from a
|
||||
note input, is rather tedious (it involves writing down rules for each
|
||||
and every single note).
|
||||
Also, there's no direct way to combine different kinds of translations
|
||||
of the same input, or to consolidate the values of multiple input
|
||||
messages into a single output message.
|
||||
(The macro facility in the following section helps with the former, but
|
||||
not with the latter problem.)
|
||||
.SS Macro Translations
|
||||
.PP
|
||||
There are some situations in which it is hard or even impossible to
|
||||
|
|
Loading…
Reference in New Issue