Control device, control method and control system

Abstract

To provide a control device, a control method, and a control system that allow at least two control devices to control an electronic musical instrument that can be connected to one control device.SOLUTION: In a control system S, headphones 30 and a pedal device 1 communicate with each other through first communication w1, and the pedal device 1 and a mobile terminal 50 communicate with each other through second communication w2. Thereby, even if the headphones 30 can be connected to only one control device, a control instruction from the pedal device 1 can be transmitted to the headphones 30 via the first communication w1, and a control instruction from the mobile terminal 50 can be transmitted to the headphones 30 via the second communication w2 and the first communication w1.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The present invention relates to a control device, a control method, and a control system. [Background technology]

[0002] Non-Patent Document 1 discloses headphones that are paired with a mobile device for use. The headphones can control the volume and the amount of built-in sound effects by operating the touch panel of the paired mobile device. [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] [Retrieved July 8, 2021], Internet<URL:https: / / static.roland.com / assets / media / pdf / WAZA-AIR_jpn04_W.pdf> Summary of the Invention [Problem to be solved by the invention]

[0004] Recently, there has been an increasing demand for electronic musical instruments to be able to control the volume and the like not only with a control device operated by hand such as a mobile terminal, but also with a control device operated by foot such as a pedal device. However, the headphones of Non-Patent Document 1 have a problem in that, since only one control device can be connected by pairing, the headphones can be controlled from one control device, but cannot be controlled from multiple control devices.

[0005] The present invention has been made to solve the above-mentioned problems, and aims to provide a control device, control method, and control system that enables an electronic musical instrument that can be connected to one control device to be controlled from at least two control devices. [Means for solving the problem]

[0006] In order to achieve this object, the control device of the present invention is a device for controlling an electronic musical instrument, and includes: input means for inputting control instructions; first communication means for wirelessly communicating with the electronic musical instrument; second communication means for wirelessly communicating with a second control device that controls the electronic musical instrument; and instruction transmission means for transmitting, to the electronic musical instrument, the control instructions input by the input means and second control instructions received from the second control device via the second communication means; a determination means for determining whether or not a second control instruction received from the second control device via the second communication means is a control instruction to the control device itself; It is equipped with:

[0007] The control method of the present invention is a method executed by a control device connected via wireless communication to an electronic musical instrument and a second control device that controls the electronic musical instrument, and includes an input step of inputting a control instruction, a first communication step of wirelessly communicating with the electronic musical instrument, a second communication step of wirelessly communicating with the second control device that controls the electronic musical instrument, and an instruction transmission step of transmitting the control instruction inputted in the input step and a second control instruction received from the second control device via the second communication step to the electronic musical instrument by the first communication step. a determination step of determining whether or not the second control instruction received from the second control device in the second communication step is a control instruction to the control device itself; It is equipped with:

[0008] The control system of the present invention is a control system comprising an electronic musical instrument, a second control device that controls the electronic musical instrument, and a control device connected to the electronic musical instrument and the second control device via wireless communication, wherein the second control device comprises a transmission means for transmitting a second control instruction to the control device, and the control device comprises an input means for inputting a control instruction, a first communication means for wireless communication with the electronic musical instrument, a second communication means for wireless communication with the second control device, and an instruction transmission means for transmitting the control instruction input by the input means and the second control instruction received from the second control device via the second communication means to the electronic musical instrument via the first communication means. a determination means for determining whether or not a second control instruction received from the second control device via the second communication means is a control instruction to the control device itself; It is equipped with: [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram showing an overview of a control system. [Diagram 2]1A is a side view of the pedal device from the left, FIG. 1B is a side view of the pedal device from the right, FIG. 1C is a rear view of the pedal device, and FIG. 1D is an external view of headphones. [Diagram 3] FIG. 1A is a diagram for explaining a procedure for establishing communication between a pedal device and headphones, and FIG. 1B is a diagram for explaining a procedure for establishing communication between the pedal device and a mobile terminal. [Figure 4] FIG. 13A is a diagram for explaining acquisition of an inquiry message from a headphone of a mobile terminal, and FIG. 13B is a diagram for explaining acquisition of an inquiry message from a pedal device of the mobile terminal. [Diagram 5] FIG. 1A is a diagram for explaining control of headphones by operating a mobile terminal, and FIG. 1B is a diagram for explaining control of a pedal device by operating a mobile terminal. [Figure 6] FIG. 13A is a diagram for explaining control of headphones by operating a pedal device, and FIG. 13B is a diagram for explaining a case where the timing of transmission of a control instruction and an update instruction overlap. [Figure 7] FIG. 2 is a functional block diagram of the pedal device. [Figure 8] FIG. 2 is a block diagram showing the electrical configuration of the control system. [Figure 9] 13 is a flowchart of headphone processing. [Figure 10] 13A is a flowchart of a peripheral connection process, and FIG. 13B is a flowchart of an identity request response process. [Figure 11] 13A is a flowchart of pedal processing, and FIG. 13B is a flowchart of central connection processing. [Figure 12] 13 is a flowchart of a pedal device transmission / reception process. [Figure 13] 13 is a flowchart of a mobile terminal process. [Figure 14] 13 is a flowchart of a mobile terminal transmission and reception process. [Figure 15] FIG. 13 is a diagram illustrating an overview of a control system according to a modified example. [Figure 16]FIG. 13 is a block diagram showing an electrical configuration of a control system in a modified example. [Figure 17] 13 is a flowchart of a process specific to a synthesizer in a modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] A preferred embodiment will be described below with reference to the accompanying drawings. An overview of a control system S according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing an overview of the control system S. The control system S is composed of a pedal device 1, headphones 30, and a mobile terminal 50. The pedal device 1 and the headphones 30 are connected by wireless communication, and the pedal device 1 and the mobile terminal 50 are also connected by wireless communication.

[0011] The pedal device 1 is a device that inputs operations of settings related to a performance (for example, volume, level of sound effects, etc.) from a user H who performs a performance, and creates and transmits control instructions, which are information instructing other devices (specifically, headphones 30 and mobile terminal 50) to control, based on parameters according to the amount of operation. The pedal device 1 also has a function of transmitting a control instruction transmitted from the mobile terminal 50 to the headphones 30, and a function of transmitting a response to the control instruction of the mobile terminal 50 transmitted from the headphones 30 to the mobile terminal 50. These transmissions will be described later with reference to Figs. 3 to 6.

[0012] The headphones 30 are an electronic musical instrument that outputs musical sounds based on the performance of an electric guitar G by a user H. The electric guitar G and the headphones 30 are wirelessly connected by a musical instrument transmitting device Gt that is connected to the electric guitar G. A performance signal output by the user H playing the electric guitar G is transmitted to the headphones 30 via the musical instrument transmitting device Gt.

[0013] In the headphones 30, performance sounds corresponding to the received performance signals are output from the speakers R and L. At this time, the headphones 30 are configured so that sound effects such as delay and distortion can be added to the output performance sounds, and the degree of the sound effects can be changed according to parameters from the pedal device 1 or the mobile terminal 50.

[0014] It should be noted that the instrument that transmits the performance signal to the headphones 30 is not limited to an electric guitar G connected to an instrument transmitting device Gt, but may also be other electric or electronic instruments, such as an electronic drum or an electronic wind instrument connected to an instrument transmitting device Gt.

[0015] The mobile terminal 50 is an information processing device (computer) that transmits control instructions to the pedal device 1 and the headphones 30. A control instruction input from the mobile terminal 50 is transmitted to the headphones 30 via the pedal device 1. This makes it possible to control the pedal device 1 and the headphones 30 from the mobile terminal 50.

[0016] The configurations of the pedal device 1 and headphones 30 will now be described with reference to Fig. 2. Fig. 2(a) is a side view of the pedal device 1 from the left, Fig. 2(b) is a side view of the pedal device 1 from the right, and Fig. 2(c) is a rear view of the pedal device 1. The pedal device 1 is provided with a pedal switch 15, an operator 16, an LED 17, a DC input terminal 18, a MIDI output terminal 19 for wired connection to an external device conforming to the MIDI (Musical Instrument Digital Interface) standard, and a communication terminal 20 for wired connection to an external information processing device.

[0017] The pedal switch 15 is provided on the upper part of the pedal device 1, and is a device that detects the angle when the pedal switch 15 is depressed by the foot of the user H. The pedal switch 15 is configured like a "see-saw" with a predetermined position as the fulcrum, and outputs a parameter according to the angle of the pedal switch 15 that changes when the pedal switch 15 is depressed by the foot of the user H. The parameter is transmitted to the headphones 30 and the mobile terminal 50 via wireless communication. In this embodiment, a control change message (hereinafter abbreviated as "CC message") conforming to the MIDI standard that includes the parameters acquired based on the pedal switch 15 is transmitted from the pedal device 1.

