JP2002023740A - Music data processor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a music data processor capable of equally processing events inputted through plural input ports. SOLUTION: As the control functions of a CPU 200 when a sound source device 100 receives MIDI(Musical Instrument Digital Interface) data, this processor is provided with serial data reception means 210-k (k=1-N) for inputting the MIDI data, MIDI event interpretation means 220-k (k=1-N) for judging whether or not an MIDI event is established or the like based on the MIDI data outputted from the serial data reception means 210-k (k=1-N), the MIDI event storage means 230-k (k=1-N) of a FIFO type for writing the MIDI event by the MIDI event interpretation means 220-k (k=1-N) and an MIDI data manager means 240 for managing an event processing overall based on an event establishment report from the MIDI event interpretation means 220-k (k=1-N).

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an apparatus for processing music data such as MIDI data.

[0002]

2. Description of the Related Art In an electronic musical instrument such as an electronic piano, in addition to generating a musical tone using a sound source built in the electronic musical instrument,
Devices provided with a communication function of performing data communication with external devices have become widespread. As described above, MID is a standard for performing data communication between an electronic musical instrument and an external device.
There is an I (Musical Instrument Digital Interface) standard, and a device corresponding to the MIDI standard includes an MID.
An I interface is mounted. The MIDI interface includes a single-port type (for example, a 1-in / 1-out type) MIDI interface that has been widely used since the beginning of the MIDI standard setting, and a so-called multi-port type having a plurality of input / output terminals. For example, there is an 8-in / 8-out type MIDI interface. By connecting a plurality of electronic musical instruments and sound sources such as a keyboard and a synthesizer to a sound source device having this multi-port type MIDI interface, it is possible to freely use many sound sources and electronic musical instruments, etc. And MIDI input from electronic musical instruments
The performance can be reproduced based on the data (see FIG. 13).

[0003]

By the way, a sound source device (music data processing device) provided with this multi-port type MIDI interface has an M interface through a plurality of ports.
It is determined in advance from which port to process the MIDI data input when the IDI data is received (hereinafter simply referred to as priority). FIG. 14 shows a flow of data processing in the case where the conventional sound source device receives MIDI data for three events via port 1 and receives MIDI data for one event via port 2 in the meantime. is there. The flow of data processing shown in FIG. 14 assumes that the priority of port 1 of the sound source device is set higher than the priority of port 2. The event (music event) shown in FIG. 14 is performance information required for performing a musical instrument performance or a process such as an operation, for example, a note-on indicating a sound, a note number indicating a pitch, and a sound intensity. Is a sounding event or the like constituted by MIDI data such as velocity indicating the sound generation event. Since conventional sound source devices performed event processing according to priority,
As shown in FIG. 14, as long as there is an event input from a high-priority port (port 1), an event input from a low-priority port (port 2) is not processed. As a result, processing of an event input from a port having a low priority is delayed, and there is a problem that a sound is generated later than a timing at which sound should be originally generated. The present invention has been made in view of the circumstances described above, and an object of the present invention is to provide a music data processing apparatus that can uniformly process events input through a plurality of input ports.

[0004]

In order to solve the above-mentioned problem, the music data processing apparatus according to the first aspect of the present invention provides a plurality of ports for connecting to an external device and a case where a music event is input from the port. And an event processing means for preferentially processing a music event input from a port different from the port to which the music event processed last time is input.

According to a second aspect of the present invention, in the music data processing apparatus according to the first aspect, the event processing means performs processing of one or a plurality of parts for one music event, and sets a port. If the music event input through the music event is a music event for processing a plurality of parts, the music event is processed for one part, and then the music input from a port different from the port. It is characterized in that it is determined whether or not there is an event, and when it is determined that there is a music event input from a different port, the music event is preferentially processed.

[0006]

Embodiments of the present invention will be described below to make the present invention easier to understand. Such an embodiment shows one aspect of the present invention, and does not limit the present invention, and can be arbitrarily changed within the scope of the present invention.

A. 1. First Embodiment (1) Configuration of Embodiment FIG. 1 is a block diagram showing a schematic configuration of a sound source device 100 according to the present embodiment. The sound source device 100 is connected via a CPU 200 that controls the components of the device, a ROM 300 that stores various control programs and fixed data, a rewritable RAM 400 that stores various data, and a multi-port type MIDI interface 510. M
A MIDI input unit 500 to which IDI data is input;
A tone generator 600 for generating a tone signal under the control of the PU 200 is provided.

