JP2006215210A - Musical piece collaborating method and musical piece collaborating program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a musical piece collaborating method and a musical piece collaborating program with which a plurality of members collaborate a musical piece by transmitting and receiving musical piece data obtained by performance among other members via a network. <P>SOLUTION: The musical piece collaborating method and the musical piece collaboration program is constituted in such a manner that one member of the plurality of members receives musical piece data in which attribute information is added to musical score data, and the member reproduces the musical score data based on the attribute information, and the member obtains musical score data which is played by the member in time to the reproduction and the member adds attribute information to the obtained musical score data, and the member transmits the musical score data to the other members. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to the joint production of music, and more specifically, a plurality of members create music data of each part by playing electronic musical instruments such as MIDI (Musical Instruments Digital Interface) musical instruments via a network, and produce music. The present invention relates to a music collaboration method and a music collaboration program.

  Computer music called DTM (Desk Top Music) has many enthusiastic enthusiasts, such as forums and annual contests, due to the spread of personal computers and related tools (MIDI instruments, sequence software, etc.) To do.

  Conventionally, in such DTM, an individual inputs data or plays a MIDI musical instrument to record musical score data, and edits it to create a song. However, some people feel that the image and composition of the song tends to be one pattern and lacks interest. For this reason, it has been attempted to work together with multiple people instead of creating a song alone.

  There are two main methods for jointly producing music.

  1) Each member creates music data and sends the data to the editor, and the editor edits the sent music data to create one song.

  2) Send the music data to one co-author, and send the music data created by editing the music data you compose to the co-creator to the other co-author Then, this is a way of baton-touching some people and composing in a relay style.

  The following method can be considered as a method of sending the music data at this time.

  1) A method of sending using e-mail.

  2) A method of uploading music data on the Internet and downloading it.

  3) A method of storing music data in a recording medium such as a floppy disk (registered trademark) and mailing it.

  In addition, since network costs have been reduced in recent years, a method of co-production with a plurality of people via a network has been proposed.

For example, a method in which a plurality of members use a chat function to come up with an idea and compose a common song, which is composed of a plurality of client PCs and a server, and the server composes a song based on composition data sent from the client PC. Data is created, and the created music data is transmitted to the client PC (Patent Document 1).
JP 2001-195064 A

  The music data created by each collaborator is sent to the editor and edited by the editor into a single song, or the collaborator sends the music data in a relay format to complete the song. The method has the problem that it is difficult to inspire because the composition work is done at different times and at different times.

  In addition, the method proposed in Patent Document 1 needs to acquire a composition data from a plurality of client PCs and to have a function to compose the server, and the system cannot be easily constructed.

  The music collaborative production method of the present invention obtains musical score data that is performed in accordance with the reproduction of music data sent from the collaborator, sends the music data to all the collaborators, and repeats this for one song. The server proposes a music co-production method and a music co-production program that do not require special functions.

The music collaborative production method and music collaborative production program of the present invention are configured as follows.
(1) 1st invention 1st invention receives and reproduce | regenerates the music data sent from one of several members, and acquires the data which the member who uses a client terminal performed according to the reproduction | regeneration Then, the music data that has been played is transmitted to other members.

  FIG. 1 shows the principle of the first invention and comprises a music data reception procedure 10, a received data storage procedure 20, a score data acquisition procedure 30, and a music data transmission procedure 40.

  The music data reception procedure 10 receives first music data transmitted from one member. The received music data is obtained by adding attribute information to musical score data.

  The received data storage procedure 20 divides the received first music data into musical score data and attribute information, extracts a music ID for identifying a music included in the attribute information, and uses the music ID as key information in the storage unit. Remember.

  In the musical score data acquisition procedure 30, attribute information and musical score data are extracted from the storage unit by the music ID and reproduced, and new musical score data is acquired by playing a MIDI musical instrument played by a member, for example.

  The music data transmission procedure 40 receives the first music data, and transmits the music data in which the attribute information is added to the new musical score data acquired by the further performance of the member who listened to the music data to the other members. The music data at this time is set as second music data.

As described above, for example, when a melody line is presented as the first music data from the member, the musical score data obtained by the member playing other parts is acquired based on the melody line (for example, the first music data is a piano part). If there is, the bass is played in accordance with the piano and the score data of the base part is acquired), and the music data is further transmitted to the members to complete the music.
(2) Second invention In the second invention, in the first invention, the musical score data received and stored has a procedure for repeating the number of measures (repeat), tempo, volume, and time signature. is there. Then, in the musical score data acquisition procedure 30, the edited musical score data is reproduced, and musical score data performed by the member is acquired in accordance with the reproduction.

