JPH03213894A - Electronic musical instrument - Google Patents

Abstract

PURPOSE:To recognize the state of performance by each player with a master equipment by recognizing an area with a key code and transferring information on area division between the master equipment and a slave equipment. CONSTITUTION:The depressing operation of a key of a keyboard is detected by a 1st instrument, e.g. the slave equipment 10 is detected to obtain the key code corresponding to the key and the key code is transmitted with a sent signal. A 2nd instrument, e.g. the master equipment 30, on the other hand, receives the sent signal from the slave equipment 10 and obtains generated key code information on the slave equipment from the received signal. The slave equipment 10 recognizes which key area the pressed key of the keyboard belongs to according to the key code information. Consequently, even when the keyboard of the salve equipment 10 is divided into plural key areas and played by plural players, the master equipment 30 recognizes who plays the keyboard and how the keyboard is played.

Description

[Detailed Description of the Invention] [Industrial Application Field] The present invention is capable of exchanging key range division information between a master unit and a slave unit by recognizing the key range of a keyboard using a key code. Regarding electronic musical instruments.

[Prior Art] Conventionally, there have been electronic musical instruments (or electronic musical instrument systems) in which a base unit and multiple slave units are connected via a cable, and the base unit can detect which slave unit is playing. Ta. This is a technology found in systems for teaching electronic musical instruments, in which a trainee performs using each slave unit, and the trainee detects the performance status of each slave unit using the base unit.

[Problem to be solved by the invention] In recent years, the keyboard of a slave device has been changed to a certain key range (for example, 2
There are cases where one child electronic musical instrument is played at a pitch of 2 Å or more.

At this time, in the conventional technology as described above, in the base unit,
It can only detect whether a certain slave unit is playing or not.
I couldn't recognize how anyone was performing. Therefore, as an electronic musical instrument system for teaching purposes, there was a problem in that the master unit could not grasp the performance status of the student.

In view of the above-mentioned problems with the conventional type, the present invention provides an electronic musical instrument that is capable of recognizing the key range of pressed keys between a base unit and a slave unit with a simple configuration without providing any new equipment. The purpose is to provide

[Means for Solving the Problems] In order to achieve the above object, an electronic musical instrument according to the present invention detects a keyboard and a key press operation of a key on the keyboard and generates a key code corresponding to the key. a first device comprising means for transmitting the generated key code by means of a transmission signal; means for receiving the transmission signal from the first device; Means for obtaining generated key code information from the first device and recognizing, based on the key code information, to which keyboard range the key of the keyboard that was pressed in the first device belongs to. and a second device comprising:

The first device may be a master device or a slave device.

Correspondingly, the second device may be a child device or a parent device.

The signal transmission between the first device and the second device may be
It is performed in IDI (Musical Instrument Digital Interface) format.

[Function] According to the above configuration, the first device, for example, the handset, detects a key press operation on a keyboard, obtains a key code corresponding to the key, and transmits the key code using a transmission signal. . On the other hand, a second device, such as a base unit, receives the transmission signal from the slave unit and obtains generated key code information in the slave unit from the received signal. Based on this key code information, it is possible to recognize which keyboard range the key on the keyboard that was pressed in the handset belongs to.

As a result, even if the keyboard of the child device is divided into a plurality of key ranges and is played by a plurality of players, it is possible to recognize who is playing and how on the parent device.

Even when the first device is used as a master device and the second device is used as a slave device, information for each key range can be similarly obtained.

[Example] Hereinafter, the present invention will be explained in detail using the drawings.

FIG. 1 is a block diagram of an electronic musical instrument (base unit and slave unit) according to an embodiment of the present invention. In this diagram,
The handset 10 includes a central processing unit (central processing unit) that controls the entire operation of the handset.
CPU) 11, MI for exchanging signals with the base unit
DI interface 12, a read-only interface that stores programs executed by the CPU II and other data.
Memory (ROM) 13, random access memory (RAM) 14 used for work registers, etc., keyboard 15,
A mode switch 16 for switching between normal mode and split mode, other switches 17, a sound source 18, and a sound system 19 are provided. Each of these blocks is connected to a bidirectional path line 20.

