JP5235517B2 - Capostat position determining device, song data transmitting device, capostat position determining method and program - Google Patents

Description

  The present invention relates to a capostat position determining device, a song data transmitting device, a capostat position determining method, and a program for causing a computer to function as a capostat position determining device.

When playing the guitar, a capo tast (hereinafter referred to as a capo) is attached to the fret to perform the modulation. Guitar song data consists of multiple types of chords (chords), and some chords require a Sach that holds down multiple strings with one finger. Since this saver is a burden for beginners, a capo is attached to a predetermined fret (see, for example, Patent Document 1).
JP 2000-75856 A

  However, it has been determined by each person based on many years of experience of playing that the capo is attached to which fret, and there is a problem that a proper capo position cannot be easily determined for beginners. The chord display device described in Patent Document 1 is also determined based on empirical rules in consideration of tonality, and does not solve the above-described problem.

  The present invention has been made in view of such circumstances, and an object of the present invention is to appropriately calculate the difficulty level from the song data by calculating the difficulty level based on the code existing in the song data and the code when the capo position is changed. An object of the present invention is to provide a capo position determining device, a song data transmitting device, a capo position determining method, and a program for causing a computer to function as a capo position determining device capable of objectively determining the capo position.

  An apparatus for determining a position of a capostat according to the present invention is an apparatus for extracting a code existing in music data including a plurality of types of codes in the apparatus for determining a position of a recommended position from a plurality of positions. Counting means for counting the number of each code extracted in the music data, the code extracted by the extracting means and the number of each code counted by the counting means, Reference is made to a determination means for determining the number of each chord and a chord file storing a string pressing method according to the chord, and points are given to the chord when the chord determined by the determination means satisfies a predetermined condition An assigning means, a code point given by the assigning means, and each of the codes determined by the determining means. Based on the number of each code corresponding to Tasuto position, characterized in that it comprises a difficulty level determining means for determining the degree of difficulty of each capo position.

  In the capostat position determining device according to the present invention, the assigning unit refers to the number of strings to be pressed by each finger stored in the chord file, and the one finger of the chord determined by the determining unit is A point is given to the chord when the number of strings to be pressed is greater than or equal to a number stored in advance.

  In the capostat position determination device according to the present invention, the difficulty level determination unit multiplies the number of codes corresponding to each capostat position determined by the determination unit by the code point allocated by the provision unit. The cappotast position determining means is configured to determine the difficulty level of each capostat position, and determines the capotast position with the minimum difficulty level determined by the difficulty level determining means as the recommended capotast position. To do.

  The capostat position determining device according to the present invention includes a total number counting unit that counts the total number of chords in music data, and the difficulty level of each capostat position determined by the difficulty level determining unit divided by the total number counted by the total number counting unit. And an auxiliary difficulty level determining means for determining the auxiliary difficulty level.

  The capostat position determining device according to the present invention is characterized by comprising means for determining, as a recommended capostat position, a capostat position having the smallest auxiliary difficulty determined by the auxiliary difficulty determining means.

  The capostat position determining device according to the present invention includes means for determining a recommended capostat position when the auxiliary difficulty level of the capotast position having the minimum auxiliary difficulty level determined by the auxiliary difficulty level determining unit is equal to or less than a predetermined value. It is characterized by that.

The capostat position determination device according to the present invention includes an auxiliary extraction unit that extracts an auxiliary difficulty level related to a predetermined capostat position from an auxiliary difficulty level of each capostat position determined by the auxiliary difficulty level determination unit, and the auxiliary difficulty level determination The capotast position with the smallest assist difficulty determined by the means is different from the predetermined capotast position, and the difference between the assist difficulty related to the minimum capotast position and the assist difficulty related to the predetermined capotast position is , if less than a predetermined value, and means for determining the capo position of the minimum as the recommended capo position, the predetermined capo position is characterized capo position der Rukoto not wearing the capo.

  The music data transmitting apparatus according to the present invention includes an accepting unit that accepts either a music data transmission request from the outside, or a music data transmission request based on the recommended capotast position determined by the capostat position determining apparatus. Transmitting means for transmitting music data based on the recommended capostat position stored in the storage unit to the outside when receiving a music data transmission request based on the recommended capotast position by the receiving means.

  The capostat position determination method according to the present invention is a capostat position determination method for determining a recommended capostat position from a plurality of capostat positions by a capostat position determination device having a control unit, and exists in song data including a plurality of types of codes. An extraction step for extracting a code by the control unit, a counting step for counting the number of each code extracted in the song in the music data by the control unit, a code extracted by the extraction step, and the counting step Based on the number of each chord counted by the above, with reference to the chord file that stores the chord corresponding to each capotast position and the number of chords determined by the control unit, and the chord file that stores how to press the string according to the chord, The code determined by the determination step satisfies a predetermined condition In addition, based on the giving step of giving points to the code by the control unit, the number of codes corresponding to the point of the code given by the granting step and each capotast position determined by the determining step, the control unit And a determining step for determining the difficulty level of each capotast position.

  The program according to the present invention is a program for determining a recommended capotast position from a plurality of capostat positions by a computer having a control unit, wherein a code existing in song data including a plurality of types of codes is transmitted to the computer by the control unit. An extracting step for extracting, a counting step for counting the number of each code extracted in the music data extracted by the step by the control unit, a code extracted by the extracting step, and a code for each code counted by the counting step Based on the number, a determination step for determining the number of chords corresponding to each capotast position and the number of each chord by the control unit, and a chord file that stores how to press a string according to the chord, were determined by the determination step. When the code satisfies a predetermined condition, the control unit The assigning step of assigning points to the chord, the points of the chord given by the assigning step, and the number of codes corresponding to each capotast position determined by the determining step, the degree of difficulty of each capotast position by the control unit And a determination step for determining the value.

  In the present invention, the extracting means extracts a code existing in the song data read from the storage unit storing the song data including a plurality of types of chords. The determining means counts the number of each extracted code in the music data. Then, the determining means determines the number of codes and codes corresponding to each capo position based on the extracted codes and the number of codes. The assigning means refers to a chord file that stores how to press a string according to the chord, and gives a point to the chord when the decided chord satisfies a predetermined condition. Specifically, referring to the number of strings to be pressed by one finger for each chord stored in the chord file, when the number of strings to be pressed by one finger of the determined chord is equal to or greater than the number stored in advance, Points are given to the code.

  The difficulty level determining means determines the difficulty level of each capo position based on the number of codes corresponding to each capo position determined by the point of the code given by the giving means and the decision means. Specifically, the difficulty level of each capo position is determined by multiplying the added code point by the number of each code corresponding to each capo position determined by the determining means and summing up. Finally, the recommended capo position determining unit determines the capo position having the minimum difficulty determined by the difficulty level determining unit as the recommended capo position.

  In the present invention, the accepting unit accepts either a music data transmission request from the outside or a music data transmission request based on the recommended capo position determined by the capo position determination device. Here, when receiving a music data transmission request based on the recommended capo position, the transmission means transmits the music data based on the recommended capo position stored in the storage unit to the outside.

  In the present invention, the difficulty level of each capo position is determined based on the number of codes corresponding to each capo position determined by the point of the code provided by the assigning means and the determining means. Then, the capo position having the minimum difficulty determined by the difficulty determining unit is determined as the recommended capo position. As described above, since the objective difficulty level can be calculated based on the song data, it is possible to provide an optimum capo position for beginners regardless of the presence or absence of tonality.

  In the present invention, when a music data transmission request based on the recommended capo position is received, the music data based on the recommended capo position stored in the storage unit is transmitted to the outside. Since it comprised in this way, the music data according to the request based on the recommendation capo from the outside can be provided, and it becomes possible to instruct inexperienced users more effectively, and the present invention has an excellent effect. .

