Keyboard electronic musical instrument with guitar emulation function

Abstract

A polyphonic electronic musical instrument is provided wherein a keyboard is used to trigger arpeggiated chords which emulate a strumming guitar sound. Select keys are provided for selecting which notes are included in chords to be strummed. At least one triggering device is also provided for triggering chords. The triggering device is constructed to alternate between two trigger states. The triggering device may be a keyboard key, foot pedal, or other device. The instrument operates in such a fashion that two arpeggiated chords of alternating direction (ascending and descending) may be produced during, and at least partially as a result of, one triggering device cycle from one state to the other and back again.

Description

FIELD OF THE INVENTION

This invention relates to a keyboard-controlled electronic musical instrument capable of emulating a strumming guitar.

BACKGROUND OF THE INVENTION

When a guitarist plays a guitar with standard string tuning and the standard physical configuration (left hand selecting notes on the fretboard and right hand strumming the strings), a downstrum (in which the right hand strokes downward) generally produces an ascending arpeggiated chord. An upstrum generally produces a descending arpeggiated chord. Generally, a guitarist will alternate up and downstrums, producing arpeggiated chords which are alternately ascending and descending. This action is easy, smooth and natural, due to the fact that two chords may be produced with a single up-down cycle of the right hand. This two-chord-per-cycle technique enables a guitarist to easily produce strums in rapid succession. Also, this technique allows a guitarist to easily introduce a swing factor into the timing of the strums. A swing factor or "feel" is present when the elapsed time between an upstrum and a downstrum is different than the elapsed time between a downstrum and an upstrum. By consistently alternating strums with the same time difference, a guitarist can produce a desired swing feel. A guitarist may easily achieve this effect by simply displacing the center of his stroke either slightly above or slightly below the vertical center of the six strings (the vertical center of the strings is between the D and G strings). This displacement of stroke is so easy and natural that guitarists are often not even aware that they are doing it.

Various known prior art processing systems enable a keyboardist to simulate guitar strums. However, these prior art systems have been found to be lacking in the above stated advantageous qualities which a guitar possesses.

For example, U.S. Pat. No. 4,379,420 (Deutsch) describes a keyboard guitar emulator in which a group of keys perform the dual function of chord selection and arpeggiated chord triggering. In text column 11, lines 44-68, an alternating strum direction feature is disclosed. A musician, or user, may trigger a first strum by depressing a chord on the keyboard. Once the chord is depressed and held, an additional strum, alternating in direction, may be triggered by lifting any key within the chord and repressing it. Since a chord is triggered only when the key moves from rest to depressed position, the two-chord-per-cycle technique described above is not possible and the above described advantages of this technique are not realized.

Other guitar emulators provide a separate trigger switch to trigger arpeggiated chords, e.g., U.S. Pat. No. 3,967,520 (Drydyk), but none of the known prior art enables a user to produce arpeggiated chords in alternating directions with the same easy, smooth, and natural action of strumming a guitar.

SUMMARY OF THE INVENTION

Overview:

According to the present invention, an electronic musical instrument is provided with a keyboard, a tone generating device, at least one user-operated triggering device for triggering arpeggiated chords, and a digital data processing system. The keyboard may be worn on the user with the same orientation as the Z-Tar (manufactured by Starr Switch Co. of San Diego, Calif.) or other strap-on keyboard, or the keyboard may be horizontally situated in the traditional fashion.

The data processing system processes key state information received from the keyboard and, following a predetermined software program, sends tone triggering/muting instructions to a tone-producing module. The keyboard, processing system, and tone-producing module may be housed within a single stand-alone unit, or separate units may be provided for each. For example, the invention may be realized through the use of a standard MIDI controller keyboard sending MIDI data to a stand-alone computer which then processes the received data according to the invention and sends this processed data via MIDI to a standard stand-alone tone producing module. In the preferred embodiment, the keyboard and microprocessor-controlled processing system are housed in a single unit and communicate via MIDI to a standard stand-alone tone producing module. The processing system and tone generating device may be incorporated into the same electronic device, circuit board, or even into the same microprocessor-driven computer system. Other hardware configurations are within the scope of the invention as well.

At least twelve keys within the keyboard are assigned to a note select function. The data processing system establishes this assignment by processing information about movement of these keys in a manner which is consistent with a note select function. The tone generating device is capable of producing at least twelve tones corresponding with the at least twelve note select keys. Numerous different tone generating devices may be used. These include (but are not limited to) MIDI or ZIPI-operated electronic "sound modules", and computer-controlled automatic pianos, e.g., PianoDisc.RTM. pianos.

The user may alternate the triggering device between two states.

The instrument operates in such a fashion that two arpeggiated chords of alternating direction (ascending and descending) may be produced during, and at least partially as a result of, one triggering device cycle from one state to the other and back again.

It should be noted that, for any type of triggering device according to the present invention, the two trigger states are not transitory. They are distinct static states. A static state is to be distinguished from a transitory event in that a static state may be maintained indefinitely, and a transitory event may not. For example, the sweeping of a guitar pick over a set of guitar strings is an event. A keyboard key in rest position is in a static state. A triggering device according to the present invention triggers an arpeggiated chord when it is shifted by the user from one static state to another. A triggering device according to the present invention is configured in such a manner that, under normal operating circumstances, the processing system is always informed of a shift from one state to the other.

The triggering device may be a key on the keyboard which may be alternated between a rest state (typically "up" position) and a selected state (typically "down", or "depressed" position). The key may comprise a stationary metal plate which is electrically connected to a finger sensing circuit. In this alternate embodiment, the triggering device comprises the metal plate key and the sensing circuit. The sensing circuit would occupy a rest key state (e.g., a low current state) when it is untouched and would occupy a selected key state (e.g., a relatively high current state) when a fingertip is making direct contact. Note select keys may operate in the same way.

Triggering device state changes may be affected through movement of a human appendage, e.g., a finger, foot, elbow, palm, knee, or other body part. The speed with which this appendage moves may be measured in ways which are familiar to those of ordinary skill in the art. Information regarding the speed with which a human appendage effects a state change may be used to determine performance parameters, such as output velocity (normally used by a tone generating device to determine loudness) or arpeggiation rate.

The invention may be realized through at least four methods which are described in the following four sections.

1. Single Trigger Method:

The invention may be realized with the use of a single triggering device. The triggering device may be alternated by the user between a first trigger state and a second trigger state. This device may be a key within the keyboard, as discussed above, a switch on the instrument control panel, a foot switch, or other device.

For example, the triggering device may be a foot position sensing device which senses horizontal position of at least a portion of one of the user's feet. This unit may include a swivel plate upon which the user's heel or toe rests, and a sensing system which senses horizontal position of the user's toe or heel (whichever is free to swing). By swinging his toe back and forth from right to left, the user alternates the triggering device between first and second trigger states. The sensing system may be optical, sensing the location of the swinging foot portion directly. Alternately, the sensing system may sense rotation of the swivel plate in which case the position of the swivel plate with the user's foot pointed to one side corresponds with one trigger state. By swinging his foot to point in the other direction, the swivel plate is partially rotated to a second position corresponding with the second trigger state.

With the single trigger method, a first state change of the triggering device (e.g., a downstroke of a trigger key) from its first trigger state (e.g., from rest key position) to its second trigger state (e.g., to depressed key position) when at least two of the note select keys are in selected key state causes the data processing system to command the tone generating device to initiate production of the tones corresponding with the selected note select keys in an ascending sequence. (For definitional purposes, the at least two keys constitute a chord.) A second state change of the triggering device (e.g., an upstroke) from its second trigger state to its first trigger state following the first trigger state change as the selected note select keys remain in selected key state causes the data processing system to command the tone generating device to terminate production of the tones initiated as a result of the first trigger state change and again initiate production of the same tones, this time in a descending sequence.

2. Double Trigger Method:

The invention may be realized with the use of a single pair of triggering devices. Each of these triggering devices may be alternated by the user between a rest trigger state and a selected trigger state. The two triggering devices may each be a key within the keyboard, as discussed above, a switch on the instrument control panel, a foot switch, or other device.

With the double trigger method, a trigger state change from selected to rest state does not initiate a chord or tone. Only state changes from rest to selected state (e.g., downstrokes) cause the data processing system to initiate tone production.

In the parlance of this specification's parent application, the two triggers "repeat" with each other. A state change of the first triggering device from rest trigger state to selected trigger state when at least two of the note select keys are in selected key state causes the data processing system to command the tone generating device to initiate production of the tones corresponding with the selected note select keys in an ascending sequence. A state change of the second triggering device from rest trigger state to selected trigger state following the state change of the first triggering device as the selected note select keys and the first triggering device continue to be held in selected state causes the data processing system to command the tone generating device to terminate production of the tones initiated as a result of the first triggering device state change and again initiate production of the same tones, this time in a descending sequence.

3. Multiple Trigger Key Pairs Method:

(This method is referred to in the Description of the Preferred Embodiment as "Single Key Strumming".)

With this method, at least twelve trigger key pairs serve the dual function of note/chord selection and strum triggering. The processing system includes a memory device which stores data. This data includes the tones (i.e., notes) contained within at least twelve predetermined chords. Each of the twelve chords corresponds with one of the key pairs. The twelve chords may all be of the same type, e.g., major seventh chords. Each of the twelve key pairs may be assigned to a different one of the twelve notes in a standard octave. The two keys within each pair may be spaced one octave apart. This arrangement works well with a standard keyboard. For a Janko Keyboard with independent keys, the two keys within each pair may occupy different key rows and be laterally aligned; i.e., they may occupy the same position on the X (left-to-right) axis.

A single keyboard may include more than one group of twelve pairs. One group may trigger major chords, another group may trigger minor chords, another group may trigger dominant seventh chords, etc. The processing system may include a patch change function which may change the type of chord which one or more groups may trigger. Thus, many different chord types may be performed with one keyboard.

Each key pair consists of an upstrum key and a downstrum key. For any one of the key pairs, a rest-to-selected state change of the upstrum key causes the data processing system to command the tone generating device to initiate production of the tones contained within that pair's corresponding predetermined chord in a descending note sequence; and a rest-to-selected state change of the downstrum key causes the data processing system to command the tone generating device to initiate production of the tones contained within the same corresponding chord in an ascending note sequence.

The two keys within a pair may repeat with each other.

4. Multiple Single Trigger Keys Method:

This method may be viewed as a combination of the Single Trigger Method and the Multiple Trigger Pairs Method. Predetermined chords are stored in memory as in the Multiple Pairs Method. However, instead of a pair of keys assigned to each predetermined chord, only one strum trigger key is used for each chord. Thus, only twelve strum keys (one octave) are required for one chord type in any of the twelve keys. Each strum key is user-alternateable between a first state (e.g., a rest state) and a second state (e.g., a selected state).

A foot pedal, keyboard key, or other auxiliary control device is used in conjunction with the strum keys. The auxiliary device may be alternated by the user between a first state (e.g., a rest state) and a second state (e.g., a selected, or depressed state).

When the auxiliary device is in its first state, a strum key state change causes the data processing system to command the tone generating device to initiate production of an audio sound. This sound may be a "chucka" sound, as would result if a guitarist strummed his guitar strings while muting them with his left hand. This sound may be produced by the playback of a "chucka" sample, by playing a series of six "click" sounds in rapid succession, or by commanding the tone generating device to play in rapid succession a very short portion (e.g., the first eight milliseconds) of six of the same guitar string tones used for the sustaining chords. Alternately, when the auxiliary device is in its first state, a strum key state change may result in no audio sound or tone at all.

When the auxiliary device is in its second state, a strum key state change from first to second state causes the data processing system to command the tone generating device to produce an ascending arpeggio of the corresponding predetermined chord; and a reverse state change (i.e., from second to first state) of the same strum key results in a descending arpeggio of the same chord. The tone generating device is allowed to continue sustaining the chord until (a) the auxiliary device is returned to its first state, at which time the chord is terminated; or (b) a second strum key state change is performed, at which time the chord is terminated and the predetermined chord corresponding with the second state change is initiated. If this second strum key state change is the reverse state change of the same key, the new chord is identical to the first chord, with the arpeggiation direction reversed.

When applied to a conventional keyboard, this method enjoys an advantage over the Multiple Trigger Pairs Method: Since only one octave is required for one type of chord, more chord types may be provided in a single keyboard without a patch change.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a general overview of electronic systems/hardware and recommended keyboard which may be used to realize the invention.

FIG. 2 shows an overview of the software program used in the preferred embodiment.

FIGS. 3-14 detail various program subroutines which are used in the preferred embodiment. Subroutines which require two drawing figures are split into two parts--a & b, for example, 14a & 14b.

FIG. 15 shows a cutaway side view of a front guide pin and bushing recommended for the keyboard of the preferred embodiment.

FIGS. 16A-D show various views of a rear guide pin and bushing recommended for the keyboard of the preferred embodiment. FIG. 16A is an exploded view, FIG. 16B is an overhead view with key not shown, FIG. 16C is cutaway rear view taken along line XVI-C of FIG. 16B, and FIG. 16D is a cutaway side view taken along line XVI-D of FIG. 16B.

ORIENTATION TERMS AND CLARIFICATIONS

In this specification and appended claims orientation terms are based on the orientation of a musician as most commonly positioned at a piano keyboard; thus:

The longitudinal axis is that which extends from the bass, or left end of the keyboard to the right, or treble end.

The lateral or transverse axis is that which extends from the front to the rear of the keyboard.

