home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Sound Sensations!
/
sound_sensations.iso
/
demos
/
gfmanual
/
part06.mnl
< prev
next >
Wrap
Text File
|
2002-07-28
|
36KB
|
1,057 lines
Edit - Part B Section 7B-1
START OF PART6.MNL
START OF PART6.MNL
START OF PART6.MNL
START OF PART6.MNL
START OF PART6.MNL
START OF PART6.MNL
START OF PART6.MNL
START OF PART6.MNL
START OF PART6.MNL
START OF PART6.MNL
START OF PART6.MNL
START OF PART6.MNL
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part B Section 7B-2
A DISCUSSION OF MAIN CONTROLL - A CONTROLL SEQUENCE
---------------------------------------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SEQUENCE # 5 NAME MAIN CONTROLL
CMND =>_________________________________________________
EVENT TYPE NOTE OCT DURAT TIME CH VEL MEAS STEP
---------------------------------------------------------
1|PROG | | 48| 0| 0| 1| 0| 1 1
2|* | | 0| 0| 0| 0| 0| 1 1
3|MELODY | 0 | 8| 1| 0| 0| 0| 1 1
4|CHORDS 1-12 | 0 | 3| 1| 0| 0| 0| 1 1
5|BASS CONTROLL+ | 0 | 4| 1| 0| 0| 0| 1 1
6|* | | 0| 0| 0| 0| 0| 1 1
7|* | | 0| 0| 0| 0| 0| 1 1
8|* | | 0| 0| 0| 0| 0| 1 1
9|* | | 0| 0| 0| 0| 0| 1 1
10|* | | 0| 0| 0| 0| 0| 1 1
11|* | | 0| 0| 0| 0| 0| 1 1
12|* | | 0| 0| 0| 0| 0| 1 1
13|* | | 0| 0| 0| 0| 0| 1 1
14|* | | 0| 0| 0| 0| 0| 1 1
15|* | | 0| 0| 0| 0| 0| 1 1
16|* | | 0| 0| 0| 0| 0| 1 1
17|* | | 0| 0| 0| 0| 0| 1 1
18|* | | 0| 0| 0| 0| 0| 1 1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You should have selected EDIT (option 2) from the Main Menu and
on the EDIT SELECTION screen specified MAIN CONTROLL as the
sequence to edit. Now you should be looking at the EDIT screen
for sequence MAIN CONTROLL.
MAIN CONTROLL is a controll sequence. Its main purpose is to
start other sequences. You can think of it as the Conductor of
an Orchestra. What follows is a discussion of each event in MAIN
CONTROLL
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part B Section 7B-3
The first event is a PROGram event (shown above but not in
GFDEMO1 as distributed). This event sends out a Midi program
change that sets a program on the synthesizers that respond to
it. To send out program changes (sometimes called "patch
changes") to your synthesizer you would have a program change(s)
in one or more of your sequences.
To put a PROGram change in your sequence you do the following :
- enter PROG in the TYPE field for the event.
- In The OCTave field you enter the program number.
The Midi spec specifies that a program change can range
from 0 to 127.
- In the TIME field goes the "time"
(see discussion of timing)
The headings on the EDIT screen are there for the most common
event type. That is, Note-On events. However, because there are
so many different types of events, some fields on the screen have
to do double duty. So, the OCTave field is used for PROGram
number for the PROG event. The same holds true for other event
TYPEs as you will see later. Which fields to put the parameters
in for the different event types was chosen based on a
combination of logical meaning (e.g. for sequence start DURATion
is used for repeats) and/or ease of entry.
The second event is a "Null Event". A null event does not do
anything. You specify a null event by entering "*" in the TYPE
field. No other fields apply except the TIME field. You need to
specify a TIME. Every event has a time. The main use for a null
event is as a timing placeholder. For example, suppose you
recorded a sequence and you wanted to 'delete' a note but not
otherwise disturb the timings of other events (e.g. notes) in the
sequence. You could simply change the TYPE field for that event
from Note-On (TYPE of blank) to "*" (null event). The note would
not be there but the timing of the sequence with respect to all
other events would remain the same. E.g. suppose you wanted to
change a chord from C7 to C. Just change the event for the A+
note to a null event.
The third event is a sequence start event. It starts sequence
MELODY and does NOT WAIT for it to complete. When a sequence
start event starts another sequence it specifies how many times
it wants that sequence to repeat. This is done by specifying a
repeat (or loop) count in the DURATion field. In this example,
MELODY is to repeat 1 time. So, this event will start MELODY and
continue on with its business (the next event).
Notice the OCT field for event 3. It contains a number. When
you create a sequence start event you DO NOT enter anything in
the OCT field. Instead, after you press ENTER and the
information is processed, the editor will put a number here. It
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part B Section 7B-4
is the Sequence Number. Ignore this. GFMUSIC deals in numbers,
but you only have to deal in names (at least as far as sequences
and songs go).
The fourth event is also a sequence start event. This time the
sequence started is CHORDS 1-12. Again, the sequence is started
with a repeat count of 1 (in the DURAT field) and then MAIN
CONTROLL goes on to the next event.
The fifth event is also a sequence start event. This time MAIN
CONTROLL starts BASS CONTROLL and waits for it to complete before
going on to the next event. That is, it is a sequence start with
a wait. MAIN CONTROLL will go no further until BASS CONTROLL has
looped 1 time. To specify "wait", add a "+" after the name of
the sequence that you are starting. Do not leave any spaces
between the + and the last character of the sequence name !!!!
At this point, BASS CONTROLL will process its own events. Since
we specified a repeat/loop count of 1 (in the DURAT field), after
BASS CONTROLL processes all of its events 1 time, then MAIN
CONTROLL will be invoked again at event number 6.
Events 6 thru 18 are Null Events. They will do nothing.
It is important to remember that all sequences must end with a
NULL EVENT (* in TYPE). The editor will make sure you do this.
MAIN CONTROLL has a TIME of zero in all of its events. This is
not always the case with controll sequences. However, in the
case of MAIN CONTROLL, it works because it merely starts
sequences and eventually waits for some of them to complete.
Sometimes you may want to start a sequence a specific length of
time after starting some other sequence. In these cases you will
have sequence start events with a non-zero TIME.
In the case of MAIN CONTROLL, when it starts the sequences
MELODY, CHORDS 1-12, and BASS CONTROLL, it does so with a zero
TIME from one sequence start to the next. The effect is that of
starting each of these sequences at the same time. This is the
most common way of starting sequences.
When we start MAIN CONTROLL from PLAY/RECORD, it will loop 999
times. The first time it is started, it will start 3 sequences.
One of the sequences it starts (BASS CONTROLL) will also start
sequences. So let's go on and examine BASS CONTROLL which itself
is a controll sequence that is started from a higher level
controll sequence (MAIN CONTROLL).
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part B Section 7B-5
A DISCUSSION OF BASS CONTROLL - ANOTHER CONTROLL SEQUENCE
=========================================================
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SEQUENCE # 4 NAME BASS CONTROLL
CMND => ________________________________________________
EVENT TYPE NOTE OCT DURAT TIME CH VEL MEAS STEP
---------------------------------------------------------
1|BASS 1-10+ | 0 | 2| 4| 0| 0| 0| 1 1
2|BASS 1-10+ | 5 | 2| 2| 0| 0| 0| 1 1
3|BASS 1-10+ | 0 | 2| 2| 0| 0| 0| 1 1
4|BASS 1-10+ | 7 | 2| 1| 0| 0| 0| 1 1
5|BASS 1-10+ | 5 | 2| 1| 0| 0| 0| 1 1
6|BASS 11-12+ | 0 | 6| 1| 0| 0| 0| 1 1
7|* | | 0| 0| 0| 0| 0| 1 1
8|* | | 0| 0| 0| 0| 0| 1 1
9|* | | 0| 0| 0| 0| 0| 1 1
10|* | | 0| 0| 0| 0| 0| 1 1
11|* | | 0| 0| 0| 0| 0| 1 1
12|* | | 0| 0| 0| 0| 0| 1 1
13|* | | 0| 0| 0| 0| 0| 1 1
14|* | | 0| 0| 0| 0| 0| 1 1
15|* | | 0| 0| 0| 0| 0| 1 1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Leave EDIT on MAIN CONTROLL by pressing ESCape twice. This is
the non-graceful way to end EDIT. You will get a message. Read
it and press ESCape. If you want to save any changes you may
have made in EDIT, you should exit via the END command. A more
thorough discussion of all commands is for later.
You should now be back at the Main Menu. Notice that "2" is
still in the data entry field of the Main Menu. Since we want to
get back to EDIT, just press ENTER. At the EDIT SELECTION
screen, change the name to BASS CONTROLL and press ENTER. You
will then see the EDIT screen for the BASS CONTROLL sequence (as
shown above).
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part B Section 7B-6
BASS CONTROLL is also a controll sequence. It starts the bass line
sequences that contain the actual notes. We still have not even
seen a Note-On EVENT.
The first EVENT is a sequence start event with a WAIT. It starts
sequence BASS 1-10 with a repeat/loop count of 4 (in the
DURATion) field and waits for it to complete before going on with
the next EVENT. Remember, WAITed sequence starts can be
identified by the "+" at the end of the sequence name in the TYPE
field.
The second event again starts sequence BASS 1-10. This time it
starts it with a repeat count (DURATion field) of 2. More
importantly, the NOTE field contains a 5. This means that when
BASS 1-10 plays, it will play all notes 5 steps higher. If we
wanted it to play 7 notes lower, we would have entered "-7" in
the NOTE field.
When we start a sequence, we can also specify a transposition
value for VELocity (either + or -). For those of you with
velocity sensitive keyboards or sound modules, you can use this
feature to great effect.
The next 4 events are all sequence start events with a WAIT
(follow the sequence name to start with a +, do not leave a space
between the last character of the sequence name and the +).
The last events are all Null Events (* in TYPE). Again, all
sequences must end with a Null Event.
So we can see that by using a controll sequence and
transpositions when we start a sequence, we can get alot of music
out of just a few notes. Specifically, BASS 1-10 is used over
and over in the 12 bars blues simply by starting the basic bass
line with the proper transposition.
Now let's look at a sequence with notes in it. Type "END" on the
command line and press ENTER. At the main menu select option 2
and press ENTER. On the EDIT SELECTION screen, enter CHORDS 1-12
and press ENTER.
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part B Section 7B-7
A DISCUSSION OF CHORDS 1-12 - A SEQUENCE WITH NOTES
------------------------------------------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SEQUENCE # 3 NAME CHORDS 1-12
CMND => ___________________________________________
EVENT TYPE NOTE OCT DURAT TIME CH VEL MEAS STEP
----------------------------------------------------
1| | E | 5| 190| 0| 1| 64| 1 1
2| | G | 5| 190| 0| 1| 64| 1 1
3| | C | 5| 190| 0| 1| 64| 1 1
4| | E | 5| 190| 192| 1| 64| 2 1
5| | G | 5| 190| 0| 1| 64| 2 1
6| | C | 5| 190| 0| 1| 64| 2 1
7| | G | 5| 190| 192| 1| 64| 3 1
8| | E | 5| 190| 0| 1| 64| 3 1
9| | C | 5| 190| 0| 1| 64| 3 1
10| | C | 5| 190| 192| 1| 64| 4 1
11| | E | 5| 190| 0| 1| 64| 4 1
12| | G | 5| 190| 0| 1| 64| 4 1
13| | F | 5| 190| 192| 1| 64| 5 1
14| | C | 5| 190| 0| 1| 64| 5 1
15| | A | 5| 190| 0| 1| 64| 5 1
16| | C | 5| 190| 192| 1| 64| 6 1
17| | F | 5| 190| 0| 1| 64| 6 1
18| | A | 5| 190| 0| 1| 64| 6 1
19| | E | 5| 190| 192| 1| 64| 7 1
20| | G | 5| 190| 0| 1| 64| 7 1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You should now be looking at the EDIT screen for CHORDS 1-12.
EVENT 1 has a type of blank. A blank TYPE is a Note-On event
(when manually entering notes in edit you could also use a type
of "ON"). A note-on event results in sending a Midi Note-On
command 'down the wire' to the synthesizer(s) at the other end.
The NOTE and OCTave fields specify which note to sound. It can
range from NOTE=C and OCTave=1 to NOTE=G and OCTave=9. Normally,
you will initially record sequences via the PLAY/RECORD feature
and later EDIT the sequence. When you create a sequence that
way, what you will see on the EDIT screen are the notes that you
played.
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part B Section 7B-8
The 1st event will sound E in the 5th octave. The note will last
for 192 steps (the DURATion field). In this case, 192 steps of
duration is the same as one measure/bar because of the way we
setup the timing parameters on the SET TIME option (discussed
later). The TIME field of event 1 is 0. That means that it will
start zero steps after the prior event was started. Since it is
the first event, a zero TIME means that it will sound the note as
soon as the sequence is started.
The CHannel field (CH) contains a 1. This means that this Midi
event will be 'tagged' with a Midi CHannel of 1. Synthesizers on
the 'wire' that are setup to respond to channel 1 will sound this
note when it is played by the sequencer.
The VELocity field (VEL) has a value of 64. VELocity only has
meaning for Note-On and Note-Off events (and almost all
manufacturers do not use Velocity as part of Note-Off). The
meaning (how the synthesizer will react) of VELocity varies from
synthesizer to synthesizer (and even from program to program on
the same synth). See the manual for your own synthesizer/sound
modules. If you have a velocity sensitive keyboard, when you
record a sequence you will see different values in the velocity
field when you EDIT the sequence you record). In this case all
of the notes have a VELocity of 64 because it was played on a
Casio CZ-3000 which is not velocity sensitive. I.e. it always
sends out 64 as the value for velocity.
The last two fields on the screen are MEAS and STEP. In this
example the first note is to be played at MEASure 1 and STEP 1.
Since this sequence was recorded with 192 steps per measure,
event 4 will be played on the beat for measure 2.
Now look at events 2 and 3. They both have a TIME of zero. That
means they will sound zero steps after the prior event.
Ultimately, this means that the first 3 events (notes) will sound
simultaneously.... i.e. we are playing a chord. Isn't it amazing
that I was able to get all three notes to sound at exactly the
same time ??? No.... I used the autocorrect feature of EDIT
after I recorded it. But that is for later.
Now look at event 4. This note will sound 192 steps after the
prior event. And events 5 and 6 have a start time of zero so
they will sound at the same time as event 4 (another chord).
Since I recorded at 192 steps per measure, notes 4-6 will all
sound EXACTLY at the beginning of measure 2 (now that is good
playing).
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part B Section 7B-9
**************************************************************
IMPORTANT TOPIC FOLLOWS
IMPORTANT TOPIC FOLLOWS
IMPORTANT TOPIC FOLLOWS
IMPORTANT TOPIC FOLLOWS
**************************************************************
USING THE PGUP AND PGDN KEYS
On the screen, you can only see 20 events at a time. To page
thru the sequence use the PgUP and PgDn keys. Try it. Now try
entering "TOP" on the command line and press ENTER or PGUP. The
editor will take you to the top of the sequence. Try entering
BOT (for bottom) on the command line and press ENTER or PGDN.
The editor will take you to the BOTtom of the sequence. Now try
this; Get to the top of the sequence. Then put the cursor on the
same row/line as event 10 and press pgdn. The editor will
position event 10 at the top of the screen. Now put the cursor
on event 25 and press pgup. The editor will position event 25 at
the bottom of the screen. You can controll which event is at
the top or bottom of the screen by positioning the cursor on the
desired row for the event and using pgup or pgdn.
For long sequences, there is also another handy feature. On the
command line, you can enter a number and then use the PGUP or
PGDN keys. If the Command Line begins with a valid number
(integer) instead of a command (e.g. 100) and you press PGDN,
then the editor will page you down 100 events. If you were to
enter "100" on the command line and press PGUP, the editor
would page up 100 events. If the number is out of range, the
editor will take you to either the beginning or ending of the
sequence. When pressing PGUP or PGDN and nothing applies (i.e.
no TOP or BOT or no valid number on the command line) then the
editor will page you up/down 19 events (1 less than a full
screen). Try it.
Something else you will notice about using the PGUP or PGDN keys
is that when they are used, the MEAS and STEP fields all get the
value 1. For large sequences, the calculations of these fields
can be time consuming. So for paging thru the sequence with the
editor, page up and page down simply sets MEAS and STEP to 1.
After you PGUP/PGDN to where you want to go, simply press enter
to have MEAS and STEP calculated for you.
**************************************************************
Now go to the bottom of the sequence. Notice the last event
(event 38). It is a Null Event (all sequences MUST end with a
Null Event). A null event does nothing..... but, the TIME field
of the null event is important. This null event has a time of
192, and it has it for a reason. If it had any other value, the
sequence would not be exactly 12 measures long. That may be ok
if the sequence will only repeat 1 time and the start of other
sequences do not depend on when this sequence ends. But if the
sequence loops, or the start of other sequences depend on it
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part B Section 7B-10
being a specific length (say exactly 12 bars long), then the time
of the last null event is important. For example, if this
sequence were not exactly 12 bars long, and I had started it with
a wait from a controll sequence, then when this sequence ended
and the controll sequence started the next sequence, it may start
the next sequence too early or too late. So..... timing is
important, and the TIME of the last Null Event is just as
important as the timing of all other events !
Now let's look at a sequence with a command that controlls Tempo.
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part B Section 7B-11
TEMPO CONTROLL - A SEQUENCE THAT USES THE BPM EVENT
=====================================================
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SEQUENCE # 7 NAME TEMPO CONTROLL
CMND => _______________________________________________
EVENT TYPE NOTE OCT DURAT TIME CH VEL MEAS STEP
--------------------------------------------------------
1|BPM | | 100| 0| 0| 0| 0| 1 1
2|MAIN CONTROLL+ | 0 | 5| 1| 0| 0| 0| 1 1
3|* | | 0| 0| 0| 0| 0| 1 1
4|BPMUP | | 30| 0| 0| 0| 0| 1 1
5|MAIN CONTROLL+ | 0 | 5| 1| 0| 0| 0| 1 1
6|* | | 0| 0| 0| 0| 0| 1 1
7|BPMUP | | 30| 0| 0| 0| 0| 1 1
8|MAIN CONTROLL+ | 0 | 5| 1| 0| 0| 0| 1 1
9|* | | 0| 0| 0| 0| 0| 1 1
10|BPMUP | | 30| 0| 0| 0| 0| 1 1
11|MAIN CONTROLL+ | 0 | 5| 1| 0| 0| 0| 1 1
12|* | | 0| 0| 0| 0| 0| 1 1
13|BPMUP | | 30| 0| 0| 0| 0| 1 1
14|MAIN CONTROLL+ | 0 | 5| 1| 0| 0| 0| 1 1
15|* | | 0| 0| 0| 0| 0| 1 1
16|BPMDN | | 30| 0| 0| 0| 0| 1 1
17|MAIN CONTROLL+ | 0 | 5| 1| 0| 0| 0| 1 1
18|* | | 0| 0| 0| 0| 0| 1 1
19|BPMDN | | 30| 0| 0| 0| 0| 1 1
20|MAIN CONTROLL+ | 0 | 5| 1| 0| 0| 0| 1 1
--------------------------------------------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
By now you should know how to get into EDIT on a sequence so go
into EDIT on TEMPO CONTROLL.
Event 1 has a TYPE of BPM. BPM stands for Beats Per Minute. You
can controll the tempo of a song from your sequences. Event 1
has a OCT value of 100. This is really a BPM value. For the BPM
event we use the OCT field for entering the tempo we want (in
beats per minute). Acceptable values are 60 thru 240. The event
TIME is like any other event. It specifies when this event is to
take place. The other fields have no meaning. Just enter BPM in
TYPE, the tempo you want in the OCT field, and the time you want
the event to occur in the TIME field.
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part B Section 7B-12
Event 2 starts MAIN CONTROLL that we looked at earlier. And it
starts it with a WAIT (a + immediately following the sequence
name). So, event 1 sets the tempo to 100 BPM and then
immediately starts MAIN CONTROLL and waits for MAIN CONTROLL to
complete 1 loop. After MAIN CONTROLL finishes 1 loop, event 3
will be started. Since it is a null event nothing will happen.
Then zero steps after the null event (i.e. at the same time)
event 4 will be 'executed'.
Event 4 is a BPMUP event. BPMUP means take the current tempo and
increase it by whatever is in the OCT field. If this results in
a setting > 240, then the tempo will be set to 240 BPM. Again,
as soon as the tempo is set up by 10, MAIN CONTROLL will be
started with a WAIT.
Later on, in event 16 we see a BPMDN event. This sets the tempo
(in beats per minute) down by the value in the OCT field.
So, you can set the tempo to a specific value, or up/dn by a
value.
To create the effect of gradually increasing/decreasing tempo,
use this technique. Create a sequence that does a BPMUP by some
value every so often and have your controll sequence invoke it
for however many repeats needed (a sequence start with no wait).
E.g. The sequence may have only two events. The first event can
be a BPMUP of 1 with a time of 48. The second and last event
would be a NULL EVENT with a time of zero. If you had started
this sequence from some other sequence with a repeat count of 100
the tempo would increase by 1 every 48 steps (or every quarter
note if 192 steps per measure and 4 beats per measure were
specified in the SET TIME feature). So after 100 iterations (25
bars) the tempo would have increased by 100 beats per minute.
Now think about this, The first event could have a time of zero
and the null event a time of 48 and the effect would be the same.
**********
At this point, let's look at the PROfile screen. You probably
did not know that one existed. Put the cursor on the command
line (the easy way is to press the HOME key) and type in PRO
followed by a space and press ENTER.
The HOME key will position the cursor on the first 'field' of the
screen. In the case of the Edit Detail screen, that is the
Command Line.
**********
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part B Section 7B-13
THE EDIT PROFILE SCREEN
=======================
When you record a sequence and process it (PLAY/RECORD followed
by the right arrow that takes you to the PROCESS RECORDED DATA
screen) you specify things like the Name of the sequence, the
PLAY KEY to assign, etc. These are important items related to a
sequence. You can also set and change them from EDIT. You
should be looking at the the Profile screen now.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SEQUENCE PROFILE
-------------------
SEQUENCE NUMB | 5 | SEQUENCE TO RECORD
SEQUENCE NAME | MAIN CONTROLL | NAME ASSIGNED
| |
MUTE | N | Y=YES, ELSE NO
VELOCITY XPOSE | 0 | -127 TO +127
| |
NOTE XPOSE | 0 | -127 TO +127
DISREGARD XPOSE | N | Y=NEVER XPOSE, ELSE XPOSE
COMPUTER PLAY KEY | K | A..Z
REPEATS | 999 | 1 TO 999
XPOSE AFFECTS | N | Y OR N
---------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Looking at the Screen :
SEQUENCE NUMB
-------------
This is a protected field and is for informational purposes.
Each sequence has a number assgned to it. This is the number for
this sequence.
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part B Section 7B-14
SEQUENCE NAME
-------------
The name of the sequence that you assigned during PLAY/RECORD
PROCESS RECORDED DATA, or if you created the sequence directly
by asking to EDIT a sequence that did not yet exist. You can
change the name of the sequence by changing it here.
If another sequence starts this sequence, it will be
automatically adjusted to start the new Name.
MUTE
----
Remember when you muted the sequence during PLAY/RECORD ?? This
is its value when you last left PLAY/RECORD.
VELOCITY XPOSE, NOTE XPOSE
------------------------------------------
Remember the velocity and/or note transpositions during
PLAY/RECORD ?? These are their values and you can set/reset them
here. However, normally you do this during PLAY/RECORD. If you
change them here it may become confusing.
DISREGARD XPOSE
---------------
If set to 'Y', then GFMUSIC will NEVER perform any transpositions
when this sequence is played. Useful for drum patterns.
Discussed previously under PLAY/RECORD.
COMPUTER PLAY KEY
-----------------
The key (A..Z) that when pressed during PLAY/RECORD will start
this sequence. If blank, then no play key is assigned. You can
set the play key here for the sequence. In fact, whenever you
create a controll sequence, you will usually come here and assign
a PLAY KEY by setting this field to A..Z. Otherwise, you could
not start the controll sequence from the computer keyboard.
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part B Section 7B-15
REPEATS
-------
How many times this sequence will repeat/loop when started from
the computer keyboard. You can set/reset this value here.
XPOSE AFFECTS
-------------
If "Y" then this sequence is in the 'affected list'. If not,
then it is not. You can set it here. Also discussed earlier
during the PLAY/RECORD discussion.
To change the values, make the changes and press ENTER. When
done, press ESCape twice to get back to the EDIT screen.
Now you know alot of how GFMUSIC works. Next there is a
discussion of timing. We will come back to EDIT later.
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part B Section 7B-16
END OF PART6.MNL
END OF PART6.MNL
END OF PART6.MNL
END OF PART6.MNL
END OF PART6.MNL
END OF PART6.MNL
END OF PART6.MNL
END OF PART6.MNL
END OF PART6.MNL
END OF PART6.MNL
END OF PART6.MNL
END OF PART6.MNL
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