Embodiment 1
FIG. 1 is a block diagram showing a hardware configuration of the capo position determining device. The capo position determination device 1 is, for example, a personal computer, a server computer that provides guitar chords and lyrics data via the Internet or a mobile phone network, a karaoke device for a karaoke store, a mobile phone, a game machine, or a PDA (Personal Digital Assistance). is there. In the following description, it is assumed that the capo position determining device 1 is a personal computer 1.

  The personal computer 1 calculates a recommended capo position from a plurality of capo tast positions based on song data including chord data. Details will be described below. The personal computer 1 includes a CPU (Central Processing Unit) 11, a RAM (Random Access Memory) 12, an input unit 13, a display unit 14, a communication unit 16, a storage unit 15, and the like as control units. The CPU 11 is connected to each part of the hardware of the server computer 3 via the bus 17 and controls them, and executes various software functions according to a control program 15P stored in the storage unit 15. The control program is described in a programming language such as C language.

  The communication unit 16 is a LAN (Local Area Network) card or the like, and is necessary information with other devices connected via the communication network N including the Internet and a mobile phone network by HTTP (HyperText Transfer Protocol) or the like. Send and receive. The input unit 13 is, for example, a keyboard and a mouse, and the display unit 14 is, for example, a liquid crystal display. The storage unit 15 is composed of, for example, a hard disk or a large-capacity memory, and in addition to the control program 15P described above, a song data file 151, a total file 152, a code file 153, a recommended capo position file 154, and the like are stored. Yes. The CPU 11 performs processing such as storage and retrieval of necessary information by interacting using SQL (Structured Query Language) or the like in a schema associated with field keys such as the music data file 151.

  FIG. 2 is an explanatory diagram showing a record layout of the music data file 151. The song data includes at least chord information necessary for playing the guitar. The song data file 151 includes a song name field and a code data field. In the present embodiment, an example in which information related to a song name and chord is stored in the song data file 151 will be described, but other data such as lyrics data, display position data, singer name data, etc. are combined. Of course, you may remember for each song. The song title field stores a song title. In the example of FIG. 2, the song name “X” and the like are stored. In the code data field, a chord field and a display time field are stored in time series in association with the music title.

  In the chord field, for example, chords necessary for playing a song such as C, C #, D, D #, and E are stored. The display time field stores the display time indicating the timing when the code is displayed on the guidance screen. This display time indicates the elapsed time from the start of the performance of the song. In the example of FIG. 2, the chord “C #” of the song title “X” is displayed on the screen as a chord to be played from 32 seconds 20 ms to 35 seconds 10 ms after the start of the performance. In addition, from 35 minutes 20 ms to 36 seconds 10 ms after the end of the display of the chord “C #”, the chord “A” to be played next to the chord “C #” is stored. The song data stored in the song data file 151 is downloaded from the communication network N via the communication unit 16. The CPU 11 stores the downloaded music data in the music data file 151. In addition, a portable recording medium (not shown) such as a USB (Universal Serial Bus) memory or a CD-ROM (Compact Disc Read Only Memory) is mounted on the recording medium reading device (not shown), and the portable recording medium is used. The stored music data may be stored in the music data file 151 by the CPU 11.

  FIG. 3 is an explanatory diagram showing the record layout of the summary file 152. The total file 152 includes a capo position field, a code field, a number field, a point field, and a difficulty level field. The total file 152 is a file for storing various data used when calculating the recommended capo position for each song. Below, the content of the totalization file 152 is demonstrated along the calculation procedure of a recommended capo position. In the capo position field, data on the position where the capo is mounted is stored. The recommended capo positions here are, for example, capo position “0” to capo position “11”. Capo position “0” indicates that no capo is attached, and capo position “1” attaches the capo to one fret. Indicates to do. The capo position “12” corresponds to the capo position “0” where no capo is attached. In this example, description will be made assuming that there are 1 to 11 fret positions including no capo mounting as recommended capo positions, but the present invention is not limited to this. For example, as a recommended capo position, it is needless to say that the processing may be performed within a range of about 1 to 6 frets including no capo.

  The CPU 11 activates the control program 15P and stores a value in the code field of the summary file 152 by the process described below. The CPU 11 refers to the code field of the music data file 151 and extracts all the codes included in the music while avoiding duplication. In other words, the CPU 11 extracts all types of codes included in the song data. The CPU 11 stores the extracted code in the code field in association with the capo position “0” of the summary file 152. In the example of FIG. 3, codes “C #”, “F #”, “G #”... Are stored in association with the capo position “0”.

  Subsequently, the CPU 11 stores the code of each capo position in the code field of the summary file 152 based on the modulation rule stored in the storage unit 15 and the code corresponding to the capo position “0”. FIG. 4 is an explanatory diagram showing a modulation rule. When the capo is attached to one fret from the capo position “0”, that is, without capo, and the capo position is “1”, the chord is lowered by one semitone, and in FIG. For example, when the code is “C #” at the capo position “0”, the code becomes “C” when the capo position is “1”. When the capo position is further shifted from “1” to “2”, the semitone is further lowered, and the chord is changed from “C” to “B”.

  The CPU 11 reads all the codes corresponding to the capo position “0” stored in the summary file 152, calculates the code after changing each capo position according to the rules stored in the storage unit 15, and calculates the calculated code after change. It is stored in the code field in association with each capo position. As a result, the type of code existing in the target song data can be ascertained for each capo position.

  The number field stores the number of each code existing in the song data in association with the capo position and the chord. The CPU 11 searches the code field of the music data file 151 based on the code in the code field at the capo position “0”, and counts the number of each code existing in the music data. The CPU 11 stores the number of each counted code in the number field in association with the capo position “0” and the code. In the example of FIG. 3, with respect to the song title X and the capo position “0”, 20 codes “C #”, 10 codes “F #”, 5 codes “G #”, etc. are stored. ing.

  Here, since the number of each code in the same music is the same even when the capo position is changed, the CPU 11 stores the number of each code at each capo position in the totaling file 152 by the following processing. The CPU 11 stores the number data of each code stored in the number field at the capo position “0” in the RAM 12 while maintaining the order of the number data of each code. Then, the CPU 11 sequentially stores the number data in which the order read from the RAM 12 is held in the number field of the total file 152 at each capo position (capo position “1”, capo position “2”...). As shown in FIG. 3, in the case of the capo position “1”, the code “C” is 20 pieces, the code “F” is 10, the code “G” is 5 pieces, etc., and the regularity is maintained. Is remembered. Other configurations of the summary file 152 will be described later.

  FIG. 5 is an explanatory diagram showing a record layout of the code file 153. The chord file 153 stores the fret and string number to be pressed by each finger for each chord. The code file 153 includes a chord field, and fret and string fields. Each code is stored in the code field. In the fret and string field, a fret number to be pressed by each finger and a string number to be pressed by each finger are stored. In the example of FIG. 5, codes “A” and “Bm” are shown as an example. FIG. 6 is an explanatory diagram showing a diagram displayed on the display unit 14. 6A shows a diagram of code “A”, and FIG. 6B shows a diagram of code “Bm”.

  The horizontal lines in FIG. 6 indicate string numbers such as string 1, string 2, string 3,. The leftmost thick vertical line indicates a nut, and the other fine vertical lines indicate frets. In addition, “medicine”, “middle”, “person” and the like surrounded by white circles are the initial letters “parent”, “person”, “middle”, thumb, forefinger, middle finger, ring finger, and little finger, "Drug" and "Small" are encoded. In the fret and string fields of FIG. 5, the fret corresponding to each finger is stored. For example, in the code “A”, the index finger, middle finger, and ring finger frets are stored as 2. Furthermore, the string number to be pressed by each finger is stored. If 1 string is stored in the string field, it indicates that the corresponding finger presses the 1st string. For example, when 1st to 6th strings are stored, this indicates that the corresponding finger presses all of the 1st to 6th strings. A finger whose string number is not stored indicates that the finger does not need to hold down the string. For example, in the case of the code “A”, the index finger presses the 2nd fret 4th string, the middle finger presses the 2nd fret 3rd string, and the ring finger presses the 2nd fret 2nd string. Note that the way the data of the code file 153 is given is merely an example, and may be appropriately changed according to the design.

  Similarly for the chord Bm, the middle finger is a 3rd fret 2 string, the ring finger is a 4th fret 4th string, and the little finger is a 4th fret 3rd string. Here, in the case of the code Bm, Saha is required for the index finger. The index finger is memorized as 1st to 6th strings. In other words, it is necessary to hold all the fingers from the 1st string to the 6th string at the same time as indicated by “person” in FIG.

  FIG. 7 is an explanatory diagram showing a record layout of the total file 152 after the point total. The CPU 11 refers to the counting file 152 and the code file, extracts a code that needs to be saved, and gives points to the extracted code. Specifically, the CPU 11 stores points when values exceeding a preset threshold value are stored in the storage unit 15 in the fret and string fields of the chord file 153. The threshold value is stored in the storage unit 15 as, for example, the number of strings to be pressed by the index finger is 4 or more. That is, when four or more string numbers to be pressed by the index finger of the code file 153 are stored, points are stored.

  The CPU 11 searches the code file based on the code in the code field of the summary file 152, and determines whether or not the number of the index finger of the corresponding code to be pressed is equal to or greater than the threshold value. When the CPU 11 determines that the value is equal to or greater than the threshold value, it stores the point “1” in the point field of the code. The CPU 11 executes the above processing for all the codes in the summary file 152. In the example of FIG. 7, there is a saver in the codes C # and F # and the point “1” is stored. On the other hand, the code “C” and the code “G” are stored as the point “0” because there is no saver. In this example, the points are stored when the number of strings to be pressed by the index finger is 4 or more. However, this is only an example, and the number of fingers and strings is not limited to this.

  The CPU 11 calculates the difficulty level by multiplying the number stored in the number field of the total file 152 by the point stored in the point field. The CPU 11 stores the difficulty level calculated for each code in the difficulty level field of the summary file 152. For example, since the code “C #” exists “20” times in the song and the point “1” is given, the difficulty level 20 is calculated by the product. On the other hand, a code stored as a point “0” like the code “C” is calculated with a difficulty level “0”.

  The CPU 11 adds the difficulty level of each code for each capo position of the total file 152. Then, the sorted difficulty is sorted in ascending order. The CPU 11 sets the capo position having the smallest total value as the recommended capo position. FIG. 8 is an explanatory diagram showing a record layout of the recommended capo position file 154. The recommended capo position file 154 includes a song title field and a recommended capo position field. A capo position to be recommended to the user is stored in association with the song name. For example, for the song name “X”, the CPU 11 stores the minimum capo position “1” of the total value as the recommended capo position. As a result, the user can easily perform a performance by attaching a capo to one fret. The recommended capo position “0” indicates that it is not necessary to attach a capo.

  A procedure of recommended capo position determination processing in the above hardware configuration will be described using a flowchart. 9 and 10 are flowcharts showing the procedure of the code extraction process and the counting process. The CPU 11 receives music data such as new music from the communication unit 16. The CPU 11 stores the received song data in the song data file 151 (step S91). The CPU 11 reads the target song data from the song data file 151 (step S92). The CPU 11 activates the control program 15P to execute the following software processing (step S93).

  The CPU 11 extracts the code in the read music data while avoiding duplication (step S94). The CPU 11 stores the extracted code in the code field in association with the capo position “0” indicating that the caps of the summary file 152 are not attached (step S95). The CPU 11 counts the number of the extracted codes existing in the read music data (step S96). The CPU 11 stores the number of each code in the number field of the counting file 152 in association with the capo position “0” (step S97).

  The CPU 11 reads the modulation rule stored in advance in the storage unit 15 (step S98). The CPU 11 calculates a code of another capo position (for example, capo position “1”) based on the read modulation rule and the code of the capo position “0” in the summary file 152 (step S99). Note that the code after modulation may be obtained by referring to a table (not shown) that stores code changes with respect to the change amount of the capo position. CPU11 memorize | stores the code | cord | chord of the calculated other capo position in a total file (step S101).

  The CPU 11 determines whether codes have been stored in the summary file 152 for all other capo positions (step S102). When the CPU 11 determines that no code is stored for all other capo positions (NO in step S102), the CPU 11 proceeds to step S99 and performs the same processing for other capo positions (for example, capo position “2”). I do. If the CPU 11 determines that the codes have been stored for all other capo positions (YES in step S102), the number of codes for the capo position “0” is read from the total file 152 while maintaining the storage order. (Step S103).

  The CPU 11 stores the number of codes corresponding to the capo position “0” in the RAM 12 while maintaining the order (step S104). The CPU 11 stores the number for the code at the capo position “0” in which the storage order for the code is held in association with the code in the number field at another capo position (step S105). That is, the number data for the code when the capo is not attached is stored in correspondence with the number data for the code at each capo position. The CPU 11 determines whether or not the number for the code at the capo position “0” in which the storage order for the codes is held is stored in the number field for all other capo positions (step S106). If the CPU 11 determines that the number of codes for all other capo positions is not stored (NO in step S106), the CPU 11 proceeds to step S105 and performs the same storage process. On the other hand, if the CPU 11 determines that the number of codes is stored for all other capo positions (YES in step S106), the process ends.

  11 and 12 are flowcharts showing the procedure of the recommended capo position determination process. The CPU 11 sets an initial value 0 at the capo position (step S121). The CPU 11 reads the code at the capo position (step S122). When the initial value is 0, a code at a capo position “0” without a capo is read. The CPU 11 refers to the chord file 153 and determines whether or not the read chord requires an operation of four or more strings with the index finger (step S123). If the CPU 11 determines that the operation is necessary (YES in step S123), the CPU 11 determines that the code has a high degree of difficulty, and stores the point “1” in the count file 152 in association with the code (step S124). ).

  On the other hand, if the CPU 11 determines that the operation is not necessary (NO in step S123), the CPU 11 determines that the code is not a highly difficult code and stores the point “0” in the summary file 152 in association with the code (step S123). S125). The CPU 11 determines whether or not the processing relating to the point assignment has been completed for all the codes in the capo position (step S126). If the CPU 11 determines that the processing has not been completed for all the codes (NO in step S126), the processing in step S123 is executed for the other codes. On the other hand, if the CPU 11 determines that the processing has been completed for all the codes (YES in step S126), the CPU 11 determines whether the processing in step S123 and the like has been completed for all capo positions in the summary file 152 (step S127). ).

  If the CPU 11 determines that the processing has not been completed for all capo positions (NO in step S127), the CPU 11 increments the capo position (step S128). Thereafter, the process returns to step S122 again. For example, when the capo position is “0”, the point giving process is subsequently executed for the code at the capo position “1”. On the other hand, if the CPU 11 determines that the point giving process has been completed for all capo positions (YES in step S127), the CPU 11 multiplies the number in the totaling file 152 by the point to calculate the difficulty level for the code at each capo position ( Step S129).

  The CPU 11 adds the difficulty levels for each capo position (step S131). Specifically, the difficulty level of the code at each capo position is added up. And CPU11 memorize | stores the total value in the total file 152 for every capo position (step S132). The CPU 11 extracts a capo position having a minimum sum value (step S133). The capo position extracted in step S133 is the recommended capo position. The CPU 11 stores the recommended capo position and the target song name stored in the song data file in the recommended capo position file 154 in association with each other (step S134).