A) Functional Configuration of Sound Source Device 100 FIG. 2 shows a CPU 200 for receiving MIDI data.
FIG. 3 is a functional block diagram illustrating the control function of FIG. CPU200
The control functions at the time of receiving the MIDI data in the first embodiment are the serial data receiving means 210-k (k = 1 to N),
Event interpretation means 220-k (k = 1 to N) and MID
I event storage means 230-k (k = 1 to N)
DI data manager means 240. As shown in FIG.
(K = 1 to N), MIDI event interpreting means 220-k
(K = 1 to N) and MIDI event storage means 230-
k (k = 1 to N) is provided corresponding to each port k (k = 1 to N) of the MIDI interface 510.

The serial data receiving means 210-k receives the MIDI data input through the port k and outputs the received MIDI data to the MIDI event interpreting means 220-k one byte at a time. The MIDI event interpreter 220-k is a MIDI data receiver 210-k.
MIDI data is received one byte at a time, and the received MIDI data in byte units is sequentially stored in the MIDI event storage means 230-k of the FIFO system, and it is determined whether one event has been established. The method of determining whether the event has been established will be described in the operation of the embodiment, and will not be described.

The MIDI data manager means 240
When the event establishment notification is received from the MIDI event interpreting means 220-k, the event processing is performed with reference to the corresponding MIDI event storage means 230-k. More specifically, the MIDI manager means 240 first
By receiving the MIDI data from the I-event interpreting means 220-k, it is possible to grasp at which port the event is established. Then, the MIDI data manager 240 determines the next event to be processed by referring to the memory 241. This memory 2
Reference numeral 41 denotes a rewritable storage unit which stores the input port number of the last processed event. MID
The I data manager means 240 refers to the memory 241 and determines an event to be processed based on a criterion such as not continuously processing events input to the same port. In addition, about concrete decision method,
A detailed description will be omitted later. Next, the operation of the tone generator 100 when MIDI data is input to a plurality of ports of the MIDI interface will be described.

(2) Operation of the Embodiment FIG. 3 is a diagram exemplifying a case where MIDI data for one event is input via the ports 1 and 2 of the MIDI interface 510, respectively. As shown in FIG.
Devices a and b on the DI data transmission side are connected to each other. Hereinafter, the sound source device 100 is a device a and a device b.
The event processing operation when MIDI data is received from the MFP will be described with reference to FIGS. Note that all the events shown in FIG. 3 have a 3-byte configuration (M
One event is established with 3 bytes of IDI data).

A) Operation of the event interpreting means 220-k The MIDI event interpreting means 220-1 and the MIDI event interpreting means 220-2 are connected to the serial data receiving means 2
01-1 and serial data receiving means 201-2 to 1
MIDI data is received byte by byte. FIG. 4 is a flowchart showing the operation of the event interpreter 220-k. In step S1, the MIDI event interpreting means 220-k determines whether or not MIDI data has been supplied from the serial data receiving means 210-k. MID
When the MIDI data is supplied (step S1; YES), the I event interpreting means 220-k proceeds to step S2, and determines whether the MIDI data for one event has been supplied, that is, whether or not one event has been established. . Specifically, the MIDI event interpretation means 220-k first
With reference to the flag of the IDI data, it is determined whether it is a status byte or a data byte.

FIG. 5 is a diagram showing MIDI constituting a sound generation event.
It is a figure showing data. The pronunciation event shown in FIG.
It consists of one status byte (note on) and two data bytes (note number and velocity). In the sounding event having such a configuration, first, a status byte is input to the MIDI event interpreting means 220-k, and then a data byte is input to the MIDI event interpreting means 220-k. Here, the flag “1” is set in the status byte, and the flag “0” is set in the data byte. The status byte includes information on the number of data bytes that follow. Therefore, the MIDI event interpretation means 220-
k is obtained by referring to the MIDI data flag.
While it is determined whether the received MIDI data is a status byte or a data byte, if the received MIDI data is a status byte, the number of subsequent data bytes is grasped based on the information contained therein.