[0018] The pedal device 1 is configured so that the angle of the pedal switch 15 that outputs the maximum parameter and the angle of the pedal switch 15 that outputs the minimum parameter can be calibrated. In addition, by depressing the tip side of the pedal switch 15 (the left side of the paper in FIG. 2(a)) with a predetermined or greater depressing force, the "number" of the CC message can be switched to a predetermined value.

[0019] The operator 16 is an input device for inputting an instruction from the user H to start pairing with another device, and is provided on the back surface of the pedal device 1. The LED 17 is a device for outputting the state of the pedal device 1 and the connection state with the headphones 30 and the mobile terminal 50 by lighting up or blinking, and is provided on the left and right side surfaces and the back surface of the pedal device 1. The DC input terminal 18 is a terminal for inputting direct current to the pedal device 1, and is provided on the back surface of the pedal device 1. The power input from the DC input terminal 18 is used to power the pedal device 1. Although not shown, a battery is built into the pedal device 1, and when no direct current is input from the DC input terminal 18, the power supplied from the battery is used to power the pedal device 1.

[0020] The data transmitted from the pedal device 1 is not limited to CC messages of the MIDI standard, but may be messages of other MIDI standards, such as system exclusive messages (hereinafter abbreviated as "SysEx messages").

[0021] Next, the headphones 30 will be described. Fig. 2(d) is an external view of the headphones 30. In addition to the above-mentioned speakers R and L, the headphones 30 are provided with an LED 38 that outputs the state of the operator 37 and the headphones 30 and the connection state with the pedal device 1 by lighting up in a certain color or flashing.

[0022] The operator 37 is an input device for inputting various instructions such as the volume of the performance sound output from the speakers R and L from the user H, switching of the sound effect added to the performance sound, and an instruction to start connection with the pedal device 1, and a plurality of operators 37 are provided on the headphones 30. When music is played through the headphones 30, the operator 37 functions as a device for controlling music playback such as play / stop and fast forward.

[0023] Next, procedures for establishing communication and transmission and reception of information among the pedal device 1, the headphones 30, and the mobile terminal 50 will be described with reference to Figures 3 to 6. First, procedures for establishing communication between the pedal device 1 and the headphones 30 will be described with reference to Figure 3(a).

[0024] 3(a) is a diagram for explaining a procedure for establishing communication between the pedal device 1 and the headphones 30. A communication mode is set in communication devices such as the pedal device 1, the headphones 30, and the mobile terminal 50 of this embodiment, and communication is performed according to the set communication mode. The communication mode is provided with a "central" that issues instructions to other communication devices, and a "peripheral" that responds to instructions from other communication devices in which the central is set.

[0025] In this embodiment, a central is set in the mobile terminal 50, and a peripheral is set in the headphones 30. In the pedal device 1, the peripheral is used when communicating with the mobile terminal 50 that is the central, and the central is used when communicating with the headphones 30 that is the peripheral. That is, the pedal device 1 is configured so that the central and the peripheral can be switched or can operate simultaneously depending on the communication mode of the communication partner.

[0026] When establishing communication with the headphones 30 and the mobile terminal 50, the pedal device 1 first attempts to establish communication with the headphones 30 in which the peripheral is set. At this time, the pedal device 1 is regarded as a central communication device, and checks whether it has received an advertising packet AD. The advertising packet AD is a signal transmitted when the peripheral communication device establishes communication with the central communication device. When the pedal device 1 receives the advertising packet AD, it establishes communication with the communication device that is the source of the advertising packet AD.

[0027] 3(a), the pedal device 1 receives an advertising packet AD transmitted from the headphones 30, thereby establishing a first communication w1 with the headphones 30 and pairing the headphones 30 with the pedal device 1. An operation of the user H on the pedal device 1 in this case will be described.

[0028] First, the user H double-clicks the operator 16, which alternates (toggles) between the central function and the peripheral function. The central function is a function for connecting the pedal device 1 to a peripheral communication device, and the peripheral function is a function for connecting the pedal device 1 to a central communication device. When the central function is set in the pedal device 1, the LED 17 lights up in white, and when the central function is set, the LED 17 lights up in blue.

[0029] First, the central function will be described. When the operator 16 is double-clicked to switch to the central function, the mode switches to a "reception standby mode" in which the mode waits for reception of an advertising packet AD transmitted from a peripheral communication device, i.e., the headphones 30. In this reception standby mode, the LED 17 slowly flashes in white.

[0030] In the reception standby mode, by single-clicking the control 16, the mode switches to a "scan mode" in which the advertising packet AD from the headphones 30 is received. In this scan mode, the LED 17 flashes quickly in white. In the scan mode, if pairing with the headphones 30 is achieved by receiving the advertising packet AD from the headphones 30, the mode switches to a "connection complete mode." In this connection complete mode, the LED 17 lights up in white. The user H can grasp the pairing status with the headphones 30 by the white lighting or flashing state of the LED 17.

[0031] Via the first communication w1 thus established, a control instruction from the central pedal device 1 is transmitted to the headphones 30, and a response to the control instruction is transmitted from the headphones 30 to the pedal device 1.

[0032] Note that the device that establishes the first communication w1 with the pedal device 1 is not limited to the headphones 30, but may be another communication device in which a peripheral is set, such as the portable effector 300 in Fig. 3(a) or a floor-mounted effector 310. Both of these effectors 300 and 310 are devices that are connected to an electric guitar G (see Fig. 1) and output performance sounds corresponding to performance signals from the electric guitar G with added sound effects.

[0033] Next, with reference to Fig. 3(b), a procedure for establishing communication between the pedal device 1 and the mobile terminal 50 using the peripheral function will be described. Fig. 3(b) is a diagram for explaining the procedure for establishing communication between the pedal device 1 and the mobile terminal 50. The pedal device 1 establishes a connection with a central communication device, i.e., the mobile terminal 50, using the peripheral function.

[0034] When the operation button 16 is double-clicked to switch to the peripheral function, the mode switches to a "transmission standby mode" in which the mode waits for transmission of an advertising packet AD to the mobile terminal 50. In the transmission standby mode, the LED 17 flashes slowly in blue.

[0035] In the transmission standby mode, by single-clicking the operator 16, the mode is switched to an "advertising mode" in which an advertising packet AD is transmitted to the mobile terminal 50. In this advertising mode, the LED 17 flashes blue quickly. In the advertising mode, if pairing with the mobile terminal 50 that received the advertising packet AD transmitted by the pedal device 1 is successful, the mode is switched to a "connection complete mode." In this connection complete mode, the LED 17 lights up blue. The user H can grasp the pairing status with the mobile terminal 50 by the blue lighting or flashing state of the LED 17.

[0036] Through the second communication w2 thus established, a control instruction from the mobile terminal 50 of the central is transmitted to the pedal device 1, and a response according to the control instruction is transmitted from the pedal device 1 to the mobile terminal 50. In this embodiment, both the first communication w1 and the second communication w2 are communicated based on the Bluetooth (registered trademark) Low Energy (BLE) standard, but the first communication w1 or the second communication w2 may be communicated based on a communication standard other than the BLE standard.

[0037] When the second communication w2 is established, if the advertising packet AD in the mobile terminal 50 contains information that communication with the headphones 30 has been established, the mobile terminal 50 can determine that communication with the headphones 30 is possible via the pedal device 1. In such a case, "ABC+" is displayed on the LCD 57 of the mobile terminal 50. On the other hand, if the advertising packet AD does not contain information that communication with the headphones 30 has been established, "ABC" (not shown) is displayed on the LCD 57.

[0038] Here, "ABC" is a name for identifying the device, and may be, for example, a model number, a product ID, or an abbreviation thereof. From "ABC+" or "ABC" displayed on the LCD 57, the user H can determine at a glance whether the pedal device 1 has completed establishing communication with the headphones 30.

[0039] Here, whether the mobile terminal 50 and the headphones 30 are connected via the pedal device 1 can also be known by checking the lighting color or the lighting or blinking state of the LED 17 of the pedal device 1. Specifically, if the pedal device 1 attempts pairing with the headphones 30, and after it is confirmed by the LED 17 lighting blue that the pairing has been established, the pedal device 1 attempts pairing with the mobile terminal 50, and after it is confirmed by the LED 17 lighting white that the pairing has been established, it can be confirmed that the mobile terminal 50 and the headphones 30 are connected. However, since the pedal device 1 is placed at the feet of the user H, the user H who plays the electric guitar G must temporarily put down the electric guitar G and change his / her posture, such as crouching down, so that the LED 17 can be seen.

