JP2785896B2 - Performance data processor - Google Patents

Description

The present invention relates to a performance data processing device provided with performance data storage means for storing performance data.

(B) Prior Art In a device provided with performance data storage means for storing performance data and the like input from a keyboard of an electronic musical instrument, a so-called event-type performance data storage method has conventionally been adopted (Japanese Patent Application Laid-Open No. 63-163). 193191). In this event-type performance data processing device, performance data input from a keyboard is stored as event data indicating a change in the key depression state of the keyboard with a key code or the like added.

(C) Problems to be Solved by the Invention However, in the performance data processing device of the conventional event type, at least for each key-on event and key-off event, at least event information (key-on event and key-off event) and a key code are stored in a memory. Must be kept. The key code in this case is the only code given directly to each key.
For this reason, the number of bits that can represent all keys is prepared, and this number of bits is given to each key code (for example, usually, 3 bits are given as octave information, and as pitch information, (The key code is composed of the octave information and the pitch information, and requires a total of 7 bits.) In order to record a long song, the memory capacity must be considerably increased.

An object of the present invention is to save memory by selecting appropriate pitch origin data from a plurality of pitch origin data and storing the difference between the pitch origin data and the key code at which the event occurred in a memory. It is an object of the present invention to provide a performance data processing device capable of performing the above.

(D) Means for Solving the Problems According to the invention of claim 1, there are provided input means for inputting performance data including pitch data, a performance data memory for sequentially storing performance data, and different musical ranges and different musical ranges of the musical ranges. Pitch origin storage means for storing a plurality of pitch origin data for specifying a pitch origin to be a reference when representing a middle pitch; origin storage means for storing one of the plurality of pitch origin data; Discriminating means for discriminating whether or not the pitch data input by the input means belongs to a designated range specified by the pitch origin data stored in the origin storage means; and pitch data input by the discriminating means. When it is determined that the pitch does not belong to the designated range, pitch origin data specifying the range including the input pitch data is selected from the pitch origin storage means, and the pitch origin data is Origin rewriting means for rewriting the origin storage means and writing the rewritten pitch origin data to the performance data memory; and converting the input pitch data to a relative value to the pitch origin data stored in the origin storage means. Writing means for writing to the performance data memory.

According to a second aspect of the present invention, there is provided a performance in which pitch origin data for designating a pitch origin which is a reference of a pitch and a pitch and pitch data representing the pitch of a musical tone to be produced as a relative value to the pitch origin data are sequentially stored. A data memory; reading means for sequentially reading data from the performance data memory in accordance with the progress of the performance; origin storage means for storing pitch origin data read by the reading means; Discriminating means for discriminating between origin data and pitch data; origin rewriting means for rewriting the origin storage means with the pitch origin data when the read data is pitch origin data; When the pitch data is high data, the pitch data is expressed as an absolute value based on the pitch origin data stored in the origin storage means. Characterized by comprising a conversion means for converting a high data.

According to a third aspect of the present invention, in the first aspect of the present invention, the pitch origin storage means is means for storing pitch origin data in correspondence with an identification code shorter than the pitch origin data,
The performance data memory is a memory for storing pitch origin data using the identification code.

The invention according to claim 4 comprises pitch origin storage means for storing a plurality of pitch origin data in correspondence with an identification code shorter than the pitch origin data, and storing the performance data memory using the identification code. Is stored in the memory.

(E) Operation In the performance data processing apparatus according to the first aspect of the present invention, when performance data is input, pitch data is converted into pitch origin correlation data correlated with predetermined pitch origin data. The pitch origin data is pitch data that is the origin of the pitch. In this case, the pitch origin data is selected from a plurality of pitch origin data. That is, a plurality of pitch origin data are set in all the pitches covered by the performance data processing device, and among them, the pitch origin data close to the input pitch data is selected. The pitch origin correlation data is, for example, pitch difference data between the pitch origin data and the pitch data. Then, instead of directly storing the pitch data, the converted pitch origin correlation data and the pitch origin data used for the conversion are stored in the performance data storage means. With such a configuration, first, one pitch origin data is stored, and as long as the pitch data that can be covered by the pitch origin data continues, the pitch data that is successively input is stored in the above-mentioned pitch origin data. The data is stored while being converted into pitch origin correlation data using the data. In the case where pitch data with a large pitch difference is input on the way, the pitch origin data is replaced.

In the above configuration, the pitch origin correlation data is obtained by converting the input pitch data into data correlated to one pitch origin data selected from a plurality of pitch origin data, and thus the number of bits is small. May be. It is necessary to store extra pitch origin data, but it is not necessary to store it for each key-on and key-off. Rather, the fact that the number of bits of the pitch origin correlation data can be small will greatly reduce memory consumption. For this reason, the storage capacity of the performance data storage means can be reduced.

Further, in the performance data processing device for restoring the stored data to the performance data by using the above-mentioned performance data storage means, after reading out the pitch origin data, the data is temporarily stored in a register or the like. The pitch origin correlation data read out is restored to the original pitch data using the above-mentioned pitch origin data. Then, a tone signal is formed from the performance data including the pitch data. Even in the performance data processing device configured as described above, the capacity of the performance data storage means can be reduced, and thus the cost of the entire device can be reduced.

(F) Embodiment FIGS. 1A and 1B show a configuration diagram of a performance data processing apparatus according to an embodiment of the present invention.

FIG. 1A shows an apparatus constituted by performance data input means 1, performance data conversion means 2, and storage means 3. The performance data input means 1 is composed of, for example, a keyboard.
The performance data conversion means 2 converts the pitch data in the input performance data into pitch origin correlation data correlated with predetermined pitch origin data. The predetermined pitch origin data is:
It is selected from a plurality of predetermined pitch origin data. The pitch origin data is a reference key code.
The pitch origin correlation data is, for example, difference data between the predetermined pitch origin data and the pitch data. Storage means 3
Is usually composed of RAM, and the performance data conversion means 2
The pitch origin correlation data converted in step is stored. Further, the storage means 3 also stores the predetermined pitch origin data.

FIG. 1 (B) is an apparatus for reading out the pitch origin correlation data stored in the storage means 3 using the storage means 3 of the apparatus of FIG. 1 (A) and converting it into a musical tone signal.

The storage means 3 stores pitch origin correlation data and the predetermined pitch origin data in the apparatus shown in FIG. 1 (A). The performance data restoring means 4 reads the pitch origin correlation data and the pitch origin data from the storage means 3 and restores the pitch origin correlation data to the original pitch data based on the pitch origin data. The tone signal forming means 5 forms a tone signal from the performance data including the restored pitch data.

2 and 3 are diagrams for explaining the outline of the operation of the above-mentioned performance data processing apparatus. FIG. 2 shows an example of data stored in the storage means 3, and FIG. 3 is a diagram showing a relationship between pitch origin data and pitch origin correlation data. In FIG. 3, the horizontal axis indicates the key arrangement direction, the left end indicates the lowest key, and the right end indicates the highest key.

Now, it is assumed that the pitch data of P1 is input by the performance data input means 1 (here, a key of the keyboard) in the configuration of FIG. At this time, the performance data conversion means 2 selects pitch origin data close to P1 from a plurality of pitch origin data. That is, the pitch origin data is TO3. At the same time, the performance data conversion means 2 generates the pitch data P1
Is converted into pitch origin correlation data correlated with the pitch origin data TO3. For example, if the correlation method is a subtraction method, pitch origin correlation data is (TO3-P1) = Δd1. That is, the pitch origin correlation data is Δd1. Note that note length data is actually stored after the pitch origin correlation data, but the description is omitted here. Subsequently, it is assumed that the pitch data P2 is input from the key. Here, the pitch origin data TO3 can cover the width of (TO3) in FIG. That is, pitch origin data can be used as pitch origin data for the pitch data within (TO3). Therefore, the pitch origin data P2
Since is within this (TO3), there is no change in the pitch origin data at this stage. That is, the pitch origin correlation data Δd1
Next, pitch origin correlation data Δd2 is stored.
Subsequently, it is assumed that the pitch data P3 has been input. This pitch data P3 is out of the range of (TO3). Therefore, the performance data conversion means 2 switches the pitch origin data from TO3 to TO1 when the pitch data P3 is input. Then, the pitch origin data TO1 is stored in the storage means 3, and subsequently, the pitch origin correlation data Δd3 is stored.

The pitch data is sequentially stored as described above. In such a storage method, the pitch origin correlation data Δd can be represented by a smaller number of bits. By properly selecting the pitch origin data, the octave bits (3 bits) conventionally required are of course unnecessary. Although it is necessary to store extra pitch origin data as compared with the conventional device, it is not necessary to store it for each key event, and it is necessary to store new pitch origin data when the pitch data jumps greatly. Is enough. Therefore, the memory capacity required for the pitch origin data is not so large, and the memory capacity can be considerably reduced as a whole.

In order to form a musical tone signal using the storage means shown in FIG. 2, the data stored in the storage means 3 is sequentially read out by the performance data restoring means 4 in the apparatus shown in FIG. 1 (B). When the pitch origin data is read, the pitch origin data is set in a register or the like, and thereafter, the read pitch origin correlation data and the original pitch data are restored from the pitch origin data. This restoration method may be performed in a manner reverse to the method of storing the pitch origin correlation data in the storage means 3.

[Explanation of specific embodiment]

[Description of Configuration] FIG. 4 is a block diagram of a sequencer according to an embodiment of the present invention. The CPU 10 controls the entire apparatus.
The melody memory 14 and the working memory 15 are composed of RAM. The ROM 16 stores, in addition to programs, tables and various parameters described later. Tone generator 17, CP
A tone signal is generated from the performance data passed from U10 and output from the speaker 18. Tempo clock generator 11
Interrupts the CPU 10 at regular intervals. The interruption is performed four times during the sixteenth note length according to the set tempo. In other words, in this device, the control resolution is 1
It is set to one-fourth of the note length. Key 12 is 61
It consists of keys. The operation switch 13 includes a tone setting switch for setting a tone, a track switch for specifying a track number, and a mode (record mode,
(Play mode, normal mode).

FIG. 5 is a schematic plan view of the operation switch 13. In the figure, a liquid crystal display 21 is disposed above an operation switch panel 20, and a switch group 22 including a tone switch and other switches is provided below the liquid crystal display 21. Two track switches 23 are arranged on the right side, and an LED 24 for displaying the mode of each track is provided on the right side. In this embodiment, the number of tracks is set to two. The upper LED (red) lights up when record mode is set for each track (1 or 2), and the lower LED when play mode is set.
(Green) lights up. Also, when in normal mode,
LED does not light. In this embodiment, only one of the two tracks can be set to the record mode, and both tracks cannot be set to the record mode at the same time. It is possible to have two tracks in play mode at the same time. Further, in the record mode, it is not possible to record a double tone, but only a single tone.

[Description of memory]

The melody memory 14 of this embodiment corresponds to the storage means of the present invention. FIG. 6 is a configuration diagram of the melody memory. As shown in the figure, the melody memory has a two-dimensional array structure, and data is sequentially stored in the direction of the arrow for each of the tracks TR1 and TR2. The address in the horizontal direction is specified by the pointer DP [TR]. For example, track TR =
1, when the music shown in FIG. 7 is input, the data arrangement is as shown in FIG. In addition, as described later,
The storage of the performance data is started when the track switch is operated and the track 1 is set to the record mode. In the first areas a and b, tone data set (or initialized) by the tone switch of the operation switch 13 is stored. Area a is the next area (here area b)
This is a code indicating that a tone color number (voice number) is stored in the. This code is represented by hexadecimal FB. In the next area c, pitch origin data is stored. Here, the pitch origin data is F4, the contents of which will be described later. In the next area d, data representing all rests is stored. In the next area e, data representing a half-rest is stored. In the following order, data representing a quarter rest and an eighth rest, respectively, are stored. After the rest data, interval origin correlation data and note length data are sequentially stored.

In this embodiment, the pitch origin correlation data is set as pitch origin difference data. The pitch origin difference data is data representing the difference between the pitch origin data (the key code indicated by it) and the stored pitch data (the key code of the pitch) (third data).
See figure). The pitch origin difference data and the note length data are represented by a total of 8 bits in this embodiment. The pitch origin difference data is represented by the upper 4 bits, and the note length data is represented by the following 4 bits. For example, in area h, 8 (1000) represents pitch origin difference data, and 3 (0011) represents note length data of eighth notes. For the reason described later, the pitch origin difference data of 8 (1000) indicates that the key code indicated by the data is a value obtained by adding 0 to the key code indicated by the pitch origin data. That is, the key code indicated by the pitch origin difference data stored in the area h is equal to the key code indicated by the pitch origin data stored in the area c. Further, the key code indicated by the pitch origin difference data of 6 (0110) stored in the area i is a value obtained by adding 2 to the key code indicated by the pitch origin data stored in the area c.

FIG. 9 shows the code and format of each data stored in the melody memory 14. In the figure, 00 to 0F indicate rest data, and 10 to EF indicate note data. F1 to FA indicate pitch origin data.

In the rest data, the upper 4 bits are 0, and the lower 4 bits are code length data. In the note data, the upper 4 bits constitute pitch origin difference data, and the lower 4 bits constitute note length data. In the pitch origin data, the upper 4 bits are represented by F, and the lower 4 bits represent the table number. FIG. 10 shows this table. The keyboard of this embodiment covers the pitches of slightly more than five octaves from C0 to G5. And within that range,
There are a total of 10 pitch origin data. The lowest pitch origin data is set to a pitch of F0 # (key code is 9), and the highest pitch origin data is set to a pitch of C5 (key code is 63).

FIG. 11 shows the contents of the pitch origin difference data indicated by 1 to E. For example, the fact that the pitch origin difference data is 8 indicates that the key code corresponding to the difference data is the value of the key code +0 indicated by the pitch origin data. Further, the fact that the pitch origin difference data is 1 indicates that the pitch data corresponding to the difference data is the value of the key code +7 indicated by the pitch origin data. From the table shown in FIG. 11, one interval origin data is obtained by adding the key code +7 indicated by the interval origin data to the right side of the keyboard (to the side with the larger code) centering on the key of the key code indicated by the interval origin data. Cover the range and cover the range of key code -6 indicated by the pitch origin data on the left side of the keyboard (on the smaller side of the code).

FIG. 12 shows note length data and the meaning of the data. According to this table, for example, note length data 3 is an eighth note. Note length data 5 is 16
This is data indicating that minute notes are continuous. For example, 4
The note length data 5 is used, for example, when a quasi-note is connected by a tie to the first note of the next bar. Details will be described later.

[Explanation of flowchart]

FIG. 13 is a flowchart showing the operation of the sequencer. Functions of the registers and flags appearing in the flowchart are described at the end of this specification.

[Main flowchart]

FIG. 13 shows a main flowchart. When the power is turned on, the process proceeds to n1, and initialization of various registers and the like is performed. Thereafter, key event processing is performed at n2, switch processing is performed at n3, and other processing is performed at n4. When n4 is completed, the process returns to n2 again, and then repeats n2, n3, and n4. Normally, the CPU 10 continuously executes n2, n3, and n4, but performs a tempo clock interrupt process each time there is an interrupt from the tempo clock 11. This will be described later.

[Switch processing]

Normally, switch processing such as tone setting is performed before operating the keyboard. FIG. 14 shows a flowchart of this switch processing.

First, it is determined whether or not there is a switch event in n10. If there is a switch event, the type of the event is determined in n11 to n13. When the track switch 23 shown in FIG. 5 is operated, the process proceeds to n14 or n15. When the tone switch 22 is operated, the process proceeds to n16, where n16 and n1
At 7, the track set to the record mode is determined.

First, an operation when any of the track switches 23 is operated will be described below.

When "1" of the track switch 23 is operated, n1
In step 4, the register TR storing the track number is set to 0. The fact that the register TR is 0 indicates that the track 1 has been designated. When "2" of the track switch 23 is operated, the register TR is set to 1 at n15. The fact that the register TR is 1 indicates that the track 2 has been designated. Then, the register RUN [TR] is looked at at n18.
This register RUN [TR] indicates the mode of the track indicated by TR. When the data of the register is 0, it indicates the stop mode, when it is 1, it indicates the record mode, and when it is 2, it indicates the play mode. Track switch 23
Each time the button is pressed, the mode advances to the next mode. The mode advances in a stop mode at first, then moves to a record mode, and then moves to a play mode. Pressing the switch again in the play mode returns to the stop mode.
Therefore, when RUN [TR] = 0 in n18, it means that the mode has shifted from the stop mode to the record mode. In this case, the process proceeds to n20 or less. When RUN [TR] = 1, it means that the mode has shifted to the play mode. In this case,
Proceed to n25 or less. When RUN [TR] = 2, it means that the mode has shifted from the play mode to the stop mode. In this case, n35 or less is executed.

RUN at n20 first when entering record mode
Set [TR] to 1 and set n21 to the red L
Turn on the ED. Further, the register DP [TR] is set to 0 at n22. This DP [TR] is a pointer of the melody memory of the track indicated by TR (see FIG. 6). Also, FF is set in the register KONC as an initial value. This KONC stores the key code of the key that is turned on. Here, FF which is not an actual key code is set as an initial value. In n22, 1 is put into the register KOF. This KO
F stores the state of the most recently pressed key. KOF
Is 1 when it is key-off, and when KOF is 0 it is key-on. Also register
Set the voice (sound) number in VOICE [TR]. V
OICE [TR] is a register that stores the voice number of the track indicated by TR.

When set to play mode, first run at n25
Set [TR] to 2 and n26 of the LED of the corresponding track,
Turn off the red LED and turn on the green LED. Next, n27
To see the state of KOF. If the most recently pressed key is in the key-on state, the process proceeds to n28. In this case,
It is necessary to store note data (consisting of pitch origin difference data and note length data) for the last key pressed key when the mode has shifted from the record mode to the play mode. Further, it is necessary to store end data as the last data of the stored data. n28 and n29 are steps for performing these processes. That is, in n28, a subroutine (record processing) for storing note data is executed, and in n29, FF (see FIG. 9) indicating end data is set to the pointer DP [TR] in the melody memory of the track indicated by TR. FF is stored in the area indicated by.

After the end of n29, the pointer DP [TR] of the track indicated by TR is set to 0 in n30. This is a preparation for reading data from the first area of the melody memory indicated by TR. Also, the stack pointer SP
[TR] is set to 0. SP [TR] is a register used when a musical score has a repeat symbol. This will be described later. Further, in n30, 0 is set in DATA [TR] and the buffer N
Put the first data in the melody memory into EXT [TR]. This NEXT [TR] is a buffer register for reading and storing 1-byte data from the melody memory in advance. At this stage of n30, DP (TR) is 0 in NEXT [TR].
Therefore, the first data of the track indicated by [TR] is stored. Then, 1 is set to NLEN [TR]. In this way, the initialization of the reproduction is performed.

If RUN [TR] = 2 in n18, it means that the mode changes from the play mode to the stop mode.
R] is set to 0, and all LEDs are turned off at n36.

