JPH03204692A - Play data processor - Google Patents

Abstract

PURPOSE:To save a memory by converting pitch data in play data into interval origin correlative data correlating with interval origin data and storing the converted data in a storage means together with reference interval origin data. CONSTITUTION:This arithmetic data processor consists of a play data input means 1, a play data converting means 2, and the storage means 3 and the play data input means 1 consists of, for example, a keyboard. The play data converting means 2 converts the pitch data in the input play data into the interval origin correlative data correlating with the specific interval origin data. The specific interval origin data is selected among plural predetermined interval origin data. The storage means 3 consists normally of a RAM and is stored with the interval origin correlative data converted by the play data converting means 2 and this storage means 3 is further stored with the specific interval origin data. Consequently, the memory is saved.

Description

DETAILED DESCRIPTION OF THE INVENTION Field of the Invention The present invention relates to a performance data processing apparatus that includes a performance data storage means for storing performance data.

(bl Prior Art) A so-called event-type performance data storage system has been adopted in devices equipped with a performance data storage means for storing performance data etc. input from the keyboard of an electronic musical instrument (Japanese Patent Laid-Open No. 63-193191 In this event-type performance data processing device, performance data input from the keyboard is stored as event data indicating a change in the state of pressed keys on the keyboard with a key code or the like added thereto.

(C) Problems to be Solved by the Invention However, in the conventional event-type performance data processing device, each time a key-on event occurs,
A small amount of event information (key-on events and key-on events) and a key code must be stored in memory. In this case, the key code is the only code directly given to each key. For this reason, we prepare a number of bits that can represent each key, and give this number of bits to each key code (for example, normally 3 bits are given as octave information, and 3 bits are given as pitch information). (The key code consists of this octave information and pitch information, requiring a total of 7 bits), which had the disadvantage that the memory capacity had to be considerably large to record long songs.

The purpose of this invention is to save memory by selecting appropriate pitch origin data from a plurality of pitch origin data and storing in memory the difference between the pitch origin data and the key code where the event occurred. An object of the present invention is to provide a performance data processing device capable of processing data.

(d) Means for Solving the Problem This invention provides a performance data input means and a pitch origin correlation that correlates pitch data in the input performance data with predetermined pitch origin data among a plurality of pitch origin data. The musical instrument is characterized by comprising means for converting into data, and performance data storage means for storing the converted pitch origin correlation data and the predetermined pitch origin data.

Further, reading out the pitch origin correlation data of the performance data storage means and the performance data storage means in which the pitch data in the performance data is stored as interval origin correlation data with the interval origin data, The pitch origin data includes means for restoring original pitch data based on the pitch origin data, and means for forming a musical tone signal from performance data including the restored pitch data. The correlation data is characterized in that it is pitch difference data between pitch origin data and pitch data.

fe) Operation In the performance data processing apparatus according to claim 1 of the present invention, pitch data is converted into pitch origin correlation data that correlates with predetermined pitch origin data when performance data is input. 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 within all pitches covered by the performance data processing device, and pitch origin data close to the input pitch data is selected from among them. The pitch origin correlation data is, for example, pitch difference data between pitch origin data and 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 this configuration, first, one piece of pitch origin data is stored, and then, as long as there is pitch data that can be covered by that pitch origin data, the pitch data that is input one after another is stored as the pitch origin data. is used to convert it into pitch origin correlation data and store it. If pitch data whose pitches are far apart is input midway through, the pitch origin data is changed.

In the above configuration, the pitch origin correlation data is obtained by converting the input pitch data into data that correlates with one pitch origin data selected from a plurality of pitch origin data, so the number of bits is small. It's fine. Although it is necessary to store extra pitch origin data, it is not necessary to store it for each key-on and key-off, and in fact, the fact that the number of bits of pitch origin correlation data is small greatly reduces memory consumption. Therefore, the storage capacity of the performance data storage means can be reduced.

Furthermore, in a performance data processing device that uses the performance data storage means described above and restores the stored data to performance data, after reading the pitch origin data, the data is temporarily stored in a register or the like, and then The pitch origin correlation data read out is restored to the original pitch data using the pitch origin data.

Then, musical tone signals are formed from performance data including pitch data. Even with the performance data processing device configured in this way,
Since the capacity of the performance data storage means is small, it is possible to reduce the cost of the entire apparatus.

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

FIG. 1A shows an apparatus comprised of 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 that correlates with predetermined pitch origin data. The predetermined pitch origin data 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. The storage means 3 is
It is usually composed of a RAM and stores the pitch origin correlation data converted by the performance data converting means 2. Furthermore, this storage means 3 also stores the predetermined pitch origin data.

FIG. 1(B) shows an apparatus that uses the storage means 3 of the apparatus shown in FIG. 1(A) to read pitch origin correlation data stored in the storage means 3 and convert it into a musical tone signal.

In the storage means 3, pitch origin correlation data and the predetermined pitch origin data are stored in the apparatus shown in FIG. 1(A).

The performance data restoring means 4 reads the interval origin correlation data and the interval origin data from the storage means 3, and restores the interval origin correlation data to the original pitch data based on the interval origin data. The musical tone signal forming means 5 forms musical tone signals from the performance data including the restored pitch data.