[0040] In contrast, the portable terminal 50 can be placed in the hand of the user H, so the user H can check whether the pedal device 1 has completed establishing communication with the headphones 30 by the display of "ABC+" or "ABC" without putting down the electric guitar he is playing or even changing his posture. In addition, the LCD 57 on which these are displayed can display more flexibly and in a variety of ways compared to the LED 17, so that it is possible to show the user H with good visibility whether the headphones 30 and the portable terminal 50 are connected.

[0041] Note that the case where the advertising packet AD includes information indicating that communication with the headphones 30 has been established / the case where the advertising packet AD does not include this information is not limited to being displayed on the LCD 57, and may be output by voice, for example, or may be output using other methods. When outputting by voice, if the advertising packet AD includes this information, "ABC+" may be output by voice, and if the advertising packet AD does not include this information, "ABC" may be output by voice.

[0042] Furthermore, the mobile terminal 50 is configured such that the communication device to be controlled can be selected from the pedal device 1 and the headphones 30 by switching between applications (hereinafter abbreviated as "app"). In FIG. 3(b), an app that controls the headphones 30 is being executed on the mobile terminal 50, so "headphones" is displayed on the LCD 57. On the other hand, when an app that controls the pedal device 1 is being executed on the mobile terminal 50, "pedal device" (see FIG. 4(b)) is displayed on the LCD 57.

[0043] After the first communication w1 and the second communication w2 are established in this way, the mobile terminal 50 acquires an inquiry message IQ of the MIDI standard, which is information about the communication device such as version information of the control programs 32a, 52a (see FIG. 8), from the communication device to be controlled. Acquisition of the inquiry message IQ will be described with reference to FIG. 4.

[0044] Fig. 4(a) is a diagram for explaining the acquisition of an inquiry message IQ from the headphones 30 of the mobile terminal 50, and Fig. 4(b) is a diagram for explaining the acquisition of an inquiry message IQ from the pedal device 1 of the mobile terminal 50. In Fig. 4(a), when the mobile terminal 50 requests an inquiry message IQ from the headphones 30, the mobile terminal 50 first creates feature request data SR instructing a request for the inquiry message IQ.

[0045] The feature request data SR includes a "model ID" that indicates the name and type of the communication device that requests the inquiry message IQ, that is, the communication device that is the control target of the mobile terminal 50. In Fig. 4(a), since the control target of the mobile terminal 50 is the headphones 30, a unique ID that identifies the headphones 30 is set as the model ID of the feature request data SR.

[0046] The background request data SR created in this manner is first transmitted to the pedal device 1 which has established the second communication w2 with the mobile terminal 50. The pedal device 1 transmits the received background request data SR to the headphones 30 via the first communication w1, and checks the model ID included in the background request data SR.

[0047] 4(a), since the model ID included in the feature request data SR is “headphones”, the pedal device 1 determines that the received feature request data SR is not intended for itself, and discards the received feature request data SR. In other words, the pedal device 1 passes the received feature request data SR through to the headphones 30.

[0048] The headphones 30 checks the model ID of the feature request data SR received from the pedal device 1, and if it is its own, transmits its own inquiry message IQ to the pedal device 1. The inquiry message IQ includes the model ID of the headphones 30 as well as the feature request data SR.

[0049] The pedal device 1 that receives the inquiry message IQ from the headphones 30 transmits the inquiry message IQ to the mobile terminal 50 and checks whether the model ID included in the inquiry message IQ is its own. In Fig. 4(a), since the model ID included in the inquiry message IQ is an ID that identifies the headphones 30, the pedal device 1 determines that the received inquiry message IQ is not intended for itself, and discards the received inquiry message IQ.

[0050] The mobile terminal 50 that has received the inquiry message IQ from the pedal device 1 checks whether the model ID included in the inquiry message IQ is its own. In Fig. 4(a) , the model ID included in the inquiry message IQ is an ID that identifies the headphones 30. In this case, the mobile terminal 50 obtains information about the headphones 30 included in the inquiry message IQ, and uses the information for subsequent control instructions to the headphones 30.

[0051] Similarly, as shown in FIG. 4(b), when the control target of the mobile terminal 50 is the pedal device 1 and an inquiry message IQ for the pedal device 1 is requested, a unique ID identifying the pedal device 1 is set as the model ID of the feature request data SR sent from the mobile terminal 50, and the feature request data SR is sent to the pedal device 1.

[0052] The pedal device 1 transmits the received feature request data SR to the headphones 30 and checks the model ID of the feature request data SR. In Fig. 4(b), since the model ID of the feature request data SR is an ID that identifies the pedal device 1, the pedal device 1 transmits its own inquiry message IQ to the mobile terminal 50. The inquiry message IQ includes the model ID of the pedal device 1.

[0053] The mobile terminal 50 that has received the inquiry message IQ from the pedal device 1 checks whether the model ID included in the inquiry message IQ is its own, and in Fig. 4(b) , the model ID included in the inquiry message IQ is an ID that identifies the pedal device 1. In this case, the mobile terminal 50 obtains information about the pedal device 1 included in the inquiry message IQ, and the information is used for subsequent control instructions to the pedal device 1.

[0054] On the other hand, the headphones 30 that received the feature request data SR from the pedal device 1 also checks the model ID of the feature request data SR. In Fig. 4(b), the model ID of the received feature request data SR is "pedal device", which does not match that of the headphones 30, so the received feature request data SR is discarded.

[0055] In this way, after the second communication w2 with the pedal device 1 is established, the mobile terminal 50 obtains the inquiry message IQ from the pedal device 1 or the headphones 30 to be controlled and uses it for the subsequent control instructions. This makes it possible to transmit appropriate control instructions according to the functions and specifications of the controlled object immediately after the communication with the controlled object is established.

[0056] In particular, when the control target of the mobile terminal 50 is the headphones 30, it can be specifically understood that the communication device connected via the pedal device 1 is the headphones 30. Furthermore, since the inquiry message IQ acquires version information of the control program 32a (see FIG. 8) of the headphones 30, it can be confirmed from the mobile terminal 50 whether the control program 32a has been updated to the appropriate version.

[0057] Next, control of the headphones 30 and the pedal device 1 by operating the mobile terminal 50 will be described with reference to Fig. 5. Fig. 5(a) is a diagram for explaining control of the headphones 30 by operating the mobile terminal 50, and Fig. 5(b) is a diagram for explaining control of the pedal device 1 by operating the mobile terminal 50.

[0058] 5(a) illustrates an example in which the volume of a performance sound output from the mobile terminal 50 to the headphones 30 is changed. Note that the target of the operation of the headphones 30 from the mobile terminal 50 is not limited to this, and for example, the degree of the acoustic effect of the performance sound output from the mobile terminal 50 to the headphones 30 or other settings of the headphones 30 may be operated.

[0059] In FIG. 5(a), when an instruction to update the volume of the headphones 30 to 35 is input from the user H to the mobile terminal 50 via the touch panel 56 (see FIG. 8), the mobile terminal 50 creates a control instruction RS for requesting the headphones 30 to carry out that instruction. The control instruction RS includes a parameter to be updated ("volume 35" in FIG. 5(a)) and a model ID of the control target (an ID identifying the headphones 30 in FIG. 5(a)). The mobile terminal 50 transmits a MIDI-standard SysEx message including such a control instruction RS to the pedal device 1.

[0060] The pedal device 1 that has received the SysEx message transmits the SysEx message to the headphones 30, and checks the model ID included in the control instruction RS of the SysEx message. In Fig. 5(a), since the model ID included in the control instruction RS is an ID that identifies the headphones 30 and is not a request to the pedal device 1, the pedal device 1 discards the received SysEx message.

[0061] The headphones 30 that received the SysEx message from the pedal device 1 check the model ID included in the control instruction RS of the SysEx message. In Fig. 5(a), since the model ID included in the control instruction RS is an ID that identifies the headphones 30, the headphones 30 update their own volume using the parameter ("volume 35") included in the control instruction RS. As a result, the volume of the headphones 30 is updated in response to the request from the mobile terminal 50.

[0062] 5(b) illustrates an example in which the type of sound effect controlled by the pedal device 1 is changed from the mobile terminal 50. Note that the type of sound effect controlled by the operation of the pedal device 1 is not limited to what can be changed from the mobile terminal 50. For example, the target of control by the pedal device 1 may be changed from sound effect to volume, or may be changed to another setting item.

[0063] In Fig. 5(b), when an instruction to change the sound effect controlled by the pedal device 1 to "reverb" is input from the user H to the mobile device 50 via the touch panel 56, the mobile device 50 creates a control instruction RS including the parameter to be updated ("sound effect (represented as "FX" in the figure)-reverb" in Fig. 5(b)) and the model ID of the control target (an ID identifying the pedal device 1 in Fig. 5(b)). The mobile device 50 then transmits a MIDI-standard SysEx message including the created control instruction RS to the pedal device 1.