When the switch event at n10 is a tone switch event, the process proceeds to n16 and n17 to determine the track in the record mode. If neither the track 1 nor the track 2 is in the record mode, the process returns. When the track 1 is in the record mode, TR = 0 is substituted in n40. When track 2 is in record mode, TR = n41
Substitute 1. Then, in n42 to n46, the voice number (tone number) is stored in the melody memory.
First, at n42, the voice number is stored in the register VOICE [T
R]. This voice number is set by a switch. Next, the FB is stored in the melody memory at n43. This FB is a voice set code (see FIG. 9). Subsequently, the pointer is advanced by one at n44. And in n45
Store the voice number set in VOICE [TR] in the melody memory. Further, the pointer is advanced by one at n46 and the routine returns.

Record of Performance Data [Key Event Processing] The record of performance data is sequentially performed by depressing or releasing a key on the keyboard.

FIG. 15 is a flowchart which is processed when a key on the keyboard is depressed.

At n60, the presence or absence of a key event is determined. If it is a key-on event, key-on processing is performed at n62. If it is a key-off event, key-off processing is performed at n80.

In the case of a key-on event, it is determined in n63 whether one of the two tracks is in the record mode. If either is in the record mode, the process proceeds to n64, and the track number in the record mode is set to TR. Then, the process proceeds to n65, where the code set in the register KONC is determined. This KONC stores the key code of the key that is turned on. If this code is O, that is, if it is a code representing a rest set in n85 described later, the process proceeds to n66 and a "record process" subroutine is called. That is, when the data of the KONC is O indicating a rest, the process proceeds to a subroutine of "record processing" to perform a rest record processing.