FIGS. 2 and 3 are diagrams for explaining the outline of the operation of the above performance data processing device. FIG. 2 shows an example of data stored in the storage means 3, and FIG. 3 is a diagram showing the relationship between pitch origin data and pitch origin correlation data. In FIG. 3, the horizontal axis indicates the direction in which the keys are arranged, with the left end representing the lowest pitched key and the right end representing the highest pitched key.

Now, in the configuration shown in FIG. 1(A), it is assumed that pitch data of Pl is inputted by the performance data input means 1 (keyboard keys in this case). At this time, the performance data converting means 2 selects pitch origin data close to Pi from among the plurality of pitch origin data. In other words, the pitch origin data is TO3
It is. At the same time, the performance data converting means 2 converts the pitch data P1 into pitch origin correlation data that correlates with the pitch origin data TO3. For example, if the correlation method is the subtraction method, the pitch origin correlation data is (TO3P1) = Δ
It becomes dl. That is, the pitch origin correlation data becomes Δdl. Note that note length data is actually stored after this interval origin correlation data, but its explanation will be omitted here. Assume that pitch data P2 is then input from the key. Here, the pitch origin data TO3 can cover the width (TO3) in FIG. In other words, pitch data within (TO3) can be used as pitch origin data. Therefore, since pitch origin data P2 is within this (TO3), there is no change in pitch origin data at this stage. . That is, after the pitch origin correlation data Δdl, the pitch origin correlation data Δd2 is stored. Next, pitch data P3
Suppose that is input. This pitch data P3 is (TO3)
is outside the range of Therefore, the performance data converting means 2 switches the pitch origin data from TO3 to TOI when this pitch data P3 is input. And storage means 3
The pitch origin data TO1 is stored in , followed by the pitch origin correlation data Δd3.

In the above manner, pitch data is sequentially stored. With such a storage method, the pitch origin correlation data Δd can be expressed with a smaller number of bits. By appropriately selecting pitch origin data, octave bits (3 pintos), which were conventionally necessary, are of course unnecessary. Although it is necessary to store additional pitch origin data compared to conventional devices, there is no need to store it for each key event, and new pitch origin data can be stored when the pitch data jumps significantly. That's enough. Therefore, the memory capacity required for the pitch origin data is not so large, and the memory capacity as a whole can be considerably reduced.

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 out, the pitch origin data is set in a register or the like, and the original pitch data is restored from the pitch origin correlation data read out thereafter and the pitch origin data. This restoration method uses storage means 3.
What is necessary is to carry out a method opposite to the method of storing pitch origin correlation data.

[Description of specific examples]

[Description of Configuration] FIG. 4 shows a block diagram of a sequencer that is an embodiment of the present invention. CPU10 controls the entire device. Melody memory 14. Working memory 15 is RAM
Consists of. In addition to programs, the ROM 16 stores tables and various parameters, which will be described later. The tone generator 17 generates a musical tone signal from the performance data passed from the CPU 10 and outputs it from the speaker 18. The tempo clock generator 11 interrupts the CPU IO 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/4 of the 16th note length.
is set to . The keys 12 are composed of, for example, 61 keys. The operation switch 13 includes a tone setting switch for setting the tone, a track switch for specifying the track number, an LED indicating the mode of each track (record mode, play mode, normal mode), and the like.

FIG. 5 shows a schematic plan view of this operation switch 13. In the figure, a liquid crystal display 21 is arranged above an operation switch panel 20, and a switch group 22 including tone switches and other switches is provided below it. Also, on the right side there are two track switches 23, and on the right side there is an L button that displays the mode of each track.
An ED 24 is provided. In this embodiment, the number of trunks is set to two. When set to record mode on each trunk (1 or 2), the upper LE
D (red) lights up, and when set to play mode, the lower LED (green) lights up. Furthermore, both LEDs do not light up in normal mode. In this embodiment, only one trunk 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. Furthermore, in record mode, it is not possible to record multiple tones, and only single tones can be recorded.

[Memory explanation]

The storage means of the present invention corresponds to the melody memory 14 of this embodiment. FIG. 6 is a block diagram of this melody memory. As shown in the figure, this melody memory has a two-dimensional array structure, and data is sequentially stored in the direction of the arrow for each track TRI and TR2. The horizontal address is specified by the pointer DP[TR]. for example,
When the song shown in FIG. 7 is input to track TR=1, the data arrangement becomes as shown in FIG. 8. In addition,
As will be described later, storage of performance data starts when the track switch is operated and track 1 is set to record mode. first area a.

Tone color data established (or initialized) by the tone color switch of the operation switch 13 is stored in b4.

Area a is a code indicating that a tone number (voice number) is stored in the next area (here, area b). This code is represented by a 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. The next area d stores data representing a whole rest. The next area e stores data representing a half rest. Data representing a quarter rest and an eighth rest are stored in this order. After the rest data, interval origin correlation data and note length data are sequentially stored.