Embodiment 2
The second embodiment relates to a form in which music data based on the recommended capo position is transmitted to the outside. FIG. 13 is an explanatory diagram showing an outline of the music data transmission system. The song data transmission system includes a song data transmission device, a communication network N, and portable terminals 2, 2,. The song data transmitting device 1 is, for example, a server computer or the recommended capo position determining device described in the first embodiment, and the song data when the capo is not attached or the song data based on the recommended capo position to the portable terminal 2. Send. Hereinafter, the music data transmitting apparatus 1 will be described as being replaced with the server computer 3.

  The mobile terminal 2 is, for example, a mobile phone, a PDA, a portable audio player or a portable game machine having a display unit, and a portable portable terminal having a display screen smaller than a monitor installed in a general karaoke store. Machine. In the present embodiment, the mobile terminal 2 will be described as the mobile phone 2. The mobile phone 2 displays chords required for music reproduction and performance based on the received song data at an appropriate timing.

  As shown in the block diagram, the cellular phone 2 shown in FIG. 13 includes a CPU 21 as a control unit, a RAM 22, an input unit 23, a display unit 24, a communication unit 26, a microphone 28, a speaker 29, a clock unit 210, and a storage unit 25. Etc. are configured. The CPU 21 is connected to the hardware units of the mobile phone 2 via the bus 27, controls them, and executes various software functions according to the control program 25P stored in the storage unit 25.

  The display unit 24 is a liquid crystal display, for example, and displays various information such as codes and lyrics. The input unit 23 includes a push button or the like. In addition, you may make it comprise the display part 24 and the input part 23 integrally like a touchscreen. The speaker 29 amplifies and outputs audio data, call data, or an audio signal related to audio input from the microphone 28. The microphone 28 converts an audio signal input from the outside into an electric signal. The converted electrical signal is converted into digital data by an A / D converter (not shown) and output to the CPU 21. The communication unit 26 includes a high-frequency transmission / reception unit and an antenna, and performs transmission / reception of various data including voice data, character data, and the like. The clock unit 210 outputs date / time information to the CPU 21.

  The storage unit 25 stores a control program 25P, a browser 251, and a playback application 252. The browser 251 analyzes an HTML (HyperText Markup Language) file transmitted / received via the communication unit 26 by HTTP (Hyper Text Transfer Protocol) and displays the file on the display unit 24. The playback application 252 is software that plays back received song data, and is downloaded via the communication unit 26. The playback application 252 displays chords necessary for playing the guitar, plays music, displays lyrics, and the like.

  FIG. 14 is a block diagram showing a hardware configuration of the server computer 3. The server computer 3 includes a CPU 31 as a control unit, a RAM 32, a display unit 34, an input unit 33, a communication unit 36, a storage unit 35, and the like. The CPU 31 is connected to the hardware units of the server computer 3 via the bus 37, controls them, and executes various software functions according to the control program 35P stored in the storage unit 35. The control program is described in a programming language such as C language. The personal computer 1 described in the first embodiment is connected to the server computer 3 via the communication unit 36 by a LAN. The personal computer 1 transmits information on the recommended capo position for the song name stored in the recommended capo position file 154 to the server computer 3.

  The communication unit 36 is a gateway or the like that functions as a firewall, and transmits and receives necessary information between the mobile phone 2 and the personal computer 1. The storage unit 35 is composed of, for example, a hard disk, and stores therein the control program 35P, the music data file 351, the authentication file 352, the HTML file 353, the recommended capo position file 354, and the like. The CPU 31 executes processing such as storage and retrieval of necessary information by interacting using SQL or the like in a schema that associates field keys of various files.

  Similar to the recommended capo position file 154 of the personal computer 1, the recommended capo position file 354 stores a recommended capo position for the song title. As described above, the server computer 3 itself may calculate the recommended capo position by the method described in the first embodiment. In the present embodiment, an example of receiving recommended capo position information for a song title from the personal computer 1 via the communication unit 36 will be described. However, a recommended capo for song titles is used by a portable recording medium such as a USB memory (not shown). In addition to storing the position information in the recommended capo position file 354, the operator may directly input information on the recommended capo position for the song name from the input unit 33.

  The authentication file 352 stores the ID and password of the user who uses the music data transmission system. Note that the ID is a MAC (Media Access Control) address, a telephone number, a mail address, or the like given to the mobile phone 2. The HTML file 353 stores information on various guidance screens displayed on the browser 251 of the mobile phone 2 in the music data transmission system.

  FIG. 15 is an explanatory diagram showing a record layout of the song data file 351. The song data file stores code data, lyrics data, music data, and the like for each song name. In the example of the figure, the code data of the song title “X”, etc., of the song titles “X”, “Y”, “Z”,. The song data file 351 includes a capo position field, a code data field, a lyrics data field, a music data field, and the like. In the capo position field, the capo position “0”, that is, information that the capo is not mounted and information of the recommended capo position are stored. The CPU 11 refers to the recommended capo position file 354 and stores the recommended capo position for the song name in the capo position field of the song data file 351. In this example, the recommended capo position is stored as “2”.

  The code data field further stores a code field, a display time field, and a display position field. In the chord field, chords such as C # necessary for playing a song are stored in time series. In the display time field, a display time indicating the timing when the code is displayed on the display unit 24 of the mobile phone 2 is stored. This display time indicates the elapsed time from the start of the performance of the song. The display position field stores a coordinate value for displaying a code symbol on the display unit 24 of the mobile phone 2. When the upper left coordinate of the display unit 24 is the origin coordinate (x, y) = (0, 0), the coordinate value of the upper left pixel of the symbol image of the rectangular code is (x, y) = (x1, y1) and the like.

  Like the karaoke, the lyric data field stores data such as lyric displayed in accordance with the performance of the music data, and includes a lyric field, a display time field, and a display position field. The lyrics of the song name “X” are stored in the lyrics field as text data or the like. The display time field stores the display timing of lyrics starting from the start of music data performance. The display position field stores the coordinate position when the lyrics are displayed on the display unit 24 of the mobile phone 2. When the upper left coordinate of the display unit 24 is the origin coordinate (x, y) = (0, 0), the coordinate value of the upper left pixel of a rectangular lyrics block composed of one or a plurality of characters is expressed as ( x, y) = (x2, y2) and the like.

  The music data field stores music files in a format such as mmf, mld, MP3 (MPEG 1 Audio Layer 3), or wav (WAVE). The CPU 31 performs processing for changing the code of the capo position “0” with reference to the recommended capo position and the modulation rule stored in the storage unit 35 in advance. In the example of FIG. 15, since the recommended capo position is “2”, the codes “C #”, “F #”, and “G #” of the capo position “0” are the codes “B” and “E”, respectively. And “F #”. The difference in information between the capo position “0” and the recommended capo position is the code after this change, and the display time of other code data, lyrics data, and the like are the same as those of the capo position “0”. The CPU 31 refers to the song data file, reads the song data based on the capo position “0” when receiving the request for the capo position “0”, and reads the song data based on the recommended capo position when receiving the request for the recommended capo position. Is read. In this example, the code data, the lyric data, the music data, and the like are stored in an integrated manner for easy explanation, but the way of holding the data is not limited to this.

  FIG. 16 is an explanatory diagram showing an image of music selection. A music selection screen shown in FIG. 16 is displayed on the display unit 24 of the mobile phone 2. The CPU 31 reads out an HTML file as a basis for music selection from the HTML file 353, and reads out a recommended capo position for the song name to be selected from the recommended capo position file 354. The CPU 31 adds the read recommended capo position to the basic HTML file and transmits it to the mobile phone 2. On the display unit 24 of the mobile phone 2, in addition to the recommended capo position, a hyperlink 241 that is operated when receiving song data for playing the song name “X” without a capo, and a song title “ A hyperlink 242 that is operated when music data for performing “X” is received is displayed.

  When the operation input of the hyperlink 241 or 242 is received via the input unit 23 of the cellular phone 2, the CPU 21 sends a request for transmitting song data without a cap or a request for transmitting song data based on a recommended capo position to a server computer. 3 to do. When the CPU 31 of the server computer 3 receives the transmission request and receives the transmission request of the song data without capo, the song data file 351 is referred to read the song data corresponding to the song name “X” and the capo position “0”. Transmit to the telephone 2. On the other hand, when a transmission request for music data at the recommended capo position is received, the music data file 351 is referred to, and the music data corresponding to the music name “X” and the capo position “2” is read and transmitted to the mobile phone 2.

  FIG. 17 is an explanatory diagram showing a display image of a code. The CPU 21 of the mobile phone 2 activates the reproduction application 252 in response to the reception of the music data, and performs music reproduction, code display, lyrics display, and various drawing processes. The CPU 21 reproduces music data. Then, the CPU 21 displays the chord and lyrics on the display unit 24 at an appropriate timing from the start of the performance based on the received chord data, lyrics data, and date / time information output from the clock unit 210. In the example of the figure, a symbol indicating the current code “C #”, a symbol indicating the next code “A”, and lyrics are displayed together with the code. This display timing is performed with reference to the display time of the code data and the display time of the lyrics data. The symbol and lyrics of the code are performed with reference to the display position of the code data and the display position of the lyrics data.

  In the diagram, finger types and positions (frets and strings) to be displayed corresponding to chords are described in the reproduction application 252, and the CPU 21 draws image data indicating the finger types at predetermined positions in accordance with this description. In the illustrated example, a diagram of “C #”, which is the current code, is displayed. In the present embodiment, at least chord position code data (code, display time, display position) is included as song data, and music data and lyrics data are added to the song data and transmitted.

  18 to 20 are flowcharts showing the procedure of music data transmission processing. Each time a new song is distributed, the CPU 31 of the server computer 3 captures the chord, the chord data including the display time and the display position, the lyrics, the lyrics data including the display time and the display position, and the song data including the music data. Is stored in the song data file 351 as shown in FIG. 15 in association with the capo position “0” and the song name indicating that the character is not used (step S181). The CPU 31 stores the recommended capo position for the song title obtained by the method described in the first embodiment in the recommended capo position file 354 (step S182). The CPU 31 reads the recommended capo position for the song title from the recommended capo position file 354 (step S183).

  The CPU 31 changes the code of the capo position “0” stored in step S181 based on the modulation rule stored in the storage unit 35 and the read recommended capo position (step S184). The CPU 31 stores the changed code in the music data file 351 in association with the recommended capo position information read out in step S183 (step S185). The CPU 31 stores the display time and display position of the code data of the music data file, the lyrics data, and the music data in association with the recommended capo position and the changed code. Thereby, the music data based on the capo position “0” and the recommended capo position is completed. When the recommended capo position stored in the recommended capo position file 354 is “0”, that is, when it is determined that the performance is easiest when the capo is not attached, the processes of steps S184 and S185 are skipped. . Hereinafter, an example in which the recommended capo position is other than “0” will be described.

  When the user accesses the server computer 3 using the mobile phone 2 to use the music data transmission system, the following processing is performed. The CPU 21 of the mobile phone 2 transmits the ID and password input from the input unit 23 to the server computer 3 (step S186) and performs login. The server computer 3 receives the ID and password, and determines whether or not it matches the ID and password stored in advance in the authentication file 352 of the storage unit 35 (step S187). If the CPU 31 determines that the ID and the password do not match (NO in step S187), the CPU 31 ends the processing as an unauthorized access.

  On the other hand, if the CPU 31 determines that the ID and password match (YES in step S187), the CPU 31 reads the song title selection screen from the HTML file 353 and transmits it to the mobile phone 2 (step S188). The CPU 21 of the mobile phone 2 displays a song title selection screen on the display unit 24 (step S189). The CPU 21 accepts the song name input by the user from the input unit 21, and transmits the accepted song name to the server computer 3 (step S191).

  The CPU 31 of the server computer 3 receives the transmitted song title (step S192). The CPU 31 reads the recommended capo position corresponding to the song title from the recommended capo position file 354 (step S193). The CPU 31 reads the basic HTML file stored in the HTML file (step S194). The CPU 31 describes the recommended capo position read in step S193 in the basic HTML file, and further transmits a song data transmission request without a capo (hyperlink 241) or a song data transmission request based on the recommended capo position (hyperlink). 242) is generated (step S195).

  The CPU 31 transmits the generated transmission request screen to the mobile phone 2 (step S196). The CPU 21 of the mobile phone 2 receives the transmission request screen and displays the transmission request screen on the display unit 24 as shown in FIG. 16 (step S197). The CPU 21 determines whether or not a music data transmission request based on the recommended capo position information has been received from the input unit 23 (step S198). Specifically, it is determined whether or not the hyperlink 242 shown in FIG. 16 has been operated. If the CPU 21 determines that the music data transmission request based on the recommended capo position information has been received (YES in step S198), the CPU 21 transmits a music data transmission request based on the recommended capo position information to the server computer 3 (step S198). S199). The CPU 31 of the server computer 3 receives a music data transmission request based on the recommended capo position information via the communication unit 36.

  On the other hand, if the CPU 21 determines that a song data transmission request based on recommended capo position information has not been received (NO in step S198), the CPU 21 determines that the hyperlink 241 has been clicked, and requests a song data transmission without a capo. Is transmitted to the server computer 3 (step S201). The CPU 31 of the server computer 3 accepts a request for transmission of song data without capo via the communication unit 36.

  The CPU 31 determines whether or not a music data transmission request based on the recommended capo position information has been received (step S202). If the CPU 31 determines that a song data transmission request based on the recommended capo position information has been received (YES in step S202), the CPU 31 reads the song data based on the recommended capo position from the song data file 351 and transmits it to the mobile phone 2 (step S202). S203). On the other hand, when the CPU 31 determines that the music data transmission request based on the recommended capo position information is not accepted (NO in step S202), the CPU 31 reads the music data at the capo position “0” from the music data file 351, and the mobile phone 2 (Step S204).

  The CPU 21 of the mobile phone 2 receives the song data transmitted from the server computer 3 (step S205). The CPU 21 activates the reproduction application 252 (step S206). The CPU 21 reproduces music data (step S207) and outputs music from the microphone 28. The CPU 21 synchronizes the display timing of the music data, the chord data, and the lyric data using the date / time information output from the clock unit 210 triggered by the reproduction of the music data. In synchronization with the reproduction of the music data, the CPU 21 refers to the display time and display position of the chord and lyrics, and displays the chord and lyrics on the display unit 24 (step S208). In this case, when the song data based on step S203 is transmitted, a performance based on the recommended capo position can be performed. On the other hand, when the song data based on step S204 is transmitted, a performance without a capo is possible.

  The second embodiment is configured as described above, and the other configurations and operations are the same as those of the first embodiment. Therefore, corresponding parts are denoted by the same reference numerals, and detailed description thereof is omitted.