Next, the content of the register KONC is determined at n67. In other words, see if this KONC is FF. As shown in the step n22 in FIG. 14, when the track 1 is first set to the record mode, the unused data FF is set in the KONC. Therefore, in this n67, KONC is FF at the first key-on, so n6
Proceed to 8. At n68, FB, which is a voice set code, is stored in the area MD [TR] of the melody memory indicated by the pointer DP [TR]. Further, the pointer is advanced by one. Subsequently, in n69, VOICE [TR] is stored in the melody memory indicated by the pointer. This VOICE [TR]
When the tone switch is not operated as the previous process, the (n22) voice data set at that time when the mode is converted is set in advance. When the tone switch is operated prior to the key-on, since n42 and below in FIG. 14 are executed, the VOICE [T
R] will be stored. This means that voice data is stored twice, but does not affect operation. When the above store is completed, the pointer is advanced by one.

Next, the content of the register KOF is determined at n70. This KOF stores the state of the last key pressed. KOF =
0 indicates a key-on state, and KOF = 1 indicates a key-off state. When KOF = 0 in n70, "record processing" in n71 is called as a subroutine. These n70 and n71 have the following meanings. In other words, until one key is turned on and the next key is turned on, normally the first key is turned off and the next key is turned on, but the next key is kept on while the first key is turned on. When turned on, the previously turned on key is treated as being turned off. That is, when the previous key is kept key-on, the process proceeds from n70 to n71, where "record processing" is executed for the key that was previously turned on.