In this embodiment, the pitch origin correlation data is used as pitch origin difference data. This pitch origin difference data is data representing the difference between the pitch origin data (the key code indicated by ) and the stored pitch data (pitch key code) (see FIG. 3). In this embodiment, the pitch origin difference data and note length data are represented by a total of 8 bits. The pitch origin difference data is represented by the upper 4 bits, and the note length data is represented by the lower 4 bits. For example, in area h, 8 (1000) represents pitch origin difference data, and 3 (0011) represents eighth note note length data. For reasons described later, pitch origin difference data of 8 (1000) indicates that the key code indicated by it is the 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 area h is area C.
This indicates that the pitch origin data stored in the key code is equal to the key code indicated. Also, 6(0) stored in area i
110) The key code indicated by the pitch origin difference data is 2 times the key code indicated by the pitch origin data stored in area C.
This indicates that the value is the sum of

FIG. 9 shows the codes and formats of each data stored in the melody memory 14. In the same figure, 00
.about.OF indicates rest data, and 10.about.EF indicate note data. Further, Fl to FA indicate pitch origin data.

The rest data has an O in the upper 4 bits and note length data in the lower 4 bits. In the note data, the upper 4 bits constitute interval origin difference data, and the lower 4 bits constitute note length data. Furthermore, in the pitch origin data, the upper 4 bits are represented by F, and the lower 4 bits represent the table number. FIG. 10 represents this table. The keyboard of this embodiment covers pitches of just over five octaves from CO to 65. Within that range, there are a total of 10 pieces of pitch origin data. The lowest pitch origin data is set to the pitch of FO# (key code is 9), and the highest pitch origin data is set to the pitch of C5 (key code is 63).

FIG. 11 shows the meaning of the pitch origin difference data indicated by 1 to E. For example, the pitch origin difference data is 8, which means that the key code corresponding to that difference data is
This indicates that the value is the key code +0 indicated by the pitch origin data. Furthermore, 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 pitch origin data is located on the right side of the keyboard (on the side with the larger chord) centering on the key of the key code indicated by the pitch origin data.
It covers the key code +7 range indicated by the pitch origin data, and covers the key code -6 range indicated by the pitch origin data on the left side of the keyboard (on the smaller chord side).

FIG. 12 shows note length data and the meaning of the data. According to this table, for example, note length data 3 indicates that it is an eighth note. Note length data 5 is 1
This data indicates that sixth notes are consecutive. for example,
This note length data 5 is used when quarter notes are tied to the first note of the next measure. Details will be described later.

[Flowchart explanation]

FIG. 13 and subsequent figures are flowcharts showing the operation of the sequencer. The functions of the registers and flags appearing in the flowcharts will be explained at the end of this specification.

[Main flowchart]

FIG. 13 shows the main flowchart. When the power is turned on, the process proceeds to nl, where initial settings of various registers and the like are performed. After this, key event processing is performed at n2, switch processing is performed at n3, and other processing is performed at n4. After finishing n4, return to n2 again and proceed to n2. n3.
Repeat n4. CPU10 normally uses this n2
．． n3n4 are executed continuously, and each time there is an interrupt from the tempo clock 11, the tempo clock interrupt is processed. This will be described later [Switch processing] Normally, switch processing such as tone color setting is performed before operating the keyboard. FIG. 14 shows a flowchart of this switch processing.

First, it is determined in nlo whether there is a switch event. If there is a switch event, n11 to n1
Step 3 determines the type of event.

When the track switch 23 shown in FIG. 5 is operated, the process advances to n14 or n15. Further, when the tone color switch 22 is operated, the process advances to n16, and in n16 and n17, it is determined which track is set to the record mode.

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

When "1" of the trunk switch 23 is operated, n
At step 14, the register TR that stores the track number is set to 0. If register TR is 0, it means that track I
is specified.

When [2] of the trunk switch 23 is operated, n
15, set register TR to 1. Register TR being 1 indicates that track 2 has been designated.

Next, check the register RUN CTR at n18. This register RUN [TR] indicates the mode of the track indicated by TR.

