JP4096734B2 - Music activity support system and program - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a technique for supporting music activities performed by musical instrument players using a communication network.
[0002]
[Prior art]
An ensemble performed by multiple musical instrument players is one of the most enjoyable for the performers. In the ensemble, you can check not only your own performance skills, but also your performance skills and compatibility. For this reason, it is also performed for the purpose of searching for suitable members of members who form a band.
[0003]
[Patent Document 1]
JP 2002-278871 A
[Patent Document 2]
JP 2002-297136 A
[Patent Document 3]
JP 2000-317144 A
[0004]
[Problems to be solved by the invention]
Even if the ensemble members are decided, the opportunity to gather together and perform at the same place is limited due to time and geographical circumstances. For this reason, even if it is going to leave the result of an ensemble, the adjustment itself between members in performing the ensemble itself is often difficult.
[0005]
The result of the concert can be recorded by recording the performance performed by each member and putting the performance records together. However, in order to do so, each member must have equipment that can record the performance or rent that equipment. This is a major limitation. On the other hand, since each member records sequentially, it takes time and effort. For this reason, there has been a need for support for music activities that can easily and easily leave ensemble results.
[0006]
An object of the present invention is to provide a technique for supporting musical activities of musical instrument players so that the result of an ensemble can be easily and easily left.
[0007]
[Means for Solving the Problems]
The music activity support system of the present invention Assuming that music activities are supported for users of terminal devices connected via a communication network, the following means are provided.
[0008]
That is, a system that supports music activities for users of a plurality of terminal devices connected via a communication network and capable of transmitting event data corresponding to performance operations in real time, Member database means in which information of users of the plurality of terminal devices is registered; Request data receiving means for receiving request data including music and date and time transmitted from any of the terminal devices, and the received request data, Refer to the member database means and transmit to the terminal device of the other member that forms the band Request data transmission means, date / time determination means for determining whether the date / time included in the received request data has arrived, and when the date / time determination means determines that the date / time has arrived, The members of the band Access determining means for determining whether or not all of the terminal devices are accessing, and the access determining means The members of the band If it is determined that all terminal devices have accessed, the requested music Extract the tempo from the music data corresponding to the Above The members of the band Send to all terminal devices Pre-sound Signal transmission means and this Pre-sound After transmitting the notification signal by the signal transmission means, The members of the band Event data receiving means for receiving event data transmitted in real time from all terminal devices, and the event data receiving means received by the event data receiving means The members of the band Data storage means for storing event data from all the terminal devices in a predetermined storage means in real time.
[0009]
Further, the access discriminating unit is configured to perform the access within a predetermined time from the date and time. The members of the band If it is determined that all of the terminal devices are not accessed, For the terminal device It is desirable to provide a screen sending means for sending a screen indicating that all of them wait until they are all ready, and for sending a warning screen indicating that all are not ready after the predetermined time has elapsed.
[0010]
The music activity support system further includes a request database for storing the request data received by the request data receiving means and an area for each terminal device, and each time request data is stored in the request database. The above Of other members of the band A request reception database in which the request data is stored in an area corresponding to the terminal device, and the request data transmission unit converts the received request data into the request reception database based on the stored contents of the request reception database. Of other members of the band It is desirable to transmit the request data to the terminal device.
Further, the music activity support system further receives the event data from the one terminal device in response to the event data receiving means receiving the event data from the one terminal device. Members of the band It is desirable to further include event data transmission means for transmitting to the terminal device in real time.
[0011]
The program of the present invention is connected to a computer used in a system for supporting music activity for users of a plurality of terminal devices connected via a communication network and capable of transmitting event data corresponding to performance operations in real time. A request data reception function for receiving request data including music and date and time transmitted from any of the terminal devices, and the received request data, Refer to member database means in which user information of the plurality of terminal devices is registered, and transmit to other member terminal devices that form a band A request data transmission function, a date and time determination function for determining whether or not a date and time included in the received request data has arrived, and when it is determined that the date and time has arrived, The members of the band An access discriminating function for discriminating whether or not all of the terminal devices are accessing; The members of the band If it is determined that all terminal devices have accessed, the requested music The tempo is extracted from the music data corresponding to the tempo, and the pre-sound signal that matches the tempo is extracted from the members of the band Send to all terminal devices Pre-sound Signal transmission function and this Pre-sound After sending the signal, The members of the band An event data receiving function for receiving event data transmitted in real time from all terminal devices; The members of the band A data storage function for storing event data from all the terminal devices in a predetermined storage means in real time is realized.
[0012]
In the present invention, when a user of a terminal device performs a performance of the same song as a member constituting a band in parallel, event data indicating the contents of performance operations performed by the plurality of users via a communication network is provided. Receiving from each terminal device and storing them in association with each other. Thereby, even if each user does not gather in the same place, the result of the band performance (ensemble) performed gathering in the same place can be saved at once.
[0013]
In the case of notifying the timing at which performance is to be started via the terminal device used by each user who performs the same song in parallel, it is possible to cause each user to start performance at the same time. When event data received from other terminal devices is sent in real time to a terminal device used by each user who performs the same song in parallel, each user plays the performance of the other user while playing his / her own performance. You can listen to the performance.
[0014]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a diagram showing a configuration of a network system having a music activity support system according to the present embodiment.
[0015]
The music activity support system according to the present embodiment is constructed using a server 1 connected to a communication network 4. As shown in FIG. 1, the network system is constructed so that the terminal device 3 to which the electronic musical instrument 2 is connected can be accessed via the network 4 by connecting the server 1 to the communication network 4. . As a result, the server 1 provides services related to support of music activities to the user of the terminal device 3 connected via the communication network 4. Hereinafter, for the sake of convenience, the description will be made on the assumption that the music activity support system is constructed by one server 1. As a matter of course, a plurality of servers including the server 1 may be used.
[0016]
The communication network 4 collectively represents, for example, the Internet or a public network. The terminal device 3 is a personal computer (hereinafter referred to as “PC”) to which the electronic musical instrument 2 can be connected, PDA (Personal Digital Assistants), etc., for example, a public network such as a telephone network or a cable TV network, and the Internet. It is connected to the Internet through an ISP (Internet Service Provider) that provides a connection service. The terminal device 3 may be an electronic musical instrument equipped with a communication function. The communication network 4 may be other than those or another combination.
[0017]
As one of the music activity support services, the server 1 performs a service for associating and storing performances performed on the electronic musical instrument 2 in parallel by each user of the plurality of terminal devices 3 with the same music.
If the performances are stored in such a manner, the result of the ensemble (band performance) by each user remains. Since the data indicating the performance content is sent from the electronic musical instrument 2 to the server 1 via the terminal device 3 and the communication network 4, no special equipment is required. Since each user performs in parallel, there is no need for the troublesome trouble of each user saving (recording) the performance sequentially. Therefore, regardless of where the user is, each user can virtually perform an ensemble, and the result can be easily and easily left. Hereinafter, such a service that virtually performs an ensemble and stores the result will be referred to as a “one-shot recording service”.
[0018]
One of the reasons is that the performance of music in parallel with each user, in other words, the performance of the music at the same time, is to make the sense of performing an ensemble more. In the present embodiment, the performance received from the terminal device 3 of another user is sent in real time to the terminal device 3 of the user who is virtually performing the ensemble so that the feeling can be further obtained. This further stimulates the sense of performing an ensemble through hearing.
[0019]
The server 1 provides services for users who have registered as members. Various DBs such as a member database (DB), a request DB, a music DB, and a request reception DB are managed for providing the one-shot recording service described above. These DBs will be described in detail with reference to the explanatory diagrams shown in FIGS. Various DBs are built on a storage device such as a hard disk device mounted on or connected to the server 1.
[0020]
FIG. 2 is a configuration diagram of the member DB.
The member DB 20 is for managing a combination of members performing the ensemble (the user of the terminal device 3 registered as a member). The combination is determined by the member. Hereinafter, an ensemble unit virtually performed by a plurality of members will be referred to as a “band”.
[0021]
As shown in FIG. 2, a member area (indicated as “member (1)” in the figure) 21 for storing the personal information is secured for each member in the DB 20. Data such as member ID, password, name, and part in charge is stored as personal information.
[0022]
FIG. 3 is a configuration diagram of the request DB 30.
The one-shot recording service is provided upon request from a band member. The DB 30 is prepared for managing requests received from members. As shown in FIG. 3, a request area 31 (denoted as “request (1)” in the figure) 31 in which request data indicating requested contents is stored for each received request is secured in the DB 30. In the area 31, as request data, an ID for identifying the received request, the requester's ID, the name of the requester, the date and time of starting the ensemble, the song ID assigned to the designated song, and the song name Is stored. The other stored password is issued to identify a member who should provide the one-shot recording service provided upon request.
[0023]
FIG. 4 is a configuration diagram of the music DB 40.
The DB 40 is for managing music that can be downloaded to the user. As shown in FIG. 4, a music area (denoted as “music (1)” in the figure) 41 is secured for each music, and each music area 41 shows a music ID, a music name, and a music performance. Music data and other data accompanying the music data are stored. The song ID is assigned to the song data and is different from the song ID in the request data.
[0024]
The music data is divided for each part. For this purpose, the music data storage area includes a plurality of part areas (denoted as “part (1)” in the figure) 51 each storing music data for each part (hereinafter referred to as “part data” for convenience). Have been secured. The part data stored in each part area 51 is configured, for example, in such a manner that time data indicating the timing at which the event data is to be processed is arranged before the event data indicating the contents (event) of the performance operation. The
[0025]
The music data stored in the music DB 40 includes original data prepared in advance and data uploaded by the user of the terminal device 3 (including data obtained by a one-time recording service here). The original music data is associated with the music ID and distinguished from the other music data.
[0026]
FIG. 5 is a configuration diagram of the request reception DB 60.
The DB 60 sends a request from the member (a request (application) for using the one-shot recording service is an ensemble to other members who form a band with the client) to other members of the band. It is prepared for receipt. As shown in FIG. 5, in the DB 60, a member area (indicated as “member (1)” or the like in the figure) 61 in which request data indicating request contents from other members is stored for each member who forms a band. In the area 61, a member ID and name are stored, and a request reception area (indicated as “request reception (1)” in the figure) 70 in which request data is stored is reserved. In the area 70, the same data as that stored in the request area 31 of FIG. 3 is stored.
[0027]
2 and 5 show the configurations of the DBs 20 and 60 on the assumption that there is one set of target bands. However, when there are multiple sets of bands, each member area is classified by band. It is secured in the prepared area (hereinafter referred to as “band area”).
[0028]
Next, the services shown in FIG. 6 to FIG. 16 and the services provided by the server 1 to the user of the terminal device 3 by managing the above-described DBs 20 to 60 and the operations performed therefor, and FIG. It demonstrates in detail with reference to the various explanatory drawings shown in FIG.
[0029]
The flowchart shown in FIGS. 6 to 16 shows an example of the flow of excerpts of the processes executed when the terminal device 3 is connected to the server 1. For example, the CPU installed in the terminal device 3 is installed in the server 1 with a program that is stored in a hard disk device or the like and includes dedicated software (hereinafter “dedicated software”) for service use provided by the server 1. The CPU is realized by executing a program such as a network OS (operating system) stored in a hard disk device or the like. Although the detailed explanation is omitted, the dedicated software has a function of automatically accessing the server 1 when access to the server 1 is necessary.
[0030]
For example, when the user instructs to start the dedicated software by operating a pointing device such as a mouse or an input device such as a keyboard, the terminal device 3 starts it and performs initialization by its control, whereby the server 1 The service provided by can be used (step TS101). After the initialization, the menu screen 300 shown in FIG. 17 (for example, data described in a markup language such as HTML data; the same applies to other screens) 300 is mounted on a connected or connected display device. It is displayed (step TS102).
[0031]
On the screen 300, as shown in FIG. 17, a “communication mode” button 301 for instructing setting of a communication mode, and a “reproduction mode” for instructing setting of a reproduction mode in which downloaded music data can be reproduced. A button 302 and a “recording mode” button 303 for instructing setting of a recording mode in which data indicating the performance of the performance performed by the user can be added to the downloaded music data. Thereby, the user is allowed to click any of them to set a desired mode.
[0032]
In step TS103 which moves after displaying the screen 300, it is determined whether the "communication mode" button was clicked. If the user clicks the button, the determination is yes and the process proceeds to step TS104, and a connection request signal for accessing the server 1 is transmitted to the server 1. Otherwise, the determination is no and the process moves to step TS155 in FIG.
[0033]
The server 1 that has received the connection request signal transmits an authentication screen 310 shown in FIG. 18 to the terminal device 3 (step SS201). On the authentication screen 310, in addition to boxes 311 and 312 for inputting ID and password, “Send” and “Cancel” buttons are arranged.
[0034]
Upon receiving the authentication screen 310 from the server 1, the terminal device 3 displays it on the display device (step TS105). In the subsequent step TS106, data is input to each of the boxes 311 and 312 in accordance with the operation performed on the input device, and after waiting for the “Send” button to be clicked, the data input to the server is used as authentication data. 1 to send.
[0035]
Upon receiving the authentication data, the server 1 searches the member DB 20 using the authentication data as a key, and executes an authentication process for confirming whether or not the member area 21 storing it is extracted (step SS202). In the next step SS203, it is determined whether or not such an area 21 has been extracted, that is, whether or not the authentication result is OK. If such an area 21 is extracted, the determination is yes, the process proceeds to step SS204, and the communication menu screen 320 shown in FIG. Otherwise, the process returns to step SS201, and the authentication screen shown in FIG. 18 is transmitted again.
[0036]
In the communication menu screen 320, as shown in FIG. 19, a “song download” button 321 for requesting a service capable of downloading music, a “song upload” button 322 for requesting a service capable of uploading music, and A “one-shot recording” button 323 for requesting the one-shot recording service is arranged. Here, the “cancel” button is omitted.
[0037]
When receiving the communication menu screen from the server 1, the terminal device 3 displays it on the display device (step TS107). After the display, the process proceeds to step TS108 in FIG. 7 to determine whether or not the “song download” button 321 is clicked. If the user clicks the button 321, the determination is yes and the process proceeds to step TS 109, and a music download request signal indicating that is transmitted to the server 1. Otherwise, the determination is no and the process moves to step TS115 in FIG.
[0038]
When the request signal is received, the server 1 displays the music name list screen 330 shown in FIG. 20 in which the names of downloadable music, that is, the names of the music data stored in the music DB 40 shown in FIG. It transmits to the apparatus 3 (step SS205 of FIG. 7). Although not specifically shown, the screen 330 is also provided with a “return” button.
[0039]
The terminal device 3 that has received the screen 330 displays it on the display device (step TS110). In the subsequent step TS111, it is determined whether or not a music name on the list has been selected. If the user clicks on a song name on the list, the determination is yes, the process moves to step TS112, and a song request signal for requesting downloading of a song corresponding to the song name is transmitted to the server 1. Otherwise, the determination is no and the process moves to step TS114.
[0040]
When the server 1 receives the music request signal from the terminal device 3, the server 1 reads the music data specified by the signal from the music DB 40 (see FIG. 4) and transmits it to the terminal device 3 (step SS206).
The terminal device 3 that transmitted the music request signal waits to receive the music data and stores it in a predetermined area (hereinafter referred to as “download area” for convenience) in the hard disk device or the like. (Step TS113). After the store, the process returns to step TS110 to display the song name list screen again. The state after the music data is stored is basically the same as that of the music area 41 secured in the music DB 40, for example.
[0041]
The music data obtained by providing the one-shot recording service is stored in the music DB 40. For this reason, the user of the terminal device 3 who performed the ensemble virtually can download the music data as the ensemble result at any time.
On the other hand, in step TS114 in which the determination in step TS111 is NO and the process proceeds, it is determined whether or not a “return” button (not shown) has been clicked. If the user clicks the button, the determination is yes, the process returns to step TS107 in FIG. 6, and the communication menu screen 320 in FIG. 19 is displayed again. Otherwise, the determination is no and the process returns to step TS111. As a result, the music data can be downloaded until the user clicks the “return” button.
[0042]
In step TS115 of FIG. 8 in which the determination in step TS108 is NO and the process proceeds to step TS115, the terminal device 3 determines whether or not the “Song Upload” button 322 has been clicked. If the user clicks the button 322, the determination is yes and the process proceeds to step TS116, and if not, the determination is no and the process proceeds to step TS120 in FIG.
[0043]
In step TS116, a list of the names of the songs in which the song data is saved is arranged in an area reserved for saving the song data (usually including at least the user's performance) (here, the download area is described above). Create a song name list screen and display it on the display device. The screen is as shown in FIG. 20, and after displaying it, the process proceeds to step TS117 to determine whether or not the “return” button has been clicked. If the user clicks the button, the determination is yes and the process returns to step TS107 in FIG. Otherwise, the determination is no and the process moves to step TS118.
[0044]
In step TS118, it is determined whether or not a song name on the list has been selected. If the user clicks on any song name on the list, the determination is yes and the process moves to step TS119, and the song data corresponding to the song name is read from the area and transmitted to the server 1. Otherwise, the determination is no and the process returns to step TS117.
[0045]
Upon receiving the music data from the terminal device 3, the server 1 stores it in the music DB 40 (step SS207 in FIG. 8). Thereafter, the process proceeds to step SS208, and an end signal indicating that the reception of the music data has been normally completed is transmitted to the terminal device 3.
[0046]
The terminal device 3 receives the signal, returns to step TS116, and displays the music name list screen again on the display device.
In this way, in the present embodiment, the user of the terminal device 3 can upload music data at any time. Thereby, a place where the user's performance technique can be presented to the user of the other terminal device 3 is provided, and the search for the partner who forms the band is supported.
[0047]
In step TS120 in FIG. 9 to step TS154 in FIG. 14 in which the determination in step TS115 is NO, processing for making the one-shot recording service by the terminal device 3 available to the user is performed.
First, in step TS120, it is determined whether or not the setting of the one-shot recording mode is instructed. If the user clicks the “one shot recording” button 323, the determination is YES and the process proceeds to step TS121, where the recording menu screen 340 shown in FIG. 21 is displayed on the display device. Otherwise, the determination is no and the process returns to step TS107 in FIG.
[0048]
On the menu screen 340, as shown in FIG. 21, a “recording request” button 341 for requesting use of the service, a “recording reception” button 342 for receiving (confirming) a request from another member, A “recording start” button 343 for requesting the start of a virtual ensemble is arranged. In addition, although not particularly shown, a “return” button is arranged.
[0049]
In step TS122 following step TS121, it is determined whether or not the “return” button has been clicked. If the user clicks the button, the determination is yes and the process returns to step TS107 in FIG. Otherwise, the determination is no and the process moves to step TS123.
[0050]
In step TS123, it is determined whether or not use of the one-shot recording service is requested. If the user clicks the “recording request” button 341, the determination is yes and the process proceeds to step TS124, where a recording request input screen 350 shown in FIG. 22 is displayed on the display device. Otherwise, the determination is no and the process moves to step TS129 in FIG.
[0051]
On the input screen 350, as shown in FIG. 22, a date input box 351 for performing virtual ensemble and a name input box 352 for music to be performed are arranged, which are not particularly shown. However, two buttons of “Send” and “Cancel” are arranged.
[0052]
In step TS125, which is shifted to after the display of the screen 350, data is input to the boxes 351 and 352 in accordance with the user's operation on the input device. When the user clicks the “Send” button on the screen 350, the process proceeds to step TS 126, and a recording request signal for requesting the provision of a service, to which the data input in each box 351, 352 is added, is sent to the server 1. Send to.
[0053]
The server 1 that has received the recording request signal identifies the user (requester) of the terminal device 3 from other data added thereto, and reads the requester's ID and name from the member DB 20 (see FIG. 2). The music ID corresponding to the music of the music name input in the box 352 is specified, and the ID for the request and the password for confirming the ensemble participant are created (issued) (step SS209 in FIG. 9). In step SS210, the request data (issued ID, requester ID, name, song name entered by the requester, date and time, song ID corresponding to the song name) and issued password are stored in step SS210. The area 31 is secured in the request DB 30 (see FIG. 3), and those data are stored in the area 31. Thereafter, the process proceeds to step SS211.
[0054]
In step SS211, other members who form a band with the client are identified with reference to the member DB 20, and the above-described step SS210 is added to the member area 61 of each identified member secured in the request reception DB 60 of FIG. The data stored in the request DB 30 is stored. After the store, the process proceeds to step SS212, and the confirmation screen 360 shown in FIG. 23 in which the password issued in step SS209, the song name received from the terminal device 3 and the date and time are arranged is created and transmitted to the terminal device 3. The service request (application) is notified.
[0055]
Upon receiving the confirmation screen 360 from the server 1, the terminal device 3 displays it (step TS127). Thereafter, it waits for the user to instruct the deletion (step TS128), and the process returns to step TS121.
In this way, when the user requests to use the service (apply), the password and ID are issued, and the request DB 30 and the request reception DB 60 are updated. As a result, as will be described later, a transition is made to a state in which the request can be notified to other members who form a band with the client.
[0056]
As described above, the determination at step TS123 in FIG. 9 is NO, and the process proceeds to step TS129 in FIG. In step TS129, it is determined whether or not the “recording receipt” button 342 has been clicked. If the user clicks the button 342, the determination is yes and the process proceeds to step TS130, and a receipt request signal indicating that the button 342 has been clicked is transmitted to the server 1. Otherwise, the determination is no and the process moves to step TS133 in FIG.
[0057]
When the server 1 receives the reception request signal from the terminal device 3, for example, the server 1 identifies the user from the data added thereto, and searches the request reception DB 60 using the user ID (step SS213 in FIG. 10). . In the next step SS214, it is determined whether request data is stored in the member area 61 extracted by the search. When the request data is stored, that is, when the request receiving area 70 is secured in the area 61, the determination is YES, and the request data stored in the area 70 is regarded as newly requested. Then, a request screen in which the request data stored in each area 70 is arranged is created (step SS217) and transmitted to the terminal device 3 (step SS217). On the other hand, if not, the determination is no, a no-request screen for notifying that there is no request is created (step SS216), and it is transmitted to the terminal device 3 (step SS217).
[0058]
The terminal device 3 receives any screen created as described above from the server 1 and displays it (step TS131). After that, it waits for the user to instruct to erase it (step TS132), and returns to step TS107 in FIG.
[0059]
In this way, in the present embodiment, the user can check the request data stored in the request reception DB 60 at any time. As a result, the virtual ensemble can be performed without any exchange between members.
In step TS133 of FIG. 11 in which the determination in step TS129 is NO, the terminal device 3 determines whether or not the “recording start” button 353 has been clicked. If the user clicks the button 353, the determination is YES and the process proceeds to step TS134, where a recording start request signal indicating that the button 353 has been clicked is transmitted to the server 1. Otherwise, the determination is no and the process returns to step TS107 in FIG.
[0060]
Upon receiving the request signal, the server 1 inputs the password issued for the confirmation in order to confirm whether or not the user of the terminal device 3 is a person (participant of virtual ensemble) who can use the one-shot recording service. Is transmitted to the terminal device 3 (step SS218 in FIG. 11). The input screen is not particularly shown, but includes a password input box and “Send” and “Cancel” buttons.
[0061]
The terminal device 3 waits to receive the input screen from the server 1 and displays it on the display device (step TS135). In the subsequent step TS136, it is determined whether or not the “return” button has been clicked. If the user clicks the button, the determination is yes and the process returns to step TS107 in FIG. Otherwise, the determination is no and the process of step TS137 is executed next.
[0062]
In step TS137, it is determined whether data indicating a password has been input. If the user operates the input device to input data in the box, the determination is yes, and after the data that the user has instructed to input is displayed in the box in step TS138, the process proceeds to step TS139. Otherwise, the determination is no and the process of step TS139 is executed next.
[0063]
In Step TS139, it is determined whether or not the “Send” button has been clicked. If the user clicks the button, the determination is yes and the process proceeds to step TS140, and the data input in the box is transmitted to the server 1 as a password. Otherwise, the determination is no and the process returns to step TS136.
[0064]
When receiving the password from the terminal device 3, the server 1 searches the request DB 30 using the password as a key, and extracts the request data corresponding to the search (step SS219). In the subsequent step SS220 of FIG. 12, the current date and time are detected. In the next step SS221, it is determined whether or not the date and time in the extracted request data and the current date and time match within an allowable range. If there is a relatively large amount of time for the date and time specified by the requester when requesting the use of the service, the determination is YES, and in order to notify that it is not the date and time specified by the requester in step SS222. A warning screen is created and transmitted to the terminal device 3. If not, that is, if the designated date matches the current date and time within the allowable range such that the designated date is close, the determination is no and the process moves to step SS223.
[0065]
In step SS223, it is determined whether or not there is a member who does not access to use the one-shot recording service among members who form the same band as the client. If such a member exists, the determination is yes and the process proceeds to step SS224, and if not, that is, if all the members forming the band are prepared, the determination is no and the step Move on to SS227.
[0066]
In step SS224, it is determined whether or not a predetermined time has passed since the designated date and time. If the current date and time is a date and time that has passed for a predetermined time or more from the specified date and time, the determination is YES and the process proceeds to step SS225 to display a warning screen for notifying that all members are not available. Send to. If not, that is, if the predetermined time or more has not elapsed, the determination is no, the process proceeds to step SS226, and a screen for requesting to wait until all the members are gathered is displayed on the terminal device 3. Send.
[0067]
When the server 1 receives the warning screen transmitted by the server 1 executing the process of step SS222 or SS225, the terminal device 3 displays it on the display device (step TS141). After that, it waits for the user to instruct to erase it (step TS142), and returns to step TS107 in FIG.
[0068]
By returning to step TS107, the one-shot recording service cannot be used. In the present embodiment, if all the members are not prepared even after a predetermined time from the specified date and time, the requested one-shot recording service is canceled, and the request data corresponding to the request is received in the request DB 30, the request received. Each is deleted from the DB 60.
[0069]
On the other hand, when the server 1 receives the screen transmitted by executing the process of step SS226, the terminal device 3 displays it on the display device (step TS143). After that, after displaying it, it waits for a predetermined time to pass (step TS144), and returns to step TS140 in FIG. In such a manner, it is confirmed whether or not the waiting member is kept waiting at any time.
[0070]
If the determination in step SS223 is NO, that is, if it is confirmed that all the members are prepared, the server 1 moves to step SS227 and is set to the original music data corresponding to the music ID in the extracted request data. The music tempo is extracted from the music data, and a music data area 41 for music data to be stored by providing the one-time recording service is secured in the music DB 40 and the ID, music name, etc. are stored. In step SS228 to be executed next, data for generating a pre-sound for informing the start of the ensemble is transmitted to the terminal device 3 of each member in accordance with the extracted tempo.
[0071]
The terminal device 3 that has received the data generates it in the form of voice (step TS145 in FIG. 13). The generation is performed by using a sound source mounted on the terminal device 3 itself or by outputting it to the electronic musical instrument 2.
Each member can start the performance at the same time by generating the above-mentioned hitting sound on all members. Thereby, even if each member does not gather in the same place, it will be able to perform in parallel in the form which gathers in the same place and performs an ensemble.
[0072]
The performance is performed on the electronic musical instrument 2. From this, the terminal device 3 that generated the pre-sounding sound next determines whether or not MIDI (event) data is input from the electronic musical instrument 2 (step TS146). When a performance operation is performed on the electronic musical instrument 2, the electronic musical instrument 2 outputs MIDI data, so the determination is YES, and the MIDI data is transmitted to the server 1 in step TS147. Otherwise, the determination is no and the process moves to step TS148.
[0073]
After transmitting the data for generating the pre-sounding sound, the server 1 proceeds to step SS229 in FIG. 13 and determines whether or not the MIDI data is received from the terminal device 3. If the MIDI data is received, the determination is yes and the process proceeds to step SS230. Otherwise, the determination is no and the process moves to step SS232.
[0074]
In step SS230, the part in charge of the user of the terminal device 3 that transmitted the MIDI data is identified from the user identification data received together with the MIDI data, and the ensemble result storage is performed in the music DB 40 (see FIG. 4). The time data indicating the timing of receiving the MIDI data is stored together with the MIDI data in the part area 51 corresponding to the assigned part prepared in the music area 41 secured in the above. In step SS231, the subsequent MIDI data is transmitted to the terminal device 3 used by the other member so that the other member can listen to the performance of the member.
[0075]
If the determination in step TS146 is NO, the terminal device 3 next executes the process of step TS148. In step TS148, it is determined whether MIDI data is received from the server 1. If the MIDI data is received from the server 1, the determination is yes and the process proceeds to step TS149, MIDI processing is performed to process the MIDI data and the corresponding musical sound is generated, and the process proceeds to step TS150. Otherwise, the determination is no and the process of step TS150 is executed next. The musical sound can be generated by the MIDI data received from the server 1, either the terminal device 3 or the electronic musical instrument 2 connected to the terminal device 3, and the user can be selected from them.
[0076]
By executing the MIDI processing, the user of the terminal device 3 can listen to performances by other members of the band. For this reason, it is possible to enjoy the atmosphere of performing more ensembles.
In step TS150, it is determined whether or not the user has instructed the end of the performance. When the user gives the instruction, the determination is YES, the process proceeds to step TS151, and an end signal indicating that is transmitted to the server 1. Otherwise, the determination is no and the process returns to step TS146. Accordingly, while the user is performing, MIDI data indicating the performance operation is transmitted to the server 1 in real time, and MIDI data indicating performance operations by other members is received from the server 1 in real time.
[0077]
In step SS232, in which the determination in step SS229 is NO and the process proceeds, the server 1 determines whether an end signal has been received. When the end signal is received, the determination is YES, the process proceeds to step SS233, the user who has finished the performance identifies the part in charge from the data added thereto, and the data to the part area 51 corresponding to that part After the recording is stopped in the form of ending the store, the process proceeds to step SS234. Otherwise, the determination is no and the process of step SS234 is next executed.
[0078]
In step SS234, it is determined whether or not the performance of all parts has been completed. If all the members making up the band have instructed the end of the performance, the determination is yes and the process moves to step SS235 in FIG. 14, otherwise the determination is no and the process returns to step SS229. Thereby, it corresponds to the member (user of the terminal device 3) who is performing.
[0079]
In step SS235 of FIG. 14, the music data (ensemble result) stored in the music area 41 secured in the music DB 40 for providing the one-time recording service is read, and reproduction is started for each part. In the subsequent step SS236, it is monitored for each part whether or not the timing specified by the time data has been reached, and when that timing is reached, the MIDI data in the form of adding the time data (next to the time data). Is transmitted to the terminal device 3 of each member.
[0080]
The terminal device 3 that has received the MIDI data transmitted in this manner executes MIDI processing for processing it and generating a musical tone (step TS152 in FIG. 14).
The server 1 that has executed the process of step SS236 next proceeds to step SS237 and determines whether or not the reproduction of the music data has been completed. When the reproduction of the part data is completed for all the parts, the determination is YES, the process proceeds to step SS238, and an OK screen for notifying that is transmitted to each terminal device 3. On the other hand, if not, the determination is no and the process returns to step SS236. Thereby, the reproduction of the music data is continued.
[0081]
The OK screen is provided with a “play” button for instructing replay and a “OK” button for notifying that the play is not requested. When the terminal device 3 receives the screen from the server 1, the terminal device 3 displays it on the display device (step TS153). After the display, the terminal device 3 proceeds to step TS154 and determines whether or not the “OK” button has been clicked. If the user clicks the “OK” button, the determination is yes and the process returns to step TS107 in FIG. If not, that is, if the user clicks the “play” button, the determination is no and the server 1 is requested to play the music data. Thereby, the server 1 next executes the process of step SS235.
[0082]
As described above, in the present embodiment, when the virtual ensemble is completed, each member is allowed to listen to the ensemble result continuously. Thereby, it responds to the request to confirm the ensemble result more quickly.
In step TS155 to TS162 in FIG. 15 in which the determination in step TS103 in FIG. 6 is NO and the transition is made, that the terminal device 3 has clicked the “playback mode” button 302 on the initial menu screen 300 in FIG. Perform processing to respond. The music data stored in the download area, that is, the music data downloaded from the server 1, is to be reproduced in the reproduction mode set by clicking the button 303.
[0083]
First, in step TS155, it is determined whether or not the “playback mode” button 302 has been clicked. If the user clicks the button 302, the determination is yes and the process proceeds to step TS156, otherwise the determination is no and the process proceeds to step TS163 in FIG.
[0084]
In step TS156, a music name list screen in which a list of music names whose music data is stored in the download area is displayed on the display device. The list screen has basically the same configuration as that shown in FIG. 20, and in step TS157 to which the process proceeds after displaying it, it is determined whether or not a song name on the list has been selected. If the user clicks on any song name on the list, the determination is yes and the process moves to step TS159. Otherwise, the determination is no and the process moves to step TS158.
[0085]
In step TS158, it is determined whether or not the “return” button has been clicked. If the user clicks the button, the determination is yes and the process returns to step TS102 in FIG. 6 to display the initial menu screen shown in FIG. 17 again. On the other hand, if not, the determination is no and the process returns to step TS157. Thereby, it waits for the user to select a song name on the list or click the “return” button.
[0086]
In step TS159, the selected music detail display screen 370 shown in FIG. 24 is displayed on the display device. The display screen 370 is for instructing the user to play back the music (music data) for which the user has selected the music name, and displays the music name and data accompanying the music data (see FIG. 4). Boxes 371 and 372 for use, and two buttons 373 and 374 for “start” and “stop” are arranged.
[0087]
In step TS160 that is shifted to after the display screen 370 is displayed, it is determined whether or not the “start” button 373 has been clicked and whether or not the music data is being reproduced. If the user clicks the button 373 or the music data is being played back, the determination is YES and the process proceeds to step TS161, and after performing a music playback process for playing music data, the process proceeds to step TS162. To do. If it is none of them, the determination is no and the process of step TS162 is executed next. The music reproduction process is performed in order to sequentially process the MIDI data at the timing specified by the time data, and the terminal device 3 has a process corresponding to the MIDI data at the timing to be processed. The music data is reproduced by causing the sound source or the sound source mounted on the electronic musical instrument 2 to perform the operation.
[0088]
In step TS162, it is determined whether or not the “stop” button 374 has been clicked and whether or not the reproduction of the music data has ended. When the user clicks the button 374 or the reproduction of the music data is finished, the determination is YES, the process returns to step TS156, and the music name list screen is displayed again. On the other hand, if none of them, the determination is no and the process returns to step TS160. Thereby, when the music data is being reproduced, the reproduction is continued until the reproduction is completed or until the user instructs the completion.
[0089]
In Steps TS163 to TS175 of FIG. 16 in which the determination in Step TS155 is NO, the process for responding to the case where the “recording mode” button 303 on the initial menu screen 300 shown in FIG. 17 is clicked is performed. Is called.
In the recording mode set by clicking the button 303, the performance is recorded by adding the part played by the user to the music data stored in the download area or replacing the previous one. Thereby, each member constituting the band can sequentially save the performance of the ensemble by recording the performance for the part he is in charge of. For this reason, the music data to be recorded is the one stored in the download area.
[0090]
In step TS163, it is determined whether or not the “recording mode” button 303 has been clicked. If the user clicks the button 303, the determination is yes and the process moves to step TS164. If not, the determination is no and the process returns to step TS102 of FIG.
[0091]
In step TS164, a song name list screen in which a list of song names for which song data is stored in the download area is arranged is displayed on the display device. The list screen also has basically the same configuration as that shown in FIG. 20, and in step TS165 that moves after displaying the list screen, it is determined whether or not a song name on the list has been selected. If the user clicks on any song name on the list, the determination is yes and the process moves to step TS167. Otherwise, the determination is no and the process moves to step TS166.
[0092]
In step TS166, it is determined whether or not the “return” button has been clicked. If the user clicks the button, the determination is yes and the process returns to step TS102 in FIG. 6 to display the initial menu screen shown in FIG. 17 again. On the other hand, if not, the determination is no and the process returns to step TS165. Thereby, it waits for the user to select a song name on the list or click the “return” button.
[0093]
In step TS167, a part selection screen for allowing the user to select a part to be played is displayed on the display device. In the selection screen, a list of part types, a “return” button, and the like are arranged. In step TS168, after the display of the selection screen, it is determined whether or not a part has been selected. If the user clicks on any part type on the list, the determination is yes, the process moves to step TS170, and the selected music detail display screen similar to that shown in FIG. 24 is displayed on the display device. Otherwise, the determination is no and the process moves to step TS169. The display screen is for allowing the user to instruct the recording of the performance of the music (music data) selected by the user.
[0094]
In step TS169, it is determined whether or not the “return” button has been clicked. If the user clicks the button, the determination is yes, the process returns to step TS164, and the music name list screen is displayed again. On the other hand, if not, the determination is no and the process returns to step TS168. Thereby, it waits for the user to select a part type on the list or to click the “Back” button.
[0095]
In step TS171 that is shifted to after the selected music detail display screen is displayed, it is determined whether or not the “start” button is clicked and whether or not the performance is being recorded. If the user clicks the button or if a performance is being recorded, the determination is yes and the process moves to step TS172. Otherwise, the process proceeds to step TS175 described later.
[0096]
In step TS172, it is determined whether MIDI data is input from the electronic musical instrument 2. If the electronic musical instrument 2 outputs MIDI data by performing a performance operation, the determination is YES and the process proceeds to step TS173. Otherwise, the process proceeds to step TS174.
[0097]
In step TS173, the input MIDI data and the time (time) data indicating the input timing are stored in the part area corresponding to the part selected by the user in the area where the music data selected by the user is stored. To do. In subsequent step TS174, reproduction processing for reproducing part data other than the part selected by the user is performed. After the reproduction process is executed, the process proceeds to step TS175.
[0098]
In step TS175, it is determined whether or not the “stop” button has been clicked and whether or not performance recording (reproduction of music data) has been completed. When the user clicks the button or the reproduction of the music data is finished, the determination is YES, the process returns to step TS164, and the music name list screen is displayed again. On the other hand, if none of them, the determination is no and the process returns to step TS171. Thereby, when the music data is being reproduced (recording the performance), the performance is continuously recorded until the reproduction ends or until the user instructs the end.
[0099]
In this embodiment, MIDI (event) data indicating the contents of the performance operation performed by the user is received from the terminal device 3 as data indicating the performance contents performed by the user. This is because the amount of data exchanged in step 3 is reduced, in other words, the time required for data transmission is reduced and the ensemble performed at the same place is made closer. If there is no need to reduce the amount of data, other types of data may be used.
[0100]
The number of ensembles performed by the one-shot recording service is one, but the number is not limited to one. The client or other members of the same band may be allowed to do as many times as desired. It may be possible to repeat until the result is satisfied. When it is possible to perform the desired number of times, it is desirable that the performer can select what to save from the results of the ensemble.
[0101]
In the present embodiment, when the server 1 receives the MIDI data from the terminal device 3, the time data indicating the timing for processing the data is created. It may be created and transmitted to the server 1 together with the MIDI data. In such a case, the server 1 can more appropriately record each user's performance.
[0102]
A program for realizing the operation of the music activity support system (server 1) as described above or the operation of the modified example is recorded on a recording medium such as a CD-ROM, DVD, or magneto-optical disk and distributed. Also good. Alternatively, part or all of the program may be distributed via a transmission medium used in a public network or the like. In such a case, the user can construct a music activity support system to which the present invention is applied using the data processing device by acquiring the program and loading it into a data processing device such as a computer. . Therefore, the recording medium may be accessible by a device that distributes the program.
[0103]
【The invention's effect】
As described above, in the present invention, when a user of a terminal device performs a performance of the same song as a member constituting a band in parallel, performance operations performed by a plurality of users via a communication network are performed. Event data indicating the contents is received from each terminal device and stored in association with each other. For this reason, even if each user does not gather in the same place, the result of the band performance (ensemble) performed gathering in the same place can be obtained at once.
[0104]
In the case of notifying the timing at which performance is to be started via the terminal device used by each user who performs the same song in parallel, it is possible to cause each user to start performance at the same time. When event data received from other terminal devices is transmitted in real time to a terminal device used by each user who performs the same song in parallel, each user plays the performance of the other user while performing his / her own performance. You can listen to the performance.
[Brief description of the drawings]
FIG. 1 is a diagram showing a configuration of a network system having a music activity support system according to the present embodiment.
FIG. 2 is a configuration diagram of a member DB.
FIG. 3 is a configuration diagram of a request DB.
FIG. 4 is a configuration diagram of a music DB.
FIG. 5 is a configuration diagram of a request reception DB.
FIG. 6 is a flowchart for explaining a flow of processing executed by the terminal device when it is connected to the server.
FIG. 7 is a flowchart for explaining the flow of processing executed when the terminal device is connected to the server (continuation 1).
FIG. 8 is a flowchart for explaining the flow of processing executed when the terminal device is connected to the server (continuation 2).
FIG. 9 is a flowchart for explaining the flow of processing executed when the terminal device is connected to the server (continuation 3).
FIG. 10 is a flowchart for explaining the flow of processing executed when the terminal device is connected to the server (continuation 4).
FIG. 11 is a flowchart for explaining the flow of processing executed by the terminal device when it is connected to the server (continuation 5).
FIG. 12 is a flowchart for explaining the flow of processing executed when the terminal device is connected to the server (continuation 6).
FIG. 13 is a flowchart for explaining the flow of processing executed when the terminal device is connected to the server (continuation 7).
FIG. 14 is a flowchart for explaining the flow of processing executed when the terminal device is connected to the server (continuation 8).
FIG. 15 is a flowchart for explaining the flow of processing executed when the terminal device is connected to the server (continuation 9).
FIG. 16 is a flowchart for explaining the flow of processing executed when the terminal device is connected to the server (continuation 10).
FIG. 17 is a diagram showing an initial menu screen.
FIG. 18 is a diagram showing an authentication screen.
FIG. 19 is a diagram showing a communication menu screen.
FIG. 20 is a diagram showing a music name list screen.
FIG. 21 is a diagram showing a recording menu screen.
FIG. 22 is a diagram showing a recording request input screen.
FIG. 23 is a diagram showing a confirmation screen.
FIG. 24 is a diagram showing a selected music detail display screen.
[Explanation of symbols]
1 server
2 Electronic musical instruments
3 Terminal equipment
4 Communication network

Claims (5)

A system for supporting music activities for users of a plurality of terminal devices connected via a communication network and capable of transmitting event data corresponding to performance operations in real time,
Member database means in which information of users of the plurality of terminal devices is registered;
Request data receiving means for receiving request data including music and date and time transmitted from any of the terminal devices;
Request data transmission means for transmitting the received request data to a terminal device of another member that forms a band with reference to the member database means ;
A date and time determination means for determining whether or not the date and time included in the received request data has arrived;
An access determining means for determining whether or not all of the terminal devices of the members forming the band are accessing when it is determined that the date and time has arrived by the date and time determining means;
When it is determined by the access determination means that all the terminal devices of the members that form the band have accessed, the tempo is extracted from the music data corresponding to the requested music , and a pre-sound signal that matches the tempo is extracted. Pre-sound signal transmission means for transmitting to all the terminal devices of the members that form the band ;
Event data receiving means for receiving event data transmitted in real time from all the terminal devices of the members that form the band after transmitting a notification signal by this pre-hit signal transmitting means,
Data storage means for storing event data from all the terminal devices of the members that form the band received by the event data reception means in a predetermined storage means in real time;
A music activity support system comprising: If the access determination means determines that all of the terminal devices of the members that form the band have not accessed within a predetermined time from the date and time, a screen to the effect that all of the terminal devices wait until they are aligned is displayed. 2. The music activity support system according to claim 1, further comprising: a screen sending means for sending a warning screen indicating that not all members are ready after the predetermined time has elapsed. The music activity support system further includes a request database for storing request data received by the request data receiving means, and an area for each terminal device, and each time request data is stored in the request database, A request reception database in which the request data is stored in an area corresponding to a terminal device of another member that forms a band ;
2. The request data transmission means transmits the received request data to the terminal device of another member that forms the band based on the stored contents of the request reception database. Music activity support system. The music activity support system further includes, in response to the event data being received from the one terminal device by the event data receiving means, the terminal device of the member that forms the band excluding the one terminal device. The music activity support system according to claim 1, further comprising event data transmission means for transmitting the data in real time. A computer used for a system that supports music activities for users of a plurality of terminal devices connected via a communication network and capable of transmitting event data corresponding to performance operations in real time,
A request data receiving function for receiving request data including music and date and time transmitted from any of the terminal devices;
A request data transmission function for transmitting the received request data to other member terminal devices that form a band with reference to member database means in which user information of the plurality of terminal devices is registered , and
A date and time determination function for determining whether or not the date and time included in the received request data has arrived;
When it is determined that the date and time has arrived, an access determination function for determining whether or not all of the terminal devices of the members that form the band are accessing,
When it is determined that all the terminal devices of the members that form the band have accessed, the tempo is extracted from the music data corresponding to the requested music , and the member that forms the band with a pre-sounding signal that matches the tempo Before-sound signal transmission function to transmit to all the terminal devices,
After transmitting this pre-sounding signal, an event data receiving function for receiving event data transmitted in real time from all the terminal devices of the members that form the band ;
A data storage function for storing event data from all the terminal devices of the members that form the band in a predetermined storage means in real time;
A program to realize

Images