[0064] The pedal device 1 that has received the SysEx message transmits the SysEx message to the headphones 30, and checks the model ID included in the control instruction RS of the SysEx message. In Fig. 5(b), since the model ID included in the control instruction RS is an ID that identifies the pedal device 1, the pedal device 1 uses the parameters (sound effect, reverb) included in the control instruction RS to change the sound effect controlled by the operation of its own pedal switch 15. As a result, the sound effect controlled by the pedal device 1 is changed in response to a request from the mobile terminal 50.

[0065] Next, control of the headphones 30 by operating the pedal device 1 will be described with reference to Fig. 6(a). Fig. 6(a) is a diagram for explaining control of the headphones 30 by operating the pedal device 1. Fig. 6(a) illustrates an example of updating the volume of the headphones 30 in response to operation of the pedal switch 15 of the pedal device 1. At this time, it is assumed that an application for controlling the headphones 30 is also executed on the mobile terminal 50.

[0066] When the pedal switch 15 of the pedal device 1 is depressed with the foot of the user H, parameters according to the angle of the pedal switch 15 are transmitted to the headphones 30 and the mobile terminal 50. At this time, a MIDI standard CC message including the acquired parameters is transmitted to the headphones 30 and the mobile terminal 50.

[0067] When the headphones 30 receive a CC message including an update instruction CC from the pedal device 1, the headphones 30 update their own volume using the parameters included in the update instruction CC.

[0068] Then, it creates a response instruction PS including the parameters included in the update instruction CC and its own model ID, and transmits a SysEx message conforming to the MIDI standard including the response instruction PS to the pedal device 1.

[0069] The pedal device 1, which has received the SysEx message including the response instruction PS, transmits the SysEx message to the mobile terminal 50 and checks the model ID included in the response instruction PS of the SysEx message. In Fig. 6(a), the model ID included in the response instruction PS is an ID that identifies the headphones 30 and is not a request to the pedal device 1, so the pedal device 1 discards the received SysEx message.

[0070] The pedal device 1 transmits to the mobile terminal 50 a SysEx message including an update instruction CC and a response instruction PS. The mobile terminal 50 discards the update instruction CC and acquires the SysEx message including the response instruction PS. The mobile terminal 50 checks the model ID of the response instruction PS in the acquired SysEx message, and if it matches its own control target (headphones 30 in FIG. 6(a)), it updates the corresponding setting (volume in FIG. 6(a)) using the parameters of the response instruction PS.

[0071] That is, the mobile terminal 50 discards the update instruction CC based on the pedal switch 15 from the pedal device 1, while updating its own settings based on the response instruction PS transmitted when the parameters are updated in the headphones 30 based on the update instruction CC based on the pedal switch 15 from the pedal device 1. Therefore, the setting of the mobile terminal 50 is updated when the setting of the headphones 30 is updated based on the update instruction CC from the pedal device 1. This makes it possible to reliably reflect the update instruction CC of the pedal device 1 in the settings of the headphones 30 and the mobile terminal 50.

[0072] Generally, the headphones 30 can communicate with only one communication device. In contrast, in the control system S of the present embodiment, the headphones 30 and the pedal device 1 communicate with each other via a first communication w1, and the pedal device 1 and the mobile terminal 50 communicate with each other via a second communication w2.

[0073] This allows a control instruction from the central pedal device 1 to be transmitted to the headphones 30, and allows a control instruction from the central mobile terminal 50 to be transmitted to the headphones 30 via the second communication w2 and the first communication w1. This makes it possible to provide flexible functions using the mobile terminal 50, pedal device 1, and headphones 30, and allows two central pedal devices 1 and mobile terminals 50 to communicate with one peripheral headphone 30 without going through another communication device, thereby minimizing the configuration and cost of the communication device.

[0074] In addition, in the first communication w1 and the second communication w2 of this embodiment, the control instruction RS from the mobile terminal 50 and the update instruction CC from the pedal device 1 can be transmitted via the same communication path.

[0075] In this embodiment, since the control instruction RS or the update instruction CC can be input from each of the pedal device 1 and the mobile terminal 50, in the pedal device 1, the timing at which the control instruction RS from the mobile terminal 50 is transmitted to the headphones 30 may overlap with the timing at which the update instruction CC based on the pedal switch 15 is transmitted to the headphones 30. The process in such a case will be described with reference to Fig. 6(b).

[0076] Fig. 6(b) is a diagram for explaining a case where the transmission timing of the control instruction RS and the update instruction CC overlap. Fig. 6(b) shows a case where the control instruction RS from the mobile terminal 50 is first transmitted to the headphones 30 by the pedal device 1, the pedal switch 15 is operated during the transmission, and an update instruction CC is created based on the operation.

[0077] In this case, the transmission of the update instruction CC starts after the previously transmitted control instruction RS is completed. This makes it possible to reliably complete the transmission of the control instruction RS and the update instruction CC from the pedal device 1 to the headphones 30 without missing either or both of them, even if the timing of transmitting the control instruction RS and the update instruction CC from the pedal device 1 to the headphones 30 overlaps.

[0078] Next, the function of the pedal device 1 will be described with reference to Fig. 7. Fig. 7 is a functional block diagram of the pedal device 1. As shown in Fig. 7, the pedal device 1 has a first communication means 501, a receiving buffer 502, a transmitting buffer 503, a second communication means 504, a receiving buffer 505, a transmitting buffer 506, an instruction transmitting means 507, the pedal switch 15 described above, a first storage unit 508, a determining means 509, a changing means 510, a MIDI message generating unit 511, the operator 16 described above, a pairing mode transition unit 512, a second storage unit 513, a first communication establishment determining unit 514, and an advertising packet generating unit 515.

[0079] The first communication means 501 is a means for wirelessly communicating with the headphones 30, and is realized by the CPU 10, which will be described later in Fig. 8. The receiving buffer 502 temporarily stores data received by the first communication means 501, and is realized by the RAM 12, which will be described later in Fig. 8. The transmitting buffer 503 temporarily stores data to be transmitted by the first communication means 501, and is realized by the RAM 12.

[0080] The second communication means 504 is a means for wirelessly communicating with the mobile terminal 50, and is realized by the CPU 10. The receiving buffer 505 temporarily stores data received by the second communication means 504, and is realized by the RAM 12. The transmitting buffer 506 temporarily stores data to be transmitted by the second communication means 504, and is realized by the RAM 12. Data such as a SysEx message from the headphones 30 that is received by the first communication means 501 and stored in the receiving buffer 502 is sent to the transmitting buffer 506, and the data is transferred from the transmitting buffer 506 to the mobile terminal 50 via the second communication means 504.

[0081] The instruction sending means 507 is a means for transmitting a CC message (control instruction) created by the MIDI message generating unit 511 based on an input from the pedal switch 15 and a SysEx message (second control instruction) received from the portable terminal 50 via the second communication means 504 to the headphones 30 via the first communication means 501, and is realized by the CPU 10. The instruction sending means 507 has a serializing unit 507a that converts the CC message created by the MIDI message generating unit 511 and the SysEx message received from the portable terminal 50 via the second communication means 504 into serial data. The CC message and the SysEx message that have been serialized by the serializing unit 507a are transmitted to the headphones 30 via the transmission buffer 503 and the first communication means 501.

[0082] In this way, a CC message based on an input from the pedal switch 15 and a SysEx message received from the mobile terminal 50 via the second communication means 504 are transmitted to the headphones 30 via the first communication means 501. This makes it possible to control the headphones 30 from two control devices, the pedal device 1 and the mobile terminal 50, even if the headphones 30 can be connected to only one control device.

[0083] Furthermore, the serialization unit 507a converts the CC message created by the MIDI message generation unit 511 and the SysEx message received from the mobile terminal 50 via the second communication means 504 into serial data, thereby making it possible to transmit the CC message and the SysEx message via the same communication path of the first communication means 501.

[0084] Next, the creation of the above-mentioned CC message will be explained. The first storage unit 508 stores the model ID and version information of the pedal device 1, and is realized by the flash ROM 11 described later in Fig. 8. The determination means 509 is a means for determining whether or not a SysEx message received from the mobile terminal 50 via the second communication means 504 and the receiving buffer 505 is a control instruction for itself, and is realized by the CPU 10.

[0085] The change means 510 is a means for changing a CC message generated by the MIDI message generation unit 511 based on the pedal switch 15 in accordance with the SysEx message when the determination means 509 determines that the SysEx message received via the second communication means 504 is a control instruction directed to the self, and is realized by the CPU 10.

[0086] The MIDI message generating unit 511 creates a CC message based on the parameters input from the pedal switch 15 and the model ID and version information in the first storage unit 508, and is realized by the CPU 10. In the MIDI message generating unit 511, when the determining means 509 determines that the SysEx message received via the second communication means 504 is a control instruction for itself, the changing means 510 changes the CC message generated by the MIDI message generating unit 511 based on the pedal switch 15 in accordance with the SysEx message. This makes it possible to change the control target that is controlled based on the operation of the pedal switch 15 by the SysEx message from the mobile terminal 50.