The main unit 30 includes a CPU 3 for controlling the operation of the entire main unit.
1. ROM 32 in which programs executed by the CPU 31 and other data are stored; RAM 3B used as a work register; storage section (RAM) 34 for storing (recording) performance information transmitted from slave units; keyboard 35; A recording switch 36, other switches 37, and a MIDI interface 38 for exchanging signals with the handset 10.
, a sound source 39, and a sound system 40. Each of these blocks is connected to a bidirectional path line 41.

The storage section 34 is divided into three tracks, and data can be stored in each track.

The recording switch 36 is a normal recording switch 51 that instructs normal recording (normal recording mode) in which the performance data transmitted from the slave unit 10 is recorded as is, and the performance data transmitted from the slave unit 10 is converted into performance data in the left and right key ranges. A split recording switch 52 for instructing split recording (split recording mode) in which each segment is recorded separately, and a recording stop F (non-recording) switch 53.
Consisting of A receive data register RD is provided inside the MIDI interface 38.

FIG. 2 is an external view of the handset 10 in the electronic musical instrument of this embodiment. Handset 10 has a keyboard 15 . This keyboard 1
5 consists of a left key area 61, a center key area 67, and a right key area 62. In the left key range 61, the leftmost key 63 is the key with pitch name C1 (key code is 36), and the rightmost key 64 is the key with pitch name C3 (key code is 60). ing. Also, the leftmost key 65 in the right key area 62 is the key with pitch name C4 (key code is 72).
The rightmost key 66 in this keyboard range 62 has the pitch name C6.
key (key code is 96).

This handset 10 can be put into normal mode or split mode by operating mode switch 16. In the normal mode, the entire keyboard range of the keyboard 15 is valid, and the keyboard stand with pitches from pitch C1 to pitch C06 can produce sounds. In split mode, key range 67
keys will be invalidated. In Figure 2, the cover is on. In the split mode, two players, one using the keyboard area 61 and the other using the keyboard area 62, can perform on one slave unit 10. At this time, the key area 61
For performances in the key range 62, the pitch of the keystrokes (pitches from C1 to CB) will be automatically raised by one octave, while for performances in the key range 62, the pitches of the keystrokes (pitches from C4 to C6) will be automatically raised by one octave. pitch 2
Automatically lowers the octave. This allows the two performers to perform at the same pitch.

Next, the registers used in the handset 10 will be explained.

(1) KCD: Key code register that stores key codes. The key code register of channel i is represented by KCDi.

(2) KON: Key-on flag. It is set to 1 when processing a key-on event, and 0 when processing a key-off event.
will be reset to Set key-on flag of channel i to K
Represented by ONi.

(3) MODE: Mode flag. O indicates normal mode (no key area division), and 1 indicates split mode (area division).

Next, the processing procedure in the handset 10 will be explained with reference to the flowchart in FIG.

In the handset 10, first, initialization is performed in step S11, then key press processing is performed in step S12, mode selection processing is performed in step 51.3, and step S14 is performed.
After performing other processing, the process returns to step S12. Repeat the above loop processing.

Referring to FIG. 4, in the key press process of step S12 in FIG. 3, first, in step S21, it is determined whether or not there is a key-on event. If there is a key-on event, channel assignment processing (the assigned channel is l) is performed in step S22 to generate the sound of the key. Then, in step 823, the key-on flag KON i is set to 1, and the key code with the key-on event is stored in the key code register KCD i. Next, step S
In step S24, a key-on and key code are transmitted based on the MIDI method, and in step S25, it is determined whether the current mode of the handset is normal mode or split mode.

If it is the normal mode, the note-on and key code KCD i are sent to the sound source in step S26, and the sound corresponding to the pressed key is generated, after which the process proceeds to step S31.