Then, the key code of the key turned on to KONC is set in n72, and the registers CNT and KOF are cleared in n73. CNT is a counter that counts the time from key-on or key-off. This CNT counts time at intervals of dividing one bar into 64 equal parts. The KOF stores the state of the last key pressed as described above. That is, being set to 0 means that the last key pressed is in the key-on state.

Subsequently, the processing of the key-off event will be described. At the time of a key-off event, data of a key that has been turned on (note data) is basically stored. First, a key-off process is performed in n80, and it is determined in n81 whether any of the two tracks is in the record mode. If any are in the record mode, go to n82.
Then, it is determined whether or not the key code of the key that has been turned off is the same as the key code stored in the KONC.
If they are not the same, the process returns as it is not necessary to store the note data of the keys stored in the KONC yet. If "YES", the process proceeds to n83, where the number of the track in the record mode is set to TR. Next, proceeding to n84, a subroutine call is made for "record processing". That is, "record processing" is performed on the key stored in the KONC in "record processing". And n8
At 5, KOF is set to 1 and CNT is reset. By resetting the CNT, the time is counted again from this time. In other words, it means that rest counting is performed thereafter. Subsequently, in n86, O, which is data representing a rest, is set in KONC and the routine returns.

By the above operation, when there is a key-on event, the CNT operates to count the note length of the note, and when there is a key-off event, the note data thereof is recorded. At the same time, the note length of the rest is counted by the CNT, and when there is a new key-on event, the rest data is recorded (n66). This operation is repeated, and notes and rests are sequentially stored in the melody memory.

