JP4207970B2 - Processing device in musical tone generation system - Google Patents

Description

The present invention relates to a processing device in a musical sound generation system in which a musical sound generation system is configured by a plurality of processing devices connected to a network.

Conventionally, a so-called MIDI (Musical Instrument Digital Interface) is known in which a plurality of electronic musical instruments are connected to each other to form an electronic musical instrument network system. This MIDI is a common standard for transmitting automatic performance data and the like, and transmitting performance data such as key codes in one direction from one of a plurality of musical instruments distributed on a network to another. It is possible. In MIDI, the MIDI message is serial data, and the MIDI lines connecting the electronic musical instruments are wired to connect the devices in series. Therefore, the MIDI lines connecting the devices are quite large. If an occupied area is taken, and even one MIDI line is mistakenly disconnected, the signal is not transmitted and sound generation is stopped. Furthermore, once the connection is removed, the wiring work to restore it becomes difficult.
Therefore, mLAN (music Local Area Network) has been proposed as a musical instrument system using a network. mLAN is a digital audio / MIDI data transmission technology using IEEE 1394, and exchanges digital audio data and MIDI data of 256 channels or more by connecting AV equipment, electronic musical instruments, and computer systems with an IEEE 1394 interface. Can do. This mLAN is based on "IEC61833-6 Audio and Music Data Transmission Protocol", which is a protocol for exchanging audio / MIDI data on IEEE1394, and controls AV equipment and electronic musical instruments or operates in cooperation with each other. Commands to control are defined. By using this mLAN, it is possible to replace the complicated connection between devices, which was conventionally done using analog cables, MIDI cables, etc., with the daisy chain connection of the IEEE1394 cable, greatly simplifying the connection between devices. Can do.

By the way, in the case of a conventional electronic musical instrument that does not have a required tone color (voice file), another related tone color is sounded instead (see Patent Document 2). It is also known to add a new timbre by inserting a recording medium (CD-ROM or floppy disk) on which a timbre is recorded in a conventional electronic musical instrument into the electronic musical instrument (see Patent Document 3).
Japanese Patent No. 3271493 Japanese Patent Laid-Open No. 59-199090 Japanese Patent Laid-Open No. 8-76752

However, since the mLAN is a daisy chain connection, there is a problem that it is difficult to physically connect a new device to an arbitrary location and perform a logical connection setting. Further, since the respective devices are wired so as to be connected in series, the line connecting the devices takes a considerable occupied space. In addition, if the line is accidentally disconnected at one location, the signal will not be transmitted beyond that point and the sound will stop. Furthermore, once the connection is disconnected, the wiring work to restore it will be difficult. There was a problem that.
A LAN (Local Area Network) is known as a network that can connect a new device to an arbitrary location. A LAN is a computer network in a relatively limited area such as an in-company network, and has recently been constructed in ordinary homes. However, there is no sound source that can be directly connected to the LAN and various musical sound generation-related devices, and a musical instrument system using a general network such as a LAN cannot be constructed. Furthermore, there is a problem in that if the timbre is replaced with another timbre that does not have the required timbre, the timbre cannot be sounded accurately because it is a substitute. In this case, if the recording medium to be inserted is replaced according to the tone color to be used, it is necessary to replace the recording medium, and it is necessary to remember which tone color is recorded on which recording medium. There was a problem that the work was troublesome.

Therefore, the present invention uses a general network such as a LAN to configure a musical sound generation system by connecting processing devices functioning as sound sources and various musical sound generation related devices to each other via the network. Another object of the present invention is to provide a processing apparatus in a musical tone generating system that can generate the required tone color as much as possible without requiring a recording medium.

To achieve the above object, the processing apparatus in the tone generation system of the present invention, tone generation system configured by respectively connecting a plurality of processing devices with each other via a network that acts as a device associated with the musical tone generating And detecting a processing device capable of providing a new voice with reference to a device table having information indicating whether or not to provide a voice for each processing device, and receiving the new voice from the detected processing device. The most important feature is to do this.

According to the present invention, it is possible to detect a processing device that can provide a new voice with reference to the device table, and to receive a new voice from a detected processing device on the network . The specified voice can be set. Furthermore, it becomes available to easily new tone simply by connecting the processing apparatus having the new tone to the network, so by utilizing the device table of its own that narrow the processing apparatus capable providing sound, network Even if the number of processing devices connected to the PC increases, it becomes possible to quickly access the target processing device and take in the timbre.

FIG. 1 is a block diagram showing the configuration of a musical tone generation system according to an embodiment of the present invention.
The musical sound generating system according to the present invention includes an internal network that can be connected to an external network as shown in FIG. The internal network is a LAN such as Ethernet. The internal network includes a router 2 and a hub 10, a hub 20, a hub 30, and a hub 40 that are connected to a plurality of LAN terminals of the router 2 via LAN cables. It is a star-type network constructed across four rooms: room 1, room 2, room 3, and room 4. The WAN terminal of the router 2 is connected to the Internet 1, and the router 3 and the router 4 connected to other networks are connected to the Internet 1. As a result, the internal network can be connected to another network connected to the router 3 or another network connected to the router 4 via the router 2 and the Internet 1.

In the room 1, there are installed SV (server) 11, TG1 (sound source) 12, TG2 (sound source) 13, KB (keyboard) 14, and SP1 (speaker) 15, and these devices have network adapters. Is provided as a LAN device. The LAN terminal upstream of the hub 10 provided in the room 1 is connected to the LAN terminal of the router 2 via a LAN cable, and a plurality of LAN terminals downstream of the hub 10 and SV (server) 11 and TG1 (sound source). 12, TG2 (sound source) 13, KB (keyboard) 14, and SP1 (speaker) 15 are respectively connected to LAN terminals of network adapters via LAN cables.
In the room 2, SP2 (speaker) 21, DU (DSP unit) 22, MX (mixer) 23, and CR (content recorder) 24 are installed, and a network adapter is provided for these devices. LAN device. The LAN terminal upstream of the hub 20 provided in the room 2 is connected to the LAN terminal of the router 2 via a LAN cable, and a plurality of LAN terminals downstream of the hub 20 and SP2 (speakers) 21, DU (DSP unit). ) 22, MX (mixer) 23, and CR (content recorder) 24 are respectively connected to LAN terminals of network adapters via LAN cables.

Further, in the room 3, there are AA (automatic accompaniment) 31, MR (MIDI recorder) 32, ED (editor) 33, EF (effector) 34, AR (audio recorder) 35, and SY (sound source, keyboard) 36. These devices are provided with network adapters to be LAN devices. The LAN terminal upstream of the hub 30 provided in the room 3 is connected to the LAN terminal of the router 2 via a LAN cable, and a plurality of LAN terminals downstream of the hub 30 and AA (auto accompaniment) 31, MR (MIDI). Recorder) 32, ED (editor) 33, EF (effector) 34, AR (audio recorder) 35, and SY (sound source, keyboard) 36 are connected to LAN terminals of network adapters respectively. Connected through.
Furthermore, the room 4 is provided with devices of MC (microphone) 41 and CD (CD player) 42, and these devices are provided with network adapters to serve as LAN devices. The LAN terminal upstream of the hub 40 provided in the room 4 is connected to the LAN terminal of the router 2 via a LAN cable, and a plurality of LAN terminals downstream of the hub 40, MC (microphone) 41, CD (CD player). ) 42 are respectively connected to the LAN terminals of the network adapters provided via the LAN cables.

With the exception of the DU (DSP unit) 22, each device connected to the internal network in the musical sound generating system of the present invention is a CPU (Central Processing Unit), RAM (Random Access Memory). ), ROM (Read Only Memory) at least, and hardware corresponding to each device. Then, by executing a program corresponding to the device name, the device name is operated. As described above, each apparatus in the present invention is a processing apparatus (computer) that can execute various programs except for the DU (DSP unit) 22. In the following description, this processing apparatus executes a program. The functions achieved by executing are defined as processing elements. That is, SV (server) 11 installed in the room 1, TG1 (sound source) 12, TG2 (sound source) 13, KB (keyboard) 14, SP1 (speaker) 15, SP2 (speaker) 21 installed in the room 2, MX (mixer) 23, CR (content recorder) 24, AA (automatic accompaniment) 31 installed in room 3, MR (MIDI recorder) 32, ED (editor) 33, EF (effector) 34, AR (audio recorder) 35, SY (sound source, keyboard) 36, MC (microphone) 41 and CD (CD player) 42 installed in the room 4 are all processing elements, and the processing elements are executed by executing the corresponding programs. Is functioning as
The SV (server) 11 is a computer that provides its own functions and data to a client computer, and the client computer is a processing device in which the above processing elements are functioning. The DU (DSP unit) 22 is constituted by a processing device including a large number of DSPs, and the DSP functions as processing elements such as a mixer, an editor, and an effector by executing a microprogram. That is, the DU (DSP unit) 22 can switch the functioning processing element by selecting and executing a microprogram.

The processing elements will be specifically described. The TG1 (sound source) 12 and the TG2 (sound source) 13 function as sound source elements when the processing device executes a sound source program. The KB (keyboard) 14 functions as a keyboard element when a processing device including a keyboard as hardware executes a keyboard program. The SP1 (speaker) 15 and the SP2 (speaker) 21 function as speaker elements when a processing device including a speaker as hardware executes a speaker program. The MX (mixer) 23 functions as a mixer element when the processing device executes a mixer program. The CR (content recorder) 24 functions as a content recorder element by a processing device having a large-capacity storage device executing a recorder program. The AA (automatic accompaniment) 31 functions as an automatic accompaniment element by the processing device executing an automatic accompaniment program. The MR (MIDI recorder) 32 functions as a MIDI recorder element by a processing device having a large-capacity storage device executing a recorder program. The ED (editor) 33 functions as an editor element when the processing device executes an editor program. The EF (effector) 34 functions as an effector element when the processing device executes an effector program. The AR (audio recorder) 35 functions as an audio recorder element when a processing device including a large-capacity storage device executes a recorder program. The SY (sound source, keyboard) 36 functions as a sound source element and a keyboard element by a processing device having a keyboard as hardware executing a sound source program and a keyboard program. The MC (microphone) 41 functions as a microphone element when a processing device including a microphone as hardware executes a microphone program. A CD (CD player) 42 functions as a CD player element when a processing device including a CD drive as hardware executes a player program.
Note that data can be exchanged by communicating between the SV (server) 11 and the DU (DSP unit) 22 or the above-described processing elements or between the processing elements. Here, the SV (server) 11 is used. The processing elements described above support TCP / IP (Transmission Control Protocol / Internet Protocol), and perform data exchange using the TCP / IP protocol.

  In the internal network, all information flowing on the LAN cable is put into a packet of a predetermined length called a MAC frame. An IP packet is encapsulated in a MAC frame, and a preamble for finding the beginning of the signal at the receiving unit and a check code for checking the validity of the contents of the MAC frame are attached to the beginning and end of the MAC frame, respectively. Yes. Further, the MAC frame header includes a MAC address (Media Access Control Address) indicating the transmission destination and the transmission source. The MAC address is a unique number uniquely assigned to all network means. In the case of Ethernet, the MAC address is 48 bits. Also, the transmission of the MAC frame is performed by CSMA / CD (Carrier Sense Multiple Access with Collision Detection) method, and each node (processing device) monitors the MAC frame on the cable and receives it if it is broadcast to itself. Like to do. CSMA / CD is a “carrier sense multiple access / collision detection method”, and a node (processing device) that wants to transmit data detects the carrier wave of the cable to monitor the communication status and starts transmission when it is free. . At this time, if a plurality of nodes (processing devices) start transmission at the same time, data collides in the cable and breaks. Therefore, this is detected (Collision Detection), and transmission is resumed after waiting for a random time.

  TCP / IP is one of the communication protocols. In the OSI reference model, IP corresponds to the third layer (network layer) and TCP corresponds to the fourth layer (transport layer). In the TCP layer, a reliable communication function with full-duplex flow control is provided to an upper processing element (application) using a datagram-oriented communication function of the IP layer. As a result, there is no data omission, duplication, or error, and the data sent on the transmission side reaches the reception side correctly in the same order. In other words, depending on the characteristics of the IP layer and the physical transmission medium below it, packets sent by the transmission side may be lost, may arrive out of order due to delay, or may arrive redundantly due to retransmission. In order to eliminate these effects, a reliable communication path for the processing element is secured by TCP. Each byte of data transmitted and received using TCP is assigned a series of consecutive numbers called sequence numbers, and it is inspected whether there are any missing or duplicated data by the sequence numbers. The data receiving side informs which sequence number of data has been received by returning an ACK (ACKnowledgement) to the transmission source, so that the transmitting side can confirm that the data has correctly arrived at the other party. . In this case, if no ACK is returned even after a predetermined time has elapsed, it is determined that data has been lost or the other party has not received the packet, and retransmission control is performed to transmit the packet again. As a result, highly reliable communication can be performed. Note that the waiting time before starting retransmission is not fixed, and it is dynamically changed according to conditions such as the delay characteristics of the communication path, the time until ACK is returned, and the number of retransmissions, enabling efficient communication. So that it is highly controlled.

  The musical tone generating system according to the present invention is configured by combining processing elements functioning in a plurality of processing devices connected to the internal network shown in FIG. For example, performance data output from the KB (keyboard) 14 is supplied to the TG1 (sound source) 12, and musical tone waveform data generated and output based on the performance data in the TG1 (sound source) 12 is supplied to the SP1 (speaker) 15. When constructing a musical tone generation system to be supplied, the musical tone is set by logically connecting KB (keyboard) 14 and TG1 (sound source) 12, and TG1 (sound source) 12 and SP1 (speaker) 15. The generation system will be constructed. Such a musical sound generation system can be constructed by combining processing elements functioning in a plurality of processing devices connected to an internal network. That is, even if the sound source function of KB (keyboard) 14 and SY (keyboard, sound source) 36 and SP2 (speaker) 21 are logically connected, a musical sound generating system can be constructed. In this case, by further logically connecting the EF (effector) 34 and the MX (mixer) 23, it is possible to apply effects to the musical sound waveform data and to mix a plurality of musical sound waveform data.

  The processing elements functioning in the processing apparatus are physically connected by a LAN. However, data can be exchanged between the processing elements functioning in the processing apparatus by being logically connected. For example, when the KB (keyboard) 14 and the TG1 (sound source) 12 are logically connected, the performance data output from the processing element KB (keyboard) 14 is used as the processing element TG1 (sound source). 12 can be handed over. In this case, the KB (keyboard) 14 and the TG1 (sound source) 12 communicate with each other using TCP / IP, so that the performance data packetized from the KB (keyboard) 14 is output as TG1 (sound source) 12. Will be received. FIG. 2 shows an outline of the generation process of the MAC frame generated in the processing element of the transmission source and output on the network in this case.

  As shown in FIG. 2, the data output from the transmission source processing element is divided into transmission data of a predetermined length, and a TCP segment is generated by adding a TCP header to the head of the transmission data of a predetermined length in the TCP layer. Is done. The TCP header includes a sequence number, a port number of a source processing element, and a port number of a destination processing element. In the IP layer, an IP packet is generated by adding an IP header to the head of this TCP segment. The IP header includes a source IP address and a destination IP address, and a packet length and a protocol number (not shown). The IP address is an identification number assigned to each of the processing devices connected to the internal network and the external network including the Internet shown in FIG. 1, and in IPv4, 32 bits divided into four 8 bits each. This is expressed by arranging four decimal numbers from 0 to 255, such as “192.168.100.8”. Then, a MAC frame is generated by adding a MAC header to the head of the IP packet in the data link layer and the physical layer. The MAC header includes a transmission source MAC address uniquely given to the transmission source processing device and a destination MAC address uniquely given to the destination processing device. The MAC frame generated in this way is sent from the processing device of the transmission source to the LAN cable, and the processing device having the same destination MAC address in the MAC frame captures this MAC frame and is specified by the IP address and the port number. The transmitted data is passed to the processing element. In this way, the port number is a sub-address below the IP address, and the processing element can be specified by the combination of the IP address and the port number, so that it functions in one processing device such as SY (sound source, keyboard) 36. Even if there are a plurality of processing elements, each processing element can be specified by a combination of an IP address and a port number, and a MAC frame can be passed.