Here, the event interpreting means 220-k again
Returning to the description of the operation described above, since the events according to the present embodiment are all three-byte events, information indicating that the number of subsequent data bytes is "2" is included in the status byte. MIDI event interpreter 220-k
Indicates that the received MIDI data is 1 byte, while the MIDI data necessary to establish one event is 3 bytes.
Since it is a byte, it is determined that the event is not established (step S2; NO), and the MIDI data for one byte is
After writing in the IDI event storage means 230-k, the process returns to step S1, and the above-described processing is repeatedly executed.

Then, the MIDI data of 2 bytes is M
It is assumed that the data is supplied to the IDI event interpreting means 220-k. When the 2-byte MIDI data is supplied, the MIDI event interpreting means 220-k determines that one event has been established (step S2; YES) and stores the last MIDI data constituting one event in the MIDI event storage means. In addition to writing to 230-k, a notification that one event has been established is sent to the MIDI data manager means 240 (step S3). Such processing is performed by MI
The execution of the DI event interpreting means 220-1 and the MIDI event interpreting means 220-2 causes the MIDI event storing means 230-1 and the MIDI event storing means 230-2 to store MIDI data for one event. .

Next, referring to FIG. 6 and FIG.
MIDI receiving event establishment notification from event interpreting means 220-1 and MIDI event interpreting means 220-2
The operation of the data manager 240 will be described.

B) MIDI data manager means 240
FIG. 6 is a flowchart showing the operation of the MIDI data manager 240, and FIG. 7 is a diagram schematically showing events input to the sound source device 100. MI
The DI data manager 240 detects an event establishment notification in step Sa1. The MIDI data manager 240 repeatedly executes the step Sa1 until receiving the event establishment notification (FIG. 7).
Stage 1).

Thereafter, an event is input from port 1 and
It is assumed that the event interpreting means 220-1 has notified the MIDI data manager means 240 of the event establishment (stage 2 shown in FIG. 7). Upon receiving the event establishment notification, the MIDI data manager 240 proceeds to step Sa2, and determines whether the port corresponding to the received event establishment notification is the same as the port corresponding to the last processed event. As described above, the port number of the last processed event is written in the memory 241. Here, it is assumed that the port number of the previously processed event is “N”. The MIDI data manager 240 determines that the port number “N” stored in the memory 241 does not match the port number “1” of the event input this time, and thus is different from the port processed last (step Sa2). NO), and proceeds to step Sa3. In step Sa3, the MIDI data manager means 240 refers to the MIDI event storage means 230-1 storing the event to be processed, and starts the event processing of the port 1. When the event processing of the port 1 is completed, the MIDI data manager 240 changes the port number written in the memory 241 from “N” to “1”. When the rewriting of the port number of the last processed event is completed, the MIDI data manager means 240 returns to step Sa1, and determines again whether or not there is a port for which the event has been established.

Thereafter, it is assumed that an event is again input from the port 1 and the event interpreting means 220-1 notifies the MIDI data manager means 240 of the event establishment (stage 3 shown in FIG. 7). Upon receiving the event establishment notification, the MIDI data manager 240 determines whether the port corresponding to the received event establishment notification is the same as the port corresponding to the last processed event, as before. The port number “1” of the last processed event is written in the memory 241. The MIDI data manager 240 determines that the port number “1” stored in the memory 241 matches the port number “1” of the event input this time, and thus is the same as the last processed port ( Step Sa
2; YES), the process proceeds to step Sa4 without performing the event processing of port 1. The MIDI data manager 240 that has proceeded to step Sa4 without performing the event processing of the port 1 determines whether or not the event has been established in another port. Where MID
Since the I data manager means 240 has not received the event establishment notification from the other event interpretation means 220-k, it determines that the event has not been established at the other port, and proceeds to step Sa3. After all, in this case MIDI
The data manager means 240 performs the event processing of the port 1, but the operation is the same as that described above, and the description is omitted.

