Event List\Exit Button:                                                                    
EXIT.IMG     

The Exit button quits the Event Editing process. You will then be asked to save the Event information on any of the 60 Tracks by selecting the Track and Clicking the Right Mouse Button. You can also Cancel at this point if you wish to discard all the Edits you have made.
If an event has been edited and the Event Edited Arrow is still displayed, you will not be able to Exit; Click on the 'Event Edited Arrow' to confirm or cancel the Edit in progress then Exit.

There are 3 basic functions the Event Editor performs:

1.	Insert an Event before the line where the Insert/Delete Arrow is located.
        FIG09.IMG    
        The New Event Inserted

2.	Delete the Event directly next to the Insert/Delete Arrow.
        FIG10.IMG    

3.	Change an existing Event by Clicking on the value you want to change.  You may Click on the actual value or the Hexadecimal value.  Once changes have been made to any Event, you may NOT change any other Event, Insert or Delete, or Scroll Up/Down until you Click on the Event Changed Arrow with:

a/The Left mouse button to Save all changes made. Once you Click on the Event Changed Arrow with either button, you may then make changes to another Event.

b/The Right mouse button to Undo all of the changes and return the Event to its original state before changes were made.
FIG11.IMG    
Click Left To SAVE 
Click Rught to CANCEL

The Key Command to Save Changed Event is the Insert Key.
The Key Command to Cancel Changed Event is the Clr/Home key.

Inserting Or Deleting Events
You can Insert MIDI Events of any kind into the Event List.
The Insert and Delete buttons are at the bottom right hand portion of the screen. They will stay active as long as the Insert/Delete Pointer Arrow is present, provided you are not currently editing an Event. The arrow will disappear off the screen if you Scroll outside the current 18 Event lines and the buttons will grey out, indicating their deactivation.  If this happens, simply point to the left of the Event Time column and Click; the Event Selection Arrow will appear and the buttons will reactivate.

To Insert An Event:
Position the Pointer Arrow next to the location number closest to where you want to place the Event.  Don't worry if the exact time doesn't exist; as soon as you've created and Inserted the Event, you can edit the time to be exactly where you want it.

Click the Insert button and a list of Event types appears to the right of the Event List.

Choose one of the MIDI Events listed and Click on it.  Clicking on Other brings up another list of choices.

Supply the needed information in the subsequent dialogs.

For example, if you want to Insert a Note On, point and Click to that item in the list.  You'll be prompted to enter the MIDI channel for that Event, which Note and Octave placement and finally what Velocity to set it at.  When you're done answering each question, the Note On Event will be Inserted in the Event list at the arrow.
FIG12.IMG

To Delete An Event:

Click the B+DeleteB- button and it's erased.

The following Events automatically readjust themselves, jumping up one line to take the Deleted Event's place.



Editing Existing Events:

Any information you can see on the screen you can edit directly with the exception of the Event description, which simply describes the Event you're viewing in words.

To Edit Any Event:
	Point to the number you want to change.
	Click with the Right button to increment.
	Click with the Left button to decrement.
	The Event Changed Arrow appears to the left of that line.  This is to W *indicate that something has been edited within that Event.

Any changes you make to the Hex column will be reflected in the related numerical column to the left of the Hex column and vice versa.  The information you see in the Hex column is the actual MIDI data the computer is working with.  You don't need to be able to read Hex in order to use this column; experimenting with it for awhile will show you which columns affect what MIDI parameters. Before you can edit another Event, you must first determine whether or not you want to save the alterations you've made on the current Event.

To SAVE the edits you've made Left Click on the Event Changed Arrow.

To CANCEL the edits and reset the Event to it's original state, Right Click on the Event Changed Arrow.

To SAVE the edits you've made Using Key Commands:
Press the B+InsertB- key. 
To CANCEL the edits Using Key Commands:
Press the B+Clr/HomeB- key.
Left button	or	INSERT key	=	SAVE 
Right button	or	CLR/HOME key	=	CANCEL and reset

This is similar to the way you edit the Event Start Time; Left saves the counter changes, Right cancels them and resets the number to its original state. Once you've saved or cancelled the edit, the Event Edited Arrow will disappear.  You can now edit another Event or Exit the Event Editor.