Next, FIG. 3 shows an apparatus table which is a correspondence table of identification information for all processing elements in the internal network shown in FIG. In this device table, all processing elements functioning in the processing devices included in the broadcast domain are included. This device table is created by the SV (server) 11 and recorded in all the processing devices on the internal network, and the contents thereof are the same. The contents of the device table when the processing device connected to the internal network is changed are updated by the SV (server) 11 and the updated device table is transmitted from the SV (server) 11 to all the processing devices. ing. The processing device connected to the internal network acquires the device table from the SV (server) 11 and records it in the device table in the own device.
In the device table shown in FIG. 3, “logical device ID” corresponds to a port number of a processing element, and a different ID is assigned to each processing element. The “IP address” is an identification number uniquely assigned to each processing apparatus connected to an internal network and an external network including the Internet. When the processing apparatus logs in to the network, DHCP (Dynamic Host The Configuration Protocol server allocates one of the IP addresses prepared in advance to the processing device. The DHCP server can be the router 2, but can also be the SV (server) 11 or one of the processing devices. The “physical device ID” is a unique number uniquely given to all network devices, corresponds to the MAC address, and is a unique number uniquely given to the processing device of the internal network in FIG. Yes. The “device name” is an abbreviation for the processing device in which the processing element functions.

  “Process ID” corresponds to the port number of the process element, and a different process ID is assigned to each process element, but may be omitted because there is a logical device ID. The “processing element name” is the name of the musical sound generation related device realized by the processing element. Since the processing element name “DSP unit” of the logical device ID “No. 7” functions as a processing element corresponding to the microprogram to be executed, the processing ID and the processing element name of the set processing element are set. Are recorded in the device table. Since the processing element name “sound source” of the logical device ID “No. 15” and the processing element name “keyboard” of the logical device ID “No. 16” are processing elements functioning in one processing device, Although the IP address and physical device ID are the same, different logical device IDs (port numbers) are given so that they can be handled independently. “Voice file provision” is information on whether or not to provide a voice file to the outside, and [○] is recorded when it can be provided, and [×] is recorded when it cannot be provided. In this case, even if the processing device records a voice file, the processing device that is prohibited from sending the voice file to the outside is [x]. “Load distribution target” is information as to whether or not the load is to be distributed, and [◯] is recorded when the load is distributed and [×] is recorded when the load is not distributed. In this case, the load distribution target is limited to processing elements that can execute the process intended by the user even if the process is left to other processing apparatuses. Note that the load refers to the load applied to the CPU in the processing device by software processing (executed by the CPU), and the processing device in which the processing element is realized by software is a target, but the processing element is performed only by hardware. The processing device that realizes the above is not a load balancing target.

  In the musical sound generating system of the present invention, the processing device can be stored in a storage means such as a hard disk device in which various programs are incorporated so as to function as the various processing elements described above. Then, by selecting and executing one of the programs stored in the storage means, it is possible to switch processing elements that function in the processing device. At this time, by selecting and executing a plurality of programs at the same time, one processing apparatus functions with a plurality of processing elements. In this case, when a processing element desired to function in the processing device is selected, the processing device is set to execute a program corresponding to the processing element, and the processing element is registered in the SV (server) 11. As a result, the logical device ID (port number) is set in the processing element. Then, the device table updated by the SV (server) 11 is transmitted and recorded to all the processing devices on the internal network.

In the musical sound generating system of the present invention, data communicated between processing elements is classified into two types: entity data and control data. Here, data that directly represents the content of music to be played back and that is preferentially communicated requiring real-time communication is defined as entity data. Specifically, MIDI data and audio (PCM and MP3) data are the actual data. Data other than the entity data is defined as control data. Transmission and reception of control data can be executed by all processing devices including the SV (server) 11.
Therefore, FIG. 4 shows a connection table recorded for each input side and each output side of each processing element capable of actual data communication in the processing elements on the internal network. The connection table is created by the SV (server) 11 and recorded in all the processing devices on the internal network, and the contents thereof are the same. In this connection table, information about each processing element functioning in all processing apparatuses connectable to the internal network shown in FIG. 1 is recorded. The processing device connected to the internal network acquires the connection table from the SV (server) 11 and records it.

  The connection table shown in FIG. 4 is a connection table of some processing elements in the internal network having the configuration shown in FIG. 1, and “x” in the connection table indicates that there is no processing element that can be connected, and the processing ID Indicates that the server with “AA” does not transmit or receive the entity data. This server is the SV (server) 11 shown in FIG. A sound source element having a process ID “AB” can be connected to a processing element that transmits performance data such as MIDI data as entity data, and can be output and connected to a processing element that receives audio data as entity data. . That is, the processing elements that can be connected to the input are the keyboard element with the process ID “AC”, the automatic accompaniment element with the process ID “AH”, the MIDI recorder element with the process ID “AI”, and the editor element with the process ID “AJ”. Thus, the processing elements that can be output-connected are the speaker with the process ID “AD”, the effector element with the process ID “AK”, and the audio recorder element with the process ID “AL”. Further, the keyboard with the process ID “AC” can output and connect a processing element that receives performance data such as MIDI data as entity data, and there is no processing element that can be input-connected due to its nature. In other words, the processing elements that can be output-connected are the sound source element whose processing ID is “AB”, the MIDI recorder element whose processing ID is “AI”, and the editor element whose processing ID is “AJ”. Furthermore, the speaker with the process ID “AD” can input and connect a processing element that transmits audio data as entity data, and there is no processing element that can be output connected due to its nature. That is, the processing elements that can be connected to the input are sound source elements whose processing ID is “AB”, mixer elements whose processing ID is “AF”, effector elements whose processing ID is “AK”, audio recorder elements whose processing ID is “AL”, A microphone element with a process ID “AM”, a CD player element with a process ID “AN”, and the like. In the connection table, the processing elements that can be connected to the input and the processing elements that can be connected to the output are shown for each processing element. By referring to the connection table, the processing element to be connected to input and the processing element to be connected to output can be selected Will be able to.

Next, FIG. 6 shows a flowchart of network connection processing executed when a processing device is newly connected (logged in) to the internal network. The client is a client for the SV (server) 11 and all processing devices other than the SV (server) 11 in the internal network are clients. Control data communicated between the client and the SV (server) 11 is communicated using the IP address of the destination processing device and a predetermined port number for control data.
When the network connection process is activated, it is determined in step S10 whether or not the newly connected new client has a plurality of processing elements. Here, the new client functions as the keyboard element KB and the sound source element TG by executing the keyboard program and the sound source program as in the processing unit NEW shown in the upper part of FIG. 5, and the MIDI data generated in the keyboard element KB is used. If it is connected so that it can be input to the sound source element TG, YES is determined and the process proceeds to step S11, and the internal connection between the keyboard element KB and the sound source element TG is disconnected as shown in the lower part of FIG. Thereby, in the processing apparatus NEW in which a plurality of processing elements are functioning, since the connection between the processing elements is automatically disconnected when logging on, the work of disconnecting in advance before logging on is omitted. Will be able to. Then, the process proceeds to step S12 in the same manner as in the case where it is determined in step S10 that the plurality of processing elements are not included, and a data part including the own device information and the registration request is created. The own device information includes logical device IDs and IP addresses of all processing elements in the processing device (IP addresses are assigned by the DHCP server when logging into the internal network), physical device IDs, and processing of all processing elements. ID, processing element name information, voice file provision information, and load distribution target information. The registration request is a request for registering own device information in the device table in the SV (server) 11. Next, transmission processing is performed in step S13. In the transmission process, the data part created in step S12 is used as transmission data, and finally a MAC frame in which the transmission data is encapsulated is generated as shown in FIG. 2 and transmitted on the internal network. In the MAC header of the MAC frame, the MAC address (physical device ID) of the SV (server) 11 is set as the destination MAC address.

  Since the MAC frame transmitted from the new client is a star-type internal network, it is received by the hub, and a route determination process is performed (step S20). In the route determination process, the hub determines the transmission route by looking at the destination MAC address of the received MAC frame, and relays the MAC frame. For example, when a new client is physically connected to the hub 30, the hub 30 relays the received MAC frame to the router 2, the router 2 relays the received MAC frame to the hub 10, and the hub 10 receives it. The MAC frame is relayed to the SV (server) 11. As a result, the MAC frame transmitted from the new client is received by the SV (server) 11 having the same destination MAC address, and reception processing is performed (step S30). In the reception process, an IP packet is extracted from the MAC frame, a TCP segment is extracted from the IP packet, and a data part is acquired from the TCP segment. Then, it is determined that the registration request processing is to be performed because there is a registration request by interpreting the acquired data part. Next, in step S31, the device information of the data part is recorded in the device table, and in step S32, the changed device table and the data part including the change request are created. This data part is transmitted on the internal network by performing transmission processing in step S33. This transmission process is the same as the transmission process in step S13 described above, but the broadcast address (FF-FF-FF-FF-FF-FF) of all “1” is set as the destination MAC address, A broadcast address is also set as the destination IP address. In this case, when the network address of the internal network is “192.168.111.0” as in the device table shown in FIG. 3, the broadcast address of the IP address is “192.168.111.255”. Is done.

  The MAC frame broadcast from the SV (server) 11 is received by the hub 10 and a route determination process is performed (step S20). In this route determination process, the same route determination process as in step S20 is performed, but since the MAC frame is a broadcast address, the router 2 and the hubs 10 to 40 relay the MAC frame to all the processing devices. become. Since the new client uses the broadcast address when the broadcast MAC frame arrives, the new client performs reception processing for receiving the same MAC frame as in step S30 (step S14). Next, the device table information extracted from the MAC frame received in step S15 is stored in the internal storage means, and the network connection process in the new client is completed. In addition, since the broadcast address is used when the broadcasted MAC frame arrives at other clients, a reception process for receiving the same MAC frame as in step S30 is performed (step S40). Next, the device table stored with the device table information extracted from the MAC frame received in step S41 is updated, and the network connection process in the other client ends. As a result, all the clients connected to the internal network have the updated device table shown in FIG. The SV (server) 11 may broadcast the connection table together with the device table to all clients connected to the internal network.

Next, FIG. 7 shows a flowchart of a network disconnection process executed when a processing device connected to the internal network is disconnected (logged off).
When the processing device connected to the internal network is disconnected (logged off), the network disconnection processing is started, and the processing device disconnected in step S50 has a plurality of processing elements and there is a connection to be restored. It is determined whether or not. Here, when it is determined that the disconnected processing apparatus has a plurality of processing elements as in the processing apparatus OLD shown in the upper part of FIG. 8 and there is a connection to be restored, the process proceeds to step S51 and the plurality of processes are performed. Restore all connections that should be restored in the element. For example, in the case of a processing device OLD having a keyboard element KB and a sound source element TG as shown in the upper part of FIG. 8, the keyboard element so that MIDI data generated in the keyboard element KB can be input to the sound source element TG. The KB and the sound source element TG are internally connected as shown in the lower part of FIG. When the process of step S51 is completed and when it is determined in step S50 that there is no connection to be restored, the network disconnection process ends. Thereby, in the processing apparatus OLD in which a plurality of processing elements are functioning, the connection between the processing elements is automatically restored when the logoff is performed, and the processing apparatus OLD can be used without connecting again between the processing elements. In addition, although the connection between processing elements is internally connected using API (Application Program Interface) etc., it is good also as an external connection logically connected using the port number assigned to each processing element.

  The SV (server) 11 periodically performs processing for confirming the existence of a client on the internal network. When a client disconnected by this processing is detected, information on the client is obtained from the device table. Delete and update device table. Then, the updated device table is broadcasted to all clients. Each client that receives the broadcast updates the device table stored in its own device with the received device table information.

Next, FIG. 10 and FIG. 11 show setting screens displayed when executing the connection selection process for setting the connection between the processing elements. This setting screen is a setting screen when the internal network has the simple configuration shown in FIG.
In the internal network shown in FIG. 9, a processing device SY1 in which a plurality of processing elements are functioning is connected to the hub HBa by a LAN cable, and a processing device SY2 in which a plurality of processing elements are functioning is connected to the hub HBa in a LAN. Connected with a cable. In the processing device SY1, the keyboard element KBa, the sound source element TGa, and the speaker element SPa function, and in the processing device SY2, the sound source element TBb and the speaker element SPb function. These processing elements in the processing devices SY1 and SY2 are logically separated from each other inside. In the processing devices SY1 and SY2 in which a plurality of processing elements are functioning in this way, connection selection of processing elements can be performed for each processing element. Here, a case where connection selection is set from the keyboard element KBa of the processing device SY1 will be described. In this case, the connection selection process is started in the processing device SY1. Then, a screen A1 shown in FIG. 10 is displayed on the screen of the processing device SY1. The screen A1 is a screen that displays three processing elements, keyboard element KBa, sound source element TGa, and speaker element SPa that are functioning in the processing device SY1, and selects one of them as a processing element for setting a connection. The Here, when the keyboard element KBa is selected as a processing element for connection setting on the screen A1, a screen A2 shown in FIG. 10 is displayed on the screen of the processing device SY1.

  The screen A2 is on the internal network shown in FIG. 9 and displays processing elements that can be connected to the keyboard element KBa that is the selected processing element, and is a screen for selecting one of them. Processing elements that can be connected to the keyboard element on the internal network are displayed with reference to the device table and the connection table. In this case, a keyboard element KBa, a sound source element TGa, a speaker SPa, a sound source TBb, and a speaker SPb are recorded in the device table. Further, referring to the connection table, since there is no input connection in the keyboard element KBa, only the processing elements that can be output connected are recorded. Then, since the only processing element on the internal network that can be output-connected to the keyboard element is the sound source element, only the sound source element is displayed on the screen A2. When the sound source element displayed on the screen A2 is selected, a screen A3 shown in FIG. 10 is displayed on the screen of the processing device SY1. The screen A3 is a screen for selecting whether to connect the sound source element that is the selected processing element (continue) or not (end). If “continue” is selected here, a screen A4 shown in FIG. 10 is displayed on the screen of the processing device SY1. The screen A4 is a processing element that can be connected to the sound source element that is the selected processing element, and displays processing elements on the internal network shown in FIG. 9, and a screen for selecting one of them. Is done.

  Connectable processing elements on the internal network are detected with reference to the device table and the connection table. In this case, the device table includes a keyboard element KBa, a sound source element TGa, a speaker SPa, a sound source TBb, and a speaker SPb. It is recorded. Then, since the processing element that can be connected to the tip of the sound source element is the speaker element, only the speaker element is displayed on the screen A4. When the speaker element displayed on this screen A4 is selected, a screen A6 shown in FIG. 10 is displayed on the screen of the processing device SY1. The screen A6 is a screen for selecting the end because there is no output connection of the speaker element and the processing element cannot be connected to the tip of the speaker element. Therefore, when the end is selected on the screen A6, a screen A7 shown in FIG. 10 is displayed on the screen of the processing device SY1. By selecting “End”, the logical connection in the order of keyboard element, sound source element, and speaker element has been set. If there are multiple identical processing elements on the internal network, one of the respective processing elements is selected. This processing element is selected and set. Therefore, first, the processing device in which the sound source element selected on the screen A2 is functioning is detected from the internal network by referring to the device table, and the device name of the processing device is displayed on the screen A7. One of the displayed device names is selected as the connection destination. In the case of the internal network shown in FIG. 9, the processing device SY1 and the processing device SY2 are detected as processing devices with functioning sound source elements, and either the device name SY1 or the device name SY2 is selected as the sound source element. Is displayed on the screen A7.

  Here, when the sound source element of the device name SY2 (or device name SY1) is selected, the processing device in which the speaker element selected on the screen A4 is functioning is detected from the internal network by referring to the device table. Then, the device name of the processing device is displayed on the screen A8, and one of the displayed device names on which the speaker element functions is selected as a connection destination. When a speaker element having the device name SY1 (or device name SY2) is selected on the screen A8, each processing element to be connected is determined, and settings for logical connection in the order of keyboard element KBa-sound source element TGb-speaker element SPa are made. The connection selection process for ending and connecting the processing elements ends. If there are a plurality of processing devices in which the selected processing element is functioning, screens for selecting device names in order for all of the processing devices are sequentially displayed.

Further, when the end is selected on the screen A3, a screen A5 shown in FIG. 10 is displayed on the screen of the processing device SY1. By selecting "End", the logical connection in the order of keyboard element-sound source element has been set. Next, if there are multiple identical processing elements on the internal network for each processing element This processing element is selected. Therefore, the processing device in which the selected sound source element is functioning is detected from the internal network by referring to the device table, the device name of the processing device is displayed on the screen A5, and the sound source element is functioning. One of the registered device names is selected as a connection destination. That is, a screen similar to the screen A7 is displayed on the screen A5. When the sound source element of the device name SY2 is selected, each processing element to be connected is determined, and the logical connection is made in the order of the keyboard element KBa-the sound source element TGb. The setting for performing the connection is completed, and the connection selection process for connecting the processing elements is completed.
When the connection selection process for connecting the processing elements is completed, the set connection information is recorded in the connection buffer of the processing apparatus in which the setting has been made. Then, when a connection establishment process that is periodically started, which will be described later, is activated, a connection establishment process is performed based on the connection information in the connection buffer to establish a logical connection, and the established connection information is stored in the current buffer. It will be recorded.

Next, description will be made on setting connection selection from the sound source element TGb of the processing device SY2. However, in this setting, it is assumed that the setting shown in FIG. 10 is performed and the setting for logical connection in the order of keyboard element KBa-sound source element TGb-speaker element SPa has been completed. Here, the connection selection process is started in the processing device SY2. Then, a screen B1 shown in FIG. 11 is displayed on the screen of the processing device SY2. The screen B1 is a screen that displays two processing elements of the sound source element TGb and the speaker element SPb that are functioning in the processing device SY2, and selects one of them as a processing element for setting a connection. Here, when the sound source element TGb is selected as the processing element for setting the connection on the screen B1, the screen B2 shown in FIG. 11 is displayed on the screen of the processing device SY2.
The screen B2 is a processing element that can be connected to the sound source element TGb that is the selected processing element, and displays processing elements on the internal network shown in FIG. 9, and is a screen for selecting one of them. The Processing elements that can be connected on the internal network are detected by referring to the device table and the connection table. In this case, a keyboard element KBa, a sound source element TGa, a speaker SPa, a sound source TBb, and a speaker SPb are registered in the device table. With reference to the connection table, since the sound source element can be connected to the input and output, a screen B2 for selecting the input connection is displayed first. Since only the keyboard element is the processing element that can be input-connected to the sound source element, only the keyboard element is displayed on the screen B2, and the title of “input connection” is also displayed. When a keyboard element is selected on this screen B2, a screen B3 shown in FIG. 11 is displayed on the screen of the processing device SY2. When a keyboard element is selected, the process of selecting a processing element connected to the keyboard element is continued. However, since a processing element cannot be connected to the keyboard element, input connection to the screen B3 is possible. Instead, the screen for selecting the output connection is displayed. When a processing element is selected, if there is a processing element that can be connected to the destination, a screen for selecting either continuation or output connection is displayed. Let them be selected.

  When an output connection is selected on the screen B3, a screen B4 shown in FIG. 11 is displayed on the screen of the processing device SY2. On the screen B4, processing elements that can be output-connected to the sound source element are displayed together with the title “output connection”. Processing elements on the internal network that can be connected to the output are detected by referring to the device table and the connection table. In this case, since only the speaker element is the processing element on the internal network that can be connected to the sound source element, either the speaker element or “END” in which setting is terminated without selecting the speaker element is displayed on the screen B4. A screen for selecting is displayed. When the speaker element is selected on the screen B4, a screen B5 shown in FIG. 11 is displayed on the screen of the processing device SY2. When a speaker element is selected, a processing element cannot be connected to the tip of the speaker element, so that a screen for selecting termination is displayed on the screen B5 together with the title “output connection”. Therefore, when the end is selected on the screen B5, a screen B7 shown in FIG. 11 is displayed on the screen of the processing device SY2. By selecting the end, the logical connection in the order of keyboard element-sound source element-speaker element has been set. Next, if there are multiple identical processing elements on the internal network, each processing element One of the processing elements is selected.

  Therefore, on the screen B7, the processing device in which the sound source element selected with reference to the device table is functioning is detected from the internal network, the device name of the processing device is displayed, and the sound source element of the displayed device name is displayed. This is a screen for selecting one of the above as a connection destination. In this case, since it is detected that the keyboard element that can be logically connected to the tone generator element TGb is functioning only in the processing device SY1, a screen for selecting the device name SY1 is displayed on the screen B7. In this case, since the setting shown in FIG. 10 has already been performed and the setting for logical connection of keyboard element KBa-sound source element TGb has been completed, the device name SY1 in which the keyboard element KBa is functioning has already been selected. Is displayed with an underline. When the device name SY1 is selected as a keyboard element on the screen B7, the processing device in which the speaker element that can be logically connected to the sound source element is detected from the internal network, and the device name of the processing device is displayed. A screen B8 for selecting one of the speaker elements of the displayed device name as the connection destination is displayed. In this case, since the setting shown in FIG. 10 is performed and the setting for logical connection between the sound source element TGb and the speaker element SPa is completed, the device name SY1 in which the speaker element SPa is functioning is already selected. Is displayed with an underline. When the speaker element with the device name SY2 is selected on the screen B8, the sound source element TGb is set to be logically connected to the speaker element SPb in addition to the speaker element SPa. Thereby, each processing element logically connected in the internal network shown in FIG. 9 is determined, and the setting for logically connecting the keyboard element KBa and the sound source element TGb, the sound source element TGb, the speaker element SPa, and the speaker element SPb are set. The setting for logical connection ends, and the connection selection process for connecting the processing elements ends. If there are a plurality of processing devices in which the selected processing element is functioning, screens for selecting device names in order for all of them are sequentially displayed.

When the end is selected on the screen B4, a screen B6 shown in FIG. 11 is displayed on the screen of the processing device SY2. By selecting "End", the logical connection in the order of keyboard element-sound source element has been set. Next, if there are multiple identical processing elements on the internal network for each processing element This processing element is selected. Therefore, the processing device in which the selected keyboard element is functioning is detected from the internal network by referring to the device table, the device name of the processing device is displayed on the screen B6, and the display in which the keyboard element is functioning. One of the registered device names is selected as a connection destination. That is, a screen that is almost the same as the screen B7 is displayed on the screen B6. Here, when a keyboard element with the device name SY1 is selected, each processing element to be connected is determined, and the logic in the order of keyboard element KBa-sound source element TGb. The setting for connection ends, and the connection selection process for connecting the processing elements ends.
When the connection selection process for connecting the processing elements is completed, the set connection information is recorded in the connection buffer of the processing apparatus in which the setting has been made. Then, when a connection establishment process that is periodically started, which will be described later, is activated, a connection establishment process is performed based on the connection information in the connection buffer to establish a logical connection, and the established connection information is stored in the current buffer. It will be recorded.

FIG. 12 shows a flowchart of connection selection processing for setting connection between processing elements on the setting screens shown in FIGS. 10 and 11.
When the connection selection process is started in the processing apparatus for setting the connection of the processing elements, all the processing elements of its own apparatus are displayed on the screen as shown in the screen A1 in FIG. 10 and the screen B1 in FIG. The selection of the processing element is accepted. If any processing element is selected, the process proceeds to step S61, and it is determined whether the selected processing element has an input connection and an output connection with reference to the connection table. Here, if the selected processing element does not have an input connection and an output connection, it is determined as NO, the process proceeds to step S62, and the processing elements that can be connected to the selected processing element are displayed, and the displayed process Displays a screen that accepts element selection. When one of the displayed processing elements is selected, if there is a processing element that can be connected subsequently to the processing element selected in step S63, either the connection or the termination is selected. Display the screen. If there is no processing element that can be connected subsequently, a screen for selecting the end is displayed. Then, in step S64, it is determined whether or not a selection to end the selection of the processing element has been made. Here, if “end” is selected, the process proceeds to step S65, but if it is selected to continue, the process returns to step S62, and the process from step S62 to step S64 is performed again to continue the processing element selected last time. The processing elements that can be connected are selected. The processes in steps S62 to S64 are repeatedly executed until there is no processing element that can be connected subsequently or until end is selected.

  If it is detected that the processing element selected in step S61 has an input connection and an output connection, the process branches to step S69. First, processing elements that can be connected to the input of the processing element are displayed and displayed. A screen for accepting selection of the processed element is displayed. When one of the displayed processing elements is selected, if there is a processing element that can be connected subsequently to the processing element selected in step S70, either the connection or the termination is selected. Display the screen. If there is no processing element that can be connected subsequently, a screen for selecting the end is displayed. Then, in step S71, it is determined whether or not a selection to end the selection of the processing element has been made. Here, if it is selected to end, the process proceeds to step S72. If it is selected to continue, the process returns to step S69, and the process from step S69 to step S71 is performed again to continue from the processing element selected last time. Processing element selection processing that can be performed is performed. The processing from step S69 to step S71 is repeatedly executed until there is no processing element that can be subsequently connected or until end is selected.

  When it is determined that the end is selected in step S71 and the process proceeds to step S72, a processing element that can be connected to the output of the processing element selected in step S61 is displayed, and a screen for accepting the selection of the displayed processing element is displayed. indicate. When one of the displayed processing elements is selected, if there is a processing element that can be connected subsequently to the processing element selected in step S73, it is selected whether to continue connection or end. Display the screen. If there is no processing element that can be connected subsequently, a screen for selecting the end is displayed. Then, in step S74, it is determined whether or not a selection to end the selection of the processing element has been made. Here, if it is selected to end, the process proceeds to step S65. If it is selected to continue, the process returns to step S72, and the process from step S72 to step S74 is performed again to continue from the previously selected processing element. Processing element selection processing that can be performed is performed. The processes in steps S72 to S74 are repeatedly executed until there is no processing element that can be connected subsequently or until end is selected.

  When it is determined that the end has been selected in step S64 or step S74 and the process proceeds to step S65, the apparatus name of the processing apparatus in which the corresponding processing element is functioning is displayed for each processing element selected with reference to the apparatus table. Then, a screen for accepting selection of any of the displayed device names is displayed. When one of the displayed device names is selected, the processing element functioning in the processing device with the selected device name is selected, and the connection information of the logical connection thus set is displayed in the connection buffer. Is recorded in step S66. In this case, the logical connection selected in succession is recorded in the connection buffer in association with continuous communication, and when the input and output connections of the processing element are selected in succession, Record that communication is taking place in the connection buffer. When the process of step S66 ends, it is determined in step S67 whether or not the automatic flag is “1”. The automatic flag is a flag indicating whether or not to update the default buffer, which will be described later. The automatic flag “0” indicates that the default buffer is updated, and the automatic flag “1” updates the default buffer. It shows no. When the power is turned on in each processing device, the connection recorded in the default buffer is automatically restored as will be described later. Therefore, when the user newly sets a connection, the set connection is reflected. The default buffer is updated so that it does. Therefore, if the automatic flag is determined to be “1” in step S67, the process branches to step S68, and the automatic flag is set to “0”, so that the connection set in the connection selection process is turned on next time. Sometimes it is automatically restored. When the process of step S68 ends, the connection selection process ends. If it is determined in step S67 that the automatic flag is not “1”, the automatic flag is “0”, and the connection selection process is terminated. Then, when a connection establishment process that is periodically activated, which will be described later, is activated, the connection establishment process is performed based on the connection information stored in the connection buffer in which the connection information set in step S66 is recorded. The established connection information is recorded in the current buffer.

FIG. 13 shows an example of connection information recorded in the connection buffer when the connection selection process shown in FIGS. 10 and 11 is performed and the logical connection of the processing elements is set.
The connection selection process shown in FIG. 10 is started in the processing device SY1 from the connection of the keyboard element KBa, the connection between the keyboard element KBa and the sound source element TGb of the processing device SY2 is set, and the connection between the sound source element TGb and the processing device SY1. Since the connection with the speaker element SPa is set, the connection information of “output 1 → SY2 sound source → SY1 speaker” is recorded in the connection buffer, as shown as “● SY1 keyboard example” in FIG. “Output 1” means the first output of the SY1 keyboard.
Further, the connection selection process shown in FIG. 11 is started from the connection of the sound source element TGb in the processing device SY2, and the setting for connecting the keyboard element KBa of the processing device SY1 to the input of the sound source element TGb and the processing of the output of the sound source element TGb are performed. Since the setting to connect the speaker element SPb of the device SY2 is performed, as shown in FIG. 13 as “● SY2 sound source example”, the connection buffer includes “input 1 ← SY1 keyboard”, “input 1 → output 1”, “ Connection information of “output 1 → SY2 speaker” is recorded. Here, “input 1 ← SY1 keyboard”, “input 1 → output 1”, and “output 1 → SY2 speaker” are MIDI data (input 1) input from the SY1 keyboard in the sound source element TGb of the own device (SY2). This is connection information indicating that the processing result (output 1) is output (associated) to the SY2 speaker.

Next, a flowchart of the connection establishment process is shown in FIG. The connection establishment process is periodically started at predetermined time intervals. Note that the control data communicated between the processing device operated in the connection establishment process and the processing device of the connection partner uses the IP address of the destination processing device and a predetermined port number for control data. Communicated.
When the connection establishment process is activated, it is determined in step S80 whether or not there is an unprocessed connection from the recorded contents of the connection buffer. Here, if it is determined that there is no unprocessed connection, the connection establishment process ends as it is. If it is determined in step S80 that there is an unprocessed connection, the process proceeds to step S81, and one of the unprocessed connections is set as a connection establishment target. The connection established here means setting of a port for communicating actual data. Next, in step S82, the current buffer is referred to and it is detected whether or not the target connection has already been established. If it is detected that the target connection has already been established, the process proceeds to step S83 without establishing a new connection. In step S83, it is detected whether there is a destination connection that is the target connection. If it is detected that there is no destination connection, the connection establishment process ends as it is. If it is detected in step S83 that there is a previous connection, the process proceeds to step S84 to create a data portion including a connection instruction. In this case, if there is a correspondence, a connection request for instructing the correspondence is included in the data portion. The connection instruction is an instruction of the other party to be connected to the connection partner, and when a plurality of connections are continuously set at the connection partner, all the information is included.

  If it is detected in step S82 that the target connection is not recorded in the current buffer and the target connection is not yet established, the process branches to step S85, and includes a connection request and a connection instruction. Create a data division. The connection request is a request for establishing a connection, and when there is a correspondence, the association is also instructed. The connection instruction is an instruction of the other party to be connected to the connection partner, and when a plurality of connections are continuously set at the connection partner, all the information is included. When the data part is created in step S84 or step S85, transmission processing for transmitting the data part is performed in step S86. In the transmission process, the data part created in step S84 or step S85 is used as transmission data, and finally a MAC frame in which the transmission data is encapsulated is generated as shown in FIG. 2 and transmitted over the internal network. The In this case, the MAC address (physical device ID) of the processing device in which the target processing element of the connection destination is functioning is set as the destination MAC address in the MAC header of the MAC frame.

  The MAC frame transmitted to the network from the processing apparatus performing the connection establishment operation is received by the hub because it is a star-type internal network, and a route determination process is performed (step S90). In the route determination process, the hub determines the transmission route by looking at the destination MAC address of the received MAC frame, and relays the MAC frame. As a result, the MAC frame transmitted from the processing device performing the connection establishment operation is received by the processing device in which the processing element of the connection partner whose destination MAC address matches is functioning, and the reception processing is performed (step). S100). In the reception process, an IP packet is extracted from the MAC frame, a TCP segment is extracted from the IP packet, and a data part is acquired from the TCP segment. In step S101, load distribution processing is performed. As will be described later, the load distribution process is a process that can change the requested connection to another client having the same processing element when the requested connection destination client cannot establish a new connection. . When the load distribution process is completed, the requested connection is established by interpreting the data part acquired in step S102. When there is an instruction for association, association is also performed, and connection information and association of the established connection are recorded in the current buffer. In establishing a connection, an IP address of a processing device that is functioning as a processing element of a connection partner to be targeted is obtained by referring to the device table, and a logical device ID (port number) of the processing element is acquired. Since the processing element of the connection partner in the processing device can be specified by the IP address and the port number, the target connection can be established by setting the IP address and the port number. When the process of step S102 ends, the process proceeds to step S103 to determine whether there is a connection instruction. If it is determined that there is a connection instruction, the connection with the other processing apparatus instructed by the connection instruction is recorded in its own connection buffer, and the process proceeds to step S105.

  If it is not detected in step S103 that there is a connection instruction in the data part, the process branches to step S105. In step S105, a data part including connection completion is created, and transmission processing for transmitting the data part is performed in step S106. In the transmission process, the data part created in step S105 is used as transmission data, and finally a MAC frame in which the transmission data is encapsulated is generated as shown in FIG. 2 and transmitted on the internal network. In this case, the MAC address of the operating processing device is set as the destination MAC address in the MAC header of the MAC frame. Since the MAC frame transmitted from the processing apparatus as the connection partner to the network is a star-type internal network, the MAC frame is received by the hub, and a route determination process is performed (step S91). In the route determination process, the hub determines the transmission route by looking at the destination MAC address of the received MAC frame, and relays the MAC frame. As a result, the MAC frame transmitted from the processing apparatus of the connection partner is received by the processing apparatus that is executing the connection establishment process with the matching destination MAC address, and the reception process is performed (step S87).