[Record processing]

“Record processing” is shown in FIG. This flowchart is composed of three subroutines of "pitch (REC)" processing of n90, "note length (REC)" processing of n91, and "STORE processing" of n92.

[Pitch (REC) processing]

 This will be described with reference to FIG.

First, it is determined whether or not KONC is O in n100. KONC = 0 means that the data to be recorded is rest data. If it is the rest data, go to n112 and register DKC
Clear The DKC stores pitch origin difference data representing a difference between the key code and the pitch origin data, as described later. However, in the case of rest data, clear this DKC.

If it is a note data record, the process proceeds to n101. Here, BKC [TR] is subtracted from the register KONC that contains the key code of the note to be recorded, and the result is expressed as D
Put in KC. BKC [TR] is a register that stores pitch origin data. However, when recording the first note data, BKC [TR] contains appropriate initial data. In this n101, the difference between the key code of the note to be recorded and the key code indicated by the pitch origin data is obtained,
The result is stored in the DKC that stores pitch origin difference data.
Subsequently, the pitch origin difference data that entered the DKC at n102 is D
It is determined whether the KC is within a coverable range (see FIG. 3). As shown in FIG. 11, the range that the DKC can cover is a range from the key code -6 indicated by the pitch origin data to the key code +7 indicated by the pitch origin data. In n102, you will see if the DKC data is within this range. If it is within that range, n111
Proceed to. In n111, subtract DKC from 8 and put the result back into DKC. This calculation is for converting the key code difference into pitch origin difference data representing the key code difference. In FIG. 11, 1 to E in the left column indicate pitch origin difference data of this chord expression.

If DKC is not within the above range in n102, n103
In the following, new pitch origin data is selected. The selection of the pitch origin difference data is performed by selecting the pitch origin data close to the KONC data. First, KONC at n103
Is divided by 6. The result is stored in a register n. Then, the size of n is determined at n104 and n105. And n
In this field, enter 1 or 10 or the integer part of the above division result. Further, at n109, F is inserted into the upper 4 bits of the area of the melody memory indicated by the pointer DP [TR], and n is inserted into the lower 4 bits. Here, the upper four bits F are codes indicating that the lower four bits of data (indicated by n) are pitch origin data (see FIG. 9). The data represented by n of the lower 4 bits represents the number of the table shown in FIG. 10 (see FIGS. 9 and 10).

FIG. 18 is an explanatory diagram when a new pitch origin data is determined below n103. The area A in the figure is the above n103
In the following, the range covered by a total of ten pieces of pitch origin data used when selecting one pitch origin data is shown. An area B indicates a range covered by one pitch origin data selected by using the area A. Here is an example. For example, assume that the result calculated in n103 is 3. This 3 enters register n. As a result, in n109, F3 is stored in a predetermined area of the melody memory. That is, the pitch origin data of table number 3 is selected. Referring to FIG. 10, in the pitch origin data of table number 3, the key code is
21.

In n110, the key code indicated by the pitch origin data selected as described above is temporarily entered in BKC [TR], and BKC [TR] is subtracted from KC containing the key code,
The result is put into DKC. In this process, the key code difference is stored in the DKC. Then, in n111, the content of the DKC is converted as described above, and the pitch origin difference data is re-entered in the DKC.

[Note length (REC) processing]

 This will be described with reference to FIG.

In the "note length (REC) processing", the note length of a note or the rest is known by using the counted content of the CNT.

First, the register L is reset at n120. This register L corresponds to the "CONTINU" of the note length data 5 shown in FIG.
Count the number of times "E". Then, register NLEN [T
R] is set to FF. This NLEN [TR] is used to store the note length data (1 to 5). Initially, the FF of unused data is set as an initial value.

In n121, the count value of the CNT is determined. As described above, the resolution of the control of the CPU is one-minute note length. However, in the actual processing, the error range is such that the count value of the CNT is 2 in the positive direction and 1 in the negative direction. For example, the count value of the CNT corresponding to a whole note is 64, but if nCNT is 63 or more in n122, it is determined that the note is a whole note. In steps n122 to n126, processing corresponding to the length of each note is performed. The reason for subtracting the length of each note from the CNT and resetting the result to the CNT is to determine whether or not the processing of “CONTINUE” is required in n127 or less in the next step. For example, when a whole note is tied to the next bar in a tie, the CNT becomes larger than 64, but when the CNT is subtracted by 64, the rest is reset to the CNT. In n127, the reset CNT is 2
It is determined whether or not exceeds. If it does not exceed 2, it is considered to be within the error range and the process returns. If CNT exceeds 2, go to n128 and CNT−
Execute Step 4. Further, L + 1 is executed. And again
Return to n127. Executing CNT-4 is one CONTINUE
Indicates the length of 16 minutes, that is, the length of four counts. L is a counter that counts the number of “CONTINUE” as described above. As will be described later, by looking at this L, it becomes possible to perform restoration processing of a sound that extends over two or more measures and a sound that cannot be represented by 2,4,8,16th notes.