As a result, the member who has received the first music data arranges (arranges) the musical score data of the first musical data by changing the tempo according to his / her sensibility, and the musical score data played in accordance with the arranged music. get.
(3) Third Invention In the third invention, in the score data acquisition procedure 30 of the first and second inventions, the musical score data that is performed in accordance with the reproduction of the received musical score data and subsequently newly played is also included. Get including.

Thereby, for example, the next melody line can be presented with respect to the melody line presented first.
(4) 4th invention 4th invention includes a message in music data.

  In the music data reception procedure 10, the music data transmitted from the member is obtained by adding attribute information and a message to the score data, and the music data is received as the first music data.

  The received data storing procedure 20 divides the received first music data into musical score data, attribute information, and a message, extracts a music ID for identifying a music included in the attribute information, and uses the music ID as key information to generate music data. And attribute information are stored in the storage unit, and the message is displayed on the display unit.

  The score data acquisition procedure 30 is the same as that of the first invention.

The music data transmission procedure 40 transmits music data in which attribute information and a message are added to the musical score data acquired by performance to all members. The music data at this time is set as second music data.
(5) Fifth Invention The fifth invention is a musical composition collaborative production program based on the first invention.

  In the first invention, it is possible to produce a song of another part in accordance with a song created by one of the members, and by repeating this, it is possible to provide a method capable of jointly producing a song composed of many parts.

  In the second invention, by changing the tempo and time signature of the received song, it is possible to produce a song with an idea that further develops the sender's idea.

  In the third invention, a new song can be developed following the song sent from the sender.

  In the fourth invention, messages can be sent at the same time, and other members can be notified of comments about the song.

  In the fifth invention, it is possible to provide a method capable of collaborative production of a song composed of many parts.