[0087] Next, an operation when communication with the mobile terminal 50 is established will be described. The pairing mode transition unit 512 determines whether the operation element 16 is double-clicked or single-clicked to transition to the advertising mode described above in FIG. 3(b), and is realized by the CPU 10. The second storage unit 513 stores information about the pedal device 1 itself ("ABC") and information indicating that communication between the pedal device 1 itself and the headphones 30 has been established ("ABC+"), and is realized by the flash ROM 11.

[0088] The first communication establishment determination unit 514 acquires information from the second storage unit 513 depending on whether or not communication with the headphones 30 by the first communication means 501 has been established, and is realized by the CPU 10. Specifically, if communication with the headphones 30 by the first communication means 501 has not been established, the first communication establishment determination unit 514 acquires information about the pedal device 1 itself from the second storage unit 513, and if communication with the headphones 30 by the first communication means 501 has been established, the first communication establishment determination unit 514 acquires information about the pedal device 1 itself and information indicating that communication with the headphones 30 has been established from the second storage unit 513.

[0089] When pairing mode transition unit 512 determines that the mode is the advertising mode, advertising packet generation unit 515 creates advertising packet AD based on information acquired from first communication establishment determination unit 514 and transmits it to mobile terminal 50 via second communication means 504, and is realized by CPU 10. The advertising packet AD generated by advertising packet generation unit 515 is transmitted to mobile terminal 50 via transmission buffer 506 and second communication means 504.

[0090] That is, when communication with the headphones 30 is established by the first communication means 501, the advertising packet AD transmitted from the advertising packet generator 515 to the mobile terminal 50 contains information about the pedal device 1 itself and information indicating that communication with the headphones 30 has been established. This allows the mobile terminal 50 connected to the headphones 30 via the pedal device 1 to determine that communication with the headphones 30 is actually possible.

[0091] Next, the electrical configuration of the control system S will be described with reference to Fig. 8. Fig. 8 is a block diagram showing the electrical configuration of the control system S. The headphones 30 have a CPU 31, a flash ROM 32, and a RAM 33, which are each connected to an input / output port 35 via a bus line 34. The input / output port 35 is further connected to a musical instrument receiving device 36, the above-mentioned controls 37 and LED 38, an amplifier 39, a wireless communication device 40 for wireless communication with the pedal device 1, and a gyro sensor 41.

[0092] The CPU 31 is a calculation device that controls each unit connected by a bus line 34. The flash ROM 32 is a rewritable non-volatile storage device that stores programs executed by the CPU 31, fixed value data, etc., and stores a control program 32a and model ID data 32b in which the model ID of the above-mentioned headphones 30 is stored. When the control program 32a is executed by the CPU 31, the headphone processing of Fig. 9 is executed. The RAM 33 is a memory for rewritably storing various work data, flags, etc. when the CPU 31 executes a program.

[0093] The musical instrument receiving device 36 is a device that receives a performance signal wirelessly transmitted from the musical instrument transmitting device Gt described above. The amplifier 39 is a device that amplifies the performance sound created by the CPU 31. The above-mentioned speakers R and L are connected to the amplifier 39, and the performance sound amplified by the amplifier 39 is output to the speakers R and L. The gyro sensor 41 is a sensor that detects angular velocity, and detects the amount of movement, tilt, and rotation of the head of the user H wearing the headphones 30 in the up-down, front-back, and left-right directions.

[0094] The headphones 30 are configured to be capable of outputting a mixed sound of a performance sound ("first musical sound") based on a performance signal input from an electric guitar G via an instrument receiving device 36 and a musical sound ("second musical sound") input from a mobile terminal 50 or the like via a wireless communication device 40.

[0095] Furthermore, in the mixed sound, the virtual position from which at least one of the first musical sound and the second musical sound is output can be changed according to the amount of movement or tilt of the head of the user H detected by the gyro sensor 41. For example, by setting the second musical sound to be a drum sound and setting the virtual position from which the drum sound is output to be behind the user H playing the electric guitar G, the user H will hear the drum sound as if it is always being output from behind him, even if the tilt of the head of the user H wearing the headphones 30 and playing the electric guitar G changes.

[0096] Next, a description will be given of the electrical configuration of the pedal device 1 of the control system S. The pedal device 1 has a CPU 10, a flash ROM 11, and a RAM 12, which are each connected to an input / output port 14 via a bus line 13. The input / output port 14 is further connected to the pedal switch 15, the operator 16, and the LED 17 described above, as well as the headphones 30 and a wireless communication device 22 for wireless communication with the mobile terminal 50.

[0097] The CPU 10 is a calculation device that controls each unit connected by a bus line 13. The flash ROM 11 is a rewritable non-volatile storage device that stores programs executed by the CPU 10, fixed value data, etc., and stores a control program 11a and model ID data 11b in which the model ID of the above-mentioned headphones 30 is stored. When the control program 11a is executed by the CPU 10, the pedal process of Fig. 11(a) is executed.

[0098] The RAM 12 is a memory for storing various work data, flags, etc. in a rewritable manner when the CPU 10 executes a program, and is provided with a transfer data memory 12a in which SysEx messages received from the headphones 30 or the mobile terminal 50 and their destinations are stored, and a performance data memory 12b in which CC messages created based on the pedal switch 15 are stored.

[0099] Next, a description will be given of the electrical configuration of the portable terminal 50 of the control system S. The portable terminal 50 has a CPU 51, a flash ROM 52, and a RAM 53, which are each connected to an input / output port 55 via a bus line 54. The input / output port 55 is further connected to a wireless communication device 58 for wirelessly communicating with the pedal device 1, a touch panel 56 into which instructions from the user H are input, and the above-mentioned LCD 57.

[0100] The CPU 51 is a calculation device that controls each part connected by the bus line 54. The flash ROM 52 is a rewritable non-volatile storage device that stores programs executed by the CPU 51, fixed value data, etc., and stores a control program 52a. When the control program 52a is executed by the CPU 51, the mobile terminal process of FIG. 13 is executed. More specifically, the control program 52a includes an application for controlling the pedal device 1 and an application for controlling the headphones 30, and the mobile terminal process corresponding to the application started in response to the operation of the touch panel 56 is executed. The details of the mobile terminal process will be described later with reference to FIG. 13.

[0101] The RAM 53 is a memory for rewritably storing various work data, flags, and the like when the CPU 51 executes a program, and is provided with an IQ memory 53a for storing the above-mentioned inquiry message IQ.

[0102] Next, the processing of the control system S will be described with reference to Figs. 9 to 13. First, the processing executed by the CPU 31 of the headphones 30 will be described. Fig. 9 is a flowchart of the headphone processing. The headphone processing is processing that is executed when the power of the headphones 30 is turned on.

[0103] The headphone processing first checks whether the user H has performed a connection start operation on the operator 37 to instruct the operator 37 to start a connection with another communication device such as the pedal device 1 (S1). Specifically, if the operator 37 is pressed and held down, it is determined that the connection start operation has been performed. If the connection start operation has been performed in the processing of S1 (S1: Yes), a peripheral connection processing (S2) is executed. Here, the peripheral connection processing will be described with reference to FIG. 10(a).

[0104] 10A is a flowchart of the peripheral connection process. The peripheral connection process is executed by the CPU 31 of the headphones 30, and the same process is also executed by the CPU 10 of the pedal device 1.

[0105] In the peripheral connection process, first, the advertising packet AD described above in Fig. 3 is transmitted to another communication device (S20). The transmission of the advertising packet AD to another communication device is performed using the wireless communication device 40 in the case of the headphones 30, and using the wireless communication device 22 in the case of the pedal device 1. Hereinafter, it is assumed that communication with another communication device in the peripheral connection process is performed using the wireless communication device 40 in the case of the headphones 30, and using the wireless communication device 22 in the case of the pedal device 1.

[0106] After the process of S20, it is confirmed whether a connection request has been received from another communication device in response to the advertising packet AD transmitted in the process of S20 (S21). If a connection request has been received in the process of S21 (S21: Yes), a process of connecting with the other communication device (i.e., the pedal device 1 or the mobile terminal 50) that transmitted the connection request is performed (S22).

[0107] On the other hand, if a connection request has not been received in the process of S21 (S21: No), it is confirmed in the process of S20 whether or not a predetermined time has passed since the start of transmission of the advertising packet AD (S23). If the predetermined time has not passed since the start of transmission of the advertising packet AD in the process of S23 (S23: No), the processes from S20 onwards are executed again. After the process of S22, or if the predetermined time has passed since the start of transmission of the advertising packet AD in the process of S23 (S23: Yes), the peripheral connection process is terminated.