In the reception process, an IP packet is extracted from the MAC frame, a TCP segment is extracted from the IP packet, and a data part is acquired from the TCP segment. Then, the data part acquired in step S88 is interpreted to establish a connection with a connection completion response (ACK). If there is a correspondence, the correspondence is also performed, and the connection information and the correspondence of the established connection are recorded in the current buffer. In establishing a connection, an IP address of a processing device that is functioning as a processing element of a connection partner to be targeted is obtained by referring to the device table, and a logical device ID (port number) of the processing element is acquired. Since the processing element of the connection partner in the processing device can be specified by the IP address and the port number, the target connection can be established by setting the IP address and the port number. When the process of step S88 ends, the connection establishment process ends.
The connection establishment based on the connection information recorded in the connection buffer of the connection partner processing device is a processing device operated by the connection partner processing device when the connection establishment processing is started in the connection partner processing device. Thus, the connection establishment process shown in FIG. 14 is executed.

As described above, the connection information and the association of the connection established by executing the connection establishment process are recorded in the current buffer. Therefore, FIG. 15 shows an example of association with connection information recorded in the current buffer. In this case, a connection for communicating entity data currently established in the own processing apparatus is recorded in the current buffer.
The connection information shown in FIG. 15 is associated with the case where the connection establishment process is performed based on the connection information recorded in the connection buffer as shown in FIG. 13, and the current buffer of the processing device SY1 is displayed in the processing device SY1. Connection information and association of each of the functioning keyboard element KBa, sound source element TGa, and speaker element SPa are recorded. In this case, the connection information of the keyboard element KBa is associated with “port 1: output → SY2 sound source”, and the MIDI data output from the keyboard element KBa is output from the port 1 of the processing device SY1 to the SY2 sound source. Is done. Further, since the sound source element TGa is not connected, there is no association with the connection information, and the connection information and association with the speaker element SPa is “port 2: input ← SY2 sound source”, and from the sound source element TGb of the processing device SY2. By receiving the output audio data at the port 2 of the processor SY1, the connection information is input to the speaker element SPa.

  Further, the connection information and the association between the sound source element TGb and the speaker element SPb functioning in the processing device SY2 are recorded in the current buffer of the processing device SY2. In this case, the connection information of the tone generator element TGb is associated with “port 1: input ← SY1 keyboard”, “port 1 → port 2”, “port 1 → port 3”, “port 2: output → SY1 speaker”, “ Port 3: Output → SY2 speaker ”. “Port 1: input ← SY1 keyboard” is connection information that is input to the sound source element TGb when MIDI data output from the keyboard element KBa of the processing device SY1 is received by the port 1 of the processing device SY2. “Port 1 → Port 2” and “Port 1 → Port 3” output from the port 2 and port 3 the audio data which is the processing result of the MIDI data input from the keyboard element KBa of the processing device SY1 in the sound source element TGb. Connection information. “Port 2: output → SY1 speaker” and “port 3: output → SY2 speaker” output audio data output from the sound source element TGb from the port 2 to the speaker element SPa of the processing device SY1, and the sound source element. This is connection information for outputting audio data output from the TGb from the port 3 to the speaker element SPb of the processing device SY2. The connection information and the association of the speaker element SPb is “port 3: input ← SY2 sound source”, and the audio data output from the sound source element TGb of the processing device SY2 is received at the port 3 and input to the speaker element SPb. It is associated with connection information.