An embodiment of the present invention will be described with reference to FIGS.
(Example 1)
FIG. 2 is a diagram showing an example of the overall system configuration of the present invention. In this configuration example, an IRC (Internet Relay Chat) server 100 that chats to a server is used, and a client terminal (administrator) 300, a client terminal (producer) 301, and a client (viewer) 302 are connected via a network 200. ing.

  The client terminal (administrator) 300 is an IRC channel operator, and is a terminal having an authority to restrict participation in, for example, music collaboration. The client terminal (administrator) 300 can also collaborate on music. A client terminal (producer) 301 is a terminal capable of collaborative production of music. That is, music data can be transmitted and received. A client (viewer) 302 is a terminal for viewing, and only receives music data.

  Next, a configuration example of the client terminal (administrator) 300 is shown in FIG. A client terminal (administrator) 300 includes a CPU (Central Processing Unit) 310 that controls data and programs, a communication control unit 320 that controls transmission / reception communication with the network 200, and MIDI for acquiring musical score data while playing. Musical instrument 331, display 332 for displaying messages, etc., keyboard 333 for giving instructions for starting computer input and programs, MIDI sound source 334 and speaker 335 for playing music, input / output control for controlling input / output devices From a unit 330, a musical score data storage unit 340 that stores musical score data, a management information storage unit 350 that stores information for managing methods including attribute information of musical score data, and a music co-production program 360 that is a program for co-production of music Constitute.

  The music collaboration program 360 further performs a music data reception unit 361 that receives music data, a reception data storage unit 362 that stores the received data in the score data storage unit 340 and the management information storage unit 350, and a MIDI instrument 331. A musical score data acquisition unit 363 that acquires musical score data and a music data transmission unit 364 that transmits the acquired musical score data to other client terminals are configured.

  The chat function is omitted from the configuration of the client terminal (manager) 300 described above. The configuration of the client terminal (producer) 301 is the same as this configuration. The configuration of the client terminal (viewer) 302 does not require acquisition of musical score data or transmission of music data, and therefore does not include the musical score data acquisition unit 363 and the music data transmission unit 364. Furthermore, in order to perform only the reproduction of music data, it is sufficient to provide either a MIDI musical instrument 331 (assuming that a MIDI sound source and a speaker are incorporated) or a MIDI sound source 334 and a speaker 335.

  Next, an example of data in this embodiment will be described.

  First, data transmitted / received between client terminals via the IRC server 100 (client terminal (viewer) 302 receives only) will be described. FIG. 4 shows an example of the data, which is roughly composed of a comment part, an attribute information part, and a score data part. The comment part is text data and describes, for example, a comment about a part created by the sender. The attribute information section is information related to the musical score data to be transmitted, and includes the sender's nickname, song ID, version, performance start position, number of transmission measures, transmission date and time, and the like. The information in the attribute information part is stored in the management information storage part 350 together with other information. The musical score data portion is musical score data obtained by playing the MIDI musical instrument 331 and is MIDI data. Here, MIDI channel No. And there are a plurality of sets of MIDI data. The score data is stored in the score data storage unit 340 using the music ID and version as key information.

  Next, management information stored in the management information storage unit 350 will be described. Before the management information is explained, in this embodiment, a person named “taro” has opened a channel for joint production of music, and by the opening of the channel, a chat is performed by the conventional technology of IRC. It is assumed that members who participate in the production of the song or members who are only watching are determined. For example, it is assumed that “raro” registers this member in the management information storage unit 350 described below and transmits the management information storage unit 350 to each member. Each member includes the management information storage unit 350 received by each terminal (client terminal).

  FIG. 5 shows an example of data in the management information storage unit 350 included in the “taro” client terminal, in which the music data has already been exchanged several times. The management information storage unit 350 includes a member ID (nickname), a category, a song ID, a version, a performance start position, the number of measures, and a transmission / reception date and time. Since “taro” opened a channel in the member ID “taro”, “channel operator” is set in the classification. The channel operator can also participate in the production of a song. Here, the version “1.00” of the song ID “sora” is created and transmitted to the other members (since the version is 1.00, the first is to other members. It is a presented song). The performance start position of the song is from the first measure, and the entire song length is 30 measures. This song data was sent at "19:30 on December 22, 20004" It is. In the second line of “taro”, the version of the song “sora” is “2.00”, which is the same as the previous version 1.00, but from the “31” measure to the next melody. “21” measures are created and sent to other members. The member ID other than taro indicates the contents of the music data received from the member ID.

  Member IDs “jiro” and “saburo” are set to “composer” indicating that they are members who co-produce songs (this is set when “taro” is determined as a member) ). From “jiro”, music data obtained by playing “sora” transmitted from “taro” is received at “21:05 on December 22, 20004”. The version at that time is “1.01”, the performance start position is from the “1” bar, and the number of bars is “30” (since it was created in accordance with the song sent by “taro”, it is a bar. The numbers will be the same). The same applies to “sabuuro”.

  Since the member ID “hanako” is specialized in viewing, the classification is set to “listener”. Accordingly, since “taro” does not receive music data from “hanako”, the fields after the music ID are blank.

  Next, the processing flow of the system in the client terminal will be described.

  FIG. 6 is a flow of creating music data and transmitting it to other members at a client terminal “taro” first. First, when a melody line of a part (for example, a piano) in which taro is a presentation tune is played with the MIDI musical instrument 331, the system acquires the played musical score data. After acquiring the musical score data, the system launches a dialog box (not shown) based on the instruction of taro, and acquires the song ID, version, performance start position (this is “1”), and the number of bars input by taro. To do. This acquired information is stored in the management information storage unit 350 as attribute information. Further, the musical score ID and version are added to the obtained musical score data and stored in the musical score data storage unit 340 (S100 to S120).

  Subsequently, a dialog box (not shown) for inputting comments to the members is displayed. When taro inputs a comment there and gives a transmission instruction, the system uses the comment information, attribute information, and score data. Create an IRC message command. For example, the system creates an IRC message command as shown in FIG. “Privmsg” in FIG. 7 is an IRC private message command. The channel name is the name of the connected channel. Subsequent colons are followed by “processing type;” (for example, “1” for comments, “2” for attribute information, and “3” for MIDI data) (S130, S140).

  The created message command is transmitted to the IRC server 100, and the transmission date and time is recorded in the management information storage unit 350 (S150, S160).

  With the above processing, the IRC server 100 distributes the received data as chat data to the members of the channel.

  Next, referring to FIG. 8, a flow of processing in which the client terminal “jiro” receives music data from the IRC server 100 and transmits music data newly created by jiro based on the music data to other members. Will be explained. First, the jiro client terminal receives music data from the IRC server 100 as chat data. The system of the client terminal identifies the data type based on the processing type of the music data, and extracts comments, attribute information, and score data (S200, S210).

  The comment is displayed on the display in the same way as in a normal chat. The attribute information is stored in the management information storage unit 350 together with the reception date and time. Further, the score data is stored in the score data storage unit 340 (S220 to S240).

  Next, in response to the instruction from jiro, the score data is extracted from the score data storage unit 340 based on the music ID (if there is score data of other parts previously received in addition to the data received this time, all the score including them are included. Retrieve data). Furthermore, if repeated measures, tempo, and time are instructed from jiro, they are set accordingly. Jiro gives an instruction to reproduce the musical score data under these setting conditions. When jiro plays the MIDI musical instrument 331 in accordance with the reproduction, the system acquires the musical score data of the played part. After the performance, a dialog box (not shown) that is set up according to the instruction from jiro can obtain the music ID, performance start position, number of measures, version given this time, etc. by referring to the attribute information of the reproduced music data. As attribute information for the score data. Jiro modifies this display as needed. The system stores the displayed attribute information in the management information storage unit 350, adds the music ID and version to the score data acquired by the performance, and stores it in the score data storage unit 340. (S250-S280).

  Thereafter, a process of creating a comment, creating an IRC message command using the comment, attribute information, and musical score data and transmitting it to the IRC server is the same as S110 to S150 shown in FIG. 6 (S290 to S320).

  In S260, the performance is performed in accordance with the reproduction. However, a new performance may be continuously performed thereafter, or the subsequent song may be performed without being reproduced. In any case, if the musical score data that has been played is acquired and the start position is recorded in the attribute information, the musical score data is reproduced from that position.

  Also, when playing back music data created with repeated measures, tempos, and time signatures, the system will play back this information with the previous music data reflected (ie, the latest version). To be played along with the music data of

  By repeating the above processing, the music data created by each member is accumulated in the score data storage unit 340 and the management information storage unit 350 of each member's client terminal, and the music is completed.

  Based on the processing flow shown above, the state of processing between the client terminal and the IRC server and the accumulation of music data will be described in more detail with reference to FIGS. Here, it is assumed that the client terminal 1 to the client terminal 3 are capable of producing a song. First, the main melody (melody) presented at the client terminal 1 is played with a MIDI musical instrument (performance 1), and the music data 1 is acquired. This music data is stored in the storage unit of the client terminal 1 and then transmitted to the IRC server. Here, it is expressed so that music data can be obtained directly by performance, but originally musical score data is obtained by performance, and attribute information is added to this to obtain music data. Here, the expression is omitted and expressed in this way (S400 to S420).

  The IRC server distributes the music data 1 to the client terminal 2 and the client terminal 3 (the IRC server distributes members participating in this channel in the same manner as the conventional chat data distribution. become). The client terminal 2 receives the music data 1 and stores it in the storage unit. Then, a performance is performed in accordance with the music data 1 (performance 1 ') to obtain music data 1'. The music data 1 'is stored in the client terminal 2, and the data is transmitted to the IRC server. The client terminal 3 simply receives the music data 1 and stores the data. At this time, the music data 1 is stored in the client terminal 1, the music data 1 and the music data 1 'are stored in the client terminal 2, and the music data 1 is stored in the client terminal 3 (S430 to S480).

  The IRC server transmits the music data 1 ′ to the client terminal 1 and the client terminal 3. The client terminal 1 and the client terminal 3 store the music data 1 '. Then, the client terminal 3 performs the performance (performance 1 ″) in accordance with the reproduction of the music data 1 and the music data 1 ′, acquires the music data 1 ″, stores this data, and transmits it to the IRC server (S490). ~ S540).

  The IRC server transmits music data 1 ″ to the client terminal 1 and the client terminal 2. Moving to FIG. 10, the client terminal 1 performs the main melody presented next to obtain music data 2. The IRC server distributes the music data 2 to the client terminal 2 and the client terminal 3. The client terminal 2 and the client terminal 3 store music data 1 to music data 1 "and music data 2. Thus, performance is performed in accordance with these data (performance 2 ′ and performance 2 ″) to obtain music data 2 ′ and music data 2 ″, respectively. Then, the client terminal 2 transmits the music data 2 'to the IRC server. At this time, the music data 1 to 1 ″ and the music data 2 are stored in the client terminal 1, the music data 1 to 1 ″ and the music data 2 and 2 ′ are stored in the client terminal 2, and the music data 1 to 1 are stored in the client terminal 3. 1 ″ and music data 2, 2 ″ are stored (S550 to S680).

  Subsequently, the IRC server distributes the music data 2 ′ to the client terminal 1 and the client terminal 3, and then transmits the music data 2 ″ to the client terminal 1 and the client terminal 2. At this time, the client terminals 1 to 3 are transmitted. , Music data 1 to 1 ″ and music data 2 to 2 ″ are stored (S690 to S750).

  According to the above description, music data obtained by playing at each client terminal is temporarily stored in its own terminal and then transmitted to other client terminals. Is stored. As described above, it is possible to construct a method capable of joint production of music using an IRC server. The IRC server may have a conventional chat function.

In S620 to S730 of the above-described embodiment, the client terminal 2 sends the music data created by itself without looking at the music data created by the client terminal 3. The same applies to the client terminal 3. In such a case, for example, when the client terminal 1 wants to develop each song separately, the song ID of one song data is forcibly changed, and the changed data set is transmitted to the other member. (In such a case, two pieces of music data are created).
(Example 2)
In Example No. 1, an IRC server was used. In the second embodiment, an example in which a music collaborative production method is constructed using a method of a conventional electronic mail server is shown. In FIGS. 11 and 12, the POP3 server and the SMTP server, which are electronic mail servers, are used in place of the IRC server. In this case, it is assumed that an email address for the member ID is stored in the management information storage unit 350 of each client terminal (this is because, for example, a music co-production leader sets members in the management information storage unit 350 in advance). And send it to each member). Each client terminal transmits the music data obtained by the performance to SMTP with reference to this mail address. At the client terminal, the mailer inquires of the POP3 server whether or not an e-mail addressed to him / her comes at every predetermined time. The e-mail may be provided with comments and attribute information in the body and MIDI data as an attachment. 11 and 12 differ from the first embodiment only in the part described above, and the same method may be used thereafter. Since the performance at each client terminal, transmission and reception of music data are the same as in the first embodiment, description thereof will be omitted. By doing so, it is possible to jointly produce music even using a conventional e-mail method.

  This can also be performed in the same manner using a Peer to Peer communication method.

  The following additional notes are disclosed with respect to the above embodiments.