[0108] Returning to Fig. 9, in the process of S1, if a connection initiation operation is not performed (S1: No), or after the peripheral connection process of S2, it is confirmed whether the background request data SR described above in Fig. 4 has been received (S3). In the process of S3, if the background request data SR has been received (S3: Yes), a background request response process (S4) is executed. Here, the background request response process will be described with reference to Fig. 10(b).

[0109] 10B is a flowchart of the feature request response process. The feature request response process is executed by the CPU 31 of the headphones 30, and an equivalent process is also executed by the CPU 10 of the pedal device 1.

[0110] The feature request response process first checks whether the model ID in the received feature request data SR is its own (S30). Specifically, the model ID included in the feature request data SR is compared with its own model ID, that is, the model ID in the model ID data 32b in the case of the headphones 30, or the model ID in the model ID data 11b in the case of the pedal device 1, to check whether they match.

[0111] In the process of S30, if the model ID of the feature request data SR is its own (S30: Yes), an inquiry message IQ (see FIG. 4) is created for itself, and the created inquiry message IQ is sent (returned) to the sender of the feature request data SR, i.e., the pedal device 1 or the mobile terminal 50 (S31). This sending is performed using the wireless communication device 40 in the case of the headphones 30, and using the wireless communication device 22 in the case of the pedal device 1.

[0112] On the other hand, if the model ID in the feature request data SR does not belong to the device itself (S30: No), the device discards the received feature request data SR (S32). After the processes of S31 and S32, the feature request response process ends.

[0113] Returning to Fig. 9, if the feature request data SR has not been received in the process of S3, or after the process of S4, it is confirmed whether a SysEx message has been received (S5). If the SysEx message has been received in the process of S5 (S5: Yes), it is confirmed whether the model ID of the control instruction RS in the SysEx message matches the model ID in the model ID data 32b (S6).

[0114] In the process of S6, if the model ID of the control instructions RS in the SysEx message matches the model ID in the model ID data 32b (S6: Yes), the device updates its own settings using the parameters included in the control instructions RS of the SysEx message (S7).On the other hand, if the model ID of the control instructions RS in the SysEx message does not match the model ID in the model ID data 32b (S6: No), the device discards the received SysEx message (S8).

[0115] In the process of S5, if a SysEx message has not been received (S5: No), or after the processes of S7 and S8, it is checked whether the CC message (see FIG. 6(a)) described above in FIG. 6 has been received (S9). In the process of S9, if a CC message has been received (S9: Yes), it is checked whether the headphones 30 are in a mode in which their settings can be updated by the received CC message (S10).

[0116] In the process of S10, if the mode is one in which the device's own settings are updated by the received CC message (S10: Yes), the device updates its own settings using the update instruction CC parameters included in the CC message (S11).

[0117] After the process of S11, a response instruction PS (see FIG. 6(a)) is created from the parameters of the update instruction CC of the CC message received in the process of S9 and the model ID of the model ID data 32b, and a SysEx message incorporating the response instruction PS is sent (returned) to the sender of the CC message, i.e., the pedal device 1 (S12). On the other hand, in the process of S10, if there is no mode for updating its own settings by the received CC message (S10: No), the received CC message is discarded (S13).

[0118] If no CC message has been received in the process of S9 (S9: No), the process of S12 and S13 is followed by a specific process (S14). The specific process is other process carried out by the headphones 30, such as outputting a performance sound based on a performance signal input from the electric guitar G via the musical instrument receiving device 36, or a performance sound input from the mobile terminal 50 via the pedal device 1, to the speakers R and L via the amplifier 39. After the specific process of S14, the process from S1 onwards is repeated.

[0119] Next, there will be described the processing executed by the CPU 10 of the pedal device 1. Fig. 11(a) is a flowchart of the pedal processing. The pedal processing is processing that is executed when the power supply of the pedal device 1 is turned on.

[0120] The pedal process first checks whether a connection scan start operation has been performed to instruct the start of reception of advertising packets AD from another communication device (specifically, headphones 30) (S50). Specifically, as described above in FIG. 3(a), when user H double-clicks the operator 16 until the lighting color of the LED 17 turns white (i.e., central function), and then user H single-clicks the operator 16 to transition to scan mode, it is determined that a connection scan start operation has been performed. In the process of S50, if a connection scan start operation has been performed (S50: Yes), central connection processing (S51) is executed. Here, the central connection processing will be described with reference to FIG. 11(b).

[0121] 11B is a flowchart of the central connection process. The central connection process is executed by the CPU 10 of the pedal device 1, and an equivalent process is also executed by the CPU 51 of the mobile terminal 50. The central connection process starts with reception of an advertising packet AD (S70). The advertising packet AD is received by the pedal device 1 using the wireless communication device 22, and by the mobile terminal 50 using the wireless communication device 58. Hereinafter, it is assumed that communication with other communication devices in the central connection process is performed by the wireless communication device 22 in the case of the pedal device 1, and by the wireless communication device 58 in the case of the mobile terminal 50.

[0122] After the process of S70, it is confirmed whether an advertising packet AD has been received from another communication device (S71). In the process of S71, if an advertising packet AD has been received (S71: Yes), a connection request is transmitted to the communication device that received the advertising packet AD (S72), and a connection process with the communication device is performed (S73).

[0123] In the process of S71, if the advertising packet AD has not been received (S71: No), it is confirmed whether or not a predetermined time has elapsed since the start of reception of the advertising packet AD in the process of S70 (S74). In the process of S74, if the predetermined time has not elapsed since the start of reception of the advertising packet AD (S74: No), the processes from S70 onwards are repeated.

[0124] On the other hand, in the process of S74, if a predetermined time or more has elapsed since the start of reception of the advertising packet AD (S74: Yes), or after the process of S73, the central connection process is terminated. By the central connection process and the peripheral connection process described above, a first communication w1 between the headphones 30 and the pedal device 1 and a second communication w2 between the pedal device 1 and the mobile terminal 50 are established.

[0125] Return to Fig. 11(a). In the process of S50, if the connection scan start operation is not performed (S50: No), or after the central connection process of S51, it is confirmed whether the connection start operation is performed from the operation device 16 (S52). Specifically, as described above in Fig. 3(b), if the user H double-clicks the operation device 16 until the lighting color of the LED 17 becomes blue (i.e., peripheral function), and then the user H single-clicks the operation device 16 to transition to the advertising mode, it is determined that the connection start operation is performed. In the process of S52, if the connection start operation is performed (S52: Yes), it is confirmed whether communication has been established with another communication device in the central connection process of S51 (S53).

[0126] In the process of S53, if communication has already been established with another communication device in the central connection process (S53: Yes), the device adds its own information and information about the communication device with which communication has been established (see FIG. 3(b)) to the advertising packet AD (S54). In the process of S53, if communication has not been established with another communication device in the central connection process (S53: No), the device adds its own information to the advertising packet AD (S55). After the processes of S54 and S55, the peripheral connection process of S2 described above is executed.

[0127] In the process of S52, if a connection start operation is not performed (S52: No), or after the process of S2, it is confirmed whether or not background request data SR (see FIG. 4) has been received (S56). In the process of S55, if background request data SR has been received (S56: Yes), the above-mentioned background request response process (S4) is executed. In the process of S56, if background request data SR has not been received (S56: No), the process of S4 is skipped. After the processes of S4 and S56, a pedal device transmission / reception process (S57) is executed, and the processes from S50 onwards are repeated. Now, the pedal device transmission / reception process will be described with reference to FIG. 12.

[0128] 12 is a flowchart of the pedal device transmission / reception process. The pedal device transmission / reception process first checks whether a SysEx message has been received (S80). If a SysEx message has been received in the process of S80 (S80: Yes), the received SysEx message and the destination of the SysEx message are stored in the transfer data memory 12a (S81). Specifically, if a SysEx message has been received from the mobile terminal 50, the headphones 30 is set as the destination of the SysEx message, and if a SysEx message has been received from the headphones 30, the mobile terminal 50 is set as the destination.

[0129] After the process of S81, it is confirmed whether the model ID of the control instruction RS in the SysEx message matches the model ID in the model ID data 11b (S82). In the process of S82, if the model ID of the control instruction RS in the SysEx message matches the model ID in the model ID data 11b (S82: Yes), the device updates its own settings using the parameters included in the control instruction RS of the SysEx message (S83). As a result, for example, if the control instruction RS of the SysEx message received from the mobile terminal 50 is to change the sound effect controlled by the pedal device 1 to "delay," from this point on, the sound effect whose effect amount is controlled by the pedal switch 15 of the pedal device 1 is changed to "delay."

[0130] On the other hand, if the model ID of the control instruction RS in the SysEx message does not match the model ID in the model ID data 11b (S82: No), the received SysEx message is discarded (S84).