If it is the split mode in step S25, the key codes KCD i and 71 are compared in step S27,
The key where the key-on event occurred is the left key area 61 in Figure 2.
or the right key area 62. If the key code is greater than 71, the right key area 62
Since it is a key-on event in step 328
Sends note-on, key code K CD ls and octave data lowering 2 octaves to the sound source, key range 6
After producing the sound corresponding to the key pressed in step 2, step 5
Proceed to 31. If the determination in step S27 is negative, it is a key-on event in the left key area 61 or the center key area 67, so the key codes KCDi and 61 are compared in step S29. Key code KCDi
If is smaller than 61, it is a key-on event in the left key range 61, so in step S30, note-on,
After transmitting the key code KCDi and the octave data for raising the pitch by l to the sound source and producing the sound corresponding to the key depression in the key range 61, the process advances to step S31. If the determination in step S29 is negative, it is a key-on event in the central key area 67, so it is ignored and the process directly proceeds to step S31.

If it is not a key-on event in step 521, the process branches directly to step 531.

In step S31, it is determined whether there is a key-off event. If there is a key-off event, step S3
2. A channel currently being sounded with a key code matching the key code of this lever is searched, and it is determined in step 533 whether or not the corresponding channel exists. Applicable channel (
If there is a channel number i), the key-on flag KON i is cleared to zero in step S34, and the key-on flag KON i is cleared to zero in step S34.
In step S35, a key-off and key code are transmitted by MIDI, and in step S36, a note-off is transmitted to the i-channel of the sound source to mute the sound, and then the process returns.

If it is determined in step S31 that it is not a key-off event, the process directly returns. Furthermore, if there is no corresponding channel in step 33B, the process returns in the same way.

Next, the mode selection process in step 813 in FIG. 3 will be described with reference to the flowchart in FIG. In the mode selection process, first, in step 541, it is determined whether or not there is a mode switch on event. If there is an on event of the mode switch, step S42
Inverts the mode flag MODE and returns. If there is no mode switch on event in step S41, the process returns directly.

As described above, the handset operates as shown in FIGS. 3, 4, and 5.

Next, the processing procedure of the base unit will be explained with reference to the flowcharts of FIGS. 6, 7, and 8. Note that the recording mode flag REC on the base unit is 0 for not recording, 1 for normal recording mode for recording the data sent from the slave unit as is, and 2 for recording the data sent from the slave unit for performance in any key range. Each indicates a split recording mode in which it is determined whether the data is data and the data is recorded separately for each key range.

Referring to FIG. 6, in the base unit, first, step S5
1, initialization is performed, and key press processing is performed in step S52. Then, a recording switch process is performed in step 853, a recording process is performed in step S54, and other processes are performed in step S55, and then the process returns to step S52. Repeat the above loop processing.

With reference to FIG. 7, the recording switch process in step S53 in FIG. 6 will be described.

In the recording switch process, first in step S61 it is determined whether there is an on event of the recording switch. If there is no recording switch on event, step S65
Proceed to. If there is an on-event of the recording switch, it is determined in step S62 whether or not it is an on-event of the normal recording switch. If it is an on event of the normal recording switch, the value 1 indicating the normal recording mode is stored in the recording mode flag REC in step 363, and the process proceeds to step S65. If it is not normal recording in step S62, the split recording switch is on, so a value 2 indicating the split recording mode is stored in the recording mode flag RFC in step S64, and the process proceeds to step S65.

In step S65, it is determined whether there is an on event of the recording stop switch. If the recording stop switch is turned on, the recording mode flag RFC is cleared to zero in step S66, and the process returns.

If there is no recording stop+It switch on event in step S65, the process returns directly.

Next, the recording process in step S54 in FIG. 6 will be described with reference to the flowchart in FIG.

In the recording process, first, in step 571, it is determined whether the recording mode flag REC is 0 or not. If the recording mode flag REC is 0, this means that the performance data sent from the slave unit will not be recorded, and the process returns directly. If the recording mode flag RFC is not 0, it is determined in step S72 whether or not there is a MIDI message. If there is no message, the process returns directly, and if there is a message, the process advances to step 573.