System Exclusive
In addition to the many standard MIDI Events, there are also Events that are only understood (Exclusively) by a specific instrument (System).  System Exclusive (Sys Ex) could be defined as "additional MIDI information W *specific to each MIDI instrument" or "Instrument Exclusive". 

Event List\System Exclusive
This feature of the program is mainly designed to transmit short System 
Exclusive messages for real-time control rather than data dumps of patch 
information or other large blocks of data.

For example, on some keyboards, you can send a message to put the keyboard in or out of split mode, or control parameters such as Filter Cutoff and Resonance.  Another example might be a Sys Ex message to change a specific parameter on a reverb unit such as reverb time.

The most commonly thought of use of System Exclusive is individual or bulk 
patch/sample storage.  The program can handle bulk dumps, but there are limitations:

a/Uses 4 times as much memory as GenEdit (Barefoot's Patch Editor / Librarian program) to store patches

b/MIDI can not send any other data in the middle of a bulk dump; yet the W *NK*counter will keep running while sending Sys Ex (although the counter on the screen won't be updated until it's done).  The sequence may pause for a number of seconds when a bulk dump is sent, and no music can be played at that time, even on other instruments.

c/Instruments that require "handshaking" (acknowledging messages W *between the computer and the MIDI instrument) may be difficult or impossible to accommodate.

Details on System Exclusive messages should be found in each manufacturer's instrument manual.  Once you know what and where the data is, putting it in the Event List is easy.

Sys Ex Recording:

-Select Input Filters from MIDI menu.
-Enable System Exclusive (defaults to disabled).
-Once Enabled, the program will record all Sys Ex messages it receives, the same way         it records any other information.
-Because Sys Ex messages can be quite long or contain large amounts of data, it is recommended that you record Sys Ex messages in Step Time.  They can be recorded while the sequencer is playing, but it is possible that the data transferred may have errors because of the great amount of data being sent in a short time.  You may also want to Disable the Mouse (see Appendix A) if recording long Sys Ex messages.



Notes For System Exclusive:

All parts of each Sys Ex message are recorded with the same time value (same tick) to insure the message doesn't get broken up during playback.

The Track Channel assignment is ignored because Sys Ex has no general provision for specifying a channel.  The format of a Sys Ex message is specific to one particular instrument, and may include a channel number encoded somewhere in the message.
You can not do anything to the sequencer while it is in the middle *of playing a Sys Ex message.  Remember, it is considered 1 message; once it starts, it must be completed.

Erasing a Region on the Graphic Screen does not erase Sys Ex messages because the program does not know which specific channel (if any ) the message is intended to be on.

How Sys Ex Is Stored

An actual MIDI System Exclusive message starts with an F0 (hex) byte, followed by a Manufacturer ID (1 byte if non-zero, 3 bytes if the first byte is 00), any number of data bytes (manufacturer-defined), and ending with an EOX (End-of-Exclusive) byte -- F7 (hex) -- which is technically a separate message.
The program breaks each Sys Ex message into 3 parts:

1	Sys Ex ID (consisting of the F0 and the first byte of the 	
	Manufacturer ID)

2	Sys Ex Data bytes (each "Event" holds 1 byte)

3	EOX (End of Exclusive)

On the Event list, each of these "Events" is listed on a separate line.
 

Sys Ex Event Editing

Due to the rules of System Exclusive message structure, there are some things to be aware of when editing Sys Ex Events using the Event List.

All "Events" associated with one Sys Ex message are recorded on the same tick and cannot be split up.  Therefore, only the Sys Ex ID Event can be moved in time.  When that is done, all subsequent contiguous Sys Ex data and EOX Events are moved with the ID Event. 
The "ID" byte and the "data" byte of the Sys Ex Data bytes are only editable in the Hexadecimal column.

Deleting Sys Ex Events

-If a Sys Ex ID Event is Deleted, all subsequent Sys Ex Data up to the next Event and the EOX Event are Deleted along with it.
-Sys Ex Data Events can be Deleted individually.
-An EOX Event can only be Deleted by itself if it is not associated with a Sys Ex ID or Data Event.

Inserting SysEx Events
	Sys Ex Data Events can only be Inserted:
			After a Sys Ex ID Event
			Before or after another Sys Ex Data Event
			Before an EOXX 

	Sys Ex ID Events and EOX can be Inserted anywhere except in the middle 
        of an existing Sys Ex message



UNDERSTANDING MIDI EVENTS

What is a MIDI Event?

A MIDI Event is a single command that changes the current state of your MIDI instrument.  This could be generalized by saying any parameter your MIDI instrument can send via the MIDI cable is a MIDI Event.

Every time you play your MIDI instrument, a minimum of two MIDI Events take place:  Note On and Note Off.  
There are 2 kinds of MIDI Events in general:

	Channel Events
	System Events

	Note On	System Exclusive
	Note Off	Song Position Pointer
	Control Change	Song Select
	Program (Patch) Change	Tune Request
	Aftertouch (Pressure)	End Of Exclusive 	(EOX)
	Pitch Wheel	Timing Clock
		
                Start
		Continue
		Stop
		Active Sensing
		Controller Reset
 

Event List\Hexadecimal Numbering

The number system most people are familiar with is the decimal system.  This counts from 0 to 9.  Hexadecimal, or base 16, counts 0-9, A, B, C, D, E, and F.  Below is a table showing how each digit (place) of decimal and hexadecimal numbers are given a value.  The x represents the number that is located in that digit.

...	fourth place	third place	second place	first place  


Let's use this table to add up place values to determine the value of a number in both decimal and hexadecimal;  we'll use the number 564.  It has three digits:   4 in the first place, 6 in the second place, and 5 in the third. When you substitute the numbers in their appropriate places, you can figure W *NK*out the value of the number. Notice that the same number has a different total value when used in the different number systems.

third place	second place	first place


			(decimal value of Hexadecimal 564)

This method can be used to figure out the value of a number in any number 
system.  Each numbering system is determined by how high the digits count.  In Binary Numbering, for example, the digits included are 0 and 1.  Here are the first 32 values in all three number systems.



How MIDI Events Are Stored

Events are stored in Hexadecimal form.  One Event may be stored as up to 3 
bytes.  A byte is two hexadecimal digits, such as F7.
A good example of this might be the first Note On Event you see when you load the sample song (SAMPLE.SNG) from the Master Program Disk. The first column of numbers is the time at which each MIDI Event takes place. The second column is a Hexadecimal representation of the current MIDI Event.  It looks like this:

90 32 58B

This is the MIDI Event for a Note On, MIDI Channel 1, Note D in the second octave, with a Velocity of 88.
The first digit is the MIDI Status Event.  A 9 represents a Note On Event.  
The 0 is a Hexadecimal value for the MIDI channel. If you count 0 - F as 1 to 16, this is MIDI Channel 1.  The 32 represents the note.  The 58 is the Velocity.  Click on each of these numbers to see which other values change and by how much.
Some MIDI messages are represented by only two bytes.  For example, (?) B+C9  20B tells a MIDI instrument receiving on MIDI Channel 10 to change to patch number 32.  MIDI internally numbers patches 0 - 127 Decimal (0 - 7F W *Hexadecimal).

EVENT List Notes

-One way to change an existing MIDI Event to another type of Event is to Insert a new Event at the selected Event, then Delete the old Event.  
The Insert/Delete Arrow will have moved down and will be ready to Delete the desired Event.
-Pressing Return will not Exit Event Editing if there is an Event Change in progress.

-There are two types of pressure Events, which some instruments call after-touch.  The most common is channel pressure, which applies equally to all Notes on a channel.  The other type of Pressure is Poly Key Pressure, where each individual key has its own unique pressure value.

-Not all instruments are capable of using all types of MIDI information.  For example, many instruments only generate or recognize 128 or 256 steps of pitch bend out of a possible 16384 steps.  Many instruments may ignore release (Note Off) Velocity, Pressure, and/or certain controllers.  See your instrument's owner's manual for information on its MIDI implementation.