[0131] In the process of S80, if a SysEx message has not been received (S80), after the processes of S83 and S84, it is confirmed whether the pedal switch 15 has been operated (S85). In the process of S85, if the pedal switch 15 has been operated (S85: Yes), parameters corresponding to the angle of the pedal switch 15 are obtained from the pedal switch 15, and an update instruction CC is created based on the obtained parameters. A CC message including the created update instruction CC is created (S86). After the process of S86, the created CC message is saved in the performance data memory 12b (S87).

[0132] In the process of S85, if the pedal switch 15 has not been operated (S85: No), or after the process of S87, it is checked whether there is a SysEx message that has not been sent or is being sent in the transfer data memory 12a (S88). In the process of S88, if there is a SysEx message that has not been sent or is being sent in the transfer data memory 12a (S88: Yes), the SysEx message in the transfer data memory 12a is sent to the destination stored in the transfer data memory 12a (S89).

[0133] On the other hand, if there is no SysEx message being sent or not sent in the transfer data memory 12a in the process of S88 (S88: No), it is checked whether there is a CC message being sent or not sent in the performance data memory 12b (S90).

[0134] In the process of S90, if there is a CC message that has not been sent or is being sent in the performance data memory 12b (S90: Yes), the CC message in the performance data memory 12b is sent to each of the communication devices connected to the pedal device 1 (S91). On the other hand, in the process of S90, if there is no CC message that has not been sent or is being sent in the performance data memory 12b (S90: No), the process of S91 is skipped.

[0135] That is, even if a SysEx message is received from the mobile terminal 50 or the headphones 30, and the pedal switch 15 is operated to create a CC message while the received SysEx message has not been transmitted or is being transmitted, the transmission of the later-created CC message will start after the transmission of the previously-received SysEx message is completed. In this way, by serializing the received SysEx message and CC message for transmission, the SysEx message and CC message can be transmitted via the same communication path (first communication w1 or second communication w2).

[0136] After the processes of S89, S90, and S91, the pedal device transmission / reception process ends.

[0137] Next, a process executed by the CPU 51 of the mobile terminal 50 will be described. Fig. 13 is a flowchart of the mobile terminal process. The mobile terminal process is executed when an instruction to start an application for controlling the pedal device 1 or an application for controlling the headphones 30 is input by an operation of the user H via the touch panel 56.

[0138] The mobile terminal process first checks whether a connection scan start operation has been performed on the touch panel 56 to instruct the start of reception of advertising packets AD from another communication device (specifically, the pedal device 1) (S100). Specifically, after an application that controls the pedal device 1 or an application that controls the headphones 30 is started in the mobile terminal 50, a button (not shown) for starting a connection scan is displayed on the LCD 57, and it is determined that a connection scan start operation has been performed when the button is selected via the touch panel 56. In the process of S100, if a connection scan start operation has been performed (S100: Yes), the above-mentioned central connection process (S51) is executed.

[0139] After the central connection process of S51, it is confirmed whether the advertising packet AD received in the central connection process contains information on the communication device with which communication has been established (S101). In the process of S105, if the advertising packet AD contains information on the communication device with which communication has been established (S101: Yes), "ABC+" is displayed on the LCD 57 (S102). On the other hand, in the process of S105, if the advertising packet AD does not contain information on the communication device with which communication has been established (S101: No), "ABC" is displayed on the LCD 57 (S103).

[0140] After the processing of S102 and S103, based on the model ID of the control target of the running application (i.e., the pedal device 1 or the headphones 30), background request data SR is created and transmitted to the connected communication device (specifically, the pedal device 1) (S104).

[0141] In the process of S100, if a connection scan start operation has not been performed (S100: No), or after the process of S104, it is confirmed whether an inquiry message IQ has been received (S105). In the process of S105, if an inquiry message IQ has been received (S105: Yes), the received inquiry message IQ is stored in the IQ memory 53a (S106). On the other hand, in the process of S105, if an inquiry message IQ has not been received (S105: No), the process of S106 is skipped.

[0142] After the processes of S105 and S106, a mobile terminal transmission / reception process (S107) is executed, and the processes from S100 onwards are repeated. Here, the mobile terminal transmission / reception process will be described with reference to FIG.

[0143] 14 is a flowchart of the mobile terminal transmission / reception process. The mobile terminal transmission / reception process first checks whether a SysEx message has been received (S120). If a SysEx message has been received (S120: Yes), the process checks whether the model ID of the control instruction RS in the SysEx message matches the model ID of the control target of the running application (S121).

[0144] In the process of S121, if the model ID of the control instruction RS in the SysEx message matches the model ID of the control target of the running application (S121: Yes), the device updates its own settings using the parameters included in the control instruction RS of the SysEx message (S122). On the other hand, if the model ID of the control instruction RS in the SysEx message does not match the model ID of the control target of the running application (S121: No), the device discards the received SysEx message (S123).

[0145] In the process of S120, if a SysEx message has not been received (S120: No), or after the processes of S122 and S123, it is checked whether a CC message has been received (S124). In the process of S124, if a CC message has been received (S124: Yes), it is checked whether the device is in a mode in which its own settings can be updated by a CC message (S125).

[0146] In the process of S125, if the mode is one in which the device's settings are updated by a CC message (S125: Yes), the device updates its settings using the update instruction CC parameters included in the CC message (S126).On the other hand, in the process of S125, if the mode is not one in which the device's settings are updated by the received CC message (S125: No), the device discards the received CC message (S127).

[0147] In the process of S124, if a CC message is received (S124: Yes), or after the processes of S126 and S127, it is confirmed whether parameters (for example, the volume in FIG. 5(a) or the type of sound effect in FIG. 5(b)) have been input by user H via touch panel 56 (S128). In the process of S128, if parameters have been input (S128: Yes), the input parameters are used to update the own settings (S129).

[0148] After the process of S129, a control instruction RS is created from the input parameters, the model ID of the control target of the running application, and the inquiry message IQ of the IQ memory 53a. A SysEx message including the created control instruction RS is created and transmitted to the connected communication device (specifically, the pedal device 1) (S130). As a result, the control instruction RS from the mobile terminal 50 is transmitted to the pedal device 1 and the headphones 30.

[0149] In the process of S128, if no parameters are input from the touch panel 56 (S128: No), or after the process of S130, the mobile terminal transmission and reception process ends.

[0150] Although the above description is based on the above embodiment, it can be easily imagined that various improvements and modifications are possible.

[0151] In the above embodiment, the headphones 30 and the effectors 300, 310 (see FIG. 3(a)) are exemplified as devices connected to the pedal device 1 and the mobile terminal 50, but the present invention is not limited to this. An electronic musical instrument other than the headphones 30 and the effectors 300, 310, for example, a synthesizer 350 shown in FIG. 15, may also be connected. That is, in the control system S' shown in FIG. 15, the above-mentioned first communication w1 is established between the synthesizer 350 and the pedal device 1.

[0152] In the modified example, the LCD 57 of the mobile terminal 50 displays a musical score. The position of the displayed musical score is changed by operating the touch panel 56. At this time, the position of the musical score displayed on the LCD 57 is also changed by operating the pedal switch 15 of the pedal device 1.

[0153] Synthesizer 350 in the modified example is mainly provided with keyboard 354, setting keys 355 for inputting various settings, and musical score LCD 356. Keyboard 354 is provided with a plurality of keys 354a, and is an input device for acquiring performance information generated by a performance by user H. Performance information conforming to the MIDI standard in response to user H's key pressing / releasing operations of keys 354a is output to CPU 351 (see FIG. 16).

[0154] The musical score LCD 356 is a display device that displays the same musical score as that displayed on the LCD 57 of the mobile terminal 50. The musical score and its display position displayed on the musical score LCD 356 are transmitted from the mobile terminal 50 and the pedal device 1.

[0155] That is, when the display position of the score is changed on the mobile terminal 50, or when the display position of the score is changed by the pedal switch 15 of the pedal device 1, the score LCD 356 displays a score equivalent to the score displayed on the LCD 57 of the mobile terminal 50. This makes it possible to change the display position of the score on one synthesizer 350 from the two mobile terminals 50 and the pedal device 1. In particular, since the pedal switch 15 of the pedal device 1 is operated by the user H stepping on it, the user H can change the display position of the score on the score LCD 356 without taking his / her hands off the keyboard 354.

[0156] Next, the electrical configuration of a control system S' in a modified example will be described with reference to Fig. 16. Fig. 16 is a block diagram showing the electrical configuration of the control system S'. A synthesizer 350 of the control system S' has a CPU 351, a flash ROM 352, and a RAM 353, which are connected to each other via a bus line 357. To the bus line 357, further connected are the above-mentioned keyboard 354, setting keys 355, and musical score LCD 356, a wireless communication device 358 which wirelessly communicates with the pedal device 1, a sound source 359, and a digital signal processor 360 (hereinafter referred to as "DSP 360"). The DSP 360 is also connected to the sound source 359.