In step 373, the data in the reception data register RD inside the MIDI interface 38 is taken into a buffer, and in step S74, it is determined whether the message sent from the slave unit is key-on or key-off. If the key is neither on nor off, simply return.

If the message is key-on or key-off in step S74, the recording mode flag R is determined in step S75.
It is determined whether or not EC is 1, that is, whether or not the mode is normal recording mode.

If the mode is normal recording mode, the performance data received in step S76 is written to track 1 of the storage section 34,
Return. If it is not the recording mode or the normal recording mode in step S75, it is the split recording mode, so it is determined in step S77 whether the key code is greater than 71, that is, whether the key code is key-on or key-off in the right key range 62. If the operation is for the right key area 62, the performance data is written to track 2 of the storage section 34 in step 578, and the process returns. In step S77, the right key area 62
If it is not the operation, the key code is 6 in step S79.
Determine whether it is smaller than 1. If the key code is smaller than 61, since the operation is in the left key area 61, the performance data is written in track 3 of the storage section 34 in step S80, and the process returns. If the key code is not smaller than 61 in step S79, the operation is in the central key area 67, so it is ignored and the process returns.

As explained above, in the electronic musical instrument of this embodiment, the slave unit sends a key code in MID I format to the base unit, and the base unit identifies this key code and performs operations in the specified key range. I can recognize what is happening. Therefore, the playing status of the performer playing in each key range of the child device can be confirmed on the parent device.

In the above-described embodiment, the transmission method is the MID1 method, but various transmission methods other than this may be used. Furthermore, the number of child devices connected to the parent device is not limited to one, and may be any number.

In the above embodiment, the base unit recognized the keyboard range of the keys pressed on the slave unit, but conversely, the slave unit can recognize the key range of the base unit, and bidirectional recognition is also possible. I'll come. Key range recognition is applied not only to recording, but also to various situations such as displaying information about the recognized key range on the receiving side or producing sound.

The key range is not limited to that of the embodiment, and the number of keys is also the same. Furthermore, although the above-described embodiments are controlled by software, they may also be controlled by hardware.

[Effects of the Invention] As explained above, according to the present invention, by recognizing the key range with a key code, area division information can be exchanged between the base unit and the slave unit, and new devices can be developed. Key ranges can be recognized between devices with a simple configuration without the need for special provision. Therefore, even when a plurality of performers are playing on one slave unit, the master unit can grasp the performance status of each performer.

[Brief explanation of drawings]

FIG. 1 is a block diagram showing a schematic configuration of an electronic musical instrument (slave unit and base unit) according to an embodiment of the present invention, FIG. 2 is an external view of the slave unit of this embodiment, and FIG. FIG. 4 is a flowchart of the main routine in the slave unit of the electronic musical instrument of this embodiment. FIG. 5 is a flowchart of key press processing of the slave unit of the electronic musical instrument of this embodiment. FIG. 6 is a flowchart of the main routine in the base unit of the electronic musical instrument of this embodiment. FIG. 7 is a flowchart of the recording switch process in the base unit of the electronic musical instrument of this embodiment. The figure is a flowchart of the recording process in the base device of the electronic musical instrument of this embodiment. 11: CPU, 12: MIDI interface, 13: ROM, 14: RAM, 15: Keyboard, 16: Mode switch, 31: CPU, 34:
Storage section (RAM), 36: Recording switch, 38: M
IDI interface, 42: MIDI transmission line. Figure ■

Claims (1)

[Claims] (1) A keyboard comprising a keyboard, means for detecting key press operations on the keyboard and generating a key code corresponding to the pressed key, and means for transmitting the generated key code by a transmission signal. 1 device; means for receiving a transmission signal from the first device; obtaining key code information generated in the first device from the received signal in the receiving device; An electronic musical instrument comprising: a second device having means for recognizing to which keyboard range a key of a keyboard pressed in the first device belongs.