Thereafter, an event is input from port 1 and port 2 and the event interpreting means 220-1 and 220-2
It is assumed that an event establishment notification has been sent to 40 (stage 4 shown in FIG. 7). Here, it is assumed that the MIDI data manager 240 first recognizes the event establishment notification from the event interpretation unit 220-1, and then recognizes the event establishment notification from the event interpretation unit 220-2.
Thereby, the MIDI data manager means 240
As in the previous case, the port number “1” stored in the memory 241 is replaced by the port number “1” of the currently input event.
Therefore, it is determined that the port is the same as the port processed last (step Sa2; YES), and the process proceeds to step Sa4 without performing the event processing of the port 1. The MIDI data manager 240 that has proceeded to step Sa4 without performing the event processing of the port 1 determines whether or not the event has been established in another port. At this time, the MIDI data manager 240 has received the event establishment notification from the event interpreter 220-2. Therefore, the MIDI data manager means 240 determines that the event has been established in another port (port 2) (step Sa).
4; YES), proceed to step Sa5.

In step Sa5, the MIDI data manager 240 determines the next event to be processed. The stage 4 shown in FIG. 7 assumes a case where an event establishment notification is made from the event interpreting means 220-2 corresponding to the port 2;
..., the event interpretation means corresponding to a large number of ports such as port N may notify the MIDI data manager means 240 of the event establishment. In such a case, it is necessary to select one of the events,
The MIDI data manager 240 determines an event to be processed next in this step Sa5. For example, when events are established in a plurality of ports, the event of the port closest to the port of the last processed event (assumed to be port 3) is determined as the event to be processed next. However, when there are two closest ports (for example, for port 3 described above,
For port 2 and port 4), the smaller port number (port 2) is selected, and the event of this port is determined as the event to be processed next. Although various other methods are conceivable, further description will be omitted, and the operation of the MIDI data manager means 240 will be continued.

Here, MIDI data manager means 2
40 is an event interpreter 230- corresponding to port 2
Event notification is received only from 2. For this reason,
The MIDI data manager 240 determines that the next event to be processed is the event of port 2, and proceeds to step Sa3. In step Sa3, MIDI
The data manager means 240 starts the event processing of the port 2 by referring to the MIDI event storage means 230-2 storing the event to be processed based on the judgment result. Has not been processed yet. In other words, the MIDI data manager means 240 preferentially processes an event of a port different from the port of the last processed event.

Thereafter, it is assumed that the event processing of the port 2 has been completed. When the event processing of port 2 ends, MI
The DI data manager 240 changes the port number written in the memory 241 from “1” to “2”.
When the rewriting of the port number of the last processed event is completed, the MIDI data manager means 240 returns to step Sa1, and determines again whether or not there is a port for which the event has been established. After that, the MIDI data manager means 240 processes the event of port 1, but the operation in this case is the same as that described above, and further description will be omitted.

As is clear from the above description, the tone generator 100 according to the present embodiment does not preferentially process only the event of a specific port even when the sound is crowded. That is, the sound source device 10 according to the present embodiment
When the event is established in a plurality of ports, the event of 0 is processed evenly for each port, so that it is possible to prevent the processing of the event from being delayed. The memory 241 according to the present embodiment is configured to store the port number of the last processed event. However, the present invention is not limited to this, and two or more (for example, the total number of ports N of the sound source device 100, etc.) Of course, a configuration for storing the data of (1) may be used. By using the memory 241 having such a configuration, an event input from a port that does not match any of the port number of the last processed event and the port number of the last processed event is processed. be able to. Thus, for example, it is possible to prevent a problem that an event is repeatedly processed between two ports and an event input from the remaining one port is not processed, even though the event is established at three ports. .

B. Second Embodiment By the way, the concept of "channel" for introducing a plurality of musical instruments individually has been introduced into a sound source device which has been widely used conventionally. Specifically, the first
A violin is set for the channel, a piano is set for the second channel, and so on. By using a sound source prepared for each channel, the sound of a plurality of instruments can be produced simultaneously. Has become. Conventionally, as many sound sources as the number of channels are required, but in recent years, a multi-sound source capable of generating sounds of a plurality of musical instruments for each channel has been developed, and this is becoming mainstream. Furthermore, among multi sound sources, a sound source called a multi-part sound source (hereinafter, referred to as a multi-part sound source) has been actively researched and developed since it can perform efficiently. Here, the multi-part sound source is a sound source having a plurality of parts (for example, piano, violin, etc.) and capable of specifying a reception channel (hereinafter sometimes simply referred to as Ch) by setting for each part. .