In n122 to n126, predetermined data is further set in NLEN [TR]. The predetermined data is any of the note length data (0 to 5) shown in FIG. If the note length cannot be represented by the respective note length data (for example,
Half notes, tied half notes and eighth notes, etc.)
The processes of n127 and n128 are performed in the same manner as described above, and are represented by CONTINUE. For example, in the case of a half note, 1 is set to NLEN [TR] (n123).

[STORE processing]

FIG. 20 shows the “STORE process”. In this “STORE process”, the pitch origin difference data calculated in FIG.
The note length data calculated in FIG. 19 is stored in the melody memory.

First, in n130, it is determined whether or not NLEN [TR] is FF. If the contents of this register are FF, CNT is 2 or less. That is, the process directly returns from n121 in FIG. That is, the counting time of the CNT has not reached the length corresponding to the sixteenth note length. In this case, the process returns.

When any of the note length data 0 to 4 (see FIG. 12) is set in NLEN [TR], the process is performed in n131. Here, first, the lower 4 bits of DKC are put into the upper 4 bits of the register DATA [TR]. This DATA
[TR] is used as a buffer for temporarily storing data to be stored in the melody memory or for temporarily storing data read from the melody memory. Then, the lower 4 bits of NLEN [TR] are set in the lower 4 bits of DATA [TR]. The DKC stores pitch origin difference data in the “pitch (REC)” processing of FIG. Since the pitch origin difference data is represented by 4 bits (1 to E), the lower 4 bits indicate the pitch origin difference data. NLEN [TR] represents the note length data from (0 to 4) from FIG. That is, pitch origin difference data is set in the upper 4 bits of DATA [TR], and note length data is set in the lower 4 bits. At this stage, the format of the note data is completed (see FIG. 9). And
Proceed to n132, and the data of DATA [TR] is changed to the pointer DP [TR]
Is stored in the area of the melody memory indicated by.
Then, the pointer is advanced by one at n133. next
At n134, it is determined whether or not L is 0. If L is 1 or more, it indicates "COTINUE" and n
Continue to 135. Here, the upper 4 bits of DATA [TR] are DKC
The lower 4 bits of That is, pitch origin difference data is entered. Then, 5 is put in the lower 4 bits of DATA [TR]. This 5 is code length data representing "CONTINUE" as shown in FIG. Subsequently, L is subtracted by one and n132 and below are executed again. In this way, data relating to “CONTINUE” is stored in the melody memory until L = 0.

The performance data is recorded in the melody memory by the above operation.

Reading Performance Data Next, the operation of reading the performance data stored in the melody memory will be described. This read operation is performed in the play mode. The play mode is set by operating the track switch 23 to turn on a green LED. In the play mode, as described later, data is read from the melody memory and processed by a subroutine call of "READ processing".

FIG. 21 is a flowchart showing the operation of the "READ process".

[READ processing]

First, in n140, the content of NEXT [TR] is set to DATA [TR]. NEXT [TR] contains data to be processed next. The data to be processed next is transferred to DATA [TR] in which data to be processed is stored.
Then, the pointer is advanced by one (n141). Subsequently, the data in the melody memory area indicated by the pointer DP [TR] is moved to NEXT [TR] in preparation for the next processing.

After the above preparations are completed, the content of DATA [TR] is determined in n143. Data is 00 to FF as shown in FIG.
, Each subroutine call from n144 to n150 is performed by checking the contents of the data. For example, if DATA [TR] = F1, a subroutine call is made to "pitch origin processing" of n145. Hereinafter, n144 to n1
Each of the 50 processes will be described.

FIG. 22 shows the process of “pitch origin processing”. Here, first, the lower 4 bits of DATA [TR] are put into register j, and the key code of the table number represented by j is set to TA.
Read from BLE and set to BKC [TR]. Now, BK
The pitch origin data is set in C [TR].

When DATA [TR] = FB in n143, “VOIC” in n146
In the subroutine, "E processing" is called. In this subroutine, the data of NEXT [TR] is first put into VOICE [TR] as shown in Fig. 23. That is, the voice number is set in NEXT [TR]. The voice number is set to VOICE [TR], and the track number and voice number are output to the sound source (TG) 17 at n171. The sound source (TG) 17 automatically receives the data to receive the data. In n172, the pointer is advanced by one, and in n173, the data in the area of the melody memory 14 indicated by the pointer is NEXT.
Set to [TR].

When DATA [TR] = FC in n143, the “REPEAT process” of n147 is called as a subroutine. Also DATA
When [TR] = F0, a subroutine call is made to the “RETURN processing” of n144. The subroutines n144 and n147 are executed when the music is repeated within a certain range. Data about the repeat is stored in the melody memory. For example, as shown in FIG.
It is assumed that data is stored in the. In this case, in the play mode, first, a code indicating REPEAT is found in the area M1, and the next data in the area M2 is recognized as a start address of a portion to be repeated. Assuming that the start address is M3, the address indicated by the pointer is set to M3. At this time, the stack pointer is M2
The next address, M5, is set. When the pointer indicates M4, a RETURN code is found, and the area M5 set in the stack pointer is set as the address indicated by the pointer. This allows the area from area M3 to area
The songs recorded in the range up to M4 will be repeated.

In n143 of FIG. 21, when DATA [TR] = FC,
A "REPEAT process" is called as a subroutine. In this subroutine, as shown in FIG. 24, a process centered on changing the address indicated by the pointer and processing the stack pointer is performed. FIG. 26 shows this “REPEAT processing”. First, in n180, the address next to the address indicated by the data pointer (area M5 in FIG. 24) is stored in the stack register RSTC indicated by the current stack pointer SP [TR].
Move to [TR] [SP [TR]]. That is, in the example of FIG. 24, the address of the area M5 is set in the stack register RSTC [TR] [SP [TR]] indicated by SP [TR]. Subsequently, the stack pointer is advanced by one (n181). Next, NEXT
[TR] data is set in the pointer DP [TR]. At this stage, for example, in the example shown in FIG.
Is set. Subsequently, in n183, the data in the melody memory area indicated by the pointer is NEXT.
Set to [TR]. In the example shown in FIG. 24, the data of the area M3 is set in NEXT [TR].