[0157] CPU 351 is a calculation device that controls each unit connected by bus line 357. Flash ROM 352 is a rewritable non-volatile storage device that stores programs executed by CPU 351, fixed value data, etc., and stores control program 352a and model ID data 352b in which a model ID is stored. When control program 352a is executed by CPU 351, processing equivalent to the headphone processing in Fig. 9 is executed. Note that, as for the specific processing in the headphone processing (S14), processing specific to synthesizer 350 is executed, and the details will be described later with reference to Fig. 17.

[0158] The RAM 353 is a memory for rewritably storing various work data, flags, etc. when the CPU 351 executes a program. The sound source 359 is a device that outputs waveform data corresponding to performance information input from the CPU 351. The DSP 360 is a calculation device that processes the waveform data input from the sound source 359. A digital-to-analog converter (DAC) 361 is connected to the DSP 360, an amplifier 362 is connected to the DAC 361, and a speaker 363 is connected to the amplifier 362.

[0159] Next, the processing executed by CPU 351 of synthesizer 350 will be described. The processing in synthesizer 350 related to communication with pedal device 1 and portable terminal 50 is substantially the same as the processing in headphones 30, except for the connection start operation (S1) and unique processing (S14) in the headphone processing of Fig. 9 in the above embodiment. In synthesizer 350, pressing and holding a predetermined setting key 355 determines that a connection start operation has been performed in the processing of S1 of the headphone processing.

[0160] Next, the inherent processing of synthesizer 350 (S14) will be described. Fig. 17 is a flowchart of the inherent processing of synthesizer 350 in the modified example. The inherent processing of synthesizer 350 first performs switch event processing (S200). In the switch event processing, it is confirmed whether setting key 355 has been operated, and if setting key 355 has been operated, processing according to setting key 355 is performed.

[0161] After the process of S200, keyboard event process (S201) is performed. In the keyboard event process, which key 354a on the keyboard 354 is pressed or released is detected. After the process of S201, MIDI process (S202) is performed. In the MIDI process, the performance sound is output or the output is stopped according to the operation of the key 354a detected in the process of S201, and the score and the display position of the score to be displayed on the score LCD 356 are obtained from parameters included in the update instruction CC from the pedal device 1 and the control instruction RS from the mobile terminal 50.

[0162] After the process of S202, an automatic performance process (S203) is performed. In this automatic performance process, a concert magic performance process, an automatic accompaniment process, a demonstration process, and the like are performed. After the process of S203, a score display process (S204) is performed. In the score display process, an image of the score is created based on the score and the score display position obtained in the MIDI process, and is displayed on the score LCD 356. As a result, a score equivalent to the score displayed on the LCD 57 of the mobile terminal 50 is displayed on the score LCD 356. After the process of S204, other processes related to the synthesizer 350 (S205) are performed, and the unique process is terminated.

[0163] In the modified example, the score displayed on the LCD 57 of the mobile terminal 50 is displayed on the score LCD 356 of the synthesizer 350, and the position of the score displayed on the score LCD 356 is changed by the operation of the pedal device 1 and the mobile terminal 50, but the present invention is not limited to this. For example, the display mode (e.g., color, size of the note, marking) of the note to be currently performed may be changed in the score displayed on the LCD 57 and the score LCD 356, and the note whose display mode is changed may be changed (forward, backward, etc.) by the operation of the mobile terminal 50 and the pedal device 1. Also, the volume of the performance sound output by the synthesizer 350 and the degree and type of the sound effect added to the performance sound may be changed by the operation of the mobile terminal 50 and the pedal device 1.

[0164] In the above embodiment, the pedal device 1 having the pedal switch 15 is exemplified as the control device, but the present invention is not limited to this. For example, the control device may be a device having a switch for switching on / off states, or a device having a "knob" or fader for variably controlling an output parameter. In addition, the control device may be a device that uses sensor information (for example, a device that obtains the amount of change in an acceleration sensor and controls a control target according to the amount of change), or a device that can set other parameters.

[0165] In the above embodiment, the mobile terminal 50 executing the control program 52a has been exemplified as the central communication device that transmits control instructions to the headphones 30 and the pedal device 1, but this is not limited thereto. For example, the control program 52a may be executed on an information processing device such as a PC or a tablet terminal, and the information processing device may be used as the central communication device that transmits control instructions to the headphones 30 and the pedal device 1. In addition, the control program 52a may be stored in a ROM or the like, and a dedicated device that executes only the control program 52a may be used as the central communication device that transmits control instructions to the headphones 30 and the pedal device 1. [Explanation of symbols]

[0166] 30 Headphones (electronic instruments) 300,310 Effector (electronic musical instrument) 350 Synthesizer (electronic musical instrument) 50 Mobile terminal (second control device) 1 Pedal device (control device) S Control System 15 Pedal switch (part of input means) S85-S87 Input method, input step S89: First communication means, instruction transmission means, first communication step, instruction transmission step S91 Second communication means, instruction transmission means, second communication step, instruction transmission step S82 Judgment means, judgment step S83 Change means, change steps

Claims

1. A control device for controlling an electronic musical instrument, An input means for inputting a control instruction; a first communication means for wirelessly communicating with the electronic musical instrument; a second communication means for wirelessly communicating with a second control device that controls the electronic musical instrument; an instruction transmitting means for transmitting, to the electronic musical instrument via the first communication means, a control instruction input by the input means and a second control instruction received from the second control device via the second communication means; a determination means for determining whether or not a second control instruction received from the second control device via the second communication means is a control instruction to the control device itself; A control device comprising:

2. 2. The control device according to claim 1, wherein the instruction transmitting means converts the control instruction input by the input means and the second control instruction received from the second control device via the second communication means into serial data and transmits the serial data to the electronic musical instrument via the first communication means.

3. A control device as described in claim 1 or 2, characterized in that when the judgment means judges that the second control instruction received from the second control device via the second communication means is a control instruction intended for itself, it is further characterized by being provided with a modification means for modifying the control instruction input by the input means in accordance with the second control instruction.

4. 4. The control device according to claim 1, wherein the first communication means performs wireless communication based on the Bluetooth (registered trademark) Low Energy standard.

5. the control instruction is an instruction using a control change message of the MIDI standard, 5. The control device according to claim 1, wherein the second control instruction is an instruction using a system exclusive message of the MIDI standard.

6. the control device is a pedal device, The control device according to any one of claims 1 to 5, wherein the second control device is a mobile terminal.

7. 1. A control method executed by a control device connected via wireless communication to an electronic musical instrument and a second control device that controls the electronic musical instrument, comprising: an input step for inputting a control instruction; a first communication step of wirelessly communicating with the electronic musical instrument; a second communication step of wirelessly communicating with a second control device that controls the electronic musical instrument; an instruction transmission step of transmitting, to the electronic musical instrument, the control instruction input in the input step and a second control instruction received from the second control device via the second communication step; a determination step of determining whether or not the second control instruction received from the second control device in the second communication step is a control instruction to the control device itself; A control method comprising:

8. The control method according to claim 7, characterized in that the instruction transmitting step converts the control instruction input in the input step and the second control instruction received from the second control device in the second communication step into serial data and transmits the serial data to the electronic musical instrument in the first communication step.

9. A control method as described in claim 7 or 8, characterized in that if the judgment step determines that the second control instruction received from the second control device in the second communication step is a control instruction for itself, the control method further comprises a modification step of modifying the control instruction input in the input step in accordance with the second control instruction.

10. A control system including an electronic musical instrument, a second control device that controls the electronic musical instrument, and a control device that is connected to the electronic musical instrument and the second control device via wireless communication, the second control device includes a transmission means for transmitting a second control instruction to the control device; The control device includes: An input means for inputting a control instruction; a first communication means for wirelessly communicating with the electronic musical instrument; A second communication means for wirelessly communicating with the second control device; an instruction transmitting means for transmitting, to the electronic musical instrument via the first communication means, a control instruction input by the input means and a second control instruction received from the second control device via the second communication means; a determination means for determining whether or not a second control instruction received from the second control device via the second communication means is a control instruction to the control device itself; A control system comprising:

11. The control system according to claim 10, characterized in that the instruction sending means of the control device converts the control instruction input by the input means and the second control instruction received from the second control device via the second communication means into serial data and sends the serial data to the electronic musical instrument via the first communication means.

12. A control system as described in claim 10 or 11, characterized in that the control device is provided with a modification means for modifying the control instruction input by the input means in accordance with the second control instruction when the determination means determines that the second control instruction received from the second control device via the second communication means is a control instruction intended for the control device itself.

Images