home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Sound Sensations!
/
sound_sensations.iso
/
demos
/
gfmanual
/
part05.mnl
< prev
next >
Wrap
Text File
|
2002-07-28
|
24KB
|
859 lines
Edit - Part A Section 7A-1
START OF PART5.MNL
START OF PART5.MNL
START OF PART5.MNL
START OF PART5.MNL
START OF PART5.MNL
START OF PART5.MNL
START OF PART5.MNL
START OF PART5.MNL
START OF PART5.MNL
START OF PART5.MNL
START OF PART5.MNL
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part A Section 7A-2
EDIT
----
GENERAL
-------
Edit and PLAY/RECORD is where you will spend much of your time
with GFMUSIC. It is here where the functionality is.
The editor is a "FULL SCREEN" editor. That is, you make all of
your changes on a screen, and then press ENTER to tell GFMUSIC
that you want them processed.
***************************************************************
Remember, F9 and F10 takes you to the next field on the next
line.
Also, look in the index for "Numeric Data" and reread the tip on
entering numeric data.
***************************************************************
Load the demo song GFDEMO1. To do this choose option 7 from the
main menu. Since this song is on the GFMUSIC disk (or if using a
hard disk it is in the same directory GFMUSIC is in) all you have
to do on the LOAD SONG screen is put GFDEMO1 in the song name
field and put "C" in the free or clear field and press ENTER.
After the song is loaded, press ESCape twice to get back to the
Main Menu. Then do the following :
- Get to the EDIT SELECTION screen via option 2 from the
Main Menu.
- On the Edit Selection Screen, enter "MAIN CONTROLL"
and press ENTER. I.e. we want to edit sequence
MAIN CONTROLL (2 L's in controLL).
- Next you will see the EDIT screen.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
EDIT SELECTION
---------------
ENTER SEQUENCE NAME |MAIN CONTROLL |
---------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part A Section 7A-3
If we had specified a non-existant sequence on the EDIT SELECTION
screen, then GFMUSIC would have created one with that name and
initialized it with a few "Null Events" (you will learn about
them later). If we had simply made a mistake, we could use the
CANCEL command on The EDIT screen when it was displayed and the
newly created sequence would have been deleted.
***************************************************************
We will discuss the EDIT features shortly, but first a general
discussion of the song GFDEMO1 is in order.
***************************************************************
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part A Section 7A-4
GFDEMO1 - A DISCUSSION OF HOW IT WAS CREATED
============================================
GFDEMO1 is a sample song intended to show most of the features of
GFMUSIC and to provide insight into how you might put a song
together. Here is the way GFDEMO1 was created. First, the SET
TIME option was selected from the main menu. On the SET TIME
screen the following was specified :
- 192 steps per measure
- 2 steps per Midi Clock
- 4 beats per measure
- Midi Clock Off (O)
- 120 Beats Per Minute
Later, read the section on timing for more information on this
feature and how it relates to sequences and events. But for now,
just follow along.
The second thing that was done is that the PLAY/RECORD feature was
selected from the main menu (option 1). No sequences existed at
this point so LOAD MODE was skipped and PLAY/RECORD mode was
entered by pressing ENTER. The metronome was on and a 1 bar bass
line was played on the synthesizer. The bass line was then
processed into a sequence by pressing the RIGHT ARROW key. The
right arrow key caused the PROCESS RECORDED DATA screen to be
presented and there the following was specified :
- a name of "BASS 1-10 ORIG"
- "Y" (yes) in ZERO 1ST EVENT field
- DISREGARD XPOSE was set to "N" (no)
- a play key was assigned
- AFFECTED BY XPOSE was set to "Y" (yes)
Then ENTER was pressed and GFMUSIC created the sequence BASS 1-10
ORIG.
At this point, I had a bass line. It was rough, and I wanted to
clean it up but I also wanted to leave it as recorded so you
could look at it later. So I made a copy of it. I ESCaped until
I got to the main menu and then used the COPY/MERGE function
(Main Menu option 5) to make a copy of BASS 1-10 ORIG. I named
the copy BASS 1-10. BASS 1-10 will be the first 10 bars of a 12
bar blues progression. I then went into EDIT on BASS 1-10 and
'cleaned' it up so that the timing was better and I also made
sure that the sequence was exactly 1 bar long. I.e. I made sure
that The measure/step field for the last event indicated MEASure
2 and STEP 1. The intent was to use only 1 bass line for the
first 10 bars by having a bass controll sequence start it with
the proper transpositions at the proper time.
Next, I recorded the bass line for bars 11 and 12. I went to the
PLAY/RECORD screen and recorded 2 bars of bass line that I wanted
for the last two bars of the 12 bar blues progression. I named
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part A Section 7A-5
it BASS 11-12. After recording this sequence and processing it
by using the right arrow key, I then ESCaped my way back to the
Main Menu and selected EDIT (option 2). At the EDIT SELECTION
screen I specified sequence BASS 11-12. I was then presented
with the EDIT screen where I 'cleaned up' this sequence. Now I
had two bass lines. One for the first 10 bars and one for the
last two bars. Now I needed a controll sequence for them. I
could have started the bass lines from the main controll sequence
I would create later, but I elected to create a controll sequence
just for controlling the bass line sequences. In this way I
could show you how higher level controll sequences can invoke
(start) lower level controll sequences.
So, next I created a sequence called BASS CONTROLL. I did this
by going to the EDIT SELECTION screen and specifying sequence
BASS CONTROLL. Since it did not exist, GFMUSIC created the
sequence with a small number of Null Events in it. I then put
into BASS CONTROLL the proper sequence start commands that would
play all 12 bars of bass. When you look at BASS CONTROLL you
will see that it does the following :
- Plays BASS 1-10 4 times without any transpositions
- Then plays BASS 1-10 2 times transposing it up 5
steps (notes).
- Then plays BASS 1-10 2 times without transposing
- Plays BASS 1-10 1 time transposing it up 7 notes
- Plays BASS 1-10 1 time transposing it up 5 notes
- Plays BASS 11-12 1 time with no transpositions.
Now I had all of my bass lines and its controll sequence. I then
went back to PLAY/RECORD and started BASS CONTROLL. As it played
the 12 bars of bass, I played the chords on my synthesizer (all
12 bars). I then processed the recorded data into a sequence and
named it CHORDS 1-12.
Again, I left PLAY/RECORD and cleaned up the timing of this
sequence by using the autocorrect features of the EDITor.
Now I had bass and chords. All I needed now was a controll
sequence. So I created sequence MAIN CONTROLL via the editor
and into it I put the correct sequence start events to invoke
BASS CONTROLL and CHORDS 1-12. I also put in an event to set
the synthesizer to 'piano' so that when I play it back it will
pick the correct synth patch/program. Now I had a main controll
sequence that would play my bass and chords for me.
The Edit Screen for MAIN CONTROLL shown below has the PROG event
that set the synthesizer to "Piano". On the distribution disk
for GFMUSIC, the MAIN CONTROLL sequence does not have the PROG
event so that it will play on everyone's synth. So when playing
GFDEMO1, you must manually set your synth to "piano". Keep this
in mind when reading the text and looking at an actual Edit
Screen for MAIN CONTROLL.
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part A Section 7A-6
I played MAIN CONTROLL from edit (that you will learn of later) and
while in PLAY/RECORD, I recorded a simple melody 12 bars long. I
processed that into a sequence called MELODY. I then ESCaped my
way back into EDIT (because I had invoked PLAY/RECORD from EDIT)
and inserted yet another sequence start event for the MELODY
sequence I had just recorded.
The only thing that remained was to clean up the timing of MELODY
since I do not play well. So I left edit of MAIN CONTROLL via
the END command so that my work would be saved and then edited
MELODY. While editing MELODY, I cleaned up the timing a little
and made sure it came out to exactly 12 bars long. Now I was
done. I saved my work and ended edit via the END command.
Finally, I went back to PLAY/RECORD to see how the whole thing
sounded.
The point of all of this is that with a sequencer that supports
controll sequences, you can put a song together with bits and
pieces. Most music is repetitive. For example, A bass line in
bars 5 and 6 is the same as bars 1 thru 4 except that it is
transposed up some number of steps. This is an important concept
to grasp especially as it relates to GFMUSIC. Record a part
of a song only one time and then invoke it when needed from a
controlling sequence via the sequence start command.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
EDITOR OPERATION - HIGH LEVEL
=============================
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part A Section 7A-7
At any rate, you should now be viewing the EDIT screen. The EDIT
screen consists of two main parts :
- The Command line (The first red rectangle on the screen)
- The Edit-Detail area (The area below the Command Line
with all the red boxes).
The Edit-Detail area contains EVENTS. EVENTS can be of many
different types that you will learn about later. You use the
editor to modify, copy, delete, and create events. You can do
this in two ways.
- By changing attributes of events directly in the
Edit-Detail area.
- Via commands from the command line.
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part A Section 7A-8
The editor will always operate in the following order :
- Items in the Edit-Detail area are checked for errors first.
If an error is found, the event number is set to blink
and an error message is issued. See left column for the event
number. All events have an event number. As you add and
delete events, the event numbers are adjusted.
- If no errors are found, then any changes that may have been
in the Edit-Detail area are captured and the command line
is then processed. If an error in the command is detected,
a message is issued and no further action takes place.
The command line is the long red rectangle at the top of the
screen. It is on the command line where commands such as
"DEL 1 5" are issued (delete events 1 thru 5).
When you are done editing a sequence, you exit by issuing an END
command. This is the graceful way to end edit and doing it this
way will save whatever changes you have made. To exit without
saving any changes, use The CANcel command, or just keep pressing
ESCape.
THE COMMAND LINE AND COMMANDS
=============================
First, a general discussion of the command line. Commands can
consist of just the command, or the command followed by up to 3
numbers. Some commands require 1 number, some 2 numbers, and
some 3 numbers following the command. When entering a command
and its parameters, the command and all parameters must be
separated by one or more spaces. When processing commands, if
the command you issue requires 2 numbers and you have issued it
with 3 numbers, only the first two numbers are processed. The
3rd number is ignored.
****************************************************************
After processing your command, the editor will leave your command
on the command line as you entered it, but it will replace the
1st character with a "?". Whenever the 1st character of the
command line is a "?", the editor will ignore whatever is on the
command line. This is a handy feature because your last command
is retained on the command line for your convenience but is not
processed until you change the "?" or type in a new command.
****************************************************************
Many commands require the second number to be an event number.
Often you want that number to be the last event number. For
commands such as these, if the second number is greater than the
last event number, the command will be processed as if you
entered the last event number. For example, If we have a
sequence with 222 events and we want to delete events 100 thru
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part A Section 7A-9
the end, we could enter "DEL 100 222" on the command line.
However, if we don't know what the last event number is, we could
enter "DEL 100 9999". Use a maximum of 4 digits on any number
associated with a command.
*****************************************************************
You can get HELP at any time by pressing ESCape followed by "H".
Try it now and see what you get.
Remember, before a command can be processed, the data in the
Edit-Detail area must pass muster first.
We will come back to command line processing later after we learn
about the types of events and the Edit-Detail area.
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part A Section 7A-10
EVENTS AND Edit-Detail
======================
You should be looking at the EDIT screen for sequence MAIN
CONTROLL. A brief discussion of fields on the EDIT screen
follows. Read thru it but don't study it. Later we will discuss
in detail every facet of the sequences as found in GFDEMO1.
The columns in the Edit-Detail area are :
EVENT TYPE NOTE OCT DURAT TIME CH VEL MEAS STEP
Look for them on the screen.
EVENT
-----
This is the event number for the event. You will use this number
in many commands issued from the command line. The EVENT field
is 'protected'. I.e. you can not change it.
TYPE
----
What 'type' of EVENT it is. For example, a Note-On event, a
Sequence Start, etc. Details for all possible event types will
follow later.
NOTE
----
For Note-On or Note-Off events, this is the note to turn on/off.
It can range from C in OCTave 1 thru G in OCTave 9. Indicate
sharps or flats by using + and - (plus and minus) respectively.
GFMUSIC will always show notes with the + designation. Thus, you
could enter a note of D-, and the next time it is displayed it
will be displayed as a C+.
The Sequence Start event uses the NOTE field for different
purposes. This will be discussed later.
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part A Section 7A-11
OCT
---
This is the OCTave field. For Note-ON and Note-Off this field
contains the octave of the note to be played or turned off.
Other event types may use this field for different purposes.
DURAT
----
This is the DURATion field. For Note-On events, the value in
this field specifies how long the note should be sounded for.
Again, this field may be used by other event types for other
purposes.
TIME
----
All events have a Time associated with them. This field
indicates when the event should be processed and is the time
since the prior event was activated. For event 1 of a sequence,
this time is the time since the sequence was started.
See the section on timing also. This is an important concept
that you should learn well.
CH
--
This is the CHannel field. This field applies only to Midi
events and is the Midi Channel that is associated with the event.
If your synthesizer is set to receive on channel 1 then Note-On
events that you want to be processed by your synthesizer should
also have 1 specified in CHannel field in the sequence(s). The
same holds true for PROGram changes, pitch BENDs, etc. When you
record (via PLAY/RECORD) and create a sequence, this field will
be the CHannel number that you synthesizer associated with the
notes and other Midi events (such as program changes) that it
sent out. CHannel can be from 1 thru 16.
VEL
---
This is the velocity field. It applies only to Note-On, Note-
Off, and Sequence Start Events. It is the velocity associated
with the Note-On or Note-Off event, or, the velocity transpose to
use when you start another sequence with a Sequence Start Event.
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part A Section 7A-12
MEAS and STEP
-------------
This is a protected field and is calculated by GFMUSIC. See the
section on timing.
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
Edit - Part A Section 7A-13
END OF PART5.MNL
END OF PART5.MNL
END OF PART5.MNL
END OF PART5.MNL
END OF PART5.MNL
END OF PART5.MNL
END OF PART5.MNL
END OF PART5.MNL
END OF PART5.MNL
END OF PART5.MNL
END OF PART5.MNL
END OF PART5.MNL
COPYRIGHT 1988 Gerald H. Felderman Tampa, Fl