Embodiment 3
The third embodiment relates to a recommended capo position calculation process when using another finger different from the one finger for Sacher described in the first embodiment. In addition to Saha, there are players who are not good at chords using specific fingers. In the present embodiment, the other finger is described as being the little finger, but is not limited to the little finger.

  FIG. 21 is a block diagram illustrating a hardware configuration of the capo position determination device according to the third embodiment. In addition to the configuration of the first embodiment, an auxiliary recommended capo position file 155 is stored in the storage unit 15. The recommended capo position file 154 stores the capo positions with less safing with the index finger for each song, while the auxiliary recommended capo position file 155 has less safing with the index finger and less chance to hold the string with the little finger. The position is memorized for each song.

  FIG. 22 is an explanatory diagram showing a record layout of the summary file 152 according to the third embodiment. In addition to the configuration of the first embodiment, an auxiliary point field is provided. In the auxiliary point field, auxiliary points to be given in association with the codes at the respective capo positions are stored. The CPU 11 refers to the string field and finger field corresponding to the chord in the chord file 153, and determines whether there is a string to be pressed by the little finger during performance. Specifically, the CPU 11 determines whether or not any string number of 1st to 6th strings is set in the string field corresponding to the little finger of the code file 153. In the example of FIG. 5, it is necessary to press the string with the little finger when playing the chord Bm.

  If the CPU 11 determines that there is a string to be pressed by the little finger, the auxiliary point field “0.5” lower than the point “1” assigned in the first embodiment is associated with the chord in the auxiliary point field of the total file 152. To remember. In the present embodiment, the auxiliary point is set to 0.5, but is not limited to this value. In the example of FIG. 22, the auxiliary point “0.5” is assigned to the code “C #”, and the auxiliary point is not assigned to the code “C”.

  The CPU 11 adds the points and the auxiliary points, and calculates the difficulty level by multiplying the added value and the number in the number field. The CPU 11 stores the calculated difficulty level in the count file 152 in association with the code. The CPU 11 adds the difficulty levels of the respective codes. Similarly, the sum of the difficulty levels of other capo positions is calculated. Finally, the CPU 11 sorts the summed values in ascending order and sets the capo position having the smallest summed value as the auxiliary recommended capo position.

  FIG. 23 is an explanatory diagram showing a record layout of the auxiliary recommended capo position file 155. The auxiliary recommended capo position file 155 includes a song title field and a recommended capo position field. In association with the song title, a capo position to be supplementarily recommended to the user is stored. For example, for the song name “X”, the CPU 11 stores the minimum capo position “2” of the total value as the recommended capo position. Thus, the user can perform the performance with less use of the index finger by using the capo on the 2nd fret and less chance of using the little finger that is not good.

  The procedure of the auxiliary recommended capo position determination process in the above hardware configuration will be described using a flowchart. 24 and 25 are flowcharts showing a procedure for determining the auxiliary recommended capo position. The CPU 11 performs the following processing after calculating the number and points in the summary file 152 in the first embodiment. The CPU 11 substitutes an initial value “0” for the capo position (step S241). The CPU 11 refers to the chord file and determines whether or not a string to be pressed by the little finger of the target chord is stored (step S242). If the CPU 11 determines that the string to be pressed by the little finger is stored (YES in step S242), the CPU 11 stores 0.5 in the auxiliary point field of the total file 152 to give the auxiliary point “0.5” (step S242). S244).

  On the other hand, when the CPU 11 determines that the string to be pressed by the little finger is not stored (NO in step S242), the CPU 11 stores 0 in the auxiliary point field of the total file 152 (step S243). After the processes of steps S244 and S243, the CPU 11 adds auxiliary points to the points obtained in the first embodiment (step S245). The CPU 11 multiplies the number of target codes by the addition value calculated in step S245 (step S246). The CPU 11 stores the multiplication value in the difficulty level field as the difficulty level of the target code (step S247).

  The CPU 11 determines whether or not the difficulty level has been calculated for all codes in the same capo position (step S248). If the CPU 11 determines that the difficulty level has not been calculated for all codes (NO in step S248), the code is changed to calculate the difficulty level for other codes (step S249), and the process returns to S242. return. When the CPU 11 determines that the calculation of the difficulty level has been completed for all the codes (YES in step S248), the CPU 11 adds the difficulty levels of all the codes based on the difficulty levels of the respective codes calculated in step S247 (step S251). .

  The CPU 11 stores the total value in the storage unit 15 in association with the capo position (step S252). The CPU 11 determines whether or not the process of calculating the sum value for all capo positions has been completed (step S253). When the CPU 11 determines that the process has not been completed (NO in step S253), the capo position is incremented (step S254), and the process returns to step S242. On the other hand, if the CPU 11 determines that the process of calculating the sum value has been completed for all capo positions (YES in step S253), the CPU 11 refers to the sum value for the capo position stored in step S252, and determines the minimum value of the sum values. Is extracted (step S255). The CPU 11 stores the extracted minimum capo position in the auxiliary recommended capo position file 155 as an auxiliary recommended capo position in association with the song name (step S256). As a result, in addition to the recommended capo position obtained in the first embodiment, it is possible to obtain an auxiliary recommended capo position that also considers the operation of a specific finger.

  FIG. 26 is a block diagram illustrating a hardware configuration of the server computer 3 according to the third embodiment. In addition to the first embodiment, an auxiliary recommended capo position file 355 is stored in the storage unit 35. The CPU 31 stores the auxiliary recommended capo position obtained in the present embodiment in the auxiliary recommended capo position file 355 in the same manner as the recommended capo position of the first embodiment. The CPU 31 provides the user with an auxiliary recommended capo position in addition to the recommended capo position.

  FIG. 27 is an explanatory diagram showing an example of a music data transmission request screen. A hyperlink 243 is further displayed on the display unit 24 of the mobile phone 2. The hyperlink 243 operates the input unit 23 when making a music data transmission request at the auxiliary recommended capo position. In the example of FIG. 27, information on the auxiliary recommended capo position “1” is provided for beginners who are not good at operating the little finger, and song data based on the auxiliary recommended capo position is also provided.

  FIG. 28 to FIG. 32 are flowcharts showing the procedure of music data transmission processing. Each time a new song is distributed, the CPU 31 of the server computer 3 captures the chord, the chord data including the display time and the display position, the lyrics, the lyrics data including the display time and the display position, and the song data including the music data. Is stored in the song data file 351 as shown in FIG. 15 in association with the capo position “0” and the song name indicating that the character is not used (step S281). The CPU 31 stores the recommended capo position for the song name obtained by the method described in the first embodiment in the recommended capo position file 354 (step S282). The CPU 31 reads the recommended capo position for the song title from the recommended capo position file 354 (step S283).

  The CPU 31 changes the code of the capo position “0” stored in step S281 based on the modulation rule stored in the storage unit 35 and the read recommended capo position (step S284). The CPU 31 stores the changed code in the music data file 351 in association with the recommended capo position information read out in step S283 (step S285). The CPU 31 stores the display time and display position of the code data of the music data file 351, the lyrics data, and the music data in association with the recommended capo position and the changed code. Thereby, the music data based on the capo position “0” and the recommended capo position is completed. Subsequently, the CPU 31 stores the auxiliary recommended capo position for the song name obtained by the method described in the present embodiment in the auxiliary recommended capo position file 355 (step S286). The CPU 31 reads the auxiliary recommended capo position for the song title from the recommended capo position file 355 (step S287).

  The CPU 31 changes the code of the capo position “0” stored in step S281 based on the modulation rule stored in the storage unit 35 and the read auxiliary recommended capo position (step S288). The CPU 31 stores the changed code in the music data file 351 in association with the auxiliary recommended capo position information read out in step S287 (step S289). The CPU 31 stores the display time and display position of the code data in the music data file 351, the lyrics data, and the music data in association with the auxiliary recommended capo position and the changed code. This completes the song data based on the auxiliary recommended capo position.

  The CPU 21 of the mobile phone 2 transmits the ID and password input from the input unit 23 to the server computer 3 (step S291) and performs login. The server computer 3 receives the ID and password, and determines whether or not it matches the ID and password stored in advance in the authentication file 352 of the storage unit 35 (step S292). If the CPU 31 determines that the ID and the password do not match (NO in step S292), the CPU 31 ends the processing as an unauthorized access.

  On the other hand, if the CPU 31 determines that the ID and password match (YES in step S292), the CPU 31 reads the song name selection screen from the HTML file 353 and transmits it to the mobile phone 2 (step S293). The CPU 21 of the mobile phone 2 displays a song title selection screen on the display unit 24 (step S294). The CPU 21 accepts the song name input by the user from the input unit 21, and transmits the accepted song name to the server computer 3 (step S295).

  The CPU 31 of the server computer 3 receives the transmitted song title (step S296). The CPU 31 reads the recommended capo position corresponding to the song title from the recommended capo position file 354 (step S297). Similarly, the CPU 31 reads the auxiliary recommended capo position corresponding to the song title from the auxiliary recommended capo position file 355 (step S298). The CPU 31 reads the basic HTML file stored in the HTML file (step S299). The CPU 31 describes the recommended capo position read in step S293 and the auxiliary recommended capo position read in step S287 in the basic HTML file, and further, based on a request for transmitting song data without a capo (hyperlink 241) and the recommended capo position. A screen for making a music data transmission request (hyperlink 242) or a music data transmission request (hyperlink 243) based on the auxiliary recommended capo position is generated (step S301).

  The CPU 31 transmits the generated transmission request screen to the mobile phone 2 (step S302). The CPU 21 of the mobile phone 2 receives the transmission request screen and displays the transmission request screen on the display unit 24 as shown in FIG. 27 (step S303). The CPU 21 determines whether or not a music data transmission request based on the recommended capo position information has been received from the input unit 23 (step S304). Specifically, it is determined whether or not the hyperlink 242 shown in FIG. 27 has been operated. If the CPU 21 determines that a song data transmission request based on recommended capo position information has been received (YES in step S304), the CPU 21 transmits a song data transmission request based on recommended capo position information to the server computer 3 (step S304). S305). The CPU 31 of the server computer 3 receives a music data transmission request based on the recommended capo position information via the communication unit 36.

  On the other hand, if the CPU 21 determines that the music data transmission request based on the recommended capo position has not been received (NO in step S304), whether or not the music data transmission request based on the auxiliary recommended capo position has been received from the input unit 23 is determined. Judgment is made (step S306). Specifically, it is determined whether or not the hyperlink 243 shown in FIG. 27 has been operated. If the CPU 21 determines that the music data transmission request based on the auxiliary recommended capo position information has been received (YES in step S306), the CPU 21 transmits a music data transmission request based on the auxiliary recommended capo position information to the server computer 3. (Step S307). The CPU 31 of the server computer 3 accepts a music data transmission request based on the auxiliary recommended capo position information via the communication unit 36.

  On the other hand, if the CPU 21 determines that the music data transmission request based on the auxiliary recommended capo position information has not been accepted (NO in step S306), the CPU 21 determines that the hyperlink 241 has been clicked and transmits the music data without the capo. The request is transmitted to the server computer 3 (step S308). The CPU 31 of the server computer 3 accepts a request for transmission of song data without capo via the communication unit 36.

  The CPU 31 determines whether or not a music data transmission request based on the recommended capo position information has been received (step S309). If the CPU 31 determines that the music data transmission request based on the recommended capo position information has been received (YES in step S309), the CPU 31 reads the music data based on the recommended capo position from the music data file 351 and transmits it to the mobile phone 2 (step). S311). If the CPU 31 determines that the music data transmission request based on the recommended capo position has not been received (NO in step S309), the CPU 31 determines whether a music data transmission request based on the auxiliary recommended capo position information has been received (step S309). S312). If the CPU 31 determines that the music data transmission request based on the auxiliary recommended capo position information has been received (YES in step S312), the CPU 31 reads the music data based on the auxiliary recommended capo position from the music data file 351 and transmits it to the mobile phone 2. (Step S313).

  On the other hand, if the CPU 31 determines that the music data transmission request based on the auxiliary recommended capo position information has not been received (NO in step S312), the CPU 31 reads the music data at the capo position “0” from the music data file 351, and 2 (step S314). The CPU 21 of the mobile phone 2 receives the song data transmitted from the server computer 3 (step S315). The CPU 21 activates the reproduction application 252 (step S316). The CPU 21 reproduces music data (step S317) and outputs music from the microphone 28. The CPU 21 synchronizes the display timing of the music data, the chord data, and the lyric data using the date / time information output from the clock unit 210 triggered by the reproduction of the music data. In synchronization with the reproduction of the music data, the CPU 21 refers to the display time and display position of the chord and lyrics, and displays the chord and lyrics on the display unit 24 (step S318). In this case, when the song data based on step S311 is transmitted, the performance based on the recommended capo position is possible. Further, when the song data based on step S313 is transmitted, the performance based on the auxiliary recommended capo position can be performed. On the other hand, when the song data based on step S314 is transmitted, the performance without the capo is possible.

  The third embodiment is configured as described above, and the other configurations and operations are the same as those of the first and second embodiments. Therefore, corresponding parts are denoted by the same reference numerals, and detailed description thereof is omitted. To do.