The vertical axis refers to the key axis of motion.

In this specification and appended claims, a statement that a key is "depressed" or "down" means that a key is moved from rest to depressed position. Depressed position does not necessarily refer to the absolute bottom end of key travel. Rather, this term refers to any depth of key depression which is beyond the threshold at which the key state sensing system interprets the key to be in depressed position. For example, this threshold may occur at 2/3 down from rest position. Likewise, rest position is any position above a predetermined rest position threshold; for example, the upper 1/3 of key travel. For example, an embodiment which is well within the scope of the 2nd aspect of the invention would be one in which when a first key is held down as a second key is depressed, the first tone is muted as the second key reaches 1/3 of its downward stroke, and the second tone is initiated when the second key reaches 2/3 of its downward stroke.

The term "key row" refers to a row of keys which extend substantially from left to right. Key rows within a keyboard according to the present invention are not necessarily precisely parallel to the left-right keyboard axis. For example, a keyboard with angled rows (e.g., the Uniscala Keyboard shown in Keyboard magazine, June 1995) may be adapted to utilize the present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENT

I. Overview

The preferred embodiment of the invention is a five-row Janko controller keyboard with independent keys. Various aspects and embodiments of this keyboard are described in the applicant's prior patents, U.S. Pat. No. 5,185,490 (Key Guide) and U.S. Pat. No. 5,469,772 (Linearly Reciprocating Keyboard Key Incorporating Two Guide Pins), and copending applications Ser. Nos. 08/173,855, now U.S. Pat. No. 5,515,763 (Tactile Key Tops), and 08/345,067, now U.S. Pat. No. 5,505,115 (Keyboard Key Return and Motion Sensing Mechanisms Incorporating a Swing Arm). These prior specifications are hereby incorporated by reference.

With guidance from these prior specifications and the present specification, a person of ordinary skill in the art may engineer a keyboard with the necessary features to implement the preferred embodiment of the present invention. Referring to FIG. 1, these features include:

(1) a keyboard 25 (A portion of a 5-level Janko keyboard is shown with an example of two keys 27 which occupy the same position on the X axis and which may be used as a strum trigger keys pair.);

(2) a key state sensing system (including key position/velocity/pressure sensors 28 and a system to scan these sensors 30) which can, for each key of the keyboard 25, sense downward/upward velocity and at least 16 levels of aftertouch pressure;