When the data in the register is O, it represents a stop mode, when it is 1, it represents a record mode, and when it is 2, it represents a play mode. Each time the track switch 23 is pressed - times, the mode advances to the next mode. The mode starts with stop mode, then moves to record mode, and then moves to play mode. Pressing the switch again in play mode returns to stop mode. Therefore, when RUN [TR] = O at n18, it means that the stop mode has been shifted to the record mode, and in this case, the process proceeds to n20 and below. Also RUN [
TR]=1 means that the play mode has been entered, and in this case, the process proceeds to n25 and below. Also, RUN [T
When R = 2, it means that the play mode has shifted to the stop mode, and in this case, n35 and below are executed.

When entering record mode, first press RU on n20.
N [Set TR to 1 and turn on the red LED of the corresponding trunk on ri21. Furthermore, the register DP [TR] is set to 0 at n22. This DP [TR] is TR
This is the melody memory pointer of the track indicated by (see FIG. 6). Further, 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. n22
Now, put 1 into register KOF again.

This KOF stores the state of the most recently pressed key. When KOF is 1, it indicates that the key is off, and when KOF is 0, it indicates that the key is on.

Also, a voice (timbre) number is set in the register VOICE [TR].

VOI CE ETR] is a register that stores the voice number of the trunk indicated by TR.

When set to play mode, first press R on n25.
UN [Set TR to 2, turn off the red LED of the corresponding trunk LED in n26, and turn on the green LED. Next, check the state of KOF at n27. if,
If the most recently pressed key is in the key-on state, n
Proceed to step 28. In this case, note data (consisting of pitch origin difference data and note length data) for the last key pressed when the record mode is changed to the play mode must be stored. Furthermore, it is necessary to also store end data as the last data of the stored data. n28. n
29 is a step for performing these processes. That is, in n28, a subroutine (record processing) for storing musical note data is executed, and in n29, FF (see FIG. 9), which means end data, is transferred to the pointer DP in the trunk melody memory indicated by TR. FF is stored in the area indicated by ].

”: After completing n29, continue with n, and T at 30.
Set pointer DP [TR] of the track indicated by R to O. This is preparation for reading data from the first area of the melody memory indicated by TR. Also,
Set stack pointer SP[TR] to O. SP [T
R] is a register used when there is a repeat symbol in the musical score. This will be discussed later. Furthermore, in n30, DATA[TR] is set to 0, and buffer NExT[TR
Input the first data in the melody memory into 1. This NEXT [TR] is a buffer register that reads and stores one hide of data from the melody memory in advance. At this n30 stage, NEXT [TR] is D.
Since P [TR] is 0, the first data of the track indicated by [TR] is stored. And NLEN [TR
] is set to 1.

In this way, initial settings for playback are made.

In n18 above, if RUN [TR] = 2, it means moving from play mode to stop mode, so n
Set RUN [TR] to O in step 35, and turn off all LEDs in step n36.

When the switch event at n10 is a tone switch event, n16. The program proceeds to step n, 17 to determine which track is in record mode, but if both trunks 1 and 2 are not in record mode, the process returns directly. When trunk l is in record mode, T is n40.
Substitute R=O. When track 2 is in record mode, TR=1 is assigned in n41. And n42 to n4
In step 6, the voice number (timbre number) is stored in the melody memory. First, in n42, the voice number is entered into the register VOI CE [TR,].

Note that this voice number is set by a switch. Next, in n43, FB is stored in the melody memory. This FB is a voice set code (see Figure 9). Next, the pointer is advanced by one at n44. And V at n45
Store the voice number set in OICE[TR] in the melody memory. Furthermore, the pointer is advanced by one at n46 and the process returns.

■Recording performance data (key-on processing) Recording of performance data is performed sequentially as the keys are pressed or released.

FIG. 15 is a flowchart of processing performed when a key on the keyboard is pressed.

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

In the case of a key-off event, it is determined in n63 whether either of the two tracks is in record mode. If either one is in the record mode, the process advances to n64 and the track No. 0 that is in the record mode is set in TR. Then, the process proceeds to n65, and the coat placed 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 inserted in n85, which will be described later, the process advances to n66 and calls the "record processing" subroutine. That is, if the KONC data is When the value is 0 representing a rest, the process moves to the "record processing" subroutine and performs record processing for the rest.

Next, in n67, the contents of register KONC are determined. In other words, check whether this KONC is FF. As shown in step n22 of FIG. 14, first,
When trunk 1 is set to record mode, FF, which is unused data, is set in KONC. Therefore, with this n67, when the first key is turned on, the KO
Since NC is FF, proceed to n68. This n6
At step 8, the voice cent code FB is stored in the melody memory area MD[TR] indicated by the pointer DP[TR]. Furthermore, the pointer is advanced by one. Subsequently, in n69, VOICE [TR] is stored in the melody memory indicated by the pointer. This VO
ICE [TR] is set in advance to the voice data (n22) that was set at the time of mode conversion when the tone switch was not operated as a previous process. When the tone switch is operated before the key is turned on, steps n42 and subsequent steps in FIG. 14 are executed, so VOICE [TR] is stored again at n69. This means that the voice data is stored twice, but does not affect operation. When the above store is completed, the pointer is advanced by one.

Next, at n70, the contents of register KOF are determined. This KOF stores the state of the last pressed key. KOF=0 indicates a key-on state, and KOF=1 indicates a key-off state. When KOF=0 in n70, n
71 "Record processing" subroutine call. These n70.n71 have the following meanings. In other words, when a key is turned on, the previous key is normally turned off until the next key is turned on. When the next key is turned on while the previous key is turned on, the key that was turned on first is treated as having been turned off. When the key remains turned on, the process proceeds from n70 to n71, where "record processing" is executed for the key that was turned on first.

Then, in n72, the key code of the key turned on is set in KONC, and in n73, register CNT and K are set.
Clear OF. CNT is a counter that counts the time since the key is turned on or off. This CNT counts time at intervals that divide one measure into 64 equal parts. As mentioned above, the KOF stores the state of the last key pressed. That is, being set to 0 means that the last key pressed is in the key-on state.

Next, key-off event processing will be explained. At the time of a key-off event, the data (note data) of the key that was turned on is basically stored. First, key-off processing is performed at n80, and it is determined at n81 whether either of the two tracks is in the record mode. If either one is in record mode, proceed to n82. Then, the key code of the key that was turned off is KON
It is determined whether the key code is the same as the key code stored in C. If they are not the same, in order to not need to store the key note data stored in KONG yet,
Return as is. If “YES”, n8
Proceed to step 3 and set the number of the track in record mode in TR. Next, the process advances to n84, and a subroutine is called for ``record processing''. In other words, in ``record processing'', ``record processing'' is performed for the keys stored in KONC.Then, in n85, the KO
Set F to 1 and reset CNT. By resetting the CNT, time is counted again from this time. That is, this means that rests will be counted from then on. Then KONC in n86
O, which is data representing a rest, is set in and returns.

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

[Record processing]

"Record processing" is shown in FIG.

This flowchart shows the n90's "pitch (REC)'"
The routine consists of three subroutines: ``processing'', ``record length (REC)'' processing in n91, and ``'5TOPE processing'' in n92.

[Pitch (REC) processing]

This will be explained with reference to FIG.

First, at n100, it is determined whether KONC is O. If KONC=O, the data to be recorded will be cleared as rest data. This DK
C stores pitch origin difference data representing the difference between the key code and pitch origin data, as will be described later. However, in the case of rest data, this DKC is cleared.

In the case of a record of musical note data, the process advances to n101.

Here, BKC[TR] is subtracted from register KONC, which contains the key code of the note to be recorded, and the result is placed in DKC. BKC[TR] is a register that stores pitch origin data. However, when recording the first note data, BKC[TR] contains appropriate initial data. In step n101, the difference between the key code of the note to be recorded and the key code indicated by the pitch origin data is calculated, and the result is stored in the DKC that stores the pitch origin difference data. Subsequently, in n102, it is determined whether the pitch origin difference data entered into the DKC is within the range that can be covered by the DKC (see FIG. 3). As shown in FIG. 11, the range that the DKC can cover is from the key code -6 indicated by the pitch origin data to the key code +7 indicated by the pitch origin data. n10
Step 2 checks whether the DKC data is within this range. If it is within that range, n111
Proceed to. At n111, DKC is subtracted from 8 and the result is put back into DKC.

This operation is an operation for converting the key code difference into pitch origin difference data representing the 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 above,
At n103 and below, new pitch origin data is selected. This selection of pitch origin difference data is performed by selecting pitch origin data that is close to the KONC data. First, n1
Divide KONC by 6 in 03. The result is stored in register n. And n104. n in n105
Determine the size of. Then, 1, 10, or the integer part of the above division result is entered into n. Furthermore, at n109, F is placed in the upper 4 bits of the melody memory area indicated by pointer DP [TR], and n is placed in the lower 4 bits.
Put in. Here, the upper 4 bits of F are a code indicating that the lower 4 bits of data (indicated by n) are interval origin data (see FIG. 9). The data represented by n of the lower four focus points represents the number of the table shown in FIG. 10 (see FIGS. 9 and 10).

FIG. 18 is an explanatory diagram when determining new pitch origin data after the above n103. Area A in the figure shows the range covered by each of the ten pitch origin data, which is used when selecting one pitch origin data for the above n103 and below. Further, region B indicates the range covered by one pitch origin data selected by using the region A described above. Give an example. For example, assume that the result of the calculation at n103 is 3. This 3 goes into register n. As a result, at n109, F3 is stored in a predetermined area of the melody memory. In other words, the pitch origin data of table number 3 has been selected. 1st
Referring to Figure 0, the key code is 21 in the pitch origin data of table number 3.

In n1lO, the key code indicated by the pitch origin data selected as described above is entered into BKC[TR], and is further transferred from the KC containing the key code to BKC[TR].
] and the result is placed in DKC. In this process, the key code difference is stored in the DKC. And n
At step 111, the contents of the DKC are converted as described above, and the pitch origin difference data is input into the DKC again.

C note length (REC) processing] This will be explained with reference to FIG.