Next, the operation when the "RETURN process" of n144 is called as a subroutine in FIG. 21 will be described with reference to FIG. In this process, first, at n190, it is confirmed whether or not the stack pointer is positive. Subsequently, the stack pointer is returned by one at n191. Next, at n192, the contents of RSTC [TR] [SP [TR]] indicated by the stack pointer are moved to the pointer DP [TR]. In the example shown in Fig. 24, DP [TR]
Is set to the address of the area M5. Then, in n193, the data in the melody memory area indicated by the data pointer DP [TR] is moved to NEXT [TR].

26 and 27, it is possible to freely repeat a part of the music. Needless to say, it is also possible to set a music repetition loop in the music repetition loop.

Next, in the "READ processing" of FIG.
The operation when the code length data or FF is read will be described. If DATA [TR] is 10 to EF, a subroutine call is made to "note processing" of n148. FIG. 28 is a flowchart of this "note processing". First, in n200,
A subroutine call is made for "pitch processing", and then a subroutine call is made for "note length processing" in n201. And
At n202, the track number, key code, and key-on information are output to the sound source 17. The sound source 17 starts sounding when receiving the information.

FIG. 29 is a flowchart showing the operation of the “pitch processing” of n200. First, in n210, the upper 4 bits of DATA [TR] are put into DKC. The upper 4 bits of DATA [TR] are pitch origin difference data (see FIG. 9). At this stage, the pitch origin difference data to be entered into the DKC is data in a code expression (see FIG. 11). Therefore, in n211 the pitch origin difference data in the code expression is converted into the key code difference of the key code indicated by the pitch origin data. Furthermore, n212
In, the difference data is added to the pitch origin data and converted into an actual key code, and the data is entered into the KC as a key code.

FIG. 30 is a flowchart showing the operation of "note length processing". First, in n220, the lower 4 bits of DATA [TR] are
Put in NLEN [TR]. The lower 4 bits of DATA [TR] represent code length data (see FIG. 9). Then, in n221, the value of the note length data is determined. The note length data is one numerical value from 0 to 5. If the note length data is, for example, 0
When, the note length means a whole note. In this case, n222 is executed. That is, 16 is set in NLEN [TR]. Here, the value 16 indicates that it is 16 times the sixteenth note length which is the resolution of this device. This NLEN [TR]
Stores the preset value at this stage. Thereafter, as time elapses, NLEN [TR] is subtracted as described later.

When the data read from the melody memory area is note data, the pitch processing shown in FIG.
"Note length processing" in the figure is performed. On the other hand, when the data read from the melody memory area is rest data, the subroutine n149 in FIG. 21 is executed. In this case, only the “note length processing” in FIG. Done.

[Tempo clock interrupt processing]

As will be described with reference to FIG. 4, the tempo clock 11 generates four interrupt clocks for a note length of 16 minutes in accordance with the tempo at that time. FIG. 31 is a flowchart showing the operation of the "tempo clock interrupt processing".

In this interrupt processing, the track designation is set to the initial value of track 1 (TR ← 0) at n300, and the mode is determined at n301. When it is determined that the mode is the play mode, the process proceeds to n302. Here, read the counter COUNT,
See if the remainder when dividing that value by 4 is zero. COUN
T is a running counter, which keeps counting up each time the interrupt processing starts after the power of the apparatus is turned on (n307). In other words, this COUNT is 64 between bars
Count. n303 is a step for executing the next n304 only once for four interrupts. That is, 4
The "PLAY process" is performed only once for each interrupt. This is because the CPU control resolution is set to a note length of 16 minutes. After the PLAY process, the track number is increased by one and the process returns to n301 again. Then, similarly, the processing of n301 to n304 is performed, and it is determined whether or not the processing has been completed for the two tracks in n305, and when it is determined that the processing has been completed, the process proceeds to n307. In n307, the counters COUNT and CNT are increased by one.

[PLAY processing]

FIG. 32 is executed in n304. The flowchart of the "PLAY process" is shown.

First, in n310, the note length data set in NLEN [TR] is reduced by one. Next, it is checked whether or not the note length data is 0 as a result. If it is not 0, the process returns. If NLEN [TR] = 0, it is determined whether the data of DATA [TR] being processed is note data or other data (n31).
2). If it is not note data, "READ processing" is performed and the routine returns. In the case of note data, it is determined in n313 whether the data at the next address is also note data. That is, the data of the next address is stored in NEXT [TR] at n142 in FIG. If the next data is also note data, there is a possibility of "CONTINUE". Therefore, in the next n314, the lower 4 bits of NEXT [TR] are put into the register X, and it is determined whether or not the value is 5 in n315. If it is 5, "CO
NTINUE "process, so go to n316
Make a subroutine call for "CONT processing". In n313, if the next data is not note data, the flow advances to n317 to output the track number and key-off information at that time to the sound source 17. When X is not 5 in n315,
That is, even when it is not necessary to execute “CONTINUE”, the process proceeds to n317. Then, the process proceeds to n318, where a subroutine call of “READ processing” is performed. In this way, the “READ process” is executed for each note or rest, and the sound source 17 performs processes such as sound generation.

The “CONT process” in n316 is executed according to the flowchart shown in FIG. First, proceed to n320. Here, NL
EN [TR] is set to 1 indicating a 16-minute note length, and DATA [T
R] is set to the next note data or rest at the time point of n313. Then the pointer is advanced by one. Next, in n321, the data of the melody memory area indicated by the pointer is moved to NEXT [TR]. Next, a subroutine call of “pitch processing” is performed in n322, and note data and note length data are sent to the sound source 17. The note data and note length data in this case are NEXT at the time of n312 in FIG.
It is the same as the data stored in [TR]. And
Proceeding to n323, the track number and the key code are output to the sound source 17. By the above “CONT processing”,
For example, restoration of a musical tone as shown in FIG. 25 becomes possible.