Next, a flowchart of the load distribution process executed in step S101 of the connection establishment process shown in FIG. 14 is shown in FIGS. In this case, the processing device itself that has started (operating) establishment of connection does not perform load distribution processing, and load distribution processing is performed in the processing device of the connection partner accessed as the connection partner from the outside. . Note that the control data communicated between the processing device operated in the load balancing process and the processing device of the connection partner uses the IP address of the destination processing device and a predetermined port number for control data. Communicated.
When the load distribution process is activated, it is determined in step S200 whether or not it is necessary to determine the execution of load distribution by looking at the information of “load distribution target” in the device table shown in FIG. That is, if [○] is added to the “load distribution target” column of the processing element for establishing connection in the processing apparatus of the connection partner, it is determined that it is necessary to determine execution of load distribution, and the process proceeds to step S201. , [X] is attached, it is determined that it is not necessary to determine execution of load balancing, and the process returns to step S102 of the connection establishment process.

  In step S201, when the CPU usage rate in the processing apparatus of the own machine exceeds a predetermined value, it is determined that load distribution is performed because there is a possibility that processing may be delayed. In this case, sound source elements, mixer elements, and effect elements configured by hardware instead of software are excluded. If it is determined that the CPU usage rate of the own device does not exceed the predetermined value and load distribution is not performed, the process returns to step S102 of the connection establishment process, and the CPU usage rate of the own device exceeds the predetermined value. If it is determined that load distribution is to be performed, the process proceeds to step S202. In step S202, all the clients (processing devices) in which the same processing elements are functioning are extracted with reference to the device table shown in FIG. 3, and the clients extracted in step S203 are extracted one by one in order. One of the processing devices is targeted. Next, in step S204, a data part for inquiring whether a new connection can be added to the target processing apparatus is created, and in step S205, transmission processing for transmitting the data part is performed. In the transmission process, the data part created in step S204 is used as transmission data, and finally a MAC frame in which the transmission data is encapsulated as shown in FIG. 2 is generated and transmitted on the internal network. In this case, the MAC address of the target processing device is set as the destination MAC address in the MAC header of the MAC frame. Since the MAC frame transmitted from the processing apparatus of the connection partner to the network is a star-type internal network, the MAC frame is received by the hub, and a route determination process is performed (step S210). In the route determination process, the hub determines the transmission route by looking at the destination MAC address of the received MAC frame, and relays the MAC frame. As a result, the MAC frame transmitted from the processing apparatus of the connection partner is received by the target processing apparatus whose destination MAC address matches, and the reception process is performed (step S220).

  In the reception process, an IP packet is extracted from the MAC frame, a TCP segment is extracted from the IP packet, and a data part is acquired from the TCP segment. Then, it is determined whether or not a new connection can be added by interpreting the data part acquired in step S221. Here, when it is determined that the CPU usage rate is high in the target processing apparatus and a new connection cannot be added, the process proceeds to step S223, and a data portion indicating that a new connection cannot be added is displayed. A transmission process is performed to transmit the data part in step S224. In the transmission process, the data part created in step S223 is used as transmission data, and finally a MAC frame in which the transmission data is encapsulated as shown in FIG. 2 is generated and transmitted on the internal network. In this case, the MAC address of the processing apparatus of the connection partner is set as the destination MAC address in the MAC header of the MAC frame. Then, the line determination process (S211) is performed in the same manner as described above, the MAC frame is received by the processing apparatus of the connection partner, and the reception process (S206) is performed. In the reception process, the data part is acquired from the MAC frame, and since the acquired data part is interpreted and a new connection cannot be added, it is determined whether there is another client (processing device) inquiring in step S207. Is done. If it is determined in step S202 that a plurality of clients have been extracted and there are clients that have not been inquired, the process returns to step S203, and the process of steps S203 to S207 is repeated until there are no clients that have not been inquired. Is called. If it is determined in step S207 that there is no client that has not inquired, the processing proceeds to the processing after B shown in FIG.

  When the process proceeds to the process after B shown in FIG. 17, a data part indicating that a connection cannot be established is created in step S230, and a transmission process for transmitting the data part is performed in step S231. In the transmission process, the data part created in step S230 is used as transmission data, and finally a MAC frame in which the transmission data is encapsulated as shown in FIG. 2 is generated and transmitted on the internal network. In this case, the MAC address of the operating processing device is set as the destination MAC address in the MAC header of the MAC frame. Then, in the same manner as described above, the line determination process (S240) is performed and the processing device that is operating receives the MAC frame, and the reception process (S250) is performed. In the reception process, the data part is acquired from the MAC frame, and since the acquired data part is interpreted and the connection cannot be established, a display indicating that the connection cannot be established is displayed in step S251. The load distribution process is terminated and the connection establishment process is terminated.

  If it is determined in step S222 that the CPU usage rate is low in the target processing device and a new connection can be added, a data portion is branched to step S225 to indicate that a new connection can be added. A transmission process is performed to transmit the data part in step S226. In the transmission process, the data part created in step S225 is used as transmission data, and finally a MAC frame in which the transmission data is encapsulated is generated as shown in FIG. 2 and transmitted on the internal network. In this case, the MAC address of the processing apparatus of the connection partner is set as the destination MAC address in the MAC header of the MAC frame. Then, the line determination process (S212) is performed in the same manner as described above, the MAC frame is received by the processing apparatus at the connection partner, and the reception process (S208) is performed. In the reception process, the data part is acquired from the MAC frame, the acquired data part is interpreted and a new connection can be added, and the process proceeds to A and subsequent processes shown in FIG.

