microtherion/VocalEasel
1
0
Fork 0
mirror of https://github.com/microtherion/VocalEasel.git synced 2024-12-23 11:44:03 +00:00
Code Issues Packages Projects Releases Wiki Activity
50a020426f
VocalEasel/mma/docs/html/ref/node3.html

489 lines
15 KiB
HTML
Raw Normal View History

Added MMA
2006-11-10 08:07:56 +00:00
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<!--Converted with LaTeX2HTML 2002-2-1 (1.71)
original version by: Nikos Drakos, CBLU, University of Leeds
* revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
* with significant contributions from:
Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
<HTML>
<HEAD>
<TITLE>Tracks and Channels</TITLE>
<META NAME="description" CONTENT="Tracks and Channels">
<META NAME="keywords" CONTENT="mma">
<META NAME="resource-type" CONTENT="document">
<META NAME="distribution" CONTENT="global">
<META NAME="Generator" CONTENT="LaTeX2HTML v2002-2-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
<LINK REL="STYLESHEET" HREF="mma.css">
<LINK REL="next" HREF="node4.html">
<LINK REL="previous" HREF="node2.html">
<LINK REL="up" HREF="mma.html">
<LINK REL="next" HREF="node4.html">
</HEAD>
<BODY bgcolor="#ffffff">
<!--Navigation Panel-->
<A NAME="tex2html340"
HREF="node4.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html338"
HREF="mma.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html332"
HREF="node2.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html341"
HREF="node4.html">Patterns</A>
<B> Up:</B> <A NAME="tex2html339"
HREF="mma.html">Reference Manual</A>
<B> Previous:</B> <A NAME="tex2html333"
HREF="node2.html">Running</A>
<BR>
<BR>
<!--End of Navigation Panel-->
<!--Table of Child-Links-->
<A NAME="CHILD_LINKS"><STRONG>Subsections</STRONG></A>
<UL>
<LI><A NAME="tex2html342"
HREF="node3.html#SECTION00310000000000000000">
<FONT Face="Serif" Color="Navy"><I>MMA</I></FONT> Tracks</A>
<LI><A NAME="tex2html343"
HREF="node3.html#SECTION00320000000000000000">Track Channels</A>
<LI><A NAME="tex2html344"
HREF="node3.html#SECTION00330000000000000000">Track Descriptions</A>
<UL>
<LI><A NAME="tex2html345"
HREF="node3.html#SECTION00331000000000000000">Drum</A>
<LI><A NAME="tex2html346"
HREF="node3.html#SECTION00332000000000000000">Chord</A>
<LI><A NAME="tex2html347"
HREF="node3.html#SECTION00333000000000000000">Arpeggio</A>
<LI><A NAME="tex2html348"
HREF="node3.html#SECTION00334000000000000000">Scale</A>
<LI><A NAME="tex2html349"
HREF="node3.html#SECTION00335000000000000000">Bass</A>
<LI><A NAME="tex2html350"
HREF="node3.html#SECTION00336000000000000000">Walk</A>
<LI><A NAME="tex2html351"
HREF="node3.html#SECTION00337000000000000000">Solo and Melody</A>
</UL>
<BR>
<LI><A NAME="tex2html352"
HREF="node3.html#SECTION00340000000000000000">Silencing a Track</A>
</UL>
<!--End of Table of Child-Links-->
<HR>
<H1><A NAME="SECTION00300000000000000000"></A>
<A NAME="sec-tracks"></A>
<BR>
Tracks and Channels
</H1>
<P>
This chapter discusses
<FONT Face="Serif" Color="Navy"><I>MMA</I></FONT> tracks and MIDI channels. If you are
reading this manual for the first time you might find some parts
confusing. If you do just skip ahead--you can run
<FONT Face="Serif" Color="Navy"><I>MMA</I></FONT> without
knowing many of these details.
<P>
<H1><A NAME="SECTION00310000000000000000">
<FONT Face="Serif" Color="Navy"><I>MMA</I></FONT> Tracks</A>
</H1>
<P>
To create your accompaniment tracks,
<FONT Face="Serif" Color="Navy"><I>MMA</I></FONT> divides output into several
internal tracks. There are a total of 8 different types of tracks, and
an unlimited number of sub-tracks.
<P>
When
<FONT Face="Serif" Color="Navy"><I>MMA</I></FONT> is initialized there are no tracks assigned; however, as
your library and song files are processed various tracks will be
created. Each track is created a unique name. The track types are discussed
later in this chapter, but for now they are B<SMALL>ASS</SMALL>, C<SMALL>HORD</SMALL>,
W<SMALL>ALK</SMALL>, D<SMALL>RUM</SMALL>, A<SMALL>RPEGGIO</SMALL>, S<SMALL>CALE</SMALL>, M<SMALL>ELODY</SMALL>
and S<SMALL>OLO</SMALL>.
<P>
All tracks are named by appending a ``-'' and ``name'' to the
type-name. This makes it very easy to remember the names, without any
complicated rules. So, drum tracks can have names ``Drum-1'',
``Drum-Loud'' or even ``Drum-a-long-name''. The other tracks follow
the same rule.
<P>
In addition to the hyphenated names described above, you can also name
a track using the type-name. So, ``DRUM'' is a valid drum track name.
In the supplied library files you'll see that the hyphenated form is
usually used to describe patterns.
<P>
All track names are case insensitive. This means that the names
``Chord-Sus'', ``CHORD-SUS'' and ``CHORD-sus'' all refer to the same
track.
<P>
If you want to see the names defined in a song, just run
<FONT Face="Serif" Color="Navy"><I>MMA</I></FONT> on the
file with the ``-c'' command line option.
<P>
<H1><A NAME="SECTION00320000000000000000">
Track Channels</A>
</H1>
<P>
MIDI defines 16 distinct channels numbered 1 to 16.<A NAME="tex2html15"
HREF="#foot997"><SUP>3.1</SUP></A> There is nothing which says that ``chording''
should be sent to a specific channel, but the drum channel should
always be channel 10.<A NAME="tex2html16"
HREF="#foot998"><SUP>3.2</SUP></A>
<P>
For
<FONT Face="Serif" Color="Navy"><I>MMA</I></FONT> to produce any output, a MIDI channel must be assigned to a
track. During initialization all of the DRUM tracks are assigned to
special MIDI channel 10. As musical data is created other MIDI
channels are assigned to various tracks as needed.
<P>
Channels are assigned from 16 down to 1. This means that the lower
numbered channels will most likely not be used, and will be available
for other programs or as a ``keyboard track'' on your synth.
<P>
In most cases this will work out just fine. However, there are a
number of methods you can use to set the channels ``manually.'' You
might want to read the sections on C<SMALL>HANNEL</SMALL>
(<A HREF="node18.html#set-channel">here</A>), C<SMALL>H</SMALL>S<SMALL>HARE</SMALL>
(<A HREF="node18.html#set-chshare">here</A>), O<SMALL>N</SMALL>
(<A HREF="node20.html#set-on">here</A>), and O<SMALL>FF</SMALL>
(<A HREF="node20.html#set-off">here</A>).
<P>
Why bother with all these channels? It would be much easier to put all
the information onto one channel, but this would not permit you to set
special effects (like MIDIG<SMALL>LIS</SMALL> or MIDIP<SMALL>AN</SMALL>) for a specific
track. It would also mean that all your tracks would need to use the
same instrumentation.
<P>
<H1><A NAME="SECTION00330000000000000000">
Track Descriptions</A>
</H1>
<P>
You might want to come back to this section after reading more of the
manual. But, somewhere, the different track types,
and why they exist needs to be detailed.
<P>
Musical accompaniment comes in a combination of the following:
<P>
<UL>
<LI>Chords played in a rhythmic or sustained manner,
<P>
</LI>
<LI>Single notes from chords played in a sustained manner,
<P>
</LI>
<LI>Bass notes. Usually played one at a time in a rhythmic manner,
<P>
</LI>
<LI>Scales, or parts of scales. Usually as an embellishment,
<P>
</LI>
<LI>Single notes from chords played one at time: arpeggios.
<P>
</LI>
<LI>Drums and other percussive instruments played rhythmically.
<P>
</LI>
</UL>
<P>
Of course, this leaves the melody ... but that is up to you, not
<FONT Face="Serif" Color="Navy"><I>MMA</I></FONT> ...but, if you suspect that some power is missing here, read
the brief description of S<SMALL>OLO</SMALL> and M<SMALL>ELODY</SMALL> tracks
(<A HREF="#sec-solo">here</A>) and the complete ``Solo and
Melody Tracks'' chapter (<A HREF="node10.html#chap-solo">here</A>).
<P>
<FONT Face="Serif" Color="Navy"><I>MMA</I></FONT> comes with several types of tracks, each designed to fill
different accompaniment roles. However, it's quite possible to use a
track for different roles than originally envisioned. For example, the
bass track can be used to generate a single, sustained treble
note--or, by enabling H<SMALL>ARMONY</SMALL>, multiple notes.
<P>
The following sections describe the tracks and give a few suggestions
on their uses.
<P>
<H2><A NAME="SECTION00331000000000000000">
Drum</A>
</H2>
<P>
Drums are the first thing one usually thinks about when we hear the word
``accompaniment''. All
<FONT Face="Serif" Color="Navy"><I>MMA</I></FONT> drum tracks share MIDI channel 10, which
is a GM MIDI convention. Drum tracks play single notes determined by
the T<SMALL>ONE</SMALL> setting for a particular sequence.
<P>
<H2><A NAME="SECTION00332000000000000000">
Chord</A>
</H2>
<P>
If you are familiar with the sound of guitar strumming, then you're
familiar with the sound of a chord.
<FONT Face="Serif" Color="Navy"><I>MMA</I></FONT> chord tracks play a number
of notes, all at the same time. The volume of the notes (and the
number of notes) and the rhythm is determined by pattern definitions.
The instrument used for the chord is determined by the V<SMALL>OICE</SMALL>
setting for a sequence.
<P>
<H2><A NAME="SECTION00333000000000000000">
Arpeggio</A>
</H2>
<P>
In musical terms an <B>arpeggio</B><A NAME="tex2html17"
HREF="#foot1041"><SUP>3.3</SUP></A> is the notes of a chord played
one at a time.
<FONT Face="Serif" Color="Navy"><I>MMA</I></FONT> arpeggio tracks take the current chord and, in
accordance to the current pattern, play single notes from the chord.
The choice of which note to play is mostly decided by
<FONT Face="Serif" Color="Navy"><I>MMA</I></FONT> . You can
help it along with the D<SMALL>IRECTION</SMALL> modifier.
<P>
A<SMALL>RPEGGIO</SMALL> tracks are used quite often to highlight rhythms. Using
the RS<SMALL>KIP</SMALL> directive produces broken arpeggios.
<P>
Using different note length values in patterns helps to make
interesting accompaniments.
<P>
<H2><A NAME="SECTION00334000000000000000">
Scale</A>
</H2>
<P>
The playing of scales is a common musical embellishment which addes
depth and character to a piece.
<P>
When
<FONT Face="Serif" Color="Navy"><I>MMA</I></FONT> plays a scale, it first determines
the current chord. There is an associated scale for each chord which
attempts to match the flavor of that chord. The following table
sums up the logic used to create the scales:
<P>
<DL>
<DT><STRONG>Major</STRONG></DT>
<DD>A major scale
<P>
</DD>
<DT><STRONG>Minor</STRONG></DT>
<DD>A melodic minor scale<A NAME="tex2html18"
HREF="#foot1047"><SUP>3.4</SUP></A>
<P>
</DD>
<DT><STRONG>Diminished</STRONG></DT>
<DD>A melodic minor scale with a minor fifth and minor
dominant seventh.
<P>
</DD>
</DL>
<P>
All scales start on the tonic of the current chord.
<P>
If the S<SMALL>CALE</SMALL>T<SMALL>YPE</SMALL> is set to C<SMALL>HROMATIC</SMALL>, then a chromatic
scale is used. The default for S<SMALL>CALE</SMALL>T<SMALL>YPE</SMALL> is A<SMALL>UTO</SMALL>.
<P>
<FONT Face="Serif" Color="Navy"><I>MMA</I></FONT> plays successive notes of a scale. The timing and length of the
notes is determined by the current pattern. Depending on the
D<SMALL>IRECTION</SMALL> setting, the notes are played up, down or up and down
the scale.
<P>
<H2><A NAME="SECTION00335000000000000000">
Bass</A>
</H2>
<P>
B<SMALL>ASS</SMALL> tracks are designed to play single notes for a chord for
standard bass patterns. The note to be played, as well as its timing,
is determined by the pattern definition. The pattern defines which
note from the current chord to play. For example, a standard bass
pattern might alternate the playing of the root and fifth notes of a
scale or chord. You can also use B<SMALL>ASS</SMALL> tracks to play single,
sustained treble notes.
<P>
<H2><A NAME="SECTION00336000000000000000">
Walk</A>
</H2>
<P>
The W<SMALL>ALK</SMALL> tracks are designed to imitate ``walking bass'' lines.
Traditionally, they are played on bass instruments like the upright
bass, bass guitar or tuba.
<P>
A W<SMALL>ALK</SMALL> track uses a pattern to define the note timing and
volume. Which note is played is determined from the current chord and
a simplistic algorithm. There is no user control over the note
selection.
<P>
<H2><A NAME="SECTION00337000000000000000"></A>
<A NAME="sec-solo"></A>
<BR>
Solo and Melody
</H2>
<P>
S<SMALL>OLO</SMALL> and M<SMALL>ELODY</SMALL> tracks are used for arbitrary note data.
Most likely, this is a melody or counter-melody ...but these
tracks can also be used to create interesting endings, introductions or
transitions.
<P>
<H1><A NAME="SECTION00340000000000000000">
Silencing a Track</A>
</H1>
<P>
There are a number of ways to silence a track:
<P>
<UL>
<LI>Use the O<SMALL>FF</SMALL> (page <A HREF="node20.html#set-off"><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]" SRC="crossref.png"></A>) command to stop the
generation of MIDI data,
<P>
</LI>
<LI>Disable the sequence for the bar with an empty sequence (page
<A HREF="node5.html#sequence-clear"><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]" SRC="crossref.png"></A>).
<P>
</LI>
<LI>Delete the entire sequence with S<SMALL>EQ</SMALL>C<SMALL>LEAR</SMALL> (page
<A HREF="node5.html#sec-seqclear"><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]" SRC="crossref.png"></A>).
<P>
</LI>
<LI>Disable the MIDI channel with a ``Channel 0'' (page
<A HREF="node18.html#channel0"><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]" SRC="crossref.png"></A>).
<P>
</LI>
</UL>
<P>
Please refer to the appropriate sections on this manual for further
details.
<P>
<P>
<BR><HR><H4>Footnotes</H4>
<DL>
<DT><A NAME="foot997">... 16.</A><A
HREF="node3.html#tex2html15"><SUP>3.1</SUP></A></DT>
<DD>The
values 1 to 16 are used in this document. Internally they are stored
as values 0 to 15.
</DD>
<DT><A NAME="foot998">... 10.</A><A
HREF="node3.html#tex2html16"><SUP>3.2</SUP></A></DT>
<DD>This is not a MIDI rule, but a
convention established in the GM (General MIDI) standard. If you
want to find out more about this, there are lots of books on MIDI
available.
</DD>
<DT><A NAME="foot1041">...arpeggio</A><A
HREF="node3.html#tex2html17"><SUP>3.3</SUP></A></DT>
<DD>The term is derived from
the Italian ``to play like a harp''.
</DD>
<DT><A NAME="foot1047">... scale</A><A
HREF="node3.html#tex2html18"><SUP>3.4</SUP></A></DT>
<DD>If
you think that support for Melodic and Harmonic minor scales is
important, please contact us.
</DD>
</DL><HR>
<!--Navigation Panel-->
<A NAME="tex2html340"
HREF="node4.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html338"
HREF="mma.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html332"
HREF="node2.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html341"
HREF="node4.html">Patterns</A>
<B> Up:</B> <A NAME="tex2html339"
HREF="mma.html">Reference Manual</A>
<B> Previous:</B> <A NAME="tex2html333"
HREF="node2.html">Running</A>
<!--End of Navigation Panel-->
<ADDRESS>
Bob
2006-10-15
</ADDRESS>
</BODY>
</HTML>
Reference in New Issue Copy Permalink