FIG. 8 is a diagram showing the relationship among ports, channels, and parts, and FIG. 9 is a diagram for explaining the concept of a multi-part. 9 will be described in further detail. FIG. 9A is a diagram illustrating a case where a reception channel for each part is designated by the user.
(B) is a diagram showing a part table to be processed by a channel viewed from the sound source device side. Note that the MIDI channels and parts shown in FIG. 8 assume port 1, but the concept of the channels and parts is common to all ports (ports 1 to N shown in FIG. 8). The description of the other ports is omitted.

In the multi-part sound source set as shown in FIG. 9, it is assumed that a violin is set in part 1, a piano is set in part 2, and an organ is set in part 3. For a multi-part sound source of such a setting, an event specifying channel 1 and an event specifying channel 2 are input, and both events specifying each channel are sounding events that generate a sound of “do”. Suppose there was. Multi-part sound source is 1Ch MID
When an I-event is received, a parameter is set in a register (not shown) so as to generate a sound of "do" with a violin tone. On the other hand, 2Ch MID
When the I-event is received, the multi-part sound source sets various parameters in a predetermined area of the register so as to produce the sound of "do" with the tone of the piano and the organ. In this way, the multi-part sound source can produce a plurality of timbres in one channel, or make the sound thicker.

However, the conventional multi-part sound source has the following problems. For example, FIG.
A multi-part sound source equipped with the part table shown in
After receiving an event of 2Ch via port 1, 1Ch via a port different from port 1, for example, port 2
It is assumed that the event of (part to be processed: part 1) is received. As shown in FIG. 10, the conventional multi-part sound source processes part 2 and part 3 to be processed at 2Ch of port 1 continuously, and then processes part 1 to be processed at 1Ch of port 2. Was. As described above, in the conventional multi-part sound source, when a part process (part process: setting various parameters for the multi-part sound source) corresponding to an event of a certain port is started, all of the events corresponding to the event are started. Until the end of the part process, there is a problem that the part process corresponding to the event of another port is not performed.

FIG. 11 is a flowchart showing the operation of the MIDI data manager 240 of the multi-part sound source according to the present embodiment, and FIG. 12 is a diagram schematically showing the flow of data processing when this flow is executed. It is.
The description of the operation of the multi-part sound source shown in FIG.
As in the case described above, it is assumed that a 2Ch event is received via port 1 and a 1Ch event is received via port 2. Since the hardware configuration and the like are the same as those in FIGS. 1 and 2 described above, corresponding portions are denoted by the same reference numerals and detailed description thereof will be omitted.

The MIDI data manager means 240
In step Sb1, MIDI event interpreting means 2
20 to detect whether there is an event establishment notification. When the multi-part sound source receives an event via the port 1, the MIDI event interpretation means 220-1
An event establishment notification is sent to the IDI data manager 240. Accordingly, the MIDI data manager 240 determines that the event has been established at the port 1 (step Sb1; YES), and proceeds to step Sb2. In step Sb2, the MIDI data manager 240 stores the MIDI event storage 230-
1 and read the channel number of the event.

The MIDI data manager means 240
If it is determined that the event stored in the MIDI event storage unit 230-1 is a 2Ch event, the RA
With reference to the part table (see FIG. 9B) stored in the M400 or the like, the part (part 2 and part 3) to be processed in this 2Ch is grasped. The MIDI data manager 240 performs processing for one part in step Sb2, but there are a plurality of parts (part 2 and part 3) to be processed in 2Ch. For this reason, MIDI
The data manager 240 determines which part should be processed first, and performs one part processing based on the result of the determination. The criterion for determining which part should be processed first has no relation to the gist of the present invention, and thus is omitted here.

Here, MIDI data manager means 2
40 determines that part 2 should be processed first (step Sb2). When the processing for one part is completed, the MIDI data manager means 240, after completing the processing for the part 2, does not perform the processing for all the parts corresponding to this event, that is, without performing the processing for the part 3, and performs processing on the other port. It is determined whether or not the event is established (step Sb3). Here, it is assumed that the MIDI data manager 240 has received a notification from the MIDI event interpreter 220-2 that the event has been established at the port 2 during the event processing of the port 1.