When the process proceeds to A and after shown in FIG. 17, a data part indicating that the connection partner is changed to the target client (processing device) is created in step S232, and the data part is transmitted in step S233. Processing is performed. In the transmission process, the data part created in step S232 is used as transmission data, and finally a MAC frame in which the transmission data is encapsulated as shown in FIG. 2 is generated and transmitted on the internal network. In this case, the MAC address of the operating processing device is set as the destination MAC address in the MAC header of the MAC frame. Then, in the same way as described above, the line determination process (S241) is performed and the processing device that is operating receives the MAC frame, and the reception process (S252) is performed. In the reception process, the data part is acquired from the MAC frame, and the acquired data part is interpreted to change the connection partner to the target client. Therefore, in step S253, the connection buffer is changed to change the connection partner to the target client. Rewrite. Then, the load distribution process is terminated and the connection establishment process is terminated. In connection establishment based on the connection setting to change the connection partner in the rewritten connection buffer to the target client, the connection establishment process is started from the next time on the operating processing device, and the connection setting is targeted for connection. The process established at the time is executed.
As described above, when it is determined that the load distribution is performed in the load distribution process, the connection establishment process is performed after step S102 when the load distribution process is ended, regardless of whether the load distribution can be performed or not. The process ends without performing the process.

Incidentally, the connection selection process described above can also be executed in the SV (server) 11. A flowchart of the connection selection process executed by the SV (server) 11 is shown in FIG. Note that control data communicated between the SV (server) 11 and the processing device as the base point is communicated using the IP address of the destination processing device and a predetermined port number for control data.
When the connection selection process is started in the SV (server) 11, the apparatus table is referred to in step S120, all the processing apparatuses on the internal network are displayed, and the selection of the processing apparatus as the connection base point is accepted. Here, when it is detected that the processing device as the connection base point has been selected, in step S121, the SV (server) 11 executes connection selection processing using the selected processing device as the base point. The connection contents of all the processing apparatuses on the internal network set by performing the selection process are stored in the SV (server) 11. Next, a data part including a connection content set by performing a connection selection process in step S122 and a connection establishment instruction for instructing to establish a connection of the connection content to the processing device as a connection base point is created. To do.

Next, transmission processing is performed in step S123. In the transmission process, the data part created in step S122 is used as transmission data, and finally a MAC frame in which the data part is encapsulated as shown in FIG. 2 is generated and transmitted on the internal network. In this case, the MAC address (physical device ID) of the processing device as the base point is set as the destination MAC address in the MAC header of the MAC frame. Since the MAC frame transmitted from the SV (server) 11 to the network is a star-type internal network, it is received by the hub, and a route determination process is performed (step S130). In the route determination process, the hub determines the transmission route by looking at the destination MAC address of the received MAC frame, and relays the MAC frame. As a result, the MAC frame transmitted from the SV (server) 11 is received by the processing device selected as the base point having the same destination MAC address, and the reception process is performed (step S140). In the reception process, an IP packet is extracted from the MAC frame, a TCP segment is extracted from the IP packet, and a data part is acquired from the TCP segment. Then, by interpreting the data part acquired in step S141, the connection contents instructed to establish connection are recorded in the connection buffer, and the connection selection process ends.
The connection establishment based on the connection information recorded in the connection buffer of the base processing device is a processing device that is operated by the base processing device when the connection establishment processing is started in the base processing device. It is established by executing the connection establishment process shown in FIG.