(Appendix 1)
A music collaboration method in which multiple members collaborate on music over a network,
A music data reception procedure for receiving, from the member, first music data in which attribute information is added to the score data;
A received data storage procedure for extracting the music ID from the attribute information and storing the score data and the attribute information in the storage unit using the music ID as key information;
Taking out the attribute information and score data from the storage unit by the music ID, playing back the score data based on the attribute information, and obtaining score data played in accordance with the playback;
A musical composition co-production method, comprising: a musical composition data transmission procedure for transmitting, to all the members, second musical composition data obtained by adding musical score data attribute information to the acquired musical score data.

(Appendix 2)
The music collaborative production method further includes an editing procedure for accepting a change in the number of measures, a change in tempo, volume, and time signature for the stored score data,
2. The musical composition co-production method according to appendix 1, wherein the musical score data obtaining procedure reproduces the edited musical score data and obtains musical score data played in accordance with the reproduction.

(Appendix 3)
3. The music piece co-production method according to Supplementary Note 1 or Supplementary Note 2, wherein the musical score acquisition procedure includes acquiring musical score data that has been newly performed in addition to the performance in accordance with the reproduction of the musical score data.

(Appendix 4)
A music collaboration method in which multiple members collaborate on music over a network,
A music data reception procedure for receiving, from the member, first music data in which attribute information and a message are added to music score data;
The received first music data is divided into the musical score data, the attribute information, and the message, and the musical score ID and the attribute information are stored in the storage unit using the music ID extracted from the attribute information as key information. Received data storage procedure for displaying the message on the display unit;
Taking out the attribute information and the score data by the music ID, reproducing the score data based on the attribute information, and obtaining the score data played in accordance with the reproduction;
A music composition co-production method, comprising: a music data transmission procedure for transmitting, to all the members, second music data in which attribute information and a message of the music score data are added to the acquired music score data.