Thus, the MIDI data manager 240 determines that the event has been established at another port (step Sb3; YES), and proceeds to step Sb5. In step Sb5, the MIDI data manager 240 processes an event established at another port. However, the processing in step Sb5 is the same as that in FIG.
1 is inherited. That is, even when there are a plurality of parts to be processed in the event of another port, only the processing for one part is performed (see step Sb2). Here, the event established at the other port is an event of 1Ch established at the port 2, and the part to be processed is only the part 1. MIDI data manager means 240
The processing of part 1 corresponding to the event is performed, and the process proceeds to step Sb4.

The MIDI data manager means 240
In this step Sb4, it is determined whether or not there is a next part to be processed with respect to the port 1 event processed last time. As described above, the MIDI data manager means 240 has only performed the processing of one part, that is, the processing of part 2 for the event of port 1, and has not performed the processing of part 3 yet. Therefore, MI
The DI data manager 240 determines that there is a part to be processed (step Sb4; YES), returns to step Sb2, and performs processing of part 3 which has not been processed. When the processing of Part 3 ends, the MIDI data manager 240 proceeds to Step Sb3. here,
The MIDI data manager means 240 determines in step Sb2
It is assumed that an event establishment notification has not been received from another port until the processing of (1) is completed.

Accordingly, the MIDI data manager means 240 determines that the event has not been established at another port (step Sb3; NO), and proceeds to step Sb4. In step Sb4, the MIDI data manager 240 determines whether there is any remaining part to be processed for the event of port 1. Here, all the part processes related to the event of the port 1 have been completed. If the MIDI data manager 240 determines that all the part processes related to the event of the port 1 have been completed, the process returns to step Sb1 and repeats the above-described processes.

As described above, in the multi-port sound source according to the present embodiment, even when there are a plurality of parts to be processed with respect to an event established in one port, the processing of the port is concentrated. It is not performed (see FIG. 12). Therefore, it is possible to prevent a problem that the processing of the event established in another port is delayed.

[0037]

As described above, according to the present invention,
There is an effect that it is possible to provide a music data processing device capable of uniformly processing events input through a plurality of input ports.

[Brief description of the drawings]

FIG. 1 shows a sound source device 10 according to a first embodiment of the present invention.
FIG. 2 is a block diagram showing a schematic configuration of a block 0.

FIG. 2 is a functional block diagram illustrating a control function of a CPU 200 according to the embodiment.

FIG. 3 shows an MID in the sound source device 100 according to the embodiment.
FIG. 3 is a diagram illustrating a case where I data is input.

FIG. 4 is an event interpretation unit 220 according to the embodiment.
6 is a flowchart showing the operation of the first embodiment.

FIG. 5 is a diagram showing MIDI data constituting an event.

FIG. 6 is a flowchart showing the operation of the MIDI data manager means 240 in the embodiment.

FIG. 7 is a diagram schematically showing MIDI data input to the sound source device 100 according to the embodiment.

FIG. 8 is a diagram showing a relationship among ports, channels, and parts.

FIG. 9 is a diagram for explaining the concept of a multi-part.

FIG. 10 is a diagram schematically showing a flow of data processing in the embodiment.

FIG. 11 is a flowchart showing an operation of a MIDI data manager means 240 in the second embodiment.

FIG. 12 is a diagram schematically showing a flow of data processing in the embodiment.

FIG. 13 is a diagram for explaining a conventional sound source device.

FIG. 14 is a diagram schematically showing a flow of data processing in a conventional sound source device.

[Explanation of symbols]

 210-k: Serial data receiving means 220-k: MIDI event interpreting means 230-k: MIDI event storage means 240: MIDI data manager means 100: Sound source device

Claims (2)

[Claims] When a music event is input from a plurality of ports for connecting to an external device and a music event is input from a port, the music event input from a port different from the port to which the music event processed last time is input is transmitted. A music data processing apparatus, comprising: an event processing unit that performs priority processing. 2. The method according to claim 1, wherein the event processing means performs one or more parts processing on one music event, and executes the processing if the music event input through the port is a music event performing multiple parts processing. Determines whether there is a music event input from a port different from the port after performing one part of processing on the music event, and determines that there is a music event input from a different port. 2. The music data processing device according to claim 1, wherein when the judgment is made, the music event is preferentially processed.