In the ``note length (REC) process'', the note length of a note or the note length of a rest is determined by using the count contents of the CNT.

First, register L is reset at 0120. This register is the rcO of note length data 5 shown in FIG.
Count the number of times NT INUEJ. Subsequently, FF is sent to register NLEN [TR]. This NL
EN [TR] is used to store note length data (1 to 5). Initially, unused data is set to OFF as the initial value.

In n121, the count value of CNT is determined. As mentioned above, the resolution of CPU control is 16th note length. However, in actual processing, the error range for the CNT count value is 2 in the child direction and 1 in one direction. For example, the count value of CNT corresponding to a whole note is 64, but in n122, CN
If T is 63 or more, it is determined that it is a whole note. n12
In steps 2 to n126, processing corresponding to the length of each note is performed. The next step, 012, subtracts the length of each note from CNT and re-centres the result to CNT.
This is to determine whether or not the process of ``rcONT INUE'' is required for 7 or below. For example, when a whole note is tied and extends to the next measure, the CNT will exceed 64, but if you subtract 64 from this CNT, the CNT will exceed 64.
The remainder is reset to NT. At n127, it is determined whether the reset CNT exceeds 2 or not. If it does not exceed 2, it is considered to be within the error range and returns as is. If CNT exceeds 2, proceed to n128 and execute CNT-4. Furthermore, L
Execute +1. Then, the process returns to n127 again. C.N.T.
-4 is executed because one C0NTINUE indicates a length of 16 minutes, that is, a length of 4 counts.

L is a counter that counts the number of rcONTI NUEJs as described above. As will be described later, by looking at this L, it becomes possible to restore sounds that span two measures or more, or sounds that have a length that cannot be represented by 2°4, 8, or 16th notes.