Next, FIG. 19 shows a flowchart of the voice change process executed when the tone color is changed in the sound source element. The voice change process is periodically started at predetermined intervals. The voice change process is a process capable of providing a requested voice file from the network when the requested voice file is not in the processing apparatus of the own device.
When the voice change process is activated, it is determined in step S300 whether a voice change request (program change) has been detected. Here, if an operation for changing the timbre is performed or a voice change request is detected from the network and a voice change request is detected, the process proceeds to step S301. If no voice change request is detected, the voice change process is continued. finish. In step S301, it is determined whether the requested voice file is in the voice memory. In this case, a plurality of voice files are recorded in the voice memory, and unique identification information is recorded for each voice file. The timbre data is recorded in the voice file, and the timbre data is timbre data in a format such as PCM, FM, or physical model that can synthesize the timbre. In step S301, it is determined whether or not the identification information in the voice memory includes the same identification information as the requested voice identification information. If it is determined that the requested voice file is in the voice memory, the process proceeds to step S302, where the requested voice file is extracted from the voice memory, and timbre data is extracted from the extracted voice file in step S303. . Then, the extracted timbre data is set as a sound source element in the processing apparatus operated in step S304, and the voice changing process is ended. For example, the setting is preparation so that PCM data can be generated when MIDI data is received.

  If it is determined in step S301 that the requested voice file is not in the voice memory, the process branches to step S305 to determine whether there is a processing device on the network that can provide the requested voice file. Is done. Here, for each logical device ID in the device table shown in FIG. 3, a processing device capable of providing a voice file is detected by referring to the “provide voice file” column. Alternatively, the type of sound source may be registered in the device table, and when searching for a processing device that can provide a voice file, the search may be performed including the type of sound source and extracted. If it is determined that there is a processing device that can provide the requested voice file on the network, the process proceeds to step S306 to extract the corresponding processing device and create a list of extracted processing devices. Next, in step S307, for one processing device in the list, in step S308, a data part including a voice file request, identification information (program change number), and a sound source type such as PCM, FM, physical model, etc. create. This data portion is sent to the processing device of the inquiry partner by the network processing in step S309. A flowchart of this network processing is shown in FIG.

  As shown in FIG. 20, in the network processing, the data part created in step S308 is used as transmission data, and finally a MAC frame in which the transmission data is encapsulated is generated as shown in FIG. The transmission process to be transmitted to is performed in step S320. In this case, the MAC address of the processing device of the inquiry partner is set as the destination MAC address in the MAC header of the MAC frame. Then, the line determination process (S330) is performed, the MAC frame is received by the processing apparatus of the inquiry partner, and the reception process (S340) is performed. In the reception process, the data part is acquired from the MAC frame, and the acquired data part is interpreted to determine whether or not the requested voice file exists in the processing apparatus of the own apparatus. If it is determined that there is a voice file with the same identification information and the same sound source type, the voice file is taken out from the voice memory in step S342, and the extracted voice file and the requested voice file are found. A data portion indicating this is created in step S343. If it is determined in step S341 that there is no requested voice file, a data portion indicating that there is no requested voice file is created in step S344. Then, the data part created in step S343 or the data part created in step S344 is used as transmission data, and finally a MAC frame in which the transmission data is encapsulated is generated as shown in FIG. The transmission process transmitted above is performed in step S345. In this case, the MAC address of the operating processing device is set as the destination MAC address in the MAC header of the MAC frame. Then, the MAC frame is received by the processing apparatus that is operating by performing the line determination process (S331), and the reception process (S321) is performed. In the reception process, the data part is acquired from the MAC frame, and the acquired data part is interpreted. The above is the network processing executed in step S309.

  When the network processing in step S309 ends, it is determined whether or not there is a voice file in the data portion interpreted in step S310. Here, it is indicated that there is a requested voice file in the data part, and when there is a requested voice file, the process branches to step S313 to extract the voice file, and the processes of steps S303 and S304 are performed. The timbre data is extracted from the voice file, and the timbre data is set as the sound source. If the requested voice file is not found in the data section, and if there is no requested voice file, the process proceeds to step S311 to determine whether there is a processing device that has not yet been inquired. . Here, if it is determined that there is a processing device that has not been inquired, the process returns to step S307, and the processing of steps S307 to S311 is performed again so that the requested voice file can be acquired. This process is executed in order for each of the processing devices extracted in step S306. If it is determined in step S311 that there is no processing apparatus that has not inquired, the process proceeds to step S312 to display a message indicating that there is no requested voice file on the display unit, and the voice changing process ends.

By the way, in the musical tone generating system according to the present invention, various settings performed on each processing device are sequentially recorded in a non-volatile default buffer. The latest setting before power off) is read and restored automatically. FIG. 21 shows a flowchart of the automatic setting process executed when the power is turned on.
When the processing device connected to the internal network is turned on and a processing device is newly connected (logged in), the network connection processing shown in FIG. 6 is executed as described above. When the network connection process is completed, the automatic setting process is subsequently started. When the automatic setting process is activated, one of the processing elements to be connected is read from the default buffer of the processing apparatus that has become the new client in step S350. Next, it is determined in step S351 whether or not the read processing element is on the network. Here, when it is determined that the processing element read by referring to the device table acquired from the SV (server) 11 in the network connection process is on the network, the process proceeds to step S352 and the processing element can be used. Create a data part to inquire about. Inquiries are made to all necessary inputs and outputs of the processing element.

  Then, the data part created in step S352 is set as transmission data, and a MAC frame in which the transmission data is finally encapsulated as shown in FIG. 2 is generated, and the transmission process is transmitted to the internal network in step S353. Done in In this case, the MAC address of the processing device in which the processing element to be connected is functioning is set as the destination MAC address in the MAC header of the MAC frame. Then, the line determination process (S370) is performed, and the MAC frame is received in the processing device in which the connection target processing element functions, and the reception process (S380) is performed in the connection target processing element. In the reception process, the data part is acquired from the MAC frame, and the acquired data part is interpreted as an inquiry as to whether the processing element can be used. Therefore, in step S381, it is determined whether the processing element can be used. Here, in the processing element inquired whether it can be used, it is determined whether it can be used for all of the inquiries on the input side and the output side. Here, referring to the recorded contents of the current buffer, the connection on the input side and the output side of the processing element that was inquired is detected, and if it is detected that it is not yet connected to another processing element, there was an inquiry It is determined that the processing element can be used, and the process proceeds to step S382. In step S382, a data portion indicating that the processing element for which the inquiry has been made can be used is created. If it is detected that the processing element is already connected to another processing element, it is determined that the processing element inquired in step S381 cannot be used, and the process branches to step S383. In step S383, a data part indicating that the inquired processing element cannot be used is created.

  Then, the data part created in step S382 or the data part created in step S383 is set as transmission data, and finally a MAC frame in which the transmission data is encapsulated is generated as shown in FIG. The transmission process to be transmitted to is performed in step S384. In this case, the MAC address of the processing device as the new client is set as the destination MAC address in the MAC header of the MAC frame. Then, the line determination process (S371) is performed, the MAC frame is received by the processing device of the new client, and the reception process (S354) is performed by the processing element to be connected. In the reception process, the data part is acquired from the MAC frame, and the acquired data part is interpreted. Next, it is determined whether or not the processing element inquired in step S355 can be used. If the received data part is a data part indicating that the data part can be used, it is determined that it can be used. Then, the process proceeds to step S357. In step S357, it is determined whether there is a processing element to be connected that has not been read from the default buffer.

  If it is determined in step S351 that the processing element read with reference to the device table is not on the network, the process branches to step S356 to display a display indicating that the default connection has not been made. The automatic setting process ends. In this case, if the processing element is not registered in the device table, a message “not registered” may be displayed. If the data part received in step S355 is a data part indicating that the data part cannot be used, it is determined that the data part cannot be used and the process branches to step S356 and the default connection is not established. Is displayed on the display unit, and the automatic setting process ends. In this case, if the processing element is connected to another, a message “used elsewhere” may be displayed.

In step S357, if it is determined that there remains a connection target processing element that has not been read from the default buffer, the process returns to step S350, and the above-described processing in steps S350 to S357 determines that the connection target processing element that has not been read. The process is repeated until it is determined in step S357 that there is no more. If it is determined in step S357 that there are no connection target processing elements that have not been read, the process proceeds to step S358 to write connection information of processing elements that can be used to the connection buffer, and the process proceeds to step S359. In step S359, the automatic flag is set to “1” and the automatic setting process ends. The automatic flag “1” is a flag indicating that the default buffer is not updated as described above, but is also a flag indicating that the connection recorded in the default buffer is restored as described above. In addition, in the automatic setting process, if even one default buffer cannot be connected, the default buffer connection information is not written to the connection buffer so that all connections of the default buffer are not performed. In this case, the automatic flag maintains the state of “0”, and the automatic flag “0” is also a flag indicating that the connection recorded in the default buffer is not performed.
Note that the user may be able to select whether or not to make a connection based on the default buffer when connecting to the network.