Embodiment 4
FIG. 33 is a block diagram showing a configuration of the personal computer 1 according to the fourth embodiment. The computer program for operating the personal computer 1 according to the fourth embodiment can be provided by a portable recording medium 1A such as a CD-ROM, MO, or DVD-ROM as in the fourth embodiment. It is. Further, the computer program can be downloaded from a server computer (not shown) via the communication network N. The contents will be described below.

  A portable recording medium 1A (CD-ROM, MO or DVD-ROM) on which a computer program for extracting a code and counting the number is read by a reader / writer (not shown) of the personal computer 1 shown in FIG. And the like are installed in the control program 15P of the storage unit 15. Alternatively, such a program may be downloaded from an external server computer (not shown) via the communication unit 16 and installed in the storage unit 15. Such a program is loaded into the RAM 12 and executed. Thereby, it functions as the personal computer 1 as described above.

  The fourth embodiment is configured as described above, and the other configurations and operations are the same as those of the first to third embodiments. Therefore, the corresponding parts are denoted by the same reference numerals and detailed description thereof is omitted. To do.

Embodiment 5
The fifth embodiment relates to a method for determining a recommended capo position in consideration of the total number of codes. FIG. 34 is an explanatory diagram showing a record layout of the summary file 152 according to the fifth embodiment. In addition to the configuration of the first embodiment, an auxiliary difficulty level field is prepared. The auxiliary difficulty level field stores the auxiliary difficulty level required when determining the recommended capo position for each capo position. The procedure for calculating the auxiliary difficulty level will be described below.

  First, the CPU 11 counts the total number of codes present in the music data. This processing can also be calculated by summing up the number of codes stored in the number field at any capo position in the total file 152. The CPU 11 obtains the auxiliary difficulty level by dividing the total value of the difficulty levels of each capo position by the total number counted and multiplying by 100. The CPU 11 determines the capo position having the smallest auxiliary difficulty level as the recommended capo position. In the example of FIG. 34, the total difficulty level of the capo position “1” is divided by the total number of codes (for example, 400) and further multiplied by 100 to obtain an auxiliary difficulty level of 25.00.

  This makes it possible to objectively obtain the recommended capo position based on the auxiliary difficulty per code regardless of the number of codes. FIG. 35 is a flowchart showing a procedure for determining a recommended capo position based on the auxiliary difficulty level. The CPU 11 sets an initial value 0 at the capo position (step S351). The CPU 11 refers to the music data file 151 in which codes are stored in time series, and counts the total number of codes existing in the target music data (step S352). This process counts the total number of all codes stored, including code duplication.

  The CPU 11 refers to the total file 152 and calculates the total difficulty level (step S353). The CPU 11 divides the total value by the total number and multiplies it by 100 to calculate the auxiliary difficulty level (step S354). The CPU 11 stores the calculated auxiliary difficulty level in the auxiliary difficulty field of the tabulation file 152 in association with the capo position (step S355). The CPU 11 determines whether or not the above-described processing has been completed for all capo positions (step S356). If the CPU 11 determines that the process has not been completed for all capo positions (NO in step S356), the capo position is incremented (step S357), the process is returned to step S353 again, and the auxiliary difficulty level of each capo position is determined. Is calculated.

  If the CPU 11 determines that the processing has been completed for all capo positions (YES in step S356), the CPU 11 extracts the capo position having the smallest assist difficulty level and determines the capo position as the recommended capo position (step S358). The CPU 11 stores the determined recommended capo position in association with the song data in the recommended capo position file 154 (step S359).

  The fifth embodiment has the above-described configuration, and the other configurations and operations are the same as those of the first to fourth embodiments. Therefore, the corresponding parts are denoted by the same reference numerals and detailed description thereof is omitted. To do.