In the above n122 to n126, further NLEN C
TR] is set to predetermined data. This predetermined data is any of the note length data (0 to 5) shown in FIG.

In the case of note lengths that cannot be represented by each note length data (for example, dotted half notes, tied half notes, and 8
diacritics, etc.) in the same way as above. n128
, and is represented by C0NTINUE. For example, in the case of a half note, NLEN [TR] is set to 1 (n123).

[5TORE processing] FIG. 20 shows "5TORE processing".

In this "5TORE process", the pitch origin difference data calculated in FIG. 17 and the note length data calculated in FIG. 19 are stored in the melody memory.

First, in n130, it is determined whether NLEN [TR] is an FF. If the contents of this register are FF
If so, the CNT is 2 or less. That is, in FIG. 19, a direct return is made from n121. In other words, CNT
The counting time has not reached the length corresponding to the 16th note length. In this case, return.

When any note length data from 0 to 4 (see FIG. 12) is set in NLEN [TR], processing is performed at n131. Here, first, the bottom four of DKC
The bits are placed in the upper 4 bits of register DATA[TR]. This DATA [TR] is used as a buffer to temporarily store data to be stored in the melody memory or to temporarily store data read from the melody memory. And this DATA [T
The lower 4 bits of NLEN[TR]
Bit is set. The DKC stores pitch origin difference data in the "Pitch pitch (REC)" process shown in FIG. indicates pitch origin difference data. NLEN [TR] indicates note length data as (0 to 4) from Fig. 19. In other words, DATA C
Pitch origin difference data is set in the upper 4 bits of TRI, and note length data is set in the lower 4 bits. At this stage, the format of the note data is completed (see Figure 9). Then, the process advances to n132, and the data of DATA[TR is stored in the area of the melody memory indicated by the pointer DP_CTRI. And n133
Advance the pointer by one. Next, at 0134, it is determined whether L is 0 or not. If L is 1 or more, it indicates rcOT I NUEJ, so proceed to n135. Here, the lower 4 bits of DKC are placed in the upper 4 bits of DATA [TR]. In other words, input pitch origin difference data. And DATA CTRI
Put 5 into the lower 4 bits of . This 5 is note length data representing rcONT I NUEJ as shown in FIG. Next, subtract L by one and execute n132 and subsequent steps again. In this way, data regarding "rcONTINUE" is stored in the melody memory until L=O.

Through the above operations, performance data is recorded in the melody memory.

(2) Reading Performance Data Next, the operation of reading performance data stored in the melody memory will be explained.

This read operation is performed in play mode.

The play mode is set by operating the track switch 23 to turn on the green LED. In the play mode, data is read from the melody memory and processed by a subroutine call of READ processing ``'', as will be described later.

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

(READ processing) First, in n140, the contents of NEXT [TR] are
Set to ATA [TR]. NEXT [TR] contains the data to be processed next. this,
Move the data to be processed next to DATA [TR], which will contain the data to be processed now. Then, the pointer is advanced by one (n 141). Next, pointer DP
The data in the melody memory area indicated by CTRI is
Move it to NEXT [TR] in preparation for the next process.

After completing the above preparations, DATA
Determine the contents of the CTRI. Since the data is classified in the range of 00 to FF as shown in Fig. 9, by looking at the contents of the data, it is possible to
Each subroutine call is made. For example, DATA [
TR] -F If 1, subroutine calls the pitch origin processing parameter of n145.Hereafter, n144 to n15
Each process of 0 will be explained.

FIG. 22 shows the process of ``'pitch origin processing''.

Here, first, the lower 4 bits of DATA [TR] are placed in register j, and the key code of the table number represented by j is read from TABLE and placed in BKCCTR3. The pitch origin data is now set in BKC[TR].

When DATA I:TR3=FB in n143, the "VOICE processing" subroutine in n146 is called. In this subroutine, as shown in FIG.
R]. That is, since the voice number is set in NEXT [TR], this voice number is set in VOICE [TR]. Then, in n171, set the track number and voice number to the sound source (TG
)17. The sound source (TG) 17 automatically sets the voice by receiving and receiving these data. At n172, advance the pointer by one and n17
Melody-memory 1 indicated by the pointer at 3
Set the data in area 4 to NEXT [TR].

When DATA [TR] = FC in n143 above, the subroutine call of "REPEAT processing" in n147 is made. Also, when DATA [TR] =FOO, "RE T U RN processing" of n144.

Call the subroutine. These subroutines n144 and n147 are executed when the song is to be repeated within a certain range. Data regarding repeats is stored in melody memory. For example, assume that data is stored in the melody memory 14 as shown in FIG. In this case, in play mode, first
1, a code indicating REPEAT is found, and the data in the next area M2 is recognized as the start address of the portion to be repeated. Assuming that this start address is M3, the address indicated by the pointer is set to M3. At this time, M5, which is the next address after M2, is set in the stack pointer. And the pointer is M4
, the RETURN code is found and the area M5 set in the stack pointer is set as the address indicated by the pointer. As a result, the songs recorded in the range from area M3 to area M4 will be repeated.

At n143 in FIG. 21, DATA [TR] =
At the time of FC, the ``'REPEAT processing'' subroutine is called, but in this subroutine, the 24th
As shown in the figure, processing mainly involves changing the address indicated by the pointer and processing the stack pointer. FIG. 26 shows this "'REPEAT processing"°. first,
At n180, the address next to the address indicated by the data pointer (area M5 in FIG. 24) is transferred to the stack register R3 indicated by the current stack pointer SP [TR].
Move it to TC [TR] [SP [TR] ].

In other words, in the example of FIG. 24, the address of area M5 is SP
Stack register R5TC[TR] indicated by [TR]
] [SP [TR] is set. Next, the stack pointer is advanced by one (n181).

Next, the data of NEXT [TR] is transferred to the pointer DP[T
R]. At this stage, for example, in the example shown in FIG. 24, the address of area M3 is set in DP [TR]. Next, at n183, the data in the melody memory area indicated by the pointer is NEXT [TR]
is set to In the example shown in FIG. 24, data in area M3 is set to NEXT[TR].

Next, in FIG. 21 above, “RETURN” of n144
The operation when "process" is called is described with reference to FIG. 27.In this process, first, in n190, it is checked whether the stack pointer is positive.Next, in n191, the stack pointer is Return one.Next, in n192, R3T indicated by the stack pointer
C[TR] Move the contents of [SP[TR]] to pointer DP[TR]. In the example shown in FIG.
R] is set to the address of area M5. and,
At n193, the data in the melody memory area indicated by the data pointer DP[TRj is NEXT[
TR].

By the above-described processing shown in FIGS. 26 and 27, it is possible to freely repeat a part of a song. Of course, it is also possible to set a repeating loop of a song within the repeating loop of a song.

Next, we will explain the operation when reading note data, note length data, or FF in the "READ process" in FIG. Call "" as a subroutine. FIG. 28 is a flowchart of this "'note processing'". First, in n200, “pitch processing °
Call the subroutine ``, and then call `` in n201.
Call the note length processing subroutine. And n2
At step 02, the track number, key code, and key-on information are output to the sound source 17. The sound source 17 starts producing sounds when it receives these pieces of information.

FIG. 29 is a flowchart showing the operation of "pitch processing" in n200. First, in n210, D
Put the upper 4 bits of ATA [TR] into DKC. D
The upper four bits of ATA [TR] are pitch origin difference data (see FIG. 9). At this stage, the pitch origin difference data stored in the DKC is chord expression data (
(See Figure 11). Therefore, in step n211, the pitch origin difference data expressed in the chord is converted into a key code difference between the key codes indicated by the pitch origin data. Furthermore, in n212, this difference data is added to the pitch origin data to convert it into an actual key code, and the data is entered into the KC as the key code.

FIG. 30 is a flowchart showing the operation of "code length processing". First, in n220, the lower 4 bits of DATACTRl are put into NLEN[TR].DATA
The lower 4 bits of [TR] represent note length data (9th
(see figure). Then, in n221, the value of the note length data is determined. The note length data is one value from 0 to 5. For example, when the note length data is 0, it means that the note length is a whole note. In this case, n222 is executed. In other words, 16 is sent to NLEN[TR]. Here, 4! ! 16 is the resolution of this device, 1
This shows that it is 16 times the length of a sixth note.

This NLEN [TR] stores a preset value at this stage. As described later, NLEN [TR] is subtracted as time passes and row (.

When the data retrieved from the melody memory area is musical note data, the "pitch processing" shown in FIG. 29 is performed.

At the same time, the "note length processing" shown in FIG. 30 is performed.

On the other hand, when the data read from the melody memory area is rest data, subroutine n149 in FIG. 21 is executed, so in this case, the "note length processing" in FIG. only is done.

[Tempo clock interrupt processing]

By the way, as explained in FIG. 4, the tempo clock 11 generates four interrupt clocks for a 16th note length in accordance with the current tempo. FIG. 31 is a flowchart showing the operation of "tempo clock interrupt processing".

In this interrupt processing, at n300, the tiger/7ri designation is set to the initial value of track 1 (TR←0), and at n300,
1, the mode is determined. When it is determined that the mode is play mode, the process advances to n302. Here, counter C
Read 0UNT and see if the remainder when dividing that value by 4 is O. C0UNT is a running counter, and continues to count up every time this interrupt processing is entered after the power of the device is turned on (n307). In other words, this C0UNT counts 64 times for one bar. n3
03 is the next n304 only once for every 4 interrupts.
This is a step to execute. In other words, the PLAY process is performed only once for every four interrupts. This is because the CPU control resolution is set to 16th note length. After the PLAY process, the track number is incremented by one and the process returns to n301. And similarly n301~
Perform the processing in n304, and in n305 judge whether the processing has finished for the two tracks. When it is judged that the processing has finished, n
Proceed to 307. In n307, counters C0UNT and CN
Increase T by one.

[PLAY Process] FIG. 32 shows the "" PLAYP executed in n304 above.
A LAY processing flowchart is shown.

First, in n310, the note length data stored in NLEN [TR] is decreased by one. Next, it is checked whether the note length data is O as a result.

If it is not 0, return as is. NLEN
[TR] If =O, the DATA currently being processed
CTR] is music note data or other data (n312). If it is other than musical note data, execute the READ processing and return.

When the data is musical note data, it is determined in n313 whether the data at the next address is also musical note data. In other words, data at the next address is stored in NEXT [TR] at n142 in FIG. if,
When the next data is also note data, rcONT I
Possibly NUEJ. Therefore, in the next n314, 1, the lower 4 bits of NEXT [TR] are set to register
and determines whether the value is 5 in n315. If it is 5, it is necessary to process rcONT INUEJ, so proceed to n316 and write “C0N
Make a subroutine call for the T process. In n313, if the next data is not note data, n31
7, the track number and key-off information at that time are output to sound #17. Also, in n315, X=5
If not, that is, if there is no need to execute rcONT I NUEJ, the process also proceeds to n317. Then, the process advances to n318, and a subroutine call for "READ processing" is made.

In this way, for each note or rest, “READ”
Then, the sound source 17 performs processing such as pronunciation.

The above ``C0NT processing'' at n316 is executed according to the flowchart shown in FIG. To, the above n313
The next note data or rest at the point in time is set.

The pointer is then advanced by one. Next, in n321, the data in the melody memory area indicated by the pointer is sent to NE.
XT [Transfer to TRI. Next, in n322, a subroutine call for "pitch processing" is made, 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 the same as the data stored in NEXT [TRI at the time of n312 in FIG. 32. Then, the process advances to n323 and outputs the trunk number and key code to the sound rX17. The above-described "C0NT processing" makes it possible to restore musical tones as shown in FIG. 25, for example.

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

In the embodiment, the pitch origin data is shown as a table number as shown in FIG. 10, but it is also possible to store the key code itself corresponding to the pitch origin data. Similarly, I stored the pitch origin difference data in chord representation,
Difference data between pitch origin data and pitch data can also be directly stored. Furthermore, although the key code is expressed as continuous data, the present invention can also be applied to a key code composed of a combination of an octave code and a note code.

〔register〕

(RUN [TRI)...Mode register indicating recording/playback/stop status.

0: Stop, 1: Record, 2: Play (TR) ...Register (D
P(TRI): Melody memory pointer.

(VOI CE [TRI)...A register that stores the voice floor.

(MD [TRI [X])...Melody memory.

(KOF): A flag that stores the state of the last key pressed.

0: Key on, 1: Key off (CNT)...Counter that counts the time since the key was turned on or off.

(KONC): A register that stores the key code of the key that is turned on.

(KC)...A register that stores the key code indicated by the pitch origin difference data read from the melody memory during playback.

(COUNT) ... A counter that performs a running count from 0 to 63.

(BKC[TRI)...Register in which pitch origin data is set.

(TABLE [i]) ... A table in which pitch origin data is stored.

(DKC) ...Register in which pitch origin difference data is set.

(NLEN [TRI) ... note length data is
register to be read.

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

(PATA [TRI)...Melody - register in which data loaded (or stored) from memory is set.

(NEXT [TRI)...: PATA [T
A register in which the data of the next address of RI is set.

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

(SP [TRI]) ... Stack pointer.

(g) Effects of the Invention According to the present invention, the pitch data in the performance data is converted into pitch origin correlation data that correlates with the pitch origin data and is stored in the memory, thereby saving memory. This has the advantage that the memory saving effect is very significant, especially when it comes to memorizing long pieces of music. Further, since the pitch origin correlation data is stored in the performance data storage means together with the pitch origin data serving as a reference, it is possible to restore the original pitch data from these data.

[Brief explanation of drawings]

FIGS. 1A and 1B are basic configuration diagrams of an embodiment of the present invention. FIGS. 2 and 3 are diagrams for explaining the operation of the same embodiment. FIG. 4 is a block diagram of a sequencer that is 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 a song stored in the melody memory.
FIG. 8 is a diagram showing data in a melody memory storing the song of FIG. 7. Also, FIG. 9 is a diagram showing the format of data stored in the melody memory, and FIG. 10 is a diagram showing the format of data stored in the melody memory.
TABLE set in OM16. FIG. 11 is a diagram showing the correspondence between data representing the difference between pitch origin data and pitch data and pitch origin difference data expressed in chords. FIG. 12 is a diagram showing note length data. Fig. 13 - Fig. 17, Fig. 19 - Fig. 23, Fig. 26 -
FIG. 33 is a flowchart showing the operation of the CPU. Also, FIGS. 18 and 24. FIG. 25 is a diagram used to explain the above flowchart. 1-Performance data input means, 2-Performance data conversion means, 3
- storage means; 4. performance data restoration means; 5. musical tone symbol formation means. TR, 1 Figure

Claims (3)

[Claims] (1) Performance data input means, means for converting pitch data in the input performance data into interval origin correlation data that correlates with predetermined interval origin data among a plurality of interval origin data, and the converted pitch A performance data processing device comprising performance data storage means for storing origin correlation data and the predetermined interval origin data. (2) Reading out the pitch origin correlation data of the performance data storage means and the performance data storage means stored as interval origin correlation data in which the pitch data in the performance data correlates with the interval origin data; A performance data processing device comprising: means for restoring original pitch data based on the pitch origin data; and means for forming a musical tone signal from performance data including the restored pitch data. (3) The pitch origin correlation data is pitch difference data between pitch origin data and pitch data.
The performance data processing device according to item 1 or 2.