(Appendix 5)
In the music collaborative production method, an administrator terminal, a creator terminal, and a viewer terminal are connected via a network,
When the manager terminal receives the request information for participation permission from the producer and the viewer, the administrator terminal transmits an answer to the participation permission,
The producer terminal obtains participation permission from the manager terminal and performs transmission / reception of the music data to the member,
The music collaborative production method according to appendix 1, wherein the viewer terminal receives the music piece data with a permission of participation from the manager terminal.

(Appendix 6)
A music collaboration program in which multiple members collaborate on music over a network,
A music data reception procedure for receiving, from the member, first music data in which attribute information is added to the score data;
A received data storage procedure for extracting the music ID from the attribute information and storing the score data and the attribute information in the storage unit using the music ID as key information;
Taking out the attribute information and score data from the storage unit by the music ID, playing back the score data based on the attribute information, and obtaining score data played in accordance with the playback;
A musical composition co-production program for causing a computer to execute a musical composition data transmission procedure for transmitting, to all the members, second musical composition data in which attribute information of musical score data is added to the obtained musical score data.

It is a principle diagram of the invention. It is an example of the whole system configuration. It is a structural example of a client terminal. It is an example of the data transmitted / received. It is a data example of management information. It is an example of the flow of a process (the 1). It is an example of creation of an IRC message command. It is a processing flow example (the 2). It is a session processing flow example (the 1) of Example 1. FIG. It is a session processing flow example (the 2) of Example 1. FIG. 10 is a session processing flow example (No. 1) according to the second embodiment. It is a session processing flow example (the 2) of Example 2. FIG.