Embodiment 6
The sixth embodiment relates to a form in which the recommended capo position is corrected based on the degree of auxiliary difficulty. Even if the CPU 11 has the minimum assistance difficulty level, if the assistance difficulty level is too high, it is less meaningful to recommend the capo position corresponding to the assistance difficulty level. In this case, the capo position “0” indicating that the capo is not attached is determined as the recommended capo position. FIG. 36 is a flowchart showing a procedure of recommended capo position determination processing according to the sixth embodiment.

  The CPU 11 reads the capo position having the smallest auxiliary difficulty level calculated in the fifth embodiment with reference to the aggregation file 152 (step S361). The CPU 11 reads a predetermined value stored in advance in the storage unit 15 (step S362). This predetermined value can be appropriately changed from the input unit 13, and for example, 35 is stored. The CPU 11 determines whether or not the minimum auxiliary difficulty level read in step S361 is a predetermined value or less (step S363).

  When the CPU 11 determines that the value is equal to or less than the predetermined value (YES in step S363), as described in the fifth embodiment, the capo position having the smallest assist difficulty is determined as the recommended capo position (step S364). On the other hand, if the CPU 11 determines that it is not equal to or less than the predetermined value (NO in step S363), since it is not meaningful to play until the capo tast is attached, the capo position “0” indicating no capo is used as the recommended capo position. (Step S365). The CPU 11 stores the recommended capo position determined in step S364 or S365 in the recommended capo position file 154 in association with the music data (step S366). This makes it possible to provide more appropriate advice to a beginner by proposing not to wear a capo when a high level of skill is required for performance even if the assistance difficulty is minimal.

  The sixth embodiment has the above-described configuration, and the other configurations and operations are the same as those of the first to fifth embodiments. Therefore, the corresponding parts are denoted by the same reference numerals and detailed description thereof is omitted. To do.