FIG. 22 shows a flowchart of flag processing that is subsequently executed when the above-described periodically started connection establishment processing shown in FIG. 14 is executed and terminated.
When the flag process is activated, it is determined in step S390 whether or not the automatic flag is “0”. Here, when the connection of the default buffer is not updated or when the connection selection process is performed, it is determined that the automatic flag is “0”, and the process proceeds to step S391 and the connection information is recorded in the current buffer. It is determined whether or not. If the default buffer connection has not been restored, and there is no connection set manually or requested from outside, connection information is not recorded in the current buffer. Is determined to be empty, and the flag processing ends as it is. If there is a manually set connection or a connection set by request from the outside, and connection information is recorded in the current buffer, the connection information recorded in the current buffer is changed to the default buffer in step S392. And flag processing ends. As a result, the default buffer is updated with the connection information of the current buffer in which the connection information of the connection set manually and the connection requested and set from the outside is reflected. If the connection of the default buffer is only restored and the connection set manually or not requested from the outside is set, the automatic flag is determined to be “1” in step S390, and the default buffer is restored. The flag process ends without updating the buffer.
As a result, when all of the connection target processing elements are available when the new client is connected to the internal network, the connection state is restored to the complete connection state before the previous power-off. In addition, at least a part of the processing elements to be connected cannot be used, and even if you log off when the connection state before the previous power-off is not restored, the incomplete connection state is not recorded in the default buffer. Therefore, it is possible to prevent an incomplete connection state from being restored at the next logon.

  6, the network disconnection process shown in FIG. 7, the connection selection process shown in FIGS. 10 to 12, the connection establishment process and the load distribution process shown in FIGS. 14 to 16, and the SV ( The connection selection process executed in the server 11, the voice change process shown in FIGS. 19 and 20, the automatic setting process shown in FIG. 21, and the flag process shown in FIG. Can be executed using a browser. The browser can perform file transfer using HTTP (HyperText Transfer Protocol), and can decode and display hypertext described in HTML (Hyper Text Markup Language). In this case, a setting screen and a selection screen necessary for the browser are displayed, and the user can perform setting and selection on the screen. Communication of control data can be performed using a request method such as “GET” that can make a file request prepared in HTTP, “POST” that sends arbitrary data, and “PUT” that can update a file. . Note that the port number used in HTTP is generally 80, but is not limited thereto.

  Next, each processing element will be described. First, a functional block diagram of the sound source element is shown in FIG. As shown in the figure, the sound source element TG receives the MIDI data from the reception port and records the received MIDI data to be processed from the reception buffer 100 in accordance with the timing of the built-in MIDI clock of the sound source element TG. The reading unit 101 that sequentially reads out the MIDI data to the tone synthesizing unit 102, the pitch is determined by the note data of the supplied MIDI data, the tone is determined by the program change data, and the control change A sound synthesis unit 102 that determines a control amount such as a volume and an effect amount from data and generates a musical tone of PCM data with the determined information, and a transmission buffer that records the PCM data generated by the musical tone synthesis unit 102 in the order of generation 103. The reception buffer 100 receives entity data (MIDI data) from the reception port of the sound source element, and the transmission buffer 103 transmits entity data (PCM data) from the transmission port of the sound source element. The port number of the reception port is the logical device ID of the corresponding sound source element recorded in the device table shown in FIG. 3, and a random port number is assigned to the transmission port at the time of transmission. It is good also as a number. Further, the PCM data transmitted from the transmission buffer 103 may be compressed and transmitted as MP3 data.

Next, a functional block diagram of the keyboard elements is shown in FIG. As shown in the figure, the keyboard element KB includes a hardware operator 111, an operation detection unit 112 that detects the operation of the operator 111, and generates timing data of generated MIDI data based on a built-in MIDI clock. The transmission buffer 113 is configured to record MIDI data and timing data from the operation detection unit 112 in pairs in the order of occurrence. The transmission buffer 113 transmits entity data which is MIDI data from the transmission port of the keyboard element. The transmission port is assigned a random port number when transmitting, but may be a fixed port number.
Next, a functional block diagram of the speaker element is shown in FIG. As shown in the figure, the speaker element SP includes a reception buffer 121 that records PCM data received from the reception port in the order of processing, and extracts the PCM data from the reception buffer 121 sample by sample in accordance with the timing of the sampling frequency fs. An output provided with a reading unit 122 to be supplied to, a DA conversion unit 123 that converts the PCM data supplied from the reading unit 122 into an analog audio signal, and a speaker that amplifies and emits the audio signal from the DA conversion unit 123 Part 124. The reception buffer 121 receives entity data (PCM data) from the reception port of the speaker element. The port number of the reception port is the logical device ID of the corresponding speaker element recorded in the device table shown in FIG.

  Next, a functional block diagram of the DSP unit is shown in FIG. The DSP unit DU is a processing device and is configured to switch functioning processing elements. The DSP unit DU includes a processing device storage unit 133 in which a microprogram and parameters for each processing element executed by the DSP for realizing the processing element are recorded, and a process to be set in the switching unit 131 by detecting a switching instruction. Switching detector 132 for instructing switching including element information, and switching for reading the processing element microprogram and parameters instructed by the switching instruction from the processing device storage unit 133 and setting them in the signal processing unit 134 having a plurality of DSPs Section 131 and a signal processing section 134 that performs signal processing based on the set microprogram and parameters. When the signal processing unit 134 performs signal processing, the DSP unit DU functions as a processing element corresponding to the microprogram. That is, the DSP unit DU can function as any of the processing elements of the functional blocks shown in FIGS. When the processing element is switched, the connection information is deleted from the current buffer so as to disconnect the connection of the processing element before the change.

FIG. 27 shows a flowchart of notification processing for notifying that the processing element has been switched when the processing element is switched in the DSP unit DU.
When a switching instruction for switching processing elements is detected in the DSP unit DU, a notification process is started (step S150). Next, the microprogram and parameter instructed to switch in step S151 are set to cause the processing element to function. Further, in step S152, a data part including own device information and a change request is created. In this case, the own device information includes logical device ID, IP address (IP address is assigned by the DHCP server when logging in to the internal network), physical device ID, device name, and processing element set in the signal processing unit 134. The change request is a request to rewrite the device table data in the SV (server) 11 with the own device information attached thereto. Next, transmission processing is performed in step S153. In the transmission process, the data part created in step S152 is used as transmission data, and finally a MAC frame is generated as shown in FIG. 2 and transmitted on the internal network. In the MAC header of the MAC frame, the MAC address (physical device ID) of the SV (server) 11 is set as the destination MAC address.

  Since the MAC frame transmitted from the DSP unit DU is a star-type internal network, it is received by the hub, and a route determination process is performed (step S161). In the route determination process, the hub determines the transmission route by looking at the destination MAC address of the received MAC frame, and relays the MAC frame. As a result, the MAC frame transmitted from the DSP unit DU is received by the SV (server) 11 having the same destination MAC address, and reception processing is performed (step S170). In the reception process, an IP packet is extracted from the MAC frame, a TCP segment is extracted from the IP packet, and a data part is acquired from the TCP segment. Then, it is determined that the change request process is performed because there is a change request by interpreting the acquired data part. Next, in step S171, the device table is rewritten with the own unit information of the DSP unit DU in the data portion, and in step S172, the changed device table and the data portion including the change request are created. This data part is transmitted on the internal network by performing transmission processing in step S173. This transmission process is the same as the transmission process in step S153 described above, but the broadcast address (FF-FF-FF-FF-FF-FF) of all “1” is set as the destination MAC address, A broadcast address is also set as the destination IP address. In this case, when the network address of the internal network is “192.168.111.0” as in the device table shown in FIG. 3, the broadcast address of the IP address is “192.168.111.255”. Is done.

  The MAC frame broadcast from the SV (server) 11 is received by the hub and route determination processing is performed (step S161). In this route determination process, the same route determination process as in step S160 is performed, but since the MAC frame is a broadcast address, the MAC frame is relayed to all the processing devices. The DSP unit DU performs reception processing for receiving the MAC frame similar to that in step S170 because the broadcast address is set when the broadcast MAC frame arrives (step S154). Next, the device table is updated by storing the device table information extracted from the MAC frame received in step S155 in the internal storage means, and the network connection process in the DSP unit is completed. In addition, since the broadcast address is set when the broadcast MAC frame arrives at the other client, a reception process for receiving the MAC frame similar to step S170 is performed (step S180). Next, the device table stored with the device table information extracted from the MAC frame received in step S181 is updated, and the network connection process in the other client ends.

  Next, a functional block diagram of the mixer element is shown in FIG. As shown in the figure, the mixer element MX receives the PCM data from the reception port and records the PCM data from the reception buffer 141 in accordance with the timing of the sampling frequency fs. A reading unit 142 that extracts one sample at a time and supplies it to the mixing unit 143, and a mixing unit that mixes (signal processes) the PCM data input from the reception buffer 141 in accordance with the settings of various parameters input from the operation unit 144. 143, an operator 144 for setting various parameters, and a transmission buffer 145 prepared for each transmission channel for recording the PCM data output from the mixing unit 143 in the order of generation. The reception buffer 141 receives entity data (PCM data) from the reception port of the mixer element, and the transmission buffer 145 transmits entity data (PCM data) from the transmission port of the mixer element. The port number of the reception port is the logical device ID of the corresponding sound source element recorded in the device table shown in FIG. 3, and a random port number is assigned to the transmission port when transmitting, but a fixed port It is good also as a number.

Next, a functional block diagram of the content recorder element is shown in FIG. Data communicated in the content recorder element CR is not actual data but control data. When communicating with other processing elements, communication is performed using a control data communication port instead of a port used for actual data communication. Do. In this case, a screen required for acquiring the content may be displayed on a processing element (processing device) that requests the content so that the user can select the content on the screen. The communication of control data can be performed using a “GET” request method for making a file request prepared in HTTP.
The processing element (processing device) that requests content from the content recorder element CR transmits the content request and the identification information of the content data in the data portion of the control data to be transmitted. Content is a file used by a specific processing element, such as a song, style, or voice. The content recorder element CR detects (receives) a content request from the reception port, supplies a request for content request and content data identification information to the reading unit 151, and stores content data corresponding to the identification information as content. The content read out from the unit 153 to the content transmission unit 154, the content storage unit 153 storing a plurality of content data together with the identification information, and the processing element (processing device) that transmitted the content request The content transmission unit 154 transmits data from a transmission port. Note that the port number of the reception port is the logical device ID of the corresponding content recorder element CR recorded in the device table shown in FIG. 3, and the transmission port is assigned a random port number when transmitting, but is fixed. The port number may be used.

Next, FIG. 30 shows a functional block diagram of the automatic accompaniment element. The automatic accompaniment element AA edits the instructed accompaniment data based on the performance data in response to a request for accompaniment data from another processing element, and sends the accompaniment data to the processing element. The automatic accompaniment request data is communicated using a control data communication port, not a port used for actual data communication. In this case, a screen required for automatic accompaniment is displayed on a processing device in which a processing element for requesting accompaniment data is functioning, and the user selects automatic accompaniment or a destination of accompaniment data on the screen. You may do it. The accompaniment data request and acquisition communication may be performed by HTTP.
The automatic accompaniment element AA receives MIDI data (performance data) from the receiving port 1 and records it in the order of processing, and MIDI data (performance data) to be processed in accordance with the timing of the built-in MIDI clock of the automatic accompaniment element AA. Data) from the reception buffer 161, and a chord detection unit 163 that detects chords in the performance data using note-on and note-off events of the MIDI data (performance data) extracted by the reading unit 162. It has.

  Further, the processing element (processing device) that requests automatic accompaniment from the automatic accompaniment element AA transmits the accompaniment data request and the accompaniment data identification information in the data portion of the control data. When the automatic accompaniment element AA detects (receives) an accompaniment data request from the receiving port 2, the request detection unit 165 passes the received accompaniment data request and automatic accompaniment identification information to the reading unit 164, and the identification information Is read from the accompaniment data storage unit 166 and passed to the accompaniment data buffer 167, the accompaniment data storage unit 166 stores a plurality of accompaniment data together with identification information, and the accompaniment data storage unit 166 An accompaniment data buffer 167 is provided for recording the read accompaniment data. The accompaniment data is a file in which MIDI data for reproducing accompaniment is recorded in the order of processing.

  The chord detection unit 163 passes the detected chord data and the supplied MIDI data (performance data) to the automatic accompaniment unit 168, and the accompaniment data buffer 167 passes the MIDI data (accompaniment data) to the automatic accompaniment unit 168. The automatic accompaniment unit 168 sequentially extracts MIDI data (accompaniment data) to be processed from the accompaniment data buffer 167 in accordance with the timing of the built-in MIDI clock of the automatic accompaniment element AA. If the extracted MIDI data (accompaniment data) is note-on, the note number is changed with the current chord data passed from the chord detection unit 163, and the changed MIDI data (accompaniment data) and the chord detection are changed. The MIDI data (performance data) received from the unit 163 is sent to the transmission buffer 169 together with timing data indicating the processing timing of each data. The transmission buffer 169 records the MIDI data and timing data sent from the automatic accompaniment unit 168 in the order of processing, and transmits from the transmission port to the processing element specified by the destination IP address and port number included in the accompaniment data request. is doing. The reception port 1 is a reception port for entity data (MIDI data), and the port number of the reception port 1 is the logical device ID of the corresponding automatic accompaniment element AA recorded in the device table shown in FIG. The port number of the reception port 2 is a port number assigned in advance for control data (generally, the number is not limited to 80 in the case of HTTP, but is not limited thereto), and the transmission port is a transmission of entity data (MIDI data). A random port number is assigned when transmitting a port, but it may be a fixed port number.

Next, FIG. 31 shows a functional block diagram of the MIDI recorder element. The MIDI recorder element MR can record the received MIDI data, and transmits the recorded MIDI data to the destination processing element (processing device) in response to the read request.
The MIDI recorder element MR receives the MIDI data from the receiving port 1 and records it in the order of processing. The MIDI recorder element MR takes out the MIDI data from the receiving buffer 171, and sets a set of MIDI event data and timing data representing the processing timing. A writing unit 172 for writing to the MIDI recording unit 173 in the order of processing and a MIDI recording unit 173 for recording performance data composed of MIDI data by the writing unit 172 as a MIDI file are provided. Further, the processing element (processing device) that requests MIDI data (performance data) from the MIDI recorder element MR transmits the read request and the identification information of the MIDI file in the data portion of the control data. In this case, a screen required for the read request is displayed on the processing device in which the processing element that requests read is displayed, and the user may select a MIDI file or a destination of MIDI data on the screen. Alternatively, communication for reading request and acquisition of MIDI data may be performed by HTTP.

  When the MIDI recorder element MR detects (receives) a read request from the reception port 2, the MIDI recorder element MR corresponds to the request detection unit 176 that passes the received read request and the identification information of the MIDI file to the reading unit 174 and the identification information. In accordance with the timing of the built-in MIDI clock of the MIDI recorder element MR from the MIDI file to be read, the reading unit 174 reads out the MIDI data to be processed from the MIDI recording unit 173 and passes it to the transmission buffer 175, and the MIDI sent from the reading unit 174 A transmission buffer 175 for recording data and timing data in the order of processing is provided. The transmission buffer 175 transmits the MIDI data and timing data recorded in the buffer from the transmission port to the processing element specified by the destination IP address and port number included in the read request. The reception port 1 is a reception port for entity data (MIDI data), and the port number of the reception port 1 is the logical device ID of the corresponding MIDI recorder element MR recorded in the device table shown in FIG. The port number of the reception port 2 is a port number assigned in advance for control data (generally, the number is not limited to 80 in the case of HTTP, but is not limited thereto), and the transmission port is a transmission of entity data (MIDI data). A random port number is assigned when transmitting a port, but it may be a fixed port number.

Next, a functional block diagram of the editor element is shown in FIG. The editor element ED edits the received MIDI data in response to the setting request and transmits it to the destination processing element (processing device).
The editor element ED receives the MIDI data from the reception port 1 and records it in the processing order, and reads out the MIDI data to be processed in accordance with the timing of the built-in MIDI clock of the editor element ED from the reception buffer 181 and edits the data. A reading unit 182 to be transferred to H.183. Also, the processing element (processing device) that requests the editor element ED to set the edit transmits the setting request and edit information in the data portion of the control data. In this case, a screen required for the setting request may be displayed on the processing device in which the processing element that requests the setting is functioning, and the content to be edited on the screen may be set by the user. Communication may be performed by HTTP. The edit information is information representing the edit contents.

    Then, when the editor element ED detects (receives) a setting request from the receiving port 2, the editor element ED sends the received setting request and editing information to the editing unit 183 and the MIDI passed from the reading unit 182. The data is edited based on the editing information from the request detection unit 185, the editing unit 183 that passes the edited MIDI data to the transmission buffer 184, and the MIDI data and timing data sent from the editing unit 183 are recorded in the order of processing. A transmission buffer 184 is provided. In the case of an automatic music piece, the edit unit 183 creates MIDI data representing a piece of music from the read MIDI data (phrase) based on the edit information, and sends the created MIDI data to the transmission buffer 184. In the case of automatic arrangement, the read MIDI data (melody) is arranged based on the edit information to create MIDI data representing the orchestra music, and the created MIDI data is transferred to the transmission buffer 184. The transmission buffer 184 transmits the MIDI data and timing data recorded in the buffer from the transmission port to the processing element specified by the destination IP address and port number included in the setting request. The reception port 1 is a reception port for entity data (MIDI data), and the port number of the reception port 1 is the logical device ID of the corresponding editor element ED recorded in the device table shown in FIG. The port number of port 2 is a port number assigned in advance for control data (generally, it is 80, but not limited to this in the case of HTTP), and the transmission port is a transmission port of entity data (MIDI data) A random port number is assigned when transmitting, but it may be a fixed port number.