Explanation of symbols

10 Music data reception procedure
20 Received data storage procedure
30 Musical score data acquisition procedure
40 Music data acquisition procedure
100 IRC server 200 Network 300 Client terminal (administrator)
301 Client terminal (producer)
302 Client terminal (viewer)
310 CPU
320 Communication Control Unit 330 Input / Output Control Unit 331 MIDI Instrument 332 Display 333 Keyboard 334 MIDI Sound Source 335 Speaker 340 Music Score Data Storage Unit 350 Management Information Storage Unit 360 Music Co-Production Program 361 Music Data Reception Unit 362 Reception Data Storage Unit 363 Music Score Data Acquisition 364 Music data transmitter

Claims (5)

A music collaboration method in which multiple members collaborate on music over a network,
A music data reception procedure for receiving, from the member, first music data in which attribute information is added to the score data;
A received data storage procedure for extracting the music ID from the attribute information and storing the score data and the attribute information in the storage unit using the music ID as key information;
Taking out the attribute information and score data from the storage unit by the music ID, playing back the score data based on the attribute information, and obtaining score data played in accordance with the playback;
A musical composition co-production method, comprising: a musical composition data transmission procedure for transmitting, to all the members, second musical composition data obtained by adding musical score data attribute information to the acquired musical score data. The music collaborative production method further includes an editing procedure for accepting a change in the number of measures, a change in tempo, volume, and time signature for the stored score data,
2. The musical composition co-production method according to claim 1, wherein the musical score data obtaining procedure reproduces the edited musical score data and obtains musical score data played in accordance with the reproduction. The musical score co-production method according to claim 1, wherein the musical score acquisition procedure includes acquiring musical score data that has been newly performed in addition to the performance in accordance with the reproduction of the musical score data. A music collaboration method in which multiple members collaborate on music over a network,
A music data reception procedure for receiving, from the member, first music data in which attribute information and a message are added to music score data;
The received first music data is divided into the musical score data, the attribute information, and the message, and the musical score ID and the attribute information are stored in the storage unit using the music ID extracted from the attribute information as key information. Received data storage procedure for displaying the message on the display unit;
Taking out the attribute information and the score data by the music ID, reproducing the score data based on the attribute information, and obtaining the score data played in accordance with the reproduction;
A music composition co-production method, comprising: a music data transmission procedure for transmitting, to all the members, second music data in which attribute information and a message of the music score data are added to the acquired music score data. A music collaboration program in which multiple members collaborate on music over a network,
A music data reception procedure for receiving, from the member, first music data in which attribute information is added to the score data;
A received data storage procedure for extracting the music ID from the attribute information and storing the score data and the attribute information in the storage unit using the music ID as key information;
Taking out the attribute information and score data from the storage unit by the music ID, playing back the score data based on the attribute information, and obtaining score data played in accordance with the playback;
A musical composition co-production program for causing a computer to execute a musical composition data transmission procedure for transmitting, to all the members, second musical composition data in which attribute information of musical score data is added to the obtained musical score data.

Images