Embodiment 7
In the seventh embodiment, a capo position having the minimum auxiliary difficulty level is determined as a recommended capo position when the difference between the auxiliary difficulty level and the minimum auxiliary difficulty level relating to a predetermined capotast position serving as a reference is equal to or greater than a predetermined value. About. In other words, even if the auxiliary difficulty level is minimum, it is less meaningful to dare to recommend a capo if there is no significant difference when compared with the auxiliary difficulty level related to the predetermined capo-tasto position as a reference. In the following description, it is assumed that the predetermined capotast position serving as a reference is the capo position “0” where no capo is attached. FIG. 37 is a flowchart showing a procedure of recommended capo position determination processing according to the seventh embodiment.

  The CPU 11 reads the capo position having the smallest auxiliary difficulty obtained by the processing of the fifth embodiment (step S371). The CPU 11 determines whether or not the capo position read out in step S371 is different from the capo position “0” indicating the absence of a capo, which is a predetermined capo position (step S372). If the CPU 11 determines that there is no difference (NO in step S372), the capo position “0” is determined as the recommended capo position as in the fifth embodiment, and the recommended capo position “0” is stored in the recommended capo position file 154 as song data. Store it in association with. In this case, it is best not to wear the capo, and the series of processing ends.

  On the other hand, when it is determined that the CPU 11 is different (YES in step S372), a predetermined value (for example, 10) stored in advance is read from the storage unit 15 (step S373). The CPU 11 refers to the summary file 152 and calculates the difference between the minimum auxiliary difficulty level read in step S371 and the auxiliary difficulty level of the capo position “0” (step S374). The CPU 11 determines whether or not the calculated difference is greater than or equal to the predetermined value read in step S373 (step S375).

  If the CPU 11 determines that the difference is equal to or greater than the predetermined value (YES in step S375), the CPU 11 determines that it is meaningful to play with the capo installed at the recommended capo position, and recommends the capo position with the minimum assistance difficulty. The capo position is determined (step S376). On the other hand, if the CPU 11 determines that the difference is not equal to or smaller than the predetermined value (NO in step S375), the CPU 11 determines that it is not meaningful to dare to install the capo, and sets the capo position “0” indicating no capo as the recommended capo position. Determination is made (step S377). The CPU 11 stores the recommended capo position determined in step S376 or S377 in the recommended capo position file 154 in association with the music data (step S378). This makes it possible to provide the user with a capo position that can more effectively reduce the performance burden as compared with the case where no capo is attached. In addition, it is possible to objectively show to the user that it is better not to wear the capo, and it is possible to provide more appropriate advice to beginners.

  The seventh embodiment has the above-described configuration, and the other configurations and operations are the same as those of the first to sixth embodiments. Therefore, the corresponding parts are denoted by the same reference numerals and detailed description thereof is omitted. To do.