Next, FIG. 33 shows a functional block diagram of the effector element. The effector element EF applies an effect corresponding to the setting request to the received PCM data and transmits it to the destination processing element (processing device).
The effector element EF receives PCM data from the reception port 1 and records the data in the order of processing (not shown), but includes a reception buffer 191 provided for each reception channel (input channel) and a timing of the sampling frequency fs from the reception buffer 191. In addition, a reading unit 192 for taking out PCM data sample by sample and sending it to the effect unit 193 is provided. Further, the processing element (processing device) that requests the effector element EF to set the effect transmits the setting request and the effect information in the data portion of the control data. In this case, the processing device in which the processing element for which setting is requested functions may display a screen necessary for the setting request, and the user may set the effect content on the screen, or communication of the setting request. May be performed by HTTP. The effect information is information representing the setting contents of the effect.

    When the effector element EF detects (receives) a setting request from the receiving port 2, the effector element EF is read from the request detecting unit 195 that passes the received setting request and effect information to the effect unit 193 and the reading unit 192. An illustration of creating new PCM data by applying an effect to the PCM data, passing the created PCM data to the transmission buffer 194, and recording the PCM data and timing data sent from the effect unit 193 in the order of processing. Although not provided, a transmission buffer 194 is provided for each transmission channel. Effects in the effect unit 193 are set (determined) based on the effect information, and effects such as reverb and chorus are applied to the PCM data. The transmission buffer 194 transmits the PCM data recorded in the buffer from the transmission port to the processing element specified by the destination IP address and port number included in the setting request. The reception port 1 is a reception port for entity data (PCM data), and the port number of the reception port 1 is the logical device ID of the corresponding effector element EF recorded in the device table shown in FIG. The port number of port 2 is a port number assigned in advance for control data (generally 80, but not limited to this in the case of HTTP), and the transmission port is a transmission port of entity data (PCM data) A random port number is assigned when transmitting, but it may be a fixed port number.

Next, a functional block diagram of the audio recorder element is shown in FIG. The audio recorder element AR can record the received PCM data, and transmits the PCM data recorded in response to the read request to a destination processing element (processing device).
The audio recorder element AR includes a reception buffer 201 that receives PCM data from the reception port 1 and records the data in the order of processing, a writing unit 202 that extracts the PCM data from the reception buffer 201 and writes the PCM data in the PCM recording unit 203, and the writing unit 202. Is provided with a PCM recording unit 203 for recording PCM data as a PCM file. Further, the processing element (processing device) that requests PCM data from the audio recorder element AR transmits the read request and identification information of the PCM file in the data portion of the control data. In this case, a screen necessary for the read request is displayed on the processing device in which the processing element that requests read is displayed, and the user may select a PCM file or a PCM data destination on the screen. Alternatively, communication for reading request and acquisition of PCM data may be performed by HTTP.

  When the audio recorder element AR detects (receives) a read request from the reception port 2, the request detector 206 passes the received read request and the PCM file identification information to the reading unit 204, and corresponds to the identification information. A reading unit 204 that reads PCM data from the PCM recording unit 203 and passes it to the transmission buffer 205 in accordance with the timing of the sampling frequency fs from the PCM file to be transmitted, and a transmission buffer 205 that records the PCM data sent from the reading unit 204 in the order of processing. And. The transmission buffer 205 transmits the PCM data recorded in the buffer from the transmission port to the processing element specified by the destination IP address and port number included in the read request. The reception port 1 is a reception port for entity data (PCM data), and the port number of the reception port 1 is the logical device ID of the corresponding audio recorder element AR recorded in the device table shown in FIG. The port number of the reception port 2 is a port number assigned in advance for control data (generally, the number is not limited to 80 in the case of HTTP, but is not limited thereto), and the transmission port is transmission of entity data (PCM data). A random port number is assigned when transmitting a port, but it may be a fixed port number.

Next, FIG. 35 shows a flowchart of communication processing executed when entity data is communicated.
When communicating entity data, communication processing is started in the processing device that transmits entity data, and data is extracted from the transmission buffer in step S190 to create a data portion. Next, transmission processing is performed in step S191. In the transmission process, the data part created in step S190 is used as transmission data, and finally a MAC frame in which the transmission data is encapsulated is generated as shown in FIG. 2 and transmitted on the internal network. In the MAC header of the MAC frame, the MAC address (physical device ID) of the destination processing device that receives the entity data is set as the destination MAC address.
The transmitted MAC frame is received by the hub because it is a star-type internal network, and a route determination process is performed (step S200). In the route determination process, the hub determines the transmission route by looking at the destination MAC address of the received MAC frame, and relays the MAC frame. Accordingly, the MAC frame transmitted from the transmitting processing device is received by the receiving processing device having the same destination MAC address, and the receiving process is performed (step S210). In the reception process, an IP packet is extracted from the MAC frame, a TCP segment is extracted from the IP packet, and a data part is acquired from the TCP segment. Next, the data part acquired in step S211 is recorded in the reception buffer. For communication, a port recorded in a current buffer established for transmitting actual data is used.

In the above description, the internal network is an Ethernet LAN, but the present invention is not limited to this and may be another network medium. Although TCP is used as the communication protocol, the present invention is not limited to this, and in the case of emphasizing real time, UDP (User Datagram Protocol) with low reliability but high transfer speed may be used, or TCP / IP Instead of this, IPX / SPX (Internetwork Packet Exchange / Sequenced Packet Exchange) may be used.
In addition, when editing information of editor elements and effect information of effector elements can be set and sent by other processing elements, editor elements and effect elements in other rooms can be operated from the room with speaker elements. Since it can be operated as if there is an editor element or an effect element in the room, the operability can be improved.
Furthermore, the connection release between a plurality of processing elements in one processing apparatus is not limited to when the network is connected, and can be released at an arbitrary timing after the network connection. In this case, the connection is not canceled at the time of network connection, and the process for confirming the connection release instruction is periodically started after the network connection, and the processing element in the processing device is detected when the connection release instruction is detected. The connection between them may be canceled. In addition, a connection release instruction may be provided by providing a special switch for instructing the connection release. Such a connection release instruction is not limited to the processing apparatus itself, but can be issued from another processing apparatus on the network.

It is a block diagram which shows the structure of the musical tone generation system of the Example of this invention. It is a figure which shows the outline | summary of the production | generation process of the MAC frame transmitted on a network in the musical tone generation system concerning this invention. It is an apparatus table which is a correspondence table of identification information for every processing element in the internal network of the musical tone generating system according to the present invention. 5 is a connection table on the input side and output side for each processing element capable of communicating entity data in the processing elements on the internal network of the musical sound generating system according to the present invention. It is a figure which shows the one aspect | mode of the process of a network connection process in the musical tone generation system concerning this invention. 5 is a flowchart of network connection processing executed when a processing device is newly connected (logged in) to an internal network in the musical sound generating system according to the present invention. 6 is a flowchart of network disconnection processing executed when a processing device connected to the internal network is disconnected (logged off) in the musical sound generating system according to the present invention. It is a figure which shows the one aspect | mode of the process of a network cutting | disconnection process in the musical tone generation system concerning this invention. It is a figure which shows the example of a structure of the internal network in the musical tone generation system concerning this invention. It is a figure which shows the example of the setting screen displayed at the time of the connection process which connects between process elements in the musical sound generation system concerning this invention. In the musical tone generating system according to the present invention, it is a diagram showing another example of a setting screen displayed at the time of connection processing for connecting between processing elements. 6 is a flowchart of a connection selection process executed when setting a connection between processing elements in the musical sound generating system according to the present invention. FIG. 6 is a diagram showing an example of connection information recorded in a connection buffer when connection selection processing is performed and logical connection of processing elements is set in the musical sound generating system according to the present invention. 6 is a flowchart of a connection establishment process executed subsequent to the connection selection process in the musical sound generating system according to the present invention. It is a figure which shows the example of matching with the connection information recorded on a current buffer in the musical sound generation system concerning this invention. It is a flowchart of the load distribution process performed in a connection establishment process in the tone generation system concerning this invention. In the musical sound generating system according to the present invention, it is a continuation of the flowchart of the load distribution process executed in the connection establishment process. 5 is a flowchart of connection selection processing executed by an SV (server) in the musical sound generation system according to the present invention. 6 is a flowchart of a voice change process executed when a tone color is changed in a sound source element in the tone generation system according to the present invention. It is a flowchart of the network process performed by the voice change process in the musical tone generating system according to the present invention. 6 is a flowchart of automatic setting processing executed when the processing apparatus is powered on in the musical sound generating system according to the present invention. 4 is a flowchart of flag processing that is periodically executed in the tone generation system according to the present invention. It is a functional block diagram of the sound source element in the musical tone generating system according to the present invention. It is a functional block diagram of the keyboard element in the musical tone generating system according to the present invention. It is a functional block diagram of the speaker element in the musical tone generating system according to the present invention. It is a functional block diagram of a DSP unit in the tone generation system according to the present invention. In the musical tone generating system according to the present invention, when a processing element is switched in a DSP unit, it is a flowchart of a notification process for notifying that switching has been performed. It is a functional block diagram of the mixer element in the musical tone generating system according to the present invention. It is a functional block diagram of the content recorder element in the musical tone generating system according to the present invention. It is a functional block diagram of the automatic accompaniment element in the musical tone generation system concerning this invention. It is a functional block diagram of a MIDI recorder element in the musical tone generating system according to the present invention. It is a functional block diagram of the editor element in the musical tone generating system according to the present invention. It is a functional block diagram of the effector element in the tone generation system concerning the present invention. It is a functional block diagram of the audio recorder element in the musical tone generating system according to the present invention. It is a flowchart of the communication process performed when communicating the substantial data in the musical tone generating system concerning this invention.

Explanation of symbols

1 Internet, 2 router, 3 router, 4 router, 10 hub, 11 SV (server), 12 TG1 (sound source), 13 TG2 (sound source), 14 KB (keyboard), 15 SP1 (speaker), 20 hub, 21 SP2 (Speaker), 22 DU (DSP unit), 23 MX (mixer), 24 CR (content recorder), 30 hub, 31 AA (automatic accompaniment), 32 MR (MIDI recorder), 33 ED (editor), 34 EF ( Effector), 35 AR (audio recorder), 36 SY (sound source, keyboard) 40 hub, 41 MC (microphone), 42 CD (CD player), 100 reception buffer, 101 reading unit, 102 musical sound synthesis unit, 103 transmission buffer, 111 operation unit, 112 operation detection unit, 113 transmission buffer, 121 Signal buffer, 122 reading unit, 123 DA conversion unit, 124 output unit, 131 switching unit, 132 switching detection unit, 133 processing device storage unit, 134 signal processing unit, 141 reception buffer, 142 reading unit, 143 mixing unit, 144 operation Child, 145 transmission buffer, 151 reading unit, 152 request detection unit, 153 content storage unit, 154 content transmission unit, 161 reception buffer, 162 reading unit, 163 chord detection unit, 164 reading unit, 165 request detection unit, 166 accompaniment data Storage unit, 167 Accompaniment data buffer, 168 Automatic accompaniment unit, 169 Transmission buffer, 171 Reception buffer, 172 Writing unit, 173 Recording unit, 174 Reading unit, 175 Transmission buffer, 176 Request detecting unit, 181 Reception buffer, 182 Reading unit 183 Edit , 184 transmission buffer, 185 request detection unit, 191 reception buffer, 192 reading unit, 193 effect unit, 194 transmission buffer, 195 request detection unit, 201 reception buffer, 202 writing unit, 203 recording unit, 204 reading unit, 205 transmission Buffer, 206 Request detector

Claims (1)

The processing device in a musical sound generation system configured by connecting a plurality of processing devices each functioning as a device related to musical sound generation via a network,
Voice storage means for storing a plurality of voices;
Table storage means for storing a device table having information indicating whether or not to provide a voice for each of the processing devices in the musical sound generation system;
An accepting means for accepting a request to change to a new voice;
Determination means for determining whether the new voice received by the reception means is stored in the voice storage means;
A reading means for reading out the new voice from the voice storage means when it is determined that the information is stored in the determination means;
Detecting means for detecting a processing device capable of providing the new voice with reference to the device table when it is determined that the information is not stored in the determining device;
Request means for requesting the new voice to the processing device detected by the detection means;
Receiving means for receiving the new voice transmitted by the processing device detected by the detecting means in response to a request by the requesting means;
Setting means for setting the new voice read by the reading means or received by the receiving means;
Processor in tone generation system comprising: a.

Images