With the above configuration and operation, the melody memory 14 stores the performance data in a compressed form, and in the play mode, the data can be correctly restored and output as a tone signal. In this embodiment, since the key-on event information and the key-off event information are not stored, the memory can be further saved.

In the embodiment, the pitch origin data is indicated by the table number as shown in FIG. 10, but the key code itself corresponding to the pitch origin data may be stored. Similarly, the pitch origin difference data was stored as a code expression,
The difference data between the pitch origin data and the pitch data can also be directly stored. Although the key code is represented by continuous data, the present invention can be applied to a case where the key code is composed of a combination of an octave code and a note code.

〔register〕

(RUN [TR]) ··· Mode register indicating recording / playback / stop state.

 0: Stop, 1: Record, 2: Play (TR) ... Register that stores the track number.

(DP [TR]) ··· Pointer of melody memory.

(VOICE [TR]) Register for storing the voice number.

(MD [TR] [X]) ··· Melody memory.

(KOF): Flag for storing the state of the last key pressed.

0: Key-on, 1: Key-off (CNT): Counter that counts the time from key-on or key-off.

(KONC) ··· Register that stores the key code of the key that was turned on.

(KC): Register for storing the key code indicated by the pitch origin difference data read from the melody memory during playback.

(COUNT) ··· A counter that counts running from 0 to 63.

(BKC [TR]) ··· Register where pitch origin data is set.

(TABLE [i]): table storing pitch origin data.

(DKC) ··· Register where pitch origin difference data is set.

(NLEN [TR]) ··· Register where note length data is set.

(L)... Register in which the number of CONTINUEs is set.

(PATA [TR]) Register where data loaded (or stored) from melody memory is set.

(NEXT [TR]) ··· Register where data of the next address of PATA [TR] is set.

(RSTC [TR] [i]): Stack register that stores the return address when a repeat call is made.

(SP [TR]): Stack pointer.

(G) Effects of the Invention According to the present invention, since pitch data in performance data is converted into pitch origin correlation data correlated with pitch origin data and stored in the memory, memory is saved. In particular, there is an advantage that the memory saving effect is very remarkable particularly when storing long music pieces. Since the pitch origin correlation data is stored in the performance data storage means together with the reference pitch origin data, the original pitch data can be restored from these data.

[Brief description of the drawings]

FIGS. 1A and 1B are basic configuration diagrams of an embodiment of the present invention. 2 and 3 are diagrams for explaining the operation of the embodiment. FIG. 4 is a block diagram of a sequencer as a specific embodiment of the present invention, FIG. 5 is a plan view of an operation switch panel, FIG. 6 is a schematic configuration diagram of a melody memory, and FIG.
The figure shows an example of music stored in the melody memory,
FIG. 8 is a diagram showing data in the melody memory storing the music of FIG. FIG. 9 is a diagram showing a format of data stored in the melody memory, and FIG.
FIG. 11 is a diagram showing the correspondence between data representing the difference between the pitch origin data and the pitch data and the pitch origin difference data in the code expression. FIG. 12 is a diagram showing note length data. FIGS. 13 to 17, FIGS. 19 to 23, FIGS. 26 to 33 show CPs.
6 is a flowchart showing the operation of U. FIG. 18, FIG. 24, and FIG. 25 are diagrams provided for explanation of the above-mentioned flowchart. 1 ... performance data input means, 2 ... performance data conversion means, 3 ... storage means, 4 ... performance data restoration means, 5 ...
... musical sound signal forming means.

Claims (4)

(57) [Claims] An input means for inputting performance data including pitch data, a performance data memory for sequentially storing performance data, and a pitch which is used as a reference when different ranges and pitches in the range are represented. Pitch origin storage means for storing a plurality of pitch origin data designating the origin; origin storage means for storing one of the plurality of pitch origin data; Discriminating means for discriminating whether or not the pitch origin data stored in the storage means belongs to a designated range specified; and when the discriminating means determines that the inputted pitch data does not belong to the designated range. When the pitch origin data specifying the range including the input pitch data is selected from the pitch origin storage means, and the origin storage means is rewritten with the pitch origin data. Origin changing means for writing the rewritten pitch origin data into the performance data memory; converting the input pitch data into a relative value with respect to the pitch origin data stored in the origin storage means; A performance data processing device comprising: writing means for writing. 2. A method according to claim 1, wherein pitch origin data for designating a pitch origin which is a reference of a pitch and a pitch, and pitch data expressing a pitch of a musical tone to be produced as a relative value to said pitch origin data are sequentially stored. Performance data memory; reading means for sequentially reading data from the performance data memory as the performance progresses; origin storage means for storing pitch origin data read by the reading means; and data read by the reading means Discriminating means for discriminating whether the data is pitch origin data or pitch data, and origin rewriting means for rewriting the origin storage means with the pitch origin data when the read data is pitch origin data; When the data is pitch data, the pitch data is expressed as an absolute value based on the pitch origin data stored in the origin storage means. Performance data processing device including a converting means for converting an absolute tone pitch data, a being. 3. The pitch origin storage means is means for storing pitch origin data in correspondence with an identification code shorter than the pitch origin data. The performance data memory stores the pitch origin data using the identification code. The performance data processing device according to claim 1, wherein the performance data processing device is a memory for storing the performance data. 4. A pitch origin storing means for storing a plurality of pitch origin data in correspondence with an identification code shorter than the pitch origin data, wherein the performance data memory stores the pitch origin data using the identification code. 3. The memory according to claim 2,
3. The performance data processing device according to 1.