The following additional notes are further disclosed with respect to the embodiments including the first to seventh embodiments.
(Appendix 1)
When there is a string to be pressed by the other finger of the chord determined by the determining means with reference to a string to be pressed by another finger different from the one finger for each chord stored in the chord file, Auxiliary point giving means for giving an auxiliary point lower than the point to the cord is provided,
The difficulty determination means includes
Multiplying the value obtained by adding the auxiliary point of the code given by the auxiliary point giving means to the code point given by the giving means and the number of each code corresponding to each capotaspo position determined by the determining means By the above, it is comprised so that the difficulty level of each capotaspo position may be determined, The capotast position determination apparatus characterized by the above-mentioned.

It is a block diagram which shows the hardware constitutions of a capo position determination apparatus. It is explanatory drawing which shows the record layout of a music data file. It is explanatory drawing which shows the record layout of a total file. It is explanatory drawing which shows a modulation rule. It is explanatory drawing which shows the record layout of a code file. It is explanatory drawing which shows the diagram displayed on a display part. It is explanatory drawing which shows the record layout of the total file after point totalization. It is explanatory drawing which shows the record layout of a recommended capo position file. It is a flowchart which shows the procedure of a code extraction process and a count process. It is a flowchart which shows the procedure of a code extraction process and a count process. It is a flowchart which shows the procedure of a recommendation capo position determination process. It is a flowchart which shows the procedure of a recommendation capo position determination process. It is explanatory drawing which shows the outline | summary of a music data transmission system. It is a block diagram which shows the hardware constitutions of a server computer. It is explanatory drawing which shows the record layout of a music data file. It is explanatory drawing which shows the image of music selection. It is explanatory drawing which shows the display image of a code | cord | chord. It is a flowchart which shows the procedure of the transmission process of music data. It is a flowchart which shows the procedure of the transmission process of music data. It is a flowchart which shows the procedure of the transmission process of music data. FIG. 10 is a block diagram illustrating a hardware configuration of a capo position determination device according to a third embodiment. FIG. 10 is an explanatory diagram showing a record layout of a summary file according to a third embodiment. It is explanatory drawing which shows the record layout of an auxiliary recommendation capo position file. It is a flowchart which shows the procedure at the time of determining an auxiliary recommendation capo position. It is a flowchart which shows the procedure at the time of determining an auxiliary recommendation capo position. FIG. 10 is a block diagram illustrating a hardware configuration of a server computer according to a third embodiment. It is explanatory drawing which shows the example of a transmission request screen of music data. It is a flowchart which shows the procedure of the transmission process of music data. It is a flowchart which shows the procedure of the transmission process of music data. It is a flowchart which shows the procedure of the transmission process of music data. It is a flowchart which shows the procedure of the transmission process of music data. It is a flowchart which shows the procedure of the transmission process of music data. FIG. 10 is a block diagram illustrating a configuration of a personal computer according to a fourth embodiment. FIG. 10 is an explanatory diagram showing a record layout of a summary file according to a fifth embodiment. It is a flowchart which shows the procedure of the recommendation capo position determination based on an auxiliary difficulty level. 18 is a flowchart illustrating a procedure of recommended capo position determination processing according to the sixth embodiment. 18 is a flowchart showing a procedure of recommended capo position determination processing according to Embodiment 7.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Personal computer 1A Portable recording medium 2 Mobile phone 3 Server computer 11 CPU (control part)
DESCRIPTION OF SYMBOLS 15 Memory | storage part 15P Control program 16 Communication part 18 Clock part 21 CPU (control part)
23 Input unit 24 Display unit 25 Storage unit 25P Control program 251 Browser 252 Playback application 26 Communication unit 28 Microphone 29 Speaker 210 Clock unit 31 CPU
35 storage unit 36 communication unit 151 music data file 152 total file 153 code file 154 recommended capo position file 155 auxiliary recommended capo position file 241 hyperlink 242 hyperlink 243 hyperlink 351 music data file 354 recommended capo position file 355 auxiliary recommended capo position File N communication network

Claims (10)

In a capo last position determining device that determines a recommended capo last position from a plurality of capo last positions,
Extracting means for extracting chords existing in song data including plural types of chords;
Counting means for counting the number of each code extracted by the means in the music data;
Determining means for determining a code corresponding to each capotast position and the number of each code based on the code extracted by the extracting means and the number of each code counted by the counting means;
Referencing a chord file storing how to hold a string according to a chord, and when the chord determined by the deciding means satisfies a predetermined condition, an attaching means for giving a point to the chord;
A difficulty level determining means for determining the difficulty level of each capo last position based on the number of codes corresponding to the point of the code given by the giving means and the number of each code point determined by the determining means. Capotast position determination device. The giving means is
Reference is made to the number of strings to be pressed by one finger for each chord stored in the chord file, and when the number of strings to be pressed by one finger of the chord determined by the determining means is greater than or equal to the number stored in advance, 2. The capostat position determining device according to claim 1, wherein a point is given to the code. The difficulty determination means includes
It is configured to determine the difficulty level of each capotast position by multiplying the number of codes corresponding to each capotast position determined by the determination means by adding to the point of the code given by the giving means,
3. The capostat position determining device according to claim 1, further comprising: a recommended capostat position determining unit that determines a capostat position having the minimum difficulty determined by the difficulty level determining unit as a recommended capostat position. 4. Total number counting means for counting the total number of chords in the song data;
The auxiliary difficulty level determining means for determining the auxiliary difficulty level by dividing the difficulty level of each capotast position determined by the difficulty level determining means by the total number counted by the total number counting means. Or the capostat position determining apparatus according to 2; The capostat position determining device according to claim 4, further comprising: a unit that determines a capostat position having the minimum auxiliary difficulty level determined by the auxiliary difficulty level determining unit as a recommended capostat position. The said assisting difficulty determination means is provided with a means to determine as a recommended capotast position, when the said assisting difficulty of the capotast position with the smallest assisting difficulty determined below is a predetermined value or less. Capotast positioning device. Auxiliary extraction means for extracting the auxiliary difficulty level related to a predetermined capotast position from the auxiliary difficulty level of each capostat position determined by the auxiliary difficulty level determination means,
The capotast position with the smallest assist difficulty determined by the assist difficulty determining means is different from the predetermined capotast position, and the assist difficulty related to the minimum capotast position and the assist difficulty related to the predetermined capotast position Means for determining the minimum capostat position as a recommended capostat position when the difference from the degree is equal to or greater than a predetermined value ;
It said predetermined capo position, capotasto locating device according to claim 4, wherein the capo location der Rukoto not wearing the capo. Accepting means for accepting either the music data transmission request from the outside or the music data transmission request based on the recommended capotast position determined by the capostat position determining device according to any one of claims 1 to 7. ,
A song data transmission comprising: a transmission means for transmitting song data based on the recommended capotast position stored in the storage unit to the outside when a reception request for song data based on the recommended capotast position is received by the receiving means. apparatus. In a capo last position determining method for determining a recommended capo last position from a plurality of capo last positions by a capo last position determining device having a control unit,
An extraction step of extracting, by the control unit, codes existing in song data including a plurality of types of codes;
A counting step in which the number of each chord extracted in the step is present in the music data is counted by the control unit;
A determination step of determining, by the control unit, the code corresponding to each capotast position and the number of each code based on the code extracted by the extraction step and the number of each code counted by the counting step;
Referencing a chord file storing how to press a string according to chords, and when the chord determined by the deciding step satisfies a predetermined condition, an assigning step of giving points to the chord by the control unit;
A determination step of determining a difficulty level of each capotast position by the control unit based on the number of codes corresponding to each point of the codepotast determined in the determination step and the point of the code provided in the determination step. Capotast position determination method. In a program for determining a recommended capostat position from a plurality of capostat positions by a computer having a control unit,
On the computer,
An extraction step of extracting, by the control unit, codes existing in song data including a plurality of types of codes;
A counting step in which the number of each chord extracted in the step is present in the music data is counted by the control unit;
A determination step of determining, by the control unit, the code corresponding to each capotast position and the number of each code based on the code extracted by the extraction step and the number of each code counted by the counting step;
Referencing a chord file storing how to press a string according to chords, and when the chord determined by the deciding step satisfies a predetermined condition, an assigning step of giving points to the chord by the control unit;
A program for executing a determination step of determining a difficulty level of each capotast position by the control unit based on a point of the code provided by the application step and the number of codes corresponding to each capotast position determined by the determination step.

Images