(3) at least two foot pedals 35 each with sensors capable of measuring downward/upward pedal velocity (The pedal unit sold with the Ensoniq SDP-1 keyboard may be employed. This pedal includes two pedals each with a contact spring which alternates between upper and lower stationary contact wires. Transit time between these two contacts may be measured and pedal velocity may thus be calculated. Alternately, a pedal employing a photointerrupter sensor may be employed. Such a pedal may be monitored by one of the key sensing daughter microcontrollers shown in applicant's copending application Ser. No. 08/345,067, now U.S. Pat. No. 5,505,115, for Keyboard Key Return and Motion Sensing Mechanisms Incorporating a Swing Arm.);

(3) a microprocessor-controlled computer system 36 (including a central processing unit 37, a random-access memory 38, and a read-only memory 39) which can process information received from the key state sensors and other input devices;

(4) a control panel including various switches 40 to perform various control duties including (a) assisting in programming of the keyboard by the user, and (b) implementing control and configuration patch changes during performance;

(5) a panel scanning circuit 41 for reading control panel key state information;

(6) a panel LED circuit 41a for informing the user of which configuration patch is currently called up and for prompting the user during the programming process;

(7) a floppy-disk drive 42 or other transferrable memory storage media for loading the keyboard operating system and patches;

(8) at least two control wheels 43 for control of parameters such as MIDI channel pitch or modulation; and

(9) at least one data input/output port 45 which can transmit processed information to a sound-producing module via MIDI, ZIPI, or both. This processed information includes note-on/velocity commands, note-off/velocity commands, and aftertouch pressure. The MIDI standardized serial protocol is well-known within the industry. Information regarding the ZIPI protocol is available from CNMAT at the Dept. of Music, University of California, Berkeley. Besides operating a tone generating module 50, the MIDI/ZIPI port also serves to allow the keyboard to receive information during performance (such as, e.g., patch changes) from another source. A small microprocessor (not shown) may be provided, dedicated to the task of sending out MIDI and/or ZIPI data.

Several references are made in the following description to the MIDI standard protocol. These references are not intended to limit the preferred embodiment or the invention itself to MIDI. An electronic/software engineer of ordinary skill in the art possessing a working knowledge of MIDI and ZIPI should encounter no difficulty in translating the MIDI terms/elements following in this specification to ZIPI. The essence of the software shown in the drawing figures and described below may remain unchanged.

II. Summary of User-programmable Features and User-programming Process

After initialization, the keyboard defaults into play mode with configuration patch #1 called up. A patch (i.e., a configuration patch) is a pre-programmed configuration of key functions. The keyboard memory is capable of storing a plurality of patches for recall (one at a time) by the user. In play mode, patch changes may be implemented and the user is also presented with the option of entering Program Mode--a menu-driven process for programming or editing patches. The software program for this process is not central to the present invention, and thus will not be described in precise detail in this specification.

Upon entering Program Mode, the user is prompted via a panel display screen 55 to select a preexisting patch to edit or to start from scratch.

The user is then prompted to define a zone, if desired. A zone is defined as all the keys within a given width on the X (left-right) axis. Keys of the same set are always in the same zone. A zone may be as small as one key set or may include the entire keyboard. A Sub-zone is one row for a selected X-axis width. A Sub-zone may be as small as one key or as large as one key row.

Zones serve two functions: They speed the programming process by automatically assigning MIDI note/channel output destinations to the keys within based on user-selected parameters. If a zone is defined as being wider than one key, adjacent keys of the zone always have destinations one semitone apart in the same MIDI channel(s). The other function of zones is to define keys which repeat or sustain with each other.

(As explained in this application's parent application, Ser. No. 08/512,547, now U.S. Pat. No. 5,648,630, a set of two or more keys "sustain with" each other when depression of a first key produces a tone which sustains without interruption as long as at least any one key of the same set is in depressed position. A set of two or more keys "repeat with" each other when depression of a key as a previously depressed key of the same set is held down causes the tone of the previously depressed key to mute and another tone corresponding with the newly depressed key to trigger.)

The user may program a zone as one of 8 types:

1. Basic Sustain: Keys of the same set trigger the same notes and sustain with each other. This type of zone corresponds in function with a standard Janko Keyboard.

2. Sub-zones Sustain: Keys of the same set trigger different notes and sustain with each other.

3. Basic Repetition: Keys of the same set trigger the same notes and repeat with each other.

4. Sub-zones Repetition: Keys of the same set trigger different notes and repeat with each other.

5. Sub-zones Independent: All keys of the zone operate independently. Each key triggers one or more MIDI destinations simultaneously (i.e. depression of a key does not produce a "strum", or arpeggiation).

For each of the above five zone types, the user is prompted to select poly or mono aftertouch and to determine whether any of the pedals will perform functions effecting the zone such as sustain or sostenuto.

The keyboard also incorporates several "guitar modes" for simulating strummed guitar sounds. For these modes, three zone types are provided:

6. Single-Key Strumming-Strum Mode 5 (Strum Modes 1-4 will be discussed below): This strum mode corresponds with the Multiple Trigger Key Pairs Method discussed in the Summary section above. In Strum Mode 5, the top row keys default to do nothing. Patch change or other functions may be assigned to these keys later. For example, top row keys one tritone apart (e.g., all C's & F#'s in the entire row) may be assigned to strum click samples and the other top row keys may be assigned to change patches to select different chord types (e.g., major 7th).

Keys of the same set in rows 1 & 3 or 2 & 4 trigger "strums" (arpeggiations) of the same notes. Rows one & two produce downstrums (ascending arpeggiations). Rows three & four produce upstrums (descending arpeggiations). The reason the directions are reversed is that a guitar is generally tuned and positioned such that a downstrum produces an ascending arpeggiation of notes and an upstrum produces a descending arpeggiation.

The output velocities (generally output volumes) of the strummed notes are determined by the downward velocities of the keys; and the arpeggiation rate is determined by the elapsed time between successive key depressions. In this regard, Single Key Strumming operates like Strum Mode 3 discussed below.

When this type of zone is selected during the user-programming process, the user is prompted to select the strum destination notes (e.g., the six notes of the guitar chord) for each key set within the zone. For example, the two keys corresponding with middle C in rows 1 & 3 may be programmed to strum the standard open tuning of a C major chord on a guitar; the two adjacent keys corresponding with D may be programmed to strum the standard open tuning of a D major chord, and so on.

To avoid control logic problems, all keys within a Single-key Strumming zone repeat with each other. This function is implemented as follows: If a key is depressed as another key is held down and the previously depressed key is the partner of the new key, (i.e., if the old & new keys are in the same set and programmed to trigger the same notes) notes are muted one at a time, just prior to being re-struck. If the previously depressed key is another key of the same Single-Key-Strumming (SKS) zone, the notes corresponding with the old key are muted at once, just prior to the new strum.

If, during the programming process, some keys of the SKS zone (other than in row 5) are left undefined & without destination notes, the user is informed of this fact before exit.

No choice between poly or mono aftertouch in an SKS zone is offered to the user since only one key is active at one time; the question is therefore moot. Poly aftertouch is automatically selected. Poly aftertouch data is sent to the sound module, which processes this data according to its own programming. No Click+Tone feature (discussed below) is offered in Single-Key Strumming.

Two zone types are provided for manually selecting notes to be strummed in real time during performance in Strum Modes 1-4. Triggering of the notes selected in these zones is accomplished by movement of other keys (called "Strum Trigger Keys") on the keyboard which are discussed below. The two strum note select zone types are:

7. Single Note Select: Depression of a single key in this zone type selects a single note to be strummed. Generally, a typical user will depress a group of approx. four or five keys (forming a chord) at a time within a note select zone.

8. Click+Tone Select: A predetermined aftertouch threshold, referred to hereinafter as the "primary note threshold", is established for keys within this zone type. In this mode, each note select key toggles between two output note/MIDI channel destinations based on whether the key is depressed below or above this threshold. The two destinations are referred to as the "alternate" and "primary" destinations and are user-programmable. They may be different notes within the same channel, the same notes in different channels, or different notes in different channels. A recommended implementation has the low-pressure alternate destination corresponding with "click" sounds only, and the deeper (heavier-pressure) primary destination corresponding with the same "click" sounds plus sustaining tones. This implementation duplicates the left-hand strumming response on a guitar.

Zone types 7 or 8 may include sub-zones. One type of note-select sub-zone configuration which may be valuable to the user would be one in which the keys within two rows (within the zone) would be programmed to select notes one octave higher than their set partners. With this configuration, one hand may reach a wider musical interval. A chord stretched over this wider interval could perhaps more closely resemble a typical guitar chord voicing.

If either of the Basic zones or Note Select zones are selected, the user is prompted to define the destinations for the zone. If Sub-zones are selected, the user is prompted to define the destinations for row one, then row 2, etc. For a Note Select zone, after the destinations are defined, the user is prompted to select the strum trigger key(s) & one of Strum Modes 1-4. Keys may be programmed as doing nothing (by default). This option serves two functions:

1. It saves time in case the user desires no function for these keys (e.g., the user may wish to rest his/her hand on keys adjacent strum trigger keys); and

2. It leaves them open for use later use as patch control, strum trigger or independent control keys (functionally identical to Zone type 5 keys) without the user being prompted to confirm.

Just prior to recording a patch (exit), the user is asked whether any patch control keys are desired in the patch. If so, the user is asked to enter (1) the patch number to be called up, and (2) the key or foot pedal which will call up the patch. If any zones are programmed as Note Select, the user is also prompted to select the corresponding strum trigger key(s) (one at a time) and decide which trigger key type they will be. Double-key trigger key pairs (Single Key Strumming and modes 3 & 4 below) always operate as in repetition mode. Defining a key as a strum trigger key overrides the previous assignment for the key.

Just prior to exit the user is also given the opportunity to program individual keys which do not repeat or sustain with other keys (they may, however, sustain with the sustain pedal). These keys are identical in function to Zone type 5 keys and hereinafter will be regarded as Zone type 5 keys regardless of whether they were programmed as part of a type 5 zone or were programmed independently.

The user is then prompted to determine whether either of the control wheels will perform functions such as pitch or modulation, and on which MIDI channel. Upon exiting, the user is asked to select a patch number and title. If a patch already exists with that number, the user is prompted to confirm overwrite. The preexisting title defaults as the new title unless a new title is entered.

When a note select zone type 7 or 8 is defined, i.e., programmed, one or two corresponding strum trigger keys must also be defined (during programming mode) and used during performance to trigger strums of the notes selected in the note select zone.

The user may select one of four strum trigger key types corresponding with four Strum Modes. Modes 1 and 2 correspond with the Single Trigger Method described in the Summary section above. Modes 3 and 4 correspond with the Double Trigger Method also described in the Summary section above.

The four Strum Modes which employ trigger keys and separate note select keys are:

Mode 1 (Single key or single foot pedal trigger):

Trigger key downstrokes trigger downstrums, or ascending arpeggiations. Trigger key upstrokes trigger upstrums, or descending arpeggiations. As mentioned above, the reason the directions are reversed is that a guitar is generally tuned and positioned such that a downstrum produces an ascending arpeggiation of notes and an upstrum produces a descending arpeggiation.

Elapsed time between trigger key down & up strokes determines arpeggiation rate (arpeggiation rate is the time between successive triggerings of notes within an up or down strum). The arpeggiation rate is proportional to the time between down & up strokes. Elapsed times greater than 400 milliseconds are interpreted as pauses between strums. The first arpeggiation rate of a performance is arbitrary and pre-programmed in the software.

Up/down stroke velocity of the trigger key (or foot pedal) determines output velocities (generally loudness) of selected strum notes. Thus, the same velocity value is sent to the sound module for all notes within a strum.

Muting of notes (note-off commands sent to sound module) are triggered by release of the note select keys (i.e., when the keys are raised above 1/3 from rest position). Release of individual keys trigger mutings of the corresponding notes; thus, notes may be muted individually and independently. In "note+click" mode, notes are muted when corresponding keys are lifted above the "click" aftertouch threshold.

Mode 2 (also single key or single foot pedal trigger):

As with mode 1, trigger key downstrokes trigger downstrums, or ascending arpeggiations; and trigger key upstrokes trigger upstrums, or descending arpeggiations.

Up/down stroke velocity of the trigger key (or foot pedal) determines arpeggiation rate. Faster trigger key velocities produce faster arpeggiation rates.

After-touch pressure of selected keys in the corresponding note-select zone determines output velocities. The user may program this pressure response as mono or poly-pressure:

In mono mode, the pressures of all selected keys within the note select zone are averaged when the trigger key (or pedal) is stroked; this average value is used to calculate a single output velocity which is assigned to all the selected notes for that stroke.

In poly mode, when the trigger key/pedal is stroked, the output velocity of each selected note is calculated independently based on the aftertouch value of its corresponding note select key.

The user is prompted to select between mono or poly mode when programming the trigger key.

If "note+click" mode is used, clicks (the user-defined destinations above the pre-determined aftertouch threshold) always have the same output velocity.

Muting of notes is processed as in Mode 1.

Mode 3 (double key or double foot pedal trigger):

Exactly two trigger keys (or foot pedals) are paired as in Sub-zones Repetition Mode; except that instead of simply triggering individual notes, the key/pedal pairs trigger strums of notes selected in the corresponding note select zone. One trigger key/pedal triggers an up-strum. The other triggers a down-strum.

Arpeggiation rate is determined as in Mode 1 except that all triggering key strokes are downstrokes. The occurrence time of trigger key upstrokes are not recorded, since elapsed times from trigger key upstrokes to other events (including other trigger key upstrokes) are not used to calculate anything. Upstrokes of either of the two trigger keys do not trigger strums and are processed as in Sub-zones Repetition Mode.

When at least one trigger key is held down, muting of notes is processed as in Mode 1. However, muting of all selected notes may be accomplished via release of both trigger keys. In other words, in order for a note to sustain, its corresponding note select key and at least one corresponding trigger key must be in depressed position.

Output velocities of selected notes are determined as in Mode 1 except that all triggering key strokes are downstrokes. In other words, output velocities are proportional to trigger key downstroke velocities.

Mode 4 (also double key or double foot pedal trigger):

Exactly two trigger keys/pedals are paired as in Mode 3. Down stroke velocities of trigger keys/pedals determine arpeggiation rates. Output velocities are determined as in Mode 2 (user selects mono or poly pressure sensing). Muting of notes is processed as in Mode 3.

No choice between poly or mono aftertouch for Mode 3 or 4 trigger keys is offered to the user since only one key is active at one time; the question is therefore moot. Poly aftertouch is automatically selected. Poly aftertouch data is sent to the sound module, which processes this data according to its own programming.

During the patch program process, the user always has the option of pressing a soft key (on the control panel) labeled "Check it Out" which implements the patch as written so far. To exit "Check it Out" mode, the user presses the same soft key again and resumes programming where he/she left off.

There are two other possible strum modes which may be incorporated for use with the invention. Flow charts for these modes are not provided in this specification. Nevertheless, a person of ordinary skill in the art may easily create flowcharts for these modes with guidance from this specification and drawing figures. The first of these two other possible strum modes is a combination of strum modes 1 and 2 in which elapsed time between down & up strokes of a single trigger key determines arpeggiation rate and aftertouch pressure of selected keys in the corresponding note-select zone determines output velocities. The second other strum mode is a combination of strum modes 3 and 4 in which elapsed time between down strokes of two trigger keys determines arpeggiation rate and aftertouch pressure of selected keys in the corresponding note-select zone determines output velocities.

III. Performance Operating Software

The preferred embodiment incorporates the key sensing system shown in FIG. 12 of copending U.S. patent application Ser. No. 08/345,067, now U.S. Pat. No. 5,505,115, (Keyboard Key Return and Motion Sensing Mechanisms Incorporating a Swing Arm). This key sensing system incorporates ten circuit boards, each sensing the states of 20 (or 19) keys. Each of these circuit boards includes a "daughter" microcontroller which sends key state information to a master microprocessor. This information includes key position (rest or depressed) and elapsed time as a key transits between 1/3 & 2/3 of key travel (when moving up or down). From this elapsed time the master processor can calculate key velocity. To sense aftertouch pressure of a depressed key, the master processor instructs that key's daughter controller to multiplex the key position sensor phototransistor output corresponding with that key to an analog/digital (A/D) bus. The master processor then performs an A/D conversion of the output.

A table of key states in RAM 38 is used to define key behaviors and to record the current state of the keyboard. Each key and pedal has a corresponding data location or "pigeonhole" in the table. Each of these pigeonholes contains information regarding several parameters which define and record key behaviors. When a new and different configuration patch is loaded, at least some of the information in at least some of the pigeonholes is changed and the keys are thus redefined.

The following are types of key defining information which are loaded into the pigeonholes with patch changes:

1. What type of action occurs when a key is moved (which type of zone the key is contained within, whether the key is a strum trigger key, etc.). This information is stored as a number referring to a key "Typecode". Fifteen typecodes are discussed below.

2. Which MIDI channel/note destinations are associated with the key. A pigeonhole for a key of any of the eight zone types listed above includes a list of one to six MIDI note/channel destinations. The manner in which these destinations are triggered or muted depends on which type of action occurs when the key is moved. For example, a Basic Repetition key may have two destinations which will sound simultaneously when the key is struck. A Single Key Strumming (SKS) (Strum Mode 5) key will trigger up to six destinations in an arpeggiated sequence. The pigeonhole for an SKS key in row 1 or 2 includes a series of destinations arranged in an ascending sequence. The pigeonhole for an SKS key in row 3 or 4 includes a series of destinations arranged in a descending sequence. A key in a Note+Click note select zone (zone type 8) will trigger either of two destinations depending on whether the key is depressed beyond a given aftertouch threshold. The destination triggered when the aftertouch pressure being exerted on the key is above the threshold (typically a sustaining tone) is referred to as the "primary" destination. The destination triggered when the pressure is below the threshold (typically a "click" sound) is referred to as the "alternate" destination.

3. Whether one of the pedals serves as a sustain pedal for the key and if so, which one;

4. For keys in zone types 1-4, whether the key is one of a group of keys for which monophonic aftertouch data is to be sent, i.e., whether the key corresponds with one of the Aftertouch Register subsets described below;

5. For keys in zone types 1-4, which Set Register (see below) is associated with the key;

6. For keys in zone types 7 & 8, which Downkey Register (see below) is associated with the key;

7. For keys in zone type 6, which SKS Register (see below) is associated with the key;

8. For each Zone Type 6 key, each trigger key in Strum Mode 1, and each trigger key pair in Strum Mode 3, which "Longtime" data item (see below) corresponds with the key.

Each key pigeonhole also contains key state and key performance information which is updated as events occur. This information includes whether the key is in rest or depressed position, whether a patch change is pending, the velocity of the key's last stroke, when the last stroke occurred, and aftertouch pressure of the key. Also, a key in a Note+Click note select zone (zone type 8) may contain a notation that the alternate destination is currently sustaining.

The table of key states also includes a Set Register for each key set (in Zones 1-4) and for each trigger key pair in Strum Modes 3 & 4. This register includes an "A" data item, or "A" entry, which identifies a key of the set which has its corresponding destination sustaining; and a "B" data item which indicates that two keys of the set are in down position. The "A" data item contains a notation which indicates whether the destination is sustaining because a key of the set is depressed or because a corresponding sustain pedal is depressed. When two keys are programmed as strum triggering keys in modes 3 or 4 a Set Register is created for the two keys regardless of whether they are physically located at the same position on the X (left-right) axis of the keyboard. The Set Register for Mode 3 trigger keys pairs includes a "C" data item which includes a time of prior key depression to determine elapsed time between key strikings. Each Set Register also includes a notation specifying whether the keys contained in its set sustain or repeat with each other. This notation is loaded into the register when patch changes are implemented.

Each Zone type 5 key pigeonhole also contains an "A" data item which serves the same function as a set register "A" data item insofar as it indicates whether the key's destination is sustaining because a corresponding sustain pedal is down.

The table of key states also includes an SKS Register for each Single Key Strumming zone (Zone type 6; Strum Mode 5) which includes an "A" data item which identifies the key whose destinations are currently sustaining; a "B" data item which indicates that two keys within the zone are in depressed position; and a "C" data item which is used only to determine elapsed time between successive key strikings when an active key is depressed as no other keys of the zone are in depressed position. The "A" and "C" data items include a record of when the associated keys were struck (to determine elapsed time between strikings).

The table of key states also includes a Sustain Pedal Register which lists keys which have been sounded and released as the corresponding pedal is in depressed position.

The table of key states also includes a Downkey Register for each note select zone (zone type 7 or 8) which keeps track of which keys in the zone are depressed.

The table of key states also includes an Aftertouch Register which maintains a list of depressed keys for which it is desired that aftertouch pressure is to be measured. Depressed keys which are located within a zone for which the user has selected monophonic aftertouch are placed within a subset within the register headed by an ID number for the zone. Also included within each of these subsets is the destination (e.g., MIDI channel) for the zone's monophonic aftertouch data. The keyboard may, at one time (configured according to one patch), include several monophonic aftertouch zones and thus, several subsets within the Aftertouch Register. The register may also contain one or more subsets headed "Note Select", each of which includes depressed keys within a Note Select zone. Although aftertouch pressure is measured for these keys, no corresponding aftertouch message is sent to the sound module. Rather, the aftertouch values are used to determine whether Note+Click keys are below the "Click" threshold (for Zone 8 keys) and to determine output velocity (for Strum Modes 2 & 4). The monophonic zone subset headings and the Note Select Zone subset headings are entered into the Aftertouch Register when a patch is called and remain in the Register until a new patch is called, regardless of whether any keys are down. Also included in the Aftertouch Register is a record of when the Aftertouch Subroutine was last entered.

The table of key states also includes a data item called "Longtime" corresponding with each Zone Type 6 (Single Key Strumming, i.e., Strum Mode 5), each trigger key in Strum Mode 1, and each trigger key pair in Strum Mode 3. Elapsed time between triggering key movements are recorded in Longtime. When the configuration patch is first loaded, a predetermined value of 250 milliseconds (a typical average elapsed time between guitar strums) is automatically entered in Longtime. This value is continually updated as the user triggers strums more frequently than one per 400 Milliseconds.

The table of key states also includes a data item called "Newpatch" which contains the number of the patch most recently selected by the user.

Referring now to FIG. 2 of the present specification, when the keyboard is first turned on the operating software program begins with an initialization process 60. This process includes loading the relevant contents of the floppy disk into RAM. These contents include the keyboard operating system and at least one configuration patch. The internal time clock is set to zero and begins an ascending count. This clock measures time in very precise units (e.g. one microsecond) in bytes with a sufficient number of bits so that no turnover will occur during a typical performance. Thus, the time at which key movement events occur may be recorded with great precision and elapsed time between events may be precisely measured as well.

In the next step 65 patch #1 is then called up and the keys of the keyboard are configured to respond accordingly.

In the next step 70, the master processor checks whether a new key state change signal has been received from one of the daughter key sense circuit boards. If not, the control panel switches 40 (see FIG. 1), pitch/mod wheels 43, foot pedals 35, & MIDI input port(s) 45 are scanned for new activity in step 73. Where new activity is found, the CPU responds accordingly. The aftertouch subroutine is then performed in step 75. Step 70 is then returned to. If a new key state signal is received, the Keyprocessor Subroutine 80 is again performed.

Referring now to FIG. 3 of the present specification, the Keyprocessor Subroutine first calculates the number of the active key as the number of the key's daughter sense board times the maximum number of keys on the sense board (e.g., 19) plus the key's location on the board (e.g., 5th key from the left) in step 85. The new position of the active key (up or down), the velocity of the key's last stroke (calculated as an inverse function of transit time between 1/3 & 2/3 points), and the time this stroke occurred are then entered into the key's pigeonhole in step 90. The pigeonhole includes a two-position shift register for recording stroke occurrence time. The most recent stroke time is recorded in the first position, and the prior stroke time is recorded in the second position. Time of prior stroke is required to carry out step 190 (see FIG. 6). If and when a note-on command is sent for the destinations listed in the pigeonhole, the velocity component of this command is taken from the velocity value in the pigeonhole which was recorded in step 90. The subroutine then determines the Typecode of the active key and calls the corresponding subroutine.

If the active key is in a Zone #1-5 and not programmed as a patch change or strum trigger key, then that key is a Typecode 1 key. The Typecode 1 Subroutine is called in step 95 and is shown in FIG. 4. In the first step 100, the subroutine determines whether the active key has just moved down or up based on the signal received from the daughter sense circuit board. If the new position is down (depressed) the active key's pigeonhole is checked in step 102 to determine whether the key is part of a monophonic aftertouch zone. If not, the key's ID number is entered into the Aftertouch Register in its own independent category in step 103 so that polyphonic aftertouch data may be sent for the key at a future time. If the active key is part of a monophonic aftertouch zone, the key's ID number is entered into the Aftertouch Register as part of a subset under the heading of the zone ID number found in the key's pigeonhole in step 104. The next step 106 determines whether the "A" data item associated with the active key (in the corresponding Set Register if the key is a Zone type 1-4 key or in the key's pigeonhole if the key is a Zone type 5 key) includes a notation that a destination associated with the key is sustaining because a corresponding sustain pedal is down. If so, a note-off command is sent for that destination in step 107. This note-off command is sent because the same destination may be triggered again in step 112. The pigeonhole of the key shown in "A" is then checked for a notation that a patch change is pending in step 107A. If so, the pigeonhole is then cleared and reloaded according to the patch shown in "Newpatch" in step 107B. In step 107B and other "reload the pigeonhole" steps, e.g., 123B, 184, etc., the data item which notes that a patch change is pending is removed as the pigeonhole is cleared and reloaded. The "A" key is then erased from the Sustain Pedal Register in step 108. Thus, if the user releases the sustain pedal while holding the key, the note will not mute. The logic of this subroutine (see steps 133, 134, 135, 138, 132) is such that the Set Register shows that "A" is sustaining due to the sustain pedal only if no other keys of the set are down. If "A" shows that the pedal is not sustaining a corresponding destination, the pigeonhole for the active key is checked in step 109 to determine whether the key repeats or sustains with any other keys. If it does not (e.g., if the key is a Sub-zones Independent Zone 5 key), then a note-on command is sent in the next step 110 to the destination(s) corresponding with the active key. The velocity component of this command is taken from the active key's pigeonhole as recorded in step 90. If the active key does have at least one rep/sus partner, the next step 111 checks the Set Register for the active key's set to see if there is a key number entered in the "A" position, i.e., to see if another key within the set is in depressed position. If not, a note-on command is sent for the active key in step 112. The "A" data item is then cleared in step 113 and the identity of the active key is recorded in "A" in the next step 114.

If the active key does have a partner in depressed position, the next step 120 consults the active key's Set Register to determine whether the keys of the register repeat or sustain with each other. If they repeat, a note-off command is sent for the sustaining note (destination in the pigeonhole of the "A" key) in step 123. The pigeonhole of the key shown in "A" is then checked for a notation that a patch change is pending in step 123A. If so, the pigeonhole is then cleared and reloaded according to the patch shown in "Newpatch" in step 123B. A note-on command is then sent for the active key in step 124. In the next step 125 the key ID number from the "A" data item is moved to the "B" data item. The active key number is then placed in "A" in step 114. If it is determined in step 120 that the set of keys sustain with each other, an entry is placed in "B" in step 126.

Referring now to FIG. 4b, if the new position of the active key is up, the active key's ID number is removed from the Aftertouch Register in step 126A. The next step 127 determines whether the active key repeats or sustains with any other keys. If not, it is determined in step 128 whether the active key has a corresponding sustain pedal. If so, that pedal's pigeonhole is checked in step 129 to determine whether that pedal is down. If not, a note-off command is sent for the active key's destination(s) in step 130. The pigeonhole of the active key is then checked for a notation that a patch change is pending in step 130a. If so, the pigeonhole is then cleared and reloaded according to the patch shown in "Newpatch" in step 130b. If the pedal is down, the identity of the active key is entered in the sustain pedal's Register in step 131. An "A" notation is then made in the active key's pigeonhole to specify that the key's destination(s) are sustaining because the pedal is down in step 132.

If the active key does have one or more repetition/sustain partners, the "B" data item of the active key's set register is checked in step 133 to determine whether another key of the set is in depressed position. If not, the active key's pigeonhole is checked in step 134 to determine whether one of the pedals is programmed as a sustain pedal for the active key. If so, the pigeonhole for the corresponding pedal is checked to see whether the pedal is down in step 135. If there is no corresponding depressed pedal, a note-off command is sent for the note corresponding to the key in "A" in step 136. The pigeonhole of the key shown in "A" is then checked for a notation that a patch change is pending in step 136A. If so, the pigeonhole is then cleared and reloaded according to the patch shown in "Newpatch" in step 136B. The "A" data item is then cleared in step 137. If the pedal is down, the key number in the set register "A" position is copied into the sustain pedal register in step 138. A notation is then made in the active key's Set Register "A" data item to specify that the key's destination(s) are sustaining because the pedal is down in step 132. Referring back to step 133, if the "B" data item indicates that another key of the set is down, the "B" data item is cleared in step 139, and no note-off command is sent. When the subroutine is exited in step 140, step 70 (see FIG. 2) is called once again.

Referring again to FIG. 3, if the active key is used to select notes to be strummed (zone 7 or 8) then that key is a Typecode 2 or 3 key. Single Note Select keys are Typecode 2; Click+Note select keys are Typecode 3. The Subroutine for these keys is called in step 150 and is shown in FIG. 5. In the first step 160 the new position of the active key is determined from information received from the daughter sense board. If the active key has just moved down, the identity of the active key is entered into the corresponding Downkey Register and into the Aftertouch Register in step 165. The keys recorded in the Downkey Register are organized in a sequence of ascending MIDI note numbers. If the active key has just been released, the active key is removed from the Downkey Register and from the Aftertouch Register in step 170. Then, in step 175, the Downkey Register is compacted so that the last key at the end of the register can be easily located. The active key's pigeonhole is then checked in step 176 to determine whether the alternate destination (typically a "click" sound) is sustaining. If the active key is a Typecode 2 key, then there is no alternate destination, and step 177 is called. If the active key is a Typecode 3 key without a notation that the alternate destination is sustaining, then step 177 is also called. In step 177, a note-off command is sent for the primary destination. If it is determined in step 176 that the key is a Typecode 3 key with its alternate destination sustaining, a note-off command is sent for the alternate destination corresponding with the active key in step 179. The notation indicating that the alternate destination is sustaining is then removed from the active key's pigeonhole in step 180. The pigeonhole of the active key is then checked for a notation that a patch change is pending in step 182. If so, the pigeonhole is then cleared and reloaded according to the patch shown in "Newpatch" in step 184.

Referring again to FIG. 3, if the active key is used to trigger strums in Strum Mode 1, then that key is a Typecode 4 key. The Strum Mode 1 Triggering Key Subroutine is called in step 185 and is shown in FIG. 6. In the first step 190 the pigeonhole of the active key is checked to see when the key was last moved (from down to up or from up to down) and elapsed time from then to present is determined. Then, in step 196, it is determined whether the elapsed time since last movement is more than 400 milliseconds. In this strum mode, (and in Strum Mode 3 as well) pauses between trigger key movements of more than 400 milliseconds are interpreted as pauses between strums. If the elapsed time is less than 400 ms, then it is recorded in Longtime in step 197, erasing the previous Longtime value. An arpeggiation rate is then calculated in step 198 as a function of the "Longtime" value. In the next step 199 the Downkey Register of the corresponding note select zone is checked to determine whether any note select keys are in depressed position. If not, the subroutine is exited.

In an alternate embodiment, not shown, step 199 may be eliminated. Instead of having an empty Downkey Register when no note select keys are down, a predetermined list of six default destinations may be provided. Note-on commands sent to these destinations would produce "click" sounds. These predetermined "click" destinations would be removed, one at a time, as note select keys are depressed; and added, one at a time, as note select keys are released. Thus, movement of the trigger key when no note select keys are down would produce an arpeggiated series of click sounds (a "chucka" sound), as when a guitar player strums the strings with one hand while lightly touching the strings with his other hand. An advantage of this alternate embodiment is that the user would be able to completely lift his fingers from the note select keys and still be able to trigger a "chucka" sound with the trigger key. A primary note aftertouch threshold would be unnecessary. Thus, arm and finger fatigue may be reduced, since the user would not have to press hard on the note select keys to produce sustaining tones. The program steps to implement this function may be incorporated into the Note Select Key Subroutine. With a predetermined number of destinations (e.g., 6) always included in the Downkey Register, step 175 (see FIG. 5) could be eliminated.

In another alternative embodiment, also not shown, instead of recording an elapsed time between key events in "Longtime", an arpeggiation rate may be calculated and stored if the answer to the step 196 question is no. This would eliminate the need to perform the step 198 calculation every time the subroutine is called.

Returning now to the shown embodiment, if it is determined in step 199 that at least one note select key is down, the velocity of the active key (an inverse function of elapsed time between 1/3 & 2/3 points) is then recorded in the pigeonhole of each key listed in the Downkey Register in step 200. It is recommended that the velocity response for upstrokes be pre-programmed with a higher gain than the downstroke response. For example, while a 1/3-2/3 downstroke transit time of 16 milliseconds may produce a MIDI velocity value of 60, a 2/3-1/3 upstroke transit time of 16 ms might produce a MIDI velocity value of 100. The reason for this recommended higher gain for upstrokes is that a user will generally be able to move a key faster on a downstroke than on an upstroke.

In the next step 204 it is determined whether the active key has just moved up or down. If it is down, the Strum Subroutine is called in step 208 with the arpeggiation rate determined by the value in Longtime and the strum direction as up. If the active key has just moved up, the Strum Subroutine is called in step 210 with the arpeggiation rate determined by the value in Longtime and the strum direction as down.

Referring again to FIG. 3, if the active key is used to trigger strums in Strum Mode 2, then that key is a Typecode 5 or 6 key. Typecode 5 keys trigger mono mode strums, i,e, output velocities are calculated based on averaged aftertouch pressure in the note select zone. Typecode 6 keys trigger poly mode strums. The Subroutine for these keys is called in step 218 and is shown in FIG. 7. In the first step 228 the Downkey Register of the corresponding note select zone is checked to determine whether any note select keys are in depressed position. If so, it is determined whether the active key is a Typecode 5 or 6 key in step 230. If it is a Typecode 6 key, the last recorded aftertouch value of each depressed note select key is used to determine the velocity value for that key in step 235. If the active key is a Typecode 5 key, the aftertouch pressure of the keys listed in the Downkey Register is averaged in step 240. This value is used to determine a single velocity value which is placed in the pigeonhole of each depressed note select key in step 245. An arpeggiation rate is then calculated based on the velocity of the active key in step 248. In the next step 251 the direction of the active key is determined. If the key just moved up, the Strum Subroutine is called in step 253 with the arpeggiation rate calculated in step 248 and the strum direction down. If the key just moved down, the Strum Subroutine is called in step 256 with the arpeggiation rate calculated in step 248 and the strum direction up.

Referring again to FIG. 3, if the active key is one of a pair of keys used to trigger strums in Strum Mode 3, then that key is a Typecode 7 or 8 key. The Subroutine for these keys is called in step 263 and is shown in FIG. 8. In the first step 268 the Downkey Register of the corresponding note select zone is checked to determine whether any note select keys are in depressed position. If so, the new position of the active key is determined in step 269. If the active key just moved up, the Set Register for the two trigger keys is checked in step 270 to see if the active key's trigger partner is down. If so, the Set Register "B" data item is cleared in step 271 to indicate that only the partner key is still down. If the partner is up, an index number of one is established to index the first note select key listed in the Downkey Register. In step 274 the pigeonhole of the indexed key is checked to determine whether the key is a Typecode 3 with its alternate destination sustaining. If not, a note-off command is sent for the key's primary destination in step 275. If the key is a Typecode 3 with its alternate destination sustaining, then a note-off command is sent for the key's alternate destination in step 276. The notation indicating that the alternate destination is sustaining is then removed from the key's pigeonhole in step 277. The key's pigeonhole is then checked to determine whether a patch change is pending for the key in step 278 and, if so, the pigeonhole is reloaded according to the patch in "Newpatch" in step 279. It is then determined in step 280 whether steps 274 & 278 (and whichever of steps 275, 276, 277, & 279 are called for) have been performed for all keys in the Downkey Register. If not, the index number is increased by one in step 281 and step 274 is returned to. If so, the "A" data item of the Set Register is then cleared in step 282. The active key's ID number is then removed from the Aftertouch Register in step 284.

If the active key just moved down, the typecode of the key is determined in step 288 (see FIG. 8b). Typecode 7 keys trigger descending arpeggiations; Typecode 8 keys trigger ascending arpeggiations. Typecode 8 keys are positioned in rows one and two of the keyboard (nearest the user) and are generally depressed with the thumb; Typecode 7 keys are positioned in rows 3 and 4. The strum (arpeggiation) direction is set accordingly in step 290 or 291. In the next step 292 the velocity of the active key (elapsed time between 1/3 & 2/3 points) is recorded in the pigeonhole of each key listed in the Downkey Register. Then, in step 293, the existence of an "A" data item in the Set Register is checked to determine whether the active key's trigger partner is down. If not, the active key and present time are recorded in "A" in step 294. The elapsed time between the time of the prior trigger key depression recorded in "C" and the present time recorded in "A" is then determined in step 295. If the partner key is down, the "A" data item including time of the prior trigger key depression is shifted to the "B" position in step 296. The active key and present time are then recorded in "A" in step 297. The elapsed time between the time of the prior trigger key depression recorded in "B" and the present time recorded in "A" is then determined in step 298. Then, in step 299, it is determined whether the elapsed time measured in step 295 or 298 is more than 400 milliseconds. If the elapsed time is less than 400 ms, then it is recorded in Longtime in step 300, erasing the previous Longtime value. An arpeggiation rate is then calculated in step 301 as a function of the "Longtime" value. The active key's ID # is then entered into the Aftertouch Register in step 302. In the next step 303, the Strum Subroutine is called with the arpeggiation rate and direction as determined above. This subroutine offers the user numerous performing options. For example, the user may strike the downstrum trigger key, producing a downstrum, and continue holding the key down while repeatedly striking the upstrum key. Since the downstrum key is being held down, the notes will not mute each time the upstrum key is released. With each up-down cycle of the upstrum key steps 276 and 296 are called. Thus, multiple upstrums may be performed without silent pauses in between. The arpeggiation rate is determined by elapsed time between successive strikings of the upstrum key.

Referring again to FIG. 3, if the active key is one of a pair of keys used to trigger strums in Strum Mode 4, then that key is a Typecode 9, 10, 11 or 12 key. The Subroutine for these keys is called in step 306 and is shown in FIG. 9. In the first step 305 the Downkey Register of the corresponding note select zone is checked to determine whether any note select keys are in depressed position. If so, the new position of the active key is determined in step 307. If the active key just moved up, the Set Register for the two trigger keys is checked in step 308 to see if the active key's trigger partner is down. If so, the Set Register "B" data item is cleared in step 309 to indicate that only the partner key is still down. If the partner is up, an index number of one is established in step 310 to index the first key listed in the Downkey Register. Then, in step 311, the pigeonhole of the indexed key is checked to determine whether the key is a Typecode 3 with its alternate destination sustaining. If not, a note-off command is sent for the key's primary destination in step 312. If the key is a Typecode 3 with its alternate destination sustaining, then a note-off command is sent for the key's alternate destination in step 313. The notation indicating that the alternate destination is sustaining is then removed from the key's pigeonhole in step 314. The key's pigeonhole is then checked to determine whether a patch change is pending for the key in step 315 and, if so, the pigeonhole is reloaded according to the patch in "Newpatch" in step 316. It is then determined in step 317 whether steps 311 & 315 (and whichever of steps 312, 313, 314, & 316 are called for) have been performed for all keys in the Downkey Register. If not, the index number is increased by one in step 318 and step 311 is returned to. If so, the "A" data item of the Set Register is then cleared in step 319. The active key's ID # is then removed from the Aftertouch Register in step 320.

If the active key just moved down, it is determined whether the active key is one of Typecode 9 & 11 or one of Typecode 10 & 12 in step 321 (see FIG. 9b). Typecode 9 & 11 keys trigger mono mode strums, i,e, output velocities are calculated based on averaged aftertouch pressure in the note select zone. Typecode 10 & 12 keys trigger poly mode strums. If the active key is a poly key, the last recorded aftertouch value of each depressed note select key is used to determine the velocity value for that key in step 324. If the active key is a mono key, the aftertouch pressure of the keys listed in the Downkey Register is averaged in step 328. This value is used to determine a single velocity value which is placed in the pigeonhole of each depressed note select key in step 331. An arpeggiation rate is then calculated based on the velocity of the active key in step 332. In the next step 333, the Set Register corresponding with the active key is checked to determine whether the active key's partner is down. If so, the partner key is placed in the "B" position in the Set Register in step 334 to specify that both trigger keys are now down. The active key is then recorded in the "A" position in step 336. The active key's ID # is then entered into the Aftertouch Register in step 337. In the next step 338 it is determined whether the active key is one of Typecode 9 & 10 or one of Typecode 11 & 12. Typecode 9 & 10 keys trigger descending arpeggiations; Typecode 11 & 12 keys trigger ascending arpeggiations. If the key is a 9 or 10, the Strum Subroutine is called in step 341 with the arpeggiation rate calculated in step 332 and the arpeggiation direction down. If the key just moved down, the Strum Subroutine is called in step 344 with the arpeggiation rate calculated in step 332 and the arpeggiation direction up.

Referring again to FIG. 3, if the active key programmed to enact a patch change, then that key is a Typecode 13 key. The Patch Change Subroutine is called in step 360 and shown in FIG. 10. This same subroutine is called when a patch change is initiated by control panel keys in step 73 (see FIG. 2). In the first step 370 it is determined whether the active key has moved up or down. If the key has moved up, the subroutine is exited. If the key has moved down, the new patch number is entered into "newpatch" in step 375. In the next step 380 it is determined whether the present patch (the patch in use prior to the most recent depression of the active key) contains any Set Registers. If so, it is determined in step 385 whether any of the Set Registers contain an "A" data item, i.e., whether a note corresponding with that register is sounding. If so, a notation is made in the pigeonhole of each "A" key that a patch change is pending for that key in step 388.

In the next step 390 it is determined whether the present patch includes any SKS Registers, i.e., whether there are any Single Key Strumming (Strum Mode 5) keys. If so, it is determined in step 394 whether any of the SKS Registers contain any "A" data items, i.e., whether any Single Key Strumming keys are down. If so, a notation is made in the pigeonhole of each "A" key that a patch change is pending for that key in step 399.

In the next step 400 it is determined whether the present patch includes a pedal which is assigned to a sustain function. If so, it is determined in step 405 whether that pedal is down. If so, a notation is made in the pedal's pigeonhole that a patch change is pending in step 407. A notation is then made in the pigeonhole of each key listed in the pedal's register that a patch change is pending in step 408.

In the next step 411 it is determined whether the present patch includes any Downkey Registers, i.e., whether the present patch includes any note select zones. If so, the Downkey Register is checked in step 414 to determine whether any note select keys are down. If so, a notation is made in the pigeonhole of each key listed in the Downkey Register that a patch change is pending in step 418.

In the next step 422 it is determined whether the present patch includes any Typecode 1 keys which have no repetition or sustain partners, i.e., whether there are any Zone 5 keys. If so, the pigeonholes of these keys are checked in step 426 to determine whether any of these keys are down. If so, a notation is made in the pigeonhole of each of depressed Zone 5 key that a patch change is pending in step 429.

In the next step 433 the pigeonhole of each pedal and each key of the keyboard is checked to determine whether a patch change is pending for that key or pedal. For each key or pedal which does not have a patch change pending, the new key defining information for that key or pedal corresponding with the patch number shown in "Newpatch" is entered into the pigeonhole.

All zone headings in the Aftertouch Register as well as depressed key data items under these headings are then deleted from the Aftertouch Register in step 435. New zone headings are then created and entered into the Aftertouch Register in step 436. The corresponding destination (e.g., MIDI channel) for each mono aftertouch zone is entered also. Mono aftertouch zone headings receive eligibility flags; Note Select zone headings do not. These data items and flags are discussed below just prior to the explanation of step 875.

The control panel display 41a (see FIG. 1) is then updated in step 438 to show the new patch.

Referring again to FIG. 3, if the active key (or pedal) is programmed to serve a sustain pedal function, then that key is a Typecode 14 key. The Sustain Pedal Subroutine is called in step 455 and is shown in FIG. 11. In the first step 460 it is determined whether the key has moved down or up. If it has moved down, the subroutine is exited. The fact that the pedal is now down has already been recorded in the pedal's pigeonhole in step 90. If the key has moved up, an index number of one is established in step 463 indexing the first key listed in the corresponding Sustain Pedal Register. Then, in step 466, the "A" data item in the key's Set Register (for Zone 1-4 keys) or pigeonhole (for Zone 5 keys) is erased. In the case of Zone 5 keys, this erasure simply serves to erase the notation that the note is sustaining because the pedal is down (entered in step 132 from step 131). A note-off command is then sent for the destination listed in the key's pigeonhole in step 470. The key's pigeonhole is then checked to determine whether a patch change is pending in step 471 and, if so, the pigeonhole is reloaded according to the patch in "Newpatch" in step 472. It is then determined in step 473 whether steps 466, 470, & 471 (and step 472 if called for) have been performed for all keys in the Aftertouch Register. If not, the index number is increased by one in step 474 and step 466 is returned to. If so, the Register is then cleared in step 477. It is then determined in step 479 whether a patch change is pending for the sustain pedal. If so, the pedal's pigeonhole is reloaded in step 481.

In the interest of brevity, sustain pedal functions are not included in the Strum Modes subroutines. The steps relating to the sustain pedal shown in FIGS. 4 & 11 may easily be duplicated in the subroutines shown in FIGS. 5-9 & FIG. 12. Also, sustain pedal functions are not necessary in the Strum Modes subroutines.

Referring again to FIG. 3, if the active key is a Single Key Strumming (Strum Mode 5) key, then that key is a Typecode 15 key. The Subroutine for this keys is called in step 488 and is shown in FIG. 12. In the first step 494 the new position of the active key is determined. If the key just moved down, the corresponding SKS Register is checked in step 499 to determine whether there is a key shown in "A", and thus, whether another key in the active key's zone is currently down. If so, the pigeonhole of the "A" key is then checked in step 500 to determine whether a patch change is pending for that key. If so, note-off commands are sent for the destinations corresponding with the "A" key in step 501. The pigeonhole of the "A" key is then reloaded in step 502 according to the patch shown in "Newpatch". If it was determined in step 500 that there was no patch change pending for the "A" key, then it is then determined in step 504 whether the "A" key is in the same set as the active key. If two SKS keys trigger the same set of notes in different directions (one ascending, the other descending), then those two keys are in the same set. SKS keys of the same set occupy the same X-axis position on the keyboard. If the two keys are not in the same set, the destinations corresponding with the previously depressed key are muted in step 508. The "A" data item is then shifted into the "B" position in step 511. Elapsed time between present and the time shown in "B" is then measured and recorded in "Longtime" in step 513. If no other SKS keys are down as determined in step 499, then elapsed time between present and the time shown in "C" is measured and recorded in "Longtime" in step 514. It is then determined in step 520 whether the elapsed time measured in step 513 or 514 is greater than 400 milliseconds. If not, the elapsed time is recorded in "Longtime" in step 522. An arpeggiation rate as a function of the "Longtime" value is then calculated in step 525. The active key's ID number and the present time are then recorded in the "A" position in step 527. An index number of one is then established in step 528, indexing the first destination in the active key's pigeonhole. A note-off command is then sent for the indexed destination listed in the pigeonhole of the active key in step 529. A note-on command is then sent for the same destination in step 533. It is then determined in step 535 whether all destinations listed in the active key's pigeonhole have been muted and triggered. If not, a pause is implemented in step 536. This pause is based on the arpeggiation rate calculated in step 525. The index number is then increased by one in step 538. Step 529 is then returned to and steps 529-535 are performed until note-off/note-on commands have been sent for all destinations listed in the active key's pigeonhole (typically step 536 will be performed five times). After the loop is exited the active key's ID # is entered into the Aftertouch Register in step 541.

If the active key's new position is up, the active key's ID # is removed from the Aftertouch Register in step 543 (see FIG. 12b). The SKS Register is then checked in step 544 to determine whether there is a data item in position "B", and thus, whether another key in the SKS zone is down. If there is no "B" data item, then no keys in the zone are down and note-off commands are sent for the destinations listed in the pigeonhole of the key shown in the SKS Register "A" position in step 550. The pigeonhole of the key whose destinations were just muted is then checked in step 553 to determine whether a patch change is pending for that key. If so, the key's pigeonhole is reloaded according to the patch shown in "Newpatch" in step 555. The time of key downstroke shown in "A" is then shifted to the SKS Register's "C" position and the "A" position is cleared in step 559. If it is determined in step 544 that there is a data item in the SKS Register "B" position, then another key within the SKS zone is still down. The "B" data item is then erased in step 563.

Referring again to FIG. 3, if it is determined in step 488 that the active key has no Typecode, then the active key performs no function, and the Keyprocessor Subroutine is exited in step 140.

The Strum Subroutine is shown in FIG. 13. This subroutine is called in steps 208, 210 (see FIG. 6), 253, 256 (see FIG. 7), 303 (see FIG. 8), 341, and 344 (see FIG. 9) with the following parameters: (1) a particular Downkey Register, (2) an arpeggiation rate, and (3) a strum direction of either ascending or descending. In the first step 600 the strum direction is determined. If the direction is ascending, an index (I) is set to 1 in step 610. This index is used as a reference number to select a particular depressed note select key which is listed in the Downkey Register to be processed in the loop which includes steps 630, 670, & 687. With the index set to 1, the first (lowest musical pitch) key listed in the register is selected. If the direction is descending, the index is set to the same number as the total number of keys listed in the Downkey Register in step 620. Typically, this number is approx. 4 or 5, since this is the number of keys which a user will typically hold down with one hand to form a guitar-like chord. It should be noted that with a Janko Keyboard or other keyboard with a shortened octave, wide chords may be formed with one hand. The pigeonhole of the key corresponding with the index number is then checked in step 630 to determine whether the key is a Typecode 3 key (in a type 8 zone) with its alternate destination (typically a "click" sound) sustaining. If the indexed key is a Typecode 2 key, then there is no alternate destination, and step 660 is called. If the indexed key is a Typecode 3 key without a notation that the alternate destination is sustaining, then step 660 is also called. In step 660, a note-off command is sent for the primary destination. If it is determined in step 630 that the indexed key is a Typecode 3 key with its alternate destination sustaining, a note-off command is sent for the alternate destination in step 640. The notation indicating that the alternate destination is sustaining is then removed from the indexed key's pigeonhole in step 650. The pigeonhole of the indexed key is then checked for a notation that a patch change is pending in step 670. If so, the pigeonhole is then cleared and reloaded according to the patch shown in "Newpatch" in step 680. The pigeonhole of the indexed key is then checked in step 687 to determine whether the key is a Typecode 3 key (a key in a type 8 zone). If not, a note-on command is sent for the primary destination in the indexed key's pigeonhole in step 693. The velocity component of this command is taken from the indexed key's pigeonhole. If the key is a Typecode 3 key, the aftertouch value recorded in the key's pigeonhole is then checked in step 700 to determine whether the key is being depressed with sufficient pressure to exceed the primary/alternate note threshold. If so, a note-on command is sent for the primary destination in step 693. If the indexed key is being depressed lightly, i.e., with insufficient pressure to exceed the threshold, then a note-on command is sent for the alternate destination in step 707. The velocity component of this command is taken from the indexed key's pigeonhole. This alternate destination is typically a "click" sound. A notation is then made in the indexed key's pigeonhole that the key's alternate destination is currently sustaining in step 714. The strum direction is then determined again in step 733. If the direction is ascending, it is then determined in step 735 whether the loop including steps 630, 670, & 687 has been performed for all keys in the Downkey Register. If so, the subroutine is exited in step 140. If not, the index number is increased by one in step 740. If it is determined in step 733 that the direction is descending, it is then determined in step 714 whether the loop including steps 630, 670, & 687 has been performed for all keys in the Downkey Register. If not, the index number is reduced by one in step 747. A brief pause is then inserted in the program in step 755. The length of this pause (e.g., one millisecond) is calculated as a function of the arpeggiation rate. Step 630 is then returned to for the next key listed in the Downkey Register.

The Aftertouch Subroutine is shown in FIG. 14. This subroutine is called in step 75 (see FIG. 2). In the first step 800 of this subroutine, the Aftertouch Register is checked to determine when the subroutine was last entered. This time is compared with the present time to determine whether less than one millisecond has elapsed since the subroutine was last entered. If so, the subroutine is exited and step 70 (see FIG. 2) is called in step 807. A 1 ms interval is included between runs of this subroutine because the MIDI protocol requires this time period to send an aftertouch message. Thus, as far as MIDI is concerned, there is no purpose in updating aftertouch values more frequently than once per millisecond. Rather, it is desired that step 70 be arrived at frequently, so that new key movement information may be processed as soon as possible after it is received from the daughter sense boards. Also, when a daughter board is multiplexed for an A/D conversion, it is prevented from scanning for new key movement. If more than 1 ms has elapsed, the present time is recorded in the Aftertouch Register in step 814. It is then determined in step 820 whether any keys are listed in the Aftertouch Register and, thus, whether any relevant keys (i.e., keys for which aftertouch is to be measured) are down. If no relevant keys are down, the subroutine is exited. If at least one relevant key is down, an index number of one is established in step 825. This index number refers to the first key in the Aftertouch Register. An index number of two refers to the second key, and so forth. In the next step 830, the pigeonhole of the indexed key is checked to determine whether less than 200 milliseconds has elapsed since the key was depressed. This is the "debounce" time allotted for the key to finish its bouncing which naturally occurs when bottom-of-travel is reached. If less than 200 ms has elapsed, step 870 (discussed below) is called. If more than 200 ms has elapsed, the indexed key's daughter microcontroller (see FIG. 12 of copending U.S. patent application Ser. No. 08/345,067, now U.S. Pat. No. 5,505,115, reference numeral 480) is instructed to multiplex the indexed key's phototransistor sensor to the A/D converter in the CPU 37 in step 835 so that an A/D conversion may be performed to determine precise key position and thus aftertouch pressure. In the next step 840 a pause of approx. 50 microseconds is carried out to compensate for rise/fall times within the photointerrupter. An A/D conversion is then performed on the indexed key in step 845. It is then determined in step 850 whether the indexed key is a Typecode 3 key. If so, it is then determined in step 855 whether the new aftertouch value is less than the primary note threshold. If so, the user is pressing softly on the key and the previous aftertouch value (still in the key's pigeonhole) is then checked in step 860 to determine whether the user was previously pressing the key more softly than the primary note threshold. If not, the user has recently decreased pressure on the key and crossed the primary note threshold. This action with a Typecode 3 key is analogous to a guitar player releasing left hand pressure on a guitar string sufficiently to mute the string. Thus, a note-off command is sent for the indexed key's primary destination in step 863. The new aftertouch value is then recorded in the indexed key's pigeonhole in step 864. The subroutine is then exited in step 865 since the MIDI note-off command sent in step 863 requires one millisecond to send. There is thus no point in proceeding further until the message is sent. If step 863 is not arrived at, the new aftertouch value for the indexed key is entered into that key's pigeonhole in step 866. It is then determined in step 870 whether new aftertouch values have been measured for all keys in the Aftertouch Register. If not, the index number is increased by one in step 874. Step 830 is then returned to.

We turn our attention now to the portion of the Aftertouch Subroutine which is responsible for sending out aftertouch messages to the tone generating device. This portion is shown in FIG. 14b. Two types of flags are provided for selected items within the Aftertouch Register: eligibility flags and a single message flag. The message flag signifies that the attached data item is the next item for which an aftertouch message is to be sent. Each time an item is entered into the Aftertouch Register, a determination is made as to whether that item is eligible to receive the message flag. If so, an eligibility flag is attached to the item. Items which are eligible to receive the message flag are ID #s for keys which are designated for polyphonic aftertouch and heading numbers for mono aftertouch zones. Ineligible data items are keys within mono aftertouch or Note Select zones and heading numbers for Note Select zones. (In this embodiment of the invention aftertouch messages are never sent to the tone generating device for keys within a Note Select zone; although the keyboard could be engineered with this option.) If it is determined in step 870 that new aftertouch values have been provided for all keys in the Register, then the Register is checked in step 875 to determine whether there are any keys listed in the Register which are not in a Note Select zone subset. In other words, it is determined whether the user is holding down any keys for which aftertouch messages need to be sent to the tone generating module. Key data items within Note Select zone subsets may be easily skipped since Note Select zone headings do not include eligibility flags. If all keys in the Register are in a Note Select zone, the subroutine is exited. If there is at least one key in the Register for which it is desired that an aftertouch message be sent, the Register is then scanned for the message flag in step 882. If no message flag is found, it is then determined in step 885 whether the first non-note-select key in the Register is within a mono aftertouch zone. If not, the key is a poly aftertouch key and the message flag is placed on the key's ID # data item in the Register in step 887. Step 904 is then called. If it is determined in step 885 that the first non-note-select key in the Register is within a mono aftertouch zone, the message flag is then placed on the heading data item for the key's zone number in step 889. Step 912 is then called. If the message flag is found in step 882, it is then determined in step 900 whether the flagged data item is a mono aftertouch zone heading or a poly aftertouch key. If the flagged item is a key, an aftertouch message is sent for the key in step 904. Information for this message, including the recently measured aftertouch value and the MIDI destination, is taken from the key's pigeonhole. If the flagged item is a zone heading, it is determined in step 906 whether any keys are listed under this heading, i.e., whether any keys within the zone are down. If not, no aftertouch message can be sent for the zone and the flag needs to be moved to the next eligible data item in the hope that that item will have a corresponding depressed key. The process of moving the message flag to the next eligible item is carried out in steps 907-909. In the first step 907 of this process it is determined whether the flagged item is the last item in the Register. If so, the message flag is moved to the first eligible item in the Register in step 908. If not, the message flag is moved to the next eligible item in step 909. Step 900 is then returned to. If it is determined in step 906 that there is at least one key listed in the flagged subset, then an average aftertouch value is calculated from the aftertouch values in the pigeonholes of all the listed keys in step 912. An aftertouch command including this average value is then sent to the tone generating device in step 916. The destination (e.g., MIDI channel) for this command is taken from the flagged subset as entered during step 65 or step 436. The message flag is then moved to the next eligible item in steps 920-928 which are identical to steps 907-909 discussed above. The subroutine is then exited.

As an alternative to the method shown, two aftertouch registers may be provided. The first register would list depressed keys for which aftertouch values need to be measured; the second would list depressed poly-aftertouch keys and mono-aftertouch zones for which aftertouch messages need to be sent to the tone generating device. This alternative would add steps insofar as some keys would have to be entered into (and deleted from) two aftertouch registers instead of one, but several steps in the Aftertouch subroutine would be simplified, including steps 875, 908, 909, 924, & 928. As another option, Note Select keys may be entered only into the Downkey Register in step 165; and the keys listed in both the Downkey and Aftertouch Registers may be processed in steps 830-874.

Other MIDI functions such as real time volume control, pitch bend, modulation, etc. have not been discussed in detail in this specification, but may easily be included in the software by a person of ordinary skill in the art.

Since filing of "Swing Arm" application Ser. No. 08/345,067, now U.S. Pat. No. 5,505,115, applicant has developed two new key guide pin bushings which are recommended for the preferred embodiment of the present invention. These two new bushings are shown in FIGS. 15 and 16A-D. An explanatory text regarding these bushings follows. An understanding of this text will be enhanced by a prior review of applicant's prior U.S. Pat. Nos. 5,185,490 (Key Guide), 5,469,772 (Linearly Reciprocating Keyboard Key Incorporating Two Guide Pins), and copending application Ser. No. 08/345,067, now U.S. Pat. No. 5,505,115 ("Swing Arm").

Referring now to FIG. 15, a recommended front key guide pin bushing is shown in cross-section. This bushing may be used with a front key pin 938 (shown in cross-section in FIG. 15) which may be identical to the front key pin shown in FIG. 6 of "Swing Arm" application Ser. No. 08/345,067, now U.S. Pat. No. 5,505,115, and referenced there by numeral 229. A circular bushing 940 is provided which encircles pin 938 with a slight clearance so pin 938 may slide vertically without resistance. Bushing 940 may be formed of Delrin.RTM. and is affixed to a front frame flange 943 through the use of a cement (e.g., cyanoacrylate) which fills an annular void 946 as shown. The flange and bushing shown are the upper of the two front flanges and bushings. The lower flanges & bushings are similar to the upper, but the two bushings are disposed upside-down with respect to each other as shown in FIG. 6 of the "Swing Arm" application. This bushing has two advantages over the front bushings shown in "Swing Arm" FIG. 6: It allows less key wobble, since there is no compressible bumper; and it is easier to assemble.

Referring now to FIGS. 16A-D, a recommended rear key guide pin bushing is shown. This bushing may be used with a rear key pin 950 (not shown in FIG. 16A) which may be identical to the rear key pin shown in FIG. 6 of "Swing Arm" application Ser. No. 08/345,067, now U.S. Pat. No. 5,505,115, and referenced there by numeral 250. A Delrin.RTM. bushing is provided which consists of a right half 955 and a left half 956. The two halves may be identical. They are mated together via four alignment pins 959 (two on each half) which mate, with slight clearance, into four bores 960 as shown in FIGS. 16A & 16B. Once mated, the two bushing halves are inserted into a rectangular aperture in a box-shaped bumper 963. Bumper 963 may be formed of extruded silicone rubber. It must be stretched before the bushing halves may be inserted. Each bushing half incorporates four flanges (upper front/rear and lower front/rear) 965 which serve to keep the bushing halves insides the bumper aperture. Bumper 963 includes a longitudinally-extending front portion 967, a longitudinally-extending rear portion 968, and laterally-extending side portions 969. After the two bushing halves are inserted into the bumper, the bumper/bushing is placed into the bushing cutout 973 in upper rear flange 975. The bumper/bushing is held in place at its front and rear ends. The rear bumper end is held in place by an upper front flange 977 and a lower front flange 978 on the front frame flange 943 of the frame rail adjacent to the rear (see FIGS. 15 & 16D). The front bumper end is held in place by a lower retaining strip 981 and an upper retaining strip 982, each shown in cross-section in FIG. 16D. These retaining strips extend the length of the keyboard, are formed of extruded plastic and are inserted into T-shaped slots in frame rail 984 (see FIG. 16D). Insertion of the strips into the slots is carried out by inserting each strip end into its corresponding slot at one end of the frame rail and sliding the strip lengthwise until the strip is properly aligned. The retaining strips and their corresponding T-shaped slots are not shown in 16A-C. The two bushing halves are shaped so that when rear pin 950 is inserted between them, the pin pushes the two halves slightly away from each other, forming a slight clearance as seen in FIG. 16B. When the bumper is at rest without the bushing halves inserted, the distance between the two bumper side portions 969 is slightly less than the left-right width of the two mated halves with pin 950 inserted. Thus, the bumper pulls the two halves together against the pin, and keeps both halves in contact with the pin at all times. Alignment pins 959 fit with slight clearance into their corresponding bores 960. Thus, the bushing halves may move slightly relative to each other in the left-right dimension during vertical key movement as a result of slight irregularities in the diameter of guide pin 950. Bushing cutout 973 is sufficiently wide that a very slight clearance exists at all times between the installed bushing/bumper and the inside walls of the cutout as shown in FIGS. 16B & 16C. This clearance will naturally shift from one side to the other as the user imposes shifting side force on the key during performance, causing the bushing/bumper to shift position in the left-right dimension. The primary advantage of this bushing design over that shown in FIG. 5 of applicant's prior U.S. Pat. No. 5,469,772 (Linearly Reciprocating Keyboard Key Incorporating Two Guide Pins) is that, since the two sides/halves of the bushing are always in contact with the rear key guide pin, far less noise is produced as a result of shifting side force during performance. Another advantage may be that injection mold tooling for the bushing halves may be less expensive than for the prior rear bushings. The FIG. 16 design utilizes the principle of using constricting force of a bumper to keep track-engaging bushing surfaces in constant contact with a track. With a ring-shaped bumper providing constricting force to at least two properly shaped bushing parts (not shown), this principle may be applied to a 360 degree side force bushing as well.

The preferred embodiment hereinabove described is intended as one possible embodiment of the invention. The above described flow charts may be modified in numerous ways while still retaining the essential features of the invention. For example, the operating software may be modified so that, in strum modes 1-4, when all note select keys are up, trigger key movement which would otherwise trigger chords instead triggers a series of clicks, e.g., a series of six clicks with an 8 millisecond pause between consecutive clicks. This series of clicks would resemble the sound of a guitarist strumming muted strings.

As another variation of the preferred embodiment, a chord recognizing software program, e.g., that shown in U.S. Pat. No. 4,282,786 (Deutsch), may be incorporated into strum modes 1-4 to enable a user to perform (using note select and trigger keys) strums of chords which are larger than can be reached with one hand in the note select zone of the keyboard (e.g., chords spanning two octaves).

Numerous different key position sensing systems and methods may be employed.

Many other modifications are possible as well. The scope of the invention is thus in no way to be considered limited by the preferred embodiment described above; but rather, by the allowed claims and their equivalents.

Claims

1. An emulator for producing a guitar style performance from a controller, said controller including a user-operated triggering device for triggering arpeggiated chords which a user may alternate between a first trigger state and a second trigger state, and at least twelve keyboard keys assigned to a note select function, each of which a user may alternate between a rest key state and a selected key state, comprising:

a digital data processing system which receives trigger state information from said triggering device and key state information from said note select keys, and which sends commands to a tone generating device wherein,

a first state change of said triggering device from said first trigger state to said second trigger state when at least two of said note select keys are in said selected key state causes said data processing system to command said tone generating device to initiate production of a plurality of tones corresponding to the selected note select keys in an ascending sequence; and,

a second state change of said triggering device from said second trigger state to said first trigger state following said first triggering device state change as said selected note select keys remain in said selected key state causes said data processing system to command said tone generating device to (a) terminate production of said plurality of tones and (b) re-initiate production of said plurality of tones in a descending sequence.

2. An emulator as in claim 1 wherein;

said triggering device is a keyboard key.

3. An emulator as in claim 2 wherein,

said triggering device key is reciprocative between a rest position and a depressed position; and

said first and second trigger states are said rest and depressed key positions, respectively.

4. An emulator as in claim 1 wherein;

said triggering device is a vertically reciprocating foot pedal.

5. An emulator as in claim 4 wherein,

said triggering device foot pedal is reciprocative between a rest position and a depressed position; and

said first and second trigger states are said rest and depressed pedal positions, respectively.

6. An emulator as in claim 1 wherein;

said triggering device is a foot position sensing device which senses horizontal position of at least a portion of one of said user's feet.

7. An emulator as in claim 1 wherein,

each of said note select keys is reciprocative between a rest position and a depressed position; and

said rest and selected key states are said rest and depressed positions, respectively.

8. An emulator as in claim 1 wherein;

production of all of said tones initiated as a result of said first trigger state change is terminated as a result of said second trigger state change before the tones are re-initiated as a result of said second state change.

9. An emulator as in claim 1 wherein;

each of said tones initiated as a result of said first trigger state change is terminated as a result of said second trigger state change immediately prior to re-initiation; whereby,

as a result of said second state change, the highest pitched selected musical tone is muted and re-triggered, then the next lowest pitched selected musical tone is muted and re-triggered, followed by the next lowest tone.

10. An emulator as in claim 1 wherein;

state changes of said triggering device are affected through movement of a human appendage;

said data processing system receives information from said triggering device regarding the velocity with which said appendage effects trigger state changes;

said commands to initiate tone production include velocity data; and,

the velocity values corresponding with commands to initiate tone production for selected tones are a function of the velocity of the appendage movement which triggers the initiation of the selected tones.

11. An emulator as in claim 1 wherein;

said key state information includes information regarding aftertouch pressure applied to selected note select keys;

said commands to initiate tone production include velocity data; and,

the velocity values for selected tones are a function of aftertouch pressure applied to note select keys near the time of corresponding trigger state change.

12. An emulator as in claim 1 wherein;

said data processing system measures elapsed time between successive triggering device state changes; and,

elapse times between successive commands to initiate tone production for selected tones initiated as a result of a trigger state change are a function of the elapsed time between that trigger state change and the preceding trigger state change.

13. An emulator as in claim 1 wherein;

state changes of said triggering device are affected through movement of a human appendage;

said data processing system receives information from said triggering device regarding the velocity with which said appendage effects trigger state changes; and

elapse times between successive commands to initiate tone production for selected tones initiated as a result of a trigger state change are an inverse function of the velocity of the appendage movement which affected the corresponding trigger state change.

14. An emulator as in claim 1 wherein;

the center-to-center distance between two of said note select keys which correspond with two tones one octave apart is not more than 14.5 centimeters.

15. An emulator as in claim 1 wherein;

said data processing system communicates with said tone generating device according to a standardized digital protocol.

16. An emulator as in claim 15 wherein;

said protocol is selected from the group consisting of MIDI and ZIPI.

17. A method of generating ascending and descending musical chord arpeggiations comprising:

assigning at least twelve of the keys within a keyboard to a note select function;

determining which keys are included within a group of said note select keys being held in a selected state by a user;

instructing a tone generating device to play an ascending arpeggiation of the notes corresponding with said group of keys in response to a first user-initiated state change of a triggering device from a first trigger state to a second trigger state as said group of keys continue to be held in selected state; and

instructing said tone generating device to (a) mute the notes played in response to said first trigger state change and (b) play a descending arpeggiation of the same notes in response to a second user-initiated state change of said triggering device from said second trigger state to said first trigger state as said group of keys continue to be held in selected state.

18. A method of generating arpeggiations as in claim 17 wherein;

said triggering device is a key within said keyboard.

19. A method of generating arpeggiations as in claim 18 wherein,

said triggering device key is reciprocative between a rest position and a depressed position; and

said first and second trigger states are said rest and depressed key positions, respectively.

20. A method of generating arpeggiations as in claim 17 wherein;

said triggering device is a foot pedal.

21. A method of generating arpeggiations as in claim 20 wherein,

said triggering device foot pedal is reciprocative between a rest position and a depressed position; and

said first and second trigger states are said rest and depressed pedal positions, respectively.

22. A method of generating arpeggiations as in claim 17 wherein,

each of said note select keys is reciprocative between a rest position and a depressed position; and

said rest and selected key states are said rest and depressed positions, respectively.

23. A method of generating arpeggiations as in claim 17 wherein;

production of all of said notes initiated in response to said first triggering device state change is terminated as a result of said second triggering device state change before the notes are re-initiated in response to said second triggering device state change.

24. A method of generating arpeggiations as in claim 17 wherein;

each of said notes initiated in response to said first triggering device state change is terminated as a result of said second triggering device state change immediately prior to re-initiation; whereby,

in response to said second state change, the highest pitched selected note is muted and re-triggered, then the next lowest pitched selected note is muted and re-triggered, followed by the next lowest note.

25. A method of generating arpeggiations as in claim 17 further comprising;

measuring the velocity with which a human appendage effects a triggering device state change; and

instructing said tone generating device to produce the corresponding arpeggiation at a volume which is a function of the measured appendage velocity.

26. A method of generating arpeggiations as in claim 17 further comprising;

measuring the aftertouch pressure applied to said group of keys near the time of a triggering device state change; and

instructing said tone generating device to produce the corresponding arpeggiation at a volume which is a function of the measured aftertouch pressure.

27. A method of generating arpeggiations as in claim 17 further comprising;

measuring elapsed time between successive triggering device state changes; and,

instructing said tone generating device to produce said arpeggiations of notes in such a manner that elapse times between successive notes within an arpeggiation are a function of the elapsed time between the triggering device state change which triggered the arpeggiation and the preceding triggering device state change.

28. A method of generating arpeggiations as in claim 17 further comprising;

measuring the velocities with which a human appendage effects triggering device state changes; and

instructing said tone generating device to produce said arpeggiations of notes in such a manner that elapse times between successive notes within an arpeggiation are an inverse function of the velocity of the appendage movement which triggered the arpeggiation.

29. A method of generating arpeggiations as in claim 17 wherein;

the center-to-center distance between two of said note select keys which correspond with two notes one octave apart is not more than 14.5 centimeters.

30. A method of generating arpeggiations as in claim 17 wherein;

instructions are sent to said tone generating device according to a standardized digital protocol.

31. A method of generating arpeggiations as in claim 30 wherein;

said protocol is selected from the group consisting of MIDI and ZIPI.

32. An emulator for producing a guitar style performance from a controller, said controller including first and second user-operated triggering devices, each of which a user may alternate between a rest trigger state and a selected trigger state, and at least twelve keyboard keys assigned to a note select function, each of which a user may alternate between a rest key state and a selected key state, comprising:

a digital data processing system which receives trigger state information from said triggering devices and key state information from said note select keys, and which sends commands to a tone generating device wherein,

a state change of said first triggering device from said rest trigger state to said selected trigger state when at least two of said note select keys are in said selected key state causes said data processing system to command said tone generating device to initiate production of a plurality of tones corresponding to the selected note select keys in an ascending sequence; and,

a state change of said second triggering device from said rest trigger state to said selected trigger state following said state change of said first triggering device as said selected note select keys and said first triggering device continue to be held in selected state causes said data processing system to command said tone generating device to (a) terminate production of said plurality of tones and (b) re-initiate production of said plurality of tones in a descending sequence.

33. An emulator as in claim 32 wherein said processing system

(a) allows said tone generating device to continue production of the tones initiated as a result of said state change of said second triggering device when either of said triggering devices is returned to rest state as the other triggering device and said selected note select keys remain in selected state; and

(b) commands said tone generating device to terminate production of the tones initiated as a result of said state change of said second triggering device when the triggering device remaining in selected state is returned to rest state.

34. An emulator as in claim 32 wherein;

at least one of said triggering devices is a keyboard key.

35. An emulator as in claim 34 wherein,

said triggering device key is reciprocative between a rest position and a depressed position; and

said rest and selected trigger states are said rest and depressed key positions, respectively.

36. An emulator as in claim 32 wherein;

at least one of said triggering devices is a foot pedal.

37. An emulator as in claim 36 wherein,

said triggering device foot pedal is reciprocative between a rest position and a depressed position; and

said rest and selected trigger states are said rest and depressed pedal positions, respectively.

38. An emulator as in claim 32 wherein,

each of said note select keys is reciprocative between a rest position and a depressed position; and

said rest and selected key states are said rest and depressed positions, respectively.

39. An emulator as in claim 32 wherein;

production of all of said tones initiated as a result of said state change of said first triggering device is terminated as a result of said state change of said second triggering device before the tones are re-initiated as a result of said state change of said second triggering device.

40. An emulator as in claim 32 wherein;

each of said tones initiated as a result of said state change of said first triggering device is terminated as a result of said state change of said second triggering device immediately prior to re-initiation; whereby,

as a result of said state change of said second triggering device, the highest pitched selected musical tone is muted and re-triggered, then the next lowest pitched selected musical tone is muted and re-triggered, followed by the next lowest tone.

41. An emulator as in claim 32 wherein;

state changes of said triggering devices from rest to selected state are affected through movement of one or more human appendages;

said data processing system receives information from said triggering devices regarding the velocity with which said one or more appendages effect state changes of said triggering devices from rest to selected state;

said commands to initiate tone production include velocity data; and,

the velocity values corresponding with commands to initiate tone production for selected tones are a function of the velocity of the appendage movement which triggers the initiation of the selected tones.

42. An emulator as in claim 32 wherein;

said key state information includes information regarding aftertouch pressure applied to selected note select keys;

said commands to initiate tone production include velocity data; and,

the velocity values corresponding with commands to initiate tone production for selected tones are a function of aftertouch pressure applied to note select keys near the time of corresponding triggering device state change from rest to selected state.

43. An emulator as in claim 32 wherein;

said data processing system measures elapsed time between successive triggering device rest-to-selected state changes; and,

elapsed time between successive commands to initiate tone production for selected tones initiated as a result of a triggering device rest-to-selected state change is a function of elapsed time between successive triggering device rest-to-selected state changes.

44. An emulator as in claim 32 wherein;

state changes of said triggering devices from rest to selected state are affected through movement of one or more human appendages;

said data processing system receives information from said triggering devices regarding the velocity with which said one or more appendages effect state changes of said triggering devices from rest to selected state; and

elapsed time between successive commands to initiate tone production for selected tones initiated as a result of a triggering device rest-to-selected state change is an inverse function of the velocity of the appendage movement which affected the corresponding rest-to-selected trigger device state change.

45. An emulator as in claim 32 wherein;

the center-to-center distance between two of said note select keys which correspond with two tones one octave apart is not more than 14.5 centimeters.

46. An emulator as in claim 32 wherein;

said data processing system communicates with said tone generating device according to a standardized digital protocol.

47. An emulator as in claim 46 wherein;

said protocol is selected from the group consisting of MIDI and ZIPI.

48. A method of generating ascending and descending musical chord arpeggiations comprising:

assigning at least twelve of the keys within a keyboard to a note select function;

determining which keys are included within a group of said note select keys being held in a selected state by a user;

instructing a tone generating device to play an ascending arpeggiation of a group of notes corresponding with said group of keys in response to a user-initiated state change of a first triggering device from a rest trigger state to a selected trigger state as said group of keys continue to be held in selected state; and

instructing said tone generating device to (a) mute said note group and (b) play a descending arpeggiation of the same note group in response to a user-initiated state change of a second triggering device from a rest trigger state to a selected trigger state as said group of keys and said first triggering device continue to be held in selected state.

49. A method of generating arpeggiations as in claim 48 wherein;

said tone generating device is allowed to continue sustaining the notes within said descending arpeggiation when either of said triggering devices is returned to rest state as the other triggering device and said group of note select keys remain in selected state; and

said tone generating device is instructed to mute the sustaining notes when the triggering device remaining in selected state is returned to rest state.

50. A method of generating arpeggiations as in claim 48 wherein;

at least one of said triggering devices is a key within said keyboard.

51. A method of generating arpeggiations as in claim 50 wherein,

said triggering device key is reciprocative between a rest position and a depressed position; and

said rest and selected trigger states are said rest and depressed key positions, respectively.

52. A method of generating arpeggiations as in claim 48 wherein;

at least one of said triggering devices is a foot pedal.

53. A method of generating arpeggiations as in claim 52 wherein,

said triggering device foot pedal is reciprocative between a rest position and a depressed position; and

said rest and selected trigger states are said rest and depressed pedal positions, respectively.

54. A method of generating arpeggiations as in claim 48 wherein,

each of said note select keys is reciprocative between a rest position and a depressed position; and

said rest and selected key states are said rest and depressed positions, respectively.

55. A method of generating arpeggiations as in claim 48 wherein;

production of all of said notes initiated in response to said first triggering device state change is terminated as a result of said second triggering device state change before the notes are re-initiated in response to said second triggering device state change.

56. A method of generating arpeggiations as in claim 48 wherein;

each of said notes initiated in response to said first triggering device state change is terminated as a result of said second triggering device state change immediately prior to re-initiation; whereby,

in response to said second triggering device state change, the highest pitched selected note is muted and re-triggered, then the next lowest pitched selected note is muted and re-triggered, followed by the next lowest note.

57. A method of generating arpeggiations as in claim 48 further comprising;

measuring the velocity with which a human appendage effects a triggering device state change; and

instructing said tone generating device to produce the corresponding arpeggiation at a volume which is a function of the measured appendage velocity.

58. A method of generating arpeggiations as in claim 48 further comprising;

measuring the aftertouch pressure applied to said group of note select keys near the time of a triggering device state change; and

instructing said tone generating device to produce the corresponding arpeggiation at a volume which is a function of the measured aftertouch pressure.

59. A method of generating arpeggiations as in claim 48 further comprising;

measuring elapsed time between successive rest-to-selected triggering device state changes; and,

instructing said tone generating device to produce said arpeggiations of notes in such a manner that elapse times between successive notes within an arpeggiation are a function of the elapsed time between the rest-to-selected triggering device state change which triggered the arpeggiation and the preceding rest-to-selected triggering device state change.

60. A method of generating arpeggiations as in claim 48 further comprising;

measuring the velocities with which a human appendage effects triggering device state changes; and

instructing said tone generating device to produce said arpeggiations of notes in such a manner that elapse times between successive notes within an arpeggiation are an inverse function of the velocity of the appendage movement which triggered the arpeggiation.

61. A method of generating arpeggiations as in claim 48 wherein;

the center-to-center distance between two of said note select keys which correspond with two notes one octave apart is not more than 14.5 centimeters.

62. A method of generating arpeggiations as in claim 48 wherein;

instructions are sent to said tone generating device according to a standardized digital protocol.

63. A method of generating arpeggiations as in claim 62 wherein;

said protocol is selected from the group consisting of MIDI and ZIPI.

64. An emulator for producing a guitar style performance from a controller, said controller including at least 24 keys, each of which a user may alternate between a rest key state and a selected key state, comprising:

a digital data processing system which receives key state information from said 24 keys, and which sends commands to a tone generating device;

said processing system including a memory device which stores data, said data including the tones contained within twelve predetermined chords, each of said twelve chords corresponding with one of the twelve notes in a standard octave; wherein,

said 24 keys are grouped by said data processing system into twelve strum key pairs, each pair corresponding with one of said twelve predetermined chords and consisting of an upstrum key and a downstrum key; and

for any one of said key pairs, (a) a rest-to-selected state change of the upstrum key causes said data processing system to command said tone generating device to initiate production of the tones contained within that pair's corresponding chord in a descending note sequence and (b) a rest-to-selected state change of the downstrum key causes said data processing system to command said tone generating device to initiate production of the tones contained within the same corresponding chord in an ascending note sequence.

65. An emulator as in claim 64 wherein,

when any one of said 24 strum keys is held in selected key state as another of said 24 strum keys is changed from rest to selected state, said processing system commands said tone generating device to

(a) terminate production of the tones contained within the chord corresponding with the previously selected key; and

(b) initiate production of the tones contained within the chord corresponding with the newly selected key.

66. An emulator as in claim 65 wherein;

the tones contained within the chord corresponding with the previously selected key are terminated before initiation of the tones contained within the chord corresponding with the newly selected key.

67. An emulator as in claim 64 wherein;

when any one of said 12 downstrum keys is changed from rest to selected key state as the other 23 strum keys are in rest state and is then held in selected key state as its pair partner upstrum key is changed from rest to selected state, said processing system commands said tone generating device to terminate each tone contained within the corresponding chord immediately prior to re-initiation; whereby,

the highest pitched tone of the chord is muted and re-triggered, then the next lowest pitched musical tone is muted and re-triggered, followed by the next lowest tone.

68. An emulator as in claim 64 wherein;

when any one of said 12 upstrum keys is changed from rest to selected key state as the other 23 strum keys are in rest state and is then held in selected key state as its pair partner downstrum key is changed from rest to selected state, said processing system commands said tone generating device to terminate each tone contained within the corresponding chord immediately prior to re-initiation; whereby,

the lowest pitched tone of the chord is muted and re-triggered, then the next highest pitched musical tone is muted and re-triggered, followed by the next highest tone.

69. An emulator as in claim 64 wherein,

each of said strum keys is reciprocative between a rest position and a depressed position; and

said rest and selected key states are said rest and depressed key positions, respectively.

70. An emulator as in claim 64 wherein;

state changes of said strum keys from rest to selected state are affected through movement of at least one of the user's fingers;

said data processing system receives information from said strum keys regarding the velocity with which said finger effects state changes of said keys from rest to selected state;

said commands to initiate tone production include velocity data; and,

the velocity values corresponding with said commands to initiate tone production are a function of the velocity of the finger movement which triggers the commands.

71. An emulator as in claim 64 wherein;

said data processing system measures elapsed time between successive rest-to-selected strum key state changes; and,

elapsed time between successive commands to initiate tone production within a note sequence initiated as a result of a rest-to-selected strum key state change is a function of elapsed time since the prior rest-to-selected strum key state change.

72. An emulator as in claim 64 wherein;

said data processing system communicates with said tone generating device according to a standardized digital protocol.

73. An emulator as in claim 72 wherein;

said protocol is selected from the group consisting of MIDI and ZIPI.

74. An emulator as in claim 64 wherein,

the two keys within each of said key pairs are spaced one octave apart on the left-to-right axis of said keyboard.

75. An emulator as in claim 64 wherein,

said keyboard includes at least two parallel key rows which extend longitudinally from left to right; and

the two keys within each of said key pairs are laterally aligned with each other.

76. An emulator as in claim 64 wherein,

said keyboard includes at least four parallel key rows.

77. An emulator as in claim 76 wherein;

said keyboard comprises a first key row, a second key row, a third key row, and a fourth key row;

said rows extend longitudinally from left to right;

said second key row is laterally positioned between said first and third rows;

said third key row is laterally positioned between said second and fourth rows;

at least a plurality of keys within said first row are laterally aligned with a plurality of keys within said third row;

at least a plurality of keys within said second row are laterally aligned with a plurality of keys within said fourth row; and

at least a plurality of keys within said second row are staggered in the longitudinal dimension halfway between adjacent keys of the first row.

78. An emulator as in claim 77 wherein,

strum keys in rows one and two are paired with laterally aligned strum keys in rows three and four, respectively.

79. An emulator as in claim 78 wherein;

at least a plurality of strum keys within rows one and two are downstrum keys, and their pair partners in rows three and four are upstrum keys.

80. A method of generating ascending and descending musical chord arpeggiations comprising:

assigning at least 24 of the keys within a keyboard to a strum triggering function;

grouping said 24 strum trigger keys into twelve key pairs, each pair corresponding with one of the twelve notes in a standard octave and consisting of an upstrum key and a downstrum key;

assigning one of twelve predetermined chords to each of said key pairs;

instructing a tone generating device to play an ascending arpeggiation of one of said chords in response to a state change of that chord's corresponding downstrum key from a rest key state to a selected key state; and

instructing said tone generating device to play a descending arpeggiation of one of said chords in response to a state change of that chord's corresponding upstrum key from a rest key state to a selected key state.

81. A method of generating arpeggiations as in claim 80 wherein,

when any one of said 24 strum keys is held in selected key state as another of said 24 strum keys is changed from rest to selected state, said tone generating device is instructed to

(a) terminate production of the tones contained within the chord corresponding with the previously selected key; and

(b) initiate production of the tones contained within the chord corresponding with the newly depressed key.

82. A method of generating arpeggiations as in claim 81 wherein;

the tones contained within the chord corresponding with the previously selected key are terminated before initiation of the tones contained within the chord corresponding with the newly depressed key.

83. A method of generating arpeggiations as in claim 80 wherein;

when any one of said 12 downstrum keys is changed from rest to selected key state as the other 23 strum keys are in rest state and is then held in selected key state as its pair partner upstrum key is changed from rest to selected state, said tone generating device is instructed to terminate each tone contained within the corresponding chord immediately prior to re-initiation; whereby,

the highest pitched tone of the chord is muted and re-triggered, then the next lowest pitched musical tone is muted and re-triggered, followed by the next lowest tone.

84. A method of generating arpeggiations as in claim 80 wherein;

when any one of said 12 upstrum keys is changed from rest to selected key state as the other 23 strum keys are in rest state and is then held in selected key state as its pair partner downstrum key is changed from rest to selected state, said tone generating device is instructed to terminate each tone contained within the corresponding chord immediately prior to re-initiation; whereby,

the lowest pitched tone of the chord is muted and re-triggered, then the next highest pitched musical tone is muted and re-triggered, followed by the next highest tone.

85. A method of generating arpeggiations as in claim 80 wherein,

each of said strum keys is reciprocative between a rest position and a depressed position; and

said rest and selected key states are said rest and depressed key positions, respectively.

86. A method of generating arpeggiations as in claim 80 further comprising:

measuring the velocity with which a user's finger effects a rest-to-selected state change of one of said keys; and

instructing said tone generating device to play that key's corresponding arpeggiated chord at a volume which is a function of the measured finger velocity.

87. A method of generating arpeggiations as in claim 80 further comprising:

measuring elapsed time between successive rest-to-selected strum key state changes; and,

instructing said tone generating device to play arpeggiated chords in such a manner that elapse times between successive notes within an arpeggiated chord are a function of the elapsed time between the rest-to-selected strum key state change which triggered the chord and the preceding rest-to-selected strum key state change.

88. A method of generating arpeggiations as in claim 80 wherein;

instructions are sent to said tone generating device according to a standardized digital protocol.

89. A method of generating arpeggiations as in claim 88 wherein;

said protocol is selected from the group consisting of MIDI and ZIPI.

90. A method of generating arpeggiations as in claim 80 wherein,

the two keys within each of said key pairs are spaced one octave apart on said keyboard.

91. A method of generating arpeggiations as in claim 80 wherein,

said keyboard includes at least two parallel key rows which extend longitudinally from left to right; and

the two keys within each of said key pairs are laterally aligned with each other.

92. A method of generating arpeggiations as in claim 80 wherein,

said keyboard includes at least four parallel key rows.

93. A method of generating arpeggiations as in claim 92 wherein;

said keyboard comprises a first key row, a second key row, a third key row, and a fourth key row;

said rows extend longitudinally from left to right;

said second key row is laterally positioned between said first and third rows;

said third key row is laterally positioned between said second and fourth rows;

at least a plurality of keys within said first row are laterally aligned with a plurality of keys within said third row;

at least a plurality of keys within said second row are laterally aligned with a plurality of keys within said fourth row; and

at least a plurality of keys within said second row are staggered in the longitudinal dimension halfway between adjacent keys of the first row.

94. A method of generating arpeggiations as in claim 93 wherein,

strum keys in rows one and two are paired with laterally aligned strum keys in rows three and four, respectively.

95. A method of generating arpeggiations as in claim 94 wherein;

at least a plurality of strum keys within rows one and two are downstrum keys, and their pair partners in rows three and four are upstrum keys.