Acoustic device, server device, library provision system, and download program

Abstract

This acoustic device includes: a request unit that requests download of a first library stored in a storage on a cloud; and a download unit that downloads a second library obtained by a server device on the cloud filtering a list of pieces of music included in the first library on the basis of an operation history added as metadata to each piece.

Description

Audio device, server device, library providing system, and download program

[0001] The present invention relates to an audio device, a server device, a library providing system, and a download program.

[0002] A library providing function is provided that enables a DJ software library stored in cloud storage to be used for DJ performances on an audio device such as a player for DJs (Disc Jockeys).

[0003] International Publication No. 2020 / 059008

[0004] However, as the size of the library increases, the size of the data that the audio device downloads also increases, which has the side effect of increasing the time required for downloading.

[0005] For example, some DJ software users have libraries with tens of thousands of songs, which can take an enormous amount of time to download. When download times are prolonged, the DJ must wait until the download is complete before starting the performance, reducing usability. Furthermore, when a single sound system is shared by multiple DJs at a live venue, it can be difficult to smoothly switch DJs, which can disrupt the excitement of the live performance.

[0006] In one aspect, an object of the present invention is to provide an audio device, a server device, a library providing system, and a download program that can reduce the time required to download a library.

[0007] In one aspect, the audio device has a request unit that requests the download of a first library stored in cloud storage, and a download unit that downloads a second library that is a list of songs included in the first library narrowed down by a server device on the cloud based on operation history added to the songs as metadata.

[0008] According to one embodiment, the time required to download a library can be reduced.

[0009] FIG. 1 is a diagram showing an example of the configuration of a library providing system. FIG. 2 is a block diagram showing an example of the functional configuration of a server device and an audio device. FIG. 3 is a schematic diagram showing an example of metadata. FIG. 4 is a diagram showing an example of a narrowing setting file. FIG. 5 is a diagram (1) showing an example of narrowing down. FIG. 6 is a diagram (2) showing an example of narrowing down. FIG. 7 is a schematic diagram explaining uploading of operation history. FIG. 8 is a sequence diagram showing the procedure of a library providing process. FIG. 9 is a flowchart showing the procedure of a narrowing down process. FIG. 10 is a flowchart showing the procedure of a narrowing down process according to an application example. FIG. 11 is a diagram showing an example of a hardware configuration.

[0010] Hereinafter, embodiments for implementing an audio device, a server device, a library providing system, and a download program according to the present disclosure (hereinafter referred to as "embodiments") will be described with reference to the accompanying drawings. Note that the embodiments merely illustrate one example or aspect, and the structures, actions, functions, properties, characteristics, methods, uses, etc. according to the present disclosure are not limited by such examples.

[0011] <First embodiment> <System configuration example> Fig. 1 is a diagram showing an example of the configuration of a library providing system 1. Fig. 1 shows an example of a library providing system 1 that provides a library providing function of providing a DJ software library 11L stored in cloud storage using a cloud storage service for use in DJ performances.

[0012] As shown in FIG. 1, the library providing system 1 may include a server device 10 , a user terminal 20 , and an audio device 30 .

[0013] The server device 10, the user terminal 20, and the audio device 30 may be communicably connected via any network NW. For example, the network NW may be realized by any technology, whether wired or wireless, such as an intranet, the Internet, or a low-power wireless communication standard for the Internet of Things (IoT). Note that the network NW may not be a single network, but may instead be a network in which an intranet and the Internet are connected via a network device such as a gateway.

[0014] The server device 10 is a computer that provides a cloud storage service and a library providing function. For example, the server device 10 can be realized as a Software as a Service (SaaS) type application. This allows the cloud storage service and the library providing function to be provided as cloud services. Note that the server device 10 does not prevent the cloud storage service and the library providing function from being provided on-premises.

[0015] The user terminal 20 is a terminal device used by a user of the DJ software. For example, the user terminal 20 may be realized by any computer, including a desktop or laptop personal computer 20A, or a mobile terminal 20B such as a smartphone, tablet terminal, or wearable terminal.

[0016] The sound device 30 is a device having a function for playing music for DJs. For example, the sound device 30 may be realized as a music player for DJs, a so-called DJ player. Alternatively, the sound device 30 may be realized as a DJ system in which multiple DJ players are connected to a DJ mixer via multiple channels.

[0017] <User> The term "user" here refers to a person who has an account that integrates various services, including DJ software, cloud storage services, and library provision functions. Naturally, the above-mentioned user is not limited to professional DJs, and may include a wide range of users, from light users to heavy users. Note that while an example is given here in which accounts for multiple services are integrated, accounts may also be issued for each individual service.

[0018] <Library> As part of the music management function provided by the DJ software, a library 21L listing a collection of songs imported into the DJ software may be created independently of the music content data files on the user terminal 20. Note that the library may include not only individual songs but also albums, playlists, and the like.

[0019] Such a library 21L has a history of various operations added as metadata. For example, the operation history may include a history of operations related to operational items such as an operation for DJ editing a song, an operation for DJing a performance using a song, and an operation for importing a song.

[0020] <Cloud Storage Service> The cloud storage service is a service that manages a DJ software library in cloud storage. The library 11L saved in this cloud storage is synchronized with the library 21L on the user terminal 20 on which the DJ software runs.

[0021] 1, the user terminal 20 accepts various operations related to the DJ software (S01). Based on the operations accepted by the user terminal 20 in this manner, the DJ software updates the library 21L on the user terminal 20 (S02).

[0022] For example, when a new song is imported, the new song is added to the collection in the library 21L, and an operation history such as the date and time of import is added as metadata for the new song. When a song is played, an operation history such as the date and time of playback is added as metadata for the song. In addition, when a song is DJ-edited, an operation history such as the settings used for DJ editing is added as metadata for the song.

[0023] The DJ editing described above may include preparation work unique to a DJ, such as setting point information such as memory cues and loops, a hot cue bank list listing one or more combinations of hot cues, and settings such as beat grids and BPM (Beats Per Minute).

[0024] Thereafter, the user terminal 20 uploads the operation history used to update the library 21L in step S02 to the server device 10 (S03). The server device 10 then updates the library 11L stored in the cloud storage based on the operation history uploaded in step S03 (S04).

[0025] Through the series of processes from step S01 to step S04, the library 11L stored in the cloud storage and the library 21L on the user terminal 20 on which the DJ software runs are synchronized.

[0026] Hereinafter, the following descriptions may be used to distinguish between the three types of libraries: a library stored in cloud storage, a library managed by DJ software running on the user terminal 20, and a library downloaded to the audio device 30. In other words, the three types of libraries may be referred to as a "cloud library," a "device library," and a "DL library," respectively.

[0027] <One aspect of the problem> As explained in the background art section above, in the library provision function according to the above-mentioned conventional technology, as the size of the library 11L on the cloud increases, the size of the data downloaded by the audio device 30 also increases, which has the side effect of increasing the time required for downloading.

[0028] For example, some DJ software users may have tens of thousands of songs in their cloud library 11L, which can take an enormous amount of time to download the cloud library 11L. When download times are prolonged, the DJ must wait until the download is complete before starting the performance, reducing usability. Furthermore, when a single sound device 30 is shared by multiple DJs at a live venue, it can be difficult to smoothly switch DJs, potentially disrupting the excitement of the live performance.

[0029] <One aspect of the problem-solving approach> Therefore, the server device 10 according to this embodiment provides a library provision function that provides a DL library 35L that narrows down a list of songs included in the cloud library 11L based on operation history added to the songs as metadata.

[0030] In addition, the audio device 30 according to this embodiment provides a download function for downloading a DL library 35L in which a list of songs included in the cloud library 11L is narrowed down based on an operation history in which the songs are added as metadata.

[0031] That is, not all of the songs in the cloud library 11L are used during a DJ performance. For example, as the number of songs registered in the cloud library 11L increases, it becomes more difficult to use all of the songs.

[0032] Based on this idea, in this embodiment, songs that are unlikely to be used in DJ performances are excluded from the DL library 35L, and the DL library 35L narrowed down to songs that are likely to be used in DJ performances is downloaded to the audio device 30.

[0033] 1, the audio device 30 requests the download of the cloud library 11L (S11). For example, when an account is authenticated by inserting a removable medium storing an authentication key that has been authenticated in advance by DJ software, the audio device 30 can request the download of the cloud library 11L of the user corresponding to the account.

[0034] Upon receiving this download request, the server device 10 narrows down the list of songs included in the cloud library 11L based on the operation history added to the songs as metadata (S12).

[0035] In this way, the DL library 35L narrowed down from the cloud library 11L based on the operation history in step S12 is downloaded from the server device 10 to the audio device 30 (S13).

[0036] Through the series of processes from step S11 to step S13, songs from the cloud library 11L that are likely to be used in DJ performances are narrowed down based on the operation history to be downloaded to the DL library 35L to the audio device 30. As a result, the size of the DL library 35L to be downloaded to the audio device 30 can be made smaller than that of the cloud library 11L.

[0037] Therefore, the server device 10 and the audio device 30 according to this embodiment can shorten the download time of the DL library 35L. As one aspect, the shortened download time allows for quicker DJ changes at live venues and the like, enabling seamless DJ changes. Ultimately, this can prevent the excitement of a live performance from dropping when a DJ changes. As another aspect, the DL library 35L is less likely to include songs that are unlikely to be used in DJ performances. For example, songs that were used long ago but are no longer used are less likely to be included. In this way, information that hinders user selection is eliminated from the DL library 35L, making it easier for users to find songs they want to see DJed.

[0038] <Configuration of Server Device 10> Next, the functional configuration of the server device 10 according to this embodiment will be described. Fig. 2 is a block diagram showing an example of the functional configuration of the server device 10 and the audio device 30. For example, Fig. 2 shows a schematic diagram of blocks related to functions related to the library providing function of the server device 10.

[0039] 2, the server device 10 includes a library storage unit 11, a music storage unit 12, a narrowing-down unit 13, a library transmission unit 14, a library update unit 15, and a music transmission unit 16. Note that Fig. 2 only shows a selection of functional units related to the above-described library provision function, and the server device 10 may also include functional units other than those shown in the figure.

[0040] The library storage unit 11 is a functional unit that stores the cloud library 11L. In one aspect, the cloud library 11L may be synchronized with the device library 21L by the cloud storage service described with reference to FIG.

[0041] FIG. 3 is a schematic diagram illustrating an example of metadata. As shown in FIG. 3, the library storage unit 11 stores a cloud library 11L for each user's identification information, for example, a user ID (ID). Operation history is added as metadata to songs and playlists included in the collection of this cloud library 11L. Examples of such operation history may include history related to operation items such as a "playback operation" for playing songs, a "DJ editing operation" for DJ editing songs, a "DJ performance operation" for performing a DJ performance using songs, and an "import operation" for importing songs. For example, the history of a "DJ editing operation" may include point information such as memory cues and loops, a hot cue bank list listing combinations of one or more hot cues, and settings such as beat grids and BPM.

[0042] The music storage unit 12 is a functional unit that stores music. In one embodiment, the music storage unit 12 stores, for each user ID, data files of music content imported via DJ software by a user identified by the user ID.

[0043] The narrowing unit 13 is a processing unit that narrows down the list of songs included in the cloud library 11L based on operation histories added as metadata to the songs in the cloud library 11L.

[0044] Below, as just one example, we will give an example of narrowing down the cloud library 11L on demand after receiving a download request.However, as will be described in detail later, we would like to add that narrowing down can also be performed in advance at a point before the request is received.

[0045] In one aspect, the narrowing-down unit 13 receives a request to download the cloud library 11L from the audio device 30. The narrowing-down unit 13 then acquires the cloud library 11L corresponding to the account of the user ID specified in the request from among the cloud libraries stored for each user ID in the library storage unit 11. The narrowing-down unit 13 then narrows down the songs included in the cloud library 11L based on the operation history.

[0046] Here, the narrowing unit 13 does not necessarily have to narrow down the cloud library 11L unconditionally, because there may be some users whose cloud library 11L is not so large that it would cause problems in terms of the storage performance of the audio device 30 or the download transmission time.

[0047] Therefore, the narrowing-down unit 13 can narrow down the cloud library 11L on the condition that the cloud library 11L exceeds a predetermined capacity. This allows the narrowing-down unit 13 to narrow down the cloud library 11L only under circumstances where there is a high possibility that the download of the cloud library 11L will take a long time.

[0048] In one aspect, the capacity threshold that determines whether or not narrowing down is necessary may be set through an instruction input by the user of the audio device 30. Alternatively, the capacity threshold may be set according to a contract plan that the user of the audio device 30 subscribes to when subscribing to a service such as the download function or the library providing function.

[0049] In another aspect, the capacity threshold that determines whether or not narrowing down is necessary can be set based on the storage capacity of the audio device 30. For example, the capacity threshold can be dynamically set for each model or model number of the audio device 30 based on the catalog specifications corresponding to that model or model number. In this case, when the audio device 30 sends a download request to the server device 10, the audio device 30 can be made to notify the type of the audio device 30, such as the model or model number. In addition, when a download request is made, the audio device 30 can be made to notify the free space in the storage of the audio device 30. This can prevent download failures due to insufficient storage capacity of the audio device 30.

[0050] As one aspect, the narrowing unit 13 can narrow down the songs included in the cloud library 11L to songs that satisfy the narrowing conditions related to the operation items, in accordance with the narrowing setting file shown in FIG.

[0051] 4 is a diagram showing an example of a filter setting file. As shown in FIG. 4, the first line of the filter setting file indicates that the target capacity for filtering the songs in the cloud library 11L is determined by the "number of songs." The second line indicates that the songs in the cloud library 11L are set to be filtered down to "100 songs." The target filter value "100 songs" given here may be used as an example of the capacity threshold. The third line indicates that the number of operation items used for filtering the cloud library 11L is set to "3."

[0052] Lines 4 to 7 indicate that the priority of the operation items used to narrow down the cloud library 11L is set as follows, in descending order: operation item 1 "Last DJ performance date and time," operation item 2 "Last DJ edit date and time," and operation item 3 "Import date and time."

[0053] The technical significance of setting the priority of operational items as "Last DJ performance date and time > Last DJ edit date and time > Import date and time" is as follows: The reason why the priority of the last DJ performance date and time is set to first is because a song used in a recent DJ performance is likely to be used in the next DJ performance. The reason why the priority of the last DJ edit date and time is set to second is because, although a song that was recently DJ edited is likely to be used in the next DJ performance, there is a possibility that the DJ may not be satisfied with the completion or quality of the edit, so it is set to a lower priority than the DJ performance. The reason why the priority of the import date and time is set to third is because there is a possibility that multiple songs may have been imported at once when importing an album, etc., leaving open the possibility that songs other than those desired for the DJ performance may have been imported as well, so it is set to a lower priority.

[0054] The eighth line indicates that the setting is to narrow down the songs to those that satisfy three narrowing conditions corresponding to three operation items, namely, the last DJ performance date and time, the last DJ edit date and time, and the import date and time, using an "AND condition."

[0055] Lines 9 to 11 indicate that the three thresholds Th1 to Th3 that are compared with the three operation items of last DJ performance date and time, last DJ edit date and time, and import date and time are set to "6 months," "3 months," and "6 months."

[0056] 4 may be set by a service provider, such as a developer or system administrator, who provides services such as the download function and the library provision function. Furthermore, the filter setting file may be customized for each user. When the filter setting file is configured differently for each user, different filtering may be achieved for each user.

[0057] The following describes the filtering process performed in accordance with this filtering setting file. Specifically, the filtering unit 13 references the last DJ performance date and time in the operation history included in the metadata of each song included in the cloud library 11L, and sorts the song IDs included in the cloud library 11L in descending order, starting with the most recent last DJ performance date and time. Songs for which there is no DJ performance operation history may be sorted at the end, since they have not been performed by a DJ.

[0058] Next, the narrowing-down unit 13 repeats the following process until the target value set in the narrowing-down setting file is reached. That is, the narrowing-down unit 13 selects the i-th song ID from a list of song IDs sorted in order of most recent last DJ performance date and time. Then, the narrowing-down unit 13 determines narrowing-down condition 1, which is whether the last DJ performance date and time of the i-th song ID is within threshold value Th1, for example, six months from the current date and time, for example, the date and time when the download request was received. Next, if the last DJ performance date and time is within threshold value Th1, the narrowing-down unit 13 determines narrowing-down condition 2, which is whether the last DJ edit date and time of the i-th song ID is within threshold value Th2, for example, three months from the current date and time. Then, if the last DJ edit date and time is within threshold value Th2, the narrowing-down unit 13 determines narrowing-down condition 3, which is whether the import date and time of the i-th song ID is within threshold value Th3, for example, six months from the current date and time.

[0059] If the three narrowing conditions, narrowing condition 1 to narrowing condition 3, are satisfied by an AND condition, the narrowing unit 13 adds the i-th song ID to the DL library 35L. On the other hand, if any one or more of the three narrowing conditions, narrowing condition 1 to narrowing condition 3, are not satisfied, the narrowing unit 13 excludes the i-th song ID and does not add it to the DL library 35L.

[0060] 5 and 6 are diagrams (1) and (2) showing examples of narrowing down. Fig. 5 and Fig. 6 show an example in which narrowing down is performed using three narrowing down conditions set in the narrowing down setting file shown in Fig. 4. It should be noted that Fig. 5 and Fig. 6 show an example in which the current date and time is February 2, 2024.

[0061] For example, FIG. 5 shows an example of determining whether song ID "XXXXX" among songs included in cloud library 11L satisfies filtering conditions 1 to 3. As shown in FIG. 5, the last DJ performance date and time of song ID "XXXXX," "January 10, 2024," is within six months of the current date and time, "February 2, 2024." Furthermore, the last DJ edit date and time of song ID "XXXXX," "December 28, 2023," is within three months of the current date and time, "February 2, 2024." Furthermore, the import date and time of song ID "XXXXX," "November 11, 2023," is within six months of the current date and time, "February 2, 2024." In this way, song ID "XXXXX" satisfies the three filtering conditions, filtering conditions 1 to 3, using the AND condition, and therefore song ID "XXXXX" is added to DL library 35L.

[0062] On the other hand, Figure 6 shows an example of determining whether song ID "XXXXX" from among the songs included in the cloud library 11L satisfies filtering conditions 1 to 3. As shown in Figure 6, the last DJ performance date and time of song ID "YYYYY" (July 8, 2023) is not within six months of the current date and time (February 2, 2024). On the other hand, the last DJ edit date and time of song ID "YYYYY" (December 28, 2023) is within three months of the current date and time (February 2, 2024). Furthermore, the import date and time of song ID "YYYYY" (November 11, 2023) is within six months of the current date and time (February 2, 2024). In this way, since the song ID "YYYYY" does not satisfy narrowing condition 1 and does not satisfy the three narrowing conditions, narrowing condition 1 to narrowing condition 3, in an AND condition, the song ID "YYYYY" is not excluded and is not added to the DL library 35L.

[0063] In this way, by narrowing down the songs in the cloud library 11L to those that satisfy filtering conditions 1 to 3, it is possible to exclude songs that are unlikely to be used in the next DJ performance and extract songs that are likely to be used in the next DJ performance.

[0064] Returning to the explanation of FIG. 2, the library transmitting unit 14 is a processing unit that transmits the DL library 35L obtained as a result of the narrowing down by the narrowing down unit 13 to the audio device 30 that has made the download request.

[0065] The library update unit 15 is a processing unit that updates the cloud library 11L based on the operation history uploaded from the audio device 30. In one aspect, the library update unit 15 updates the cloud library 11L corresponding to the account of the user ID specified at the time of uploading, among the cloud libraries 11L stored for each user in the library storage unit 11.

[0066] In one aspect, when a new song is imported, the library update unit 15 adds the new song to the collection of the cloud library 11L and adds an operation history, such as the date and time of the import, as metadata for the new song. In another aspect, when a song is DJ-performed, the library update unit 15 adds an operation history, such as the date and time of the DJ performance, as metadata for the song. In a further aspect, when a song is DJ-edited, the library update unit 15 adds an operation history, such as the settings used for the DJ edit, as metadata for the song.

[0067] The music transmitting unit 16 is a processing unit that transmits data files of music content to the audio device 30. In one aspect, when a download of music content is requested from the audio device 30, the music transmitting unit 16 transmits a data file of the music content stored in the music storage unit 12 that corresponds to the music ID specified in the request.

[0068] <Configuration of the audio device 30> Next, a functional configuration of the audio device 30 according to this embodiment will be described. For example, Fig. 2 shows a block diagram of functions related to the download function of the audio device 30.

[0069] 2, the audio device 30 has an operation unit 31, an audio output unit 32, a request unit 33, a download unit 34, a library storage unit 35, a library update unit 36, an upload unit 37, a playback reception unit 38, and a playback unit 39. Note that Fig. 2 only shows an excerpt of functional units related to the functions corresponding to the download provision function described above, and the server device 10 may also be provided with functional units other than those shown, such as a display unit.

[0070] The operation unit 31 is a functional unit that accepts operations for the audio device 30. For example, the operation unit 31 may be realized by a physical interface such as a cue button, a play / pause button, a jog dial, or a tempo slider that is arranged on the deck housing. Alternatively, the operation unit 31 may be realized by a GUI (Graphical User Interface) displayed on a touch panel.

[0071] The audio output unit 32 is a functional unit that outputs the audio of the music content played by the playback unit 39. In one aspect, the audio output unit 32 may be realized by a speaker or a speaker unit including a plurality of speakers.

[0072] The request unit 33 is a processing unit that requests the download of the cloud library 11L. In one aspect, when an account is authenticated by attaching removable media that stores the authentication key, the request unit 33 can request the download of the cloud library 11L of the user corresponding to the account. In this case, if multiple removable media can be attached to the housing of the audio device 30, the account for which the download is requested can be selected from accounts displayed on the display unit or a list of cloud libraries 11L corresponding to the accounts.

[0073] The download unit 34 is a processing unit that downloads a DL library 35L that is generated by the server device 10 by narrowing down the list of songs included in the cloud library 11L based on the operation history. The DL library 35L downloaded in this manner is stored in the library storage unit 35.

[0074] The library update unit 36 ​​is a processing unit that updates the DL library 35L stored in the library storage unit 35 based on operations received via the operation unit 31. In one aspect, when a new song is imported, the library update unit 36 ​​adds the new song to the collection of the DL library 35L and adds an operation history, such as the date and time of the import, as metadata for the new song. In another aspect, when a song is DJ-performed, the library update unit 36 ​​adds an operation history, such as the date and time of the DJ performance, as metadata for the song. In yet another aspect, when a song is DJ-edited, the library update unit 36 ​​adds an operation history, such as the settings used for the DJ edit, as metadata for the song.

[0075] The upload unit 37 is a processing unit that, when an operation on a song included in the DL library 35L stored in the library storage unit 35 is received, uploads an operation history corresponding to the operation to the server device 10 .

[0076] 7 is a schematic diagram illustrating uploading of an operation history. As shown in FIG. 7, the operation unit 31 of the audio device 30 accepts operations such as DJ performance and DJ editing (S21). The upload unit 37 of the audio device 30 then uploads the operation history related to the operations accepted via the operation unit 31 in step S21 to the server device 10 (S22). The DL library 35L stored in the library storage unit 35 of the audio device 30 may also be updated based on the operations accepted via the operation unit 31 in step S21.

[0077] The library update unit 15 of the server device 10 that has received the upload in this manner updates the cloud library 11L based on the operation history uploaded in step S22 (S23).

[0078] Through the series of processes from step S21 to step S23, the cloud library 11L and the DL library 35L can be synchronized.

[0079] Returning to the explanation of FIG. 2, when a playback accepting unit 38 accepts an operation to play music content via the operation unit 31, it requests the server device 10 to download the music content.

[0080] The playback unit 39 is a processing unit that plays music downloaded from the server device 10. In one aspect, the playback unit 39 causes the audio output unit 32 to output the data file of music content downloaded from the server device 10 as audio. At this time, if an operation related to a hot cue, BPM, or the like is received via the operation unit 31, the playback unit 39 can change the playback position of the music to the playback position of the hot cue set in the point information, or can change the tempo of the music being played.

[0081] <Processing Flow> Next, a processing flow of the library provision system according to this embodiment will be described. Here, (1) Library provision processing executed by the library provision system 1 will be described, followed by (2) Narrowing processing executed by the audio device 30.

[0082] (1) Library Provision Process Fig. 8 is a sequence diagram showing the procedure of the library provision process. This process can be started, as an example only, by receiving a designation from an account that has been authenticated by inserting a removable medium that stores an authentication key that has been authenticated in advance by the DJ software, via the operation unit 31 or the like.

[0083] As shown in Figure 8, when an account specification is received via the operation unit 31 of the audio device 30 (step S101), the request unit 33 of the audio device 30 requests the server device 10 to download the cloud library 11L of the user corresponding to the account specified in step S101 (step S102).

[0084] Upon receiving such a request, the narrowing-down unit 13 of the server device 10 acquires the cloud library 11L corresponding to the account of the user ID specified in the request of step S102 from the cloud libraries stored for each user ID in the library storage unit 11 (step S103).

[0085] At this time, if the number of songs included in the cloud library 11L acquired in step S103 is equal to or greater than the target value (step S104: Yes), the narrowing-down unit 13 of the server device 10 executes a "narrowing-down process" to narrow down the songs included in the cloud library 11L based on the operation history (step S105). Note that if the number of songs in the cloud library 11L is not equal to or greater than the target value (step S104: No), the process of step S105 is skipped.

[0086] Then, the library transmission unit 14 of the server device 10 transmits the DL library 35L obtained as a result of the narrowing down in step S105 to the acoustic device 30 that requested the download, and the download unit 34 of the acoustic device 30 downloads the DL library 35L transmitted by the library transmission unit 14 (step S106).

[0087] Then, the download unit 34 of the audio device 30 stores the DL library 35L downloaded in step S106 in the library storage unit 35 (step S107), and the process ends.

[0088] (2) Narrowing Down Processing Fig. 9 is a flowchart showing the procedure of the narrowing down processing. The series of processes shown in Fig. 9 corresponds to the process of step S105 shown in Fig. 8. Note that Fig. 9 illustrates, as an example only, the procedure of the narrowing down processing executed in accordance with the narrowing down setting file shown in Fig. 4, but the procedure and parameters used in the processing may differ depending on the description of the narrowing down setting file.

[0089] As shown in Figure 9, the narrowing down unit 13 refers to the last DJ performance date and time in the operation history included in the metadata of each song included in the cloud library 11L, and sorts the song IDs included in the cloud library 11L in order of most recent last DJ performance date and time (step S301).

[0090] Thereafter, the narrowing-down unit 13 executes loop process 1, which repeats the processes from step S302 to step S306 until the target value set in the narrowing-down setting file shown in FIG. 4, for example, the number of songs to be added to the DL library 35L, reaches 100 songs.

[0091] That is, the narrowing-down unit 13 selects the i-th song ID from the list of song IDs sorted in order of most recent last DJ performance date and time in step S301 (step S302).The narrowing-down unit 13 then determines narrowing-down condition 1, which is whether the last DJ performance date and time of the i-th song ID is within a threshold value Th1, for example, six months, from the current date and time (step S303).

[0092] Next, if the last DJ performance date and time is within threshold value Th1 (step S303 Yes), the narrowing-down unit 13 determines narrowing-down condition 2, which is whether the last DJ edit date and time of the i-th song ID is within threshold value Th2, for example, 3 months, from the current date and time (step S304).

[0093] Then, if the last DJ edit date and time is within threshold Th2 (Yes in step S304), the narrowing-down unit 13 determines narrowing-down condition 3, which is whether the import date and time of the i-th song ID is within threshold Th3, for example, six months, from the current date and time (step S305).

[0094] If the three narrowing conditions, narrowing condition 1 to narrowing condition 3, are all satisfied as an AND condition, i.e., if the results are Yes in step S303, Yes in step S304, and Yes in step S305, the narrowing unit 13 adds the i-th song ID to the DL library 35L (step S306).

[0095] On the other hand, if one or more of the three filtering conditions 1 to 3 are not met (step S303 No, step S304 No, or step S305 No), the filtering unit 13 excludes the i-th song ID and does not add it to the DL library 35L.

[0096] By repeating the series of processes from step S302 to step S306, songs that satisfy the above three filtering conditions under an AND condition can be added to the DL library 35L until the number of songs corresponding to the target value is reached.

[0097] <Effects of Embodiment 1> As described above, the server device 10 according to this embodiment provides a library provision function that provides a DL library 35L that narrows down a list of songs included in the cloud library 11L based on operation history added to the songs as metadata.

[0098] In addition, the audio device 30 according to this embodiment provides a download function for downloading a DL library 35L in which a list of songs included in the cloud library 11L is narrowed down based on an operation history in which the songs are added as metadata.

[0099] These library providing and downloading functions narrow down the songs from the cloud library 11L that are likely to be used in DJ performances based on the operation history to the DL library 35L downloaded to the audio device 30. As a result, the size of the DL library 35L downloaded to the audio device 30 can be made smaller than that of the cloud library 11L.

[0100] Therefore, the server device 10 and the audio device 30 according to this embodiment can shorten the download time of the DL library 35L. As one aspect, the shortened download time allows for quicker DJ changes at live venues and the like, enabling seamless DJ changes. Ultimately, this can prevent the excitement of a live performance from dropping when a DJ changes. As another aspect, the DL library 35L is less likely to include songs that are unlikely to be used in DJ performances. For example, songs that were used long ago but are no longer used are less likely to be included. In this way, information that hinders user selection is eliminated from the DL library 35L, making it easier for users to find songs they want to see DJed.

[0101] Other Embodiments Although the embodiments of the present disclosure have been described above, various applications are possible, and further, the present disclosure may be implemented in various different forms other than the above-described embodiments.

[0102] <Numeric Values, etc.> The matters described in the above embodiment, such as the format and description of the narrowing-down setting file shown in Fig. 4, and specific examples of the procedure and parameters of the narrowing-down process using the same, are merely examples and can be changed. Furthermore, the order of processing in the flowchart described in the embodiment can also be changed within a consistent range.

[0103] <Application Example 1> For example, the filtering setting file shown in Figure 4 provides an example of filtering songs included in the cloud library 11L to songs that satisfy multiple filtering conditions using an AND condition, but this is not limited to this, and it is also possible to narrow down the songs to songs that satisfy an OR condition.

[0104] 10 is a flowchart showing the procedure of the narrowing-down process according to the application example. Similar to FIG. 9, the series of processes shown in FIG. 10 also correspond to the process of step S105 shown in FIG.

[0105] As shown in Figure 10, the narrowing down unit 13 refers to the last DJ performance date and time in the operation history included in the metadata of each song included in the cloud library 11L, and sorts the song IDs included in the cloud library 11L in order of most recent last DJ performance date and time (step S501).

[0106] Next, the narrowing unit 13 extracts song IDs whose last DJ performance date and time is within a threshold Th1 from the list of song IDs sorted in order of most recent last DJ performance date and time in step S501 (step S502).

[0107] Here, if the target value, for example, 100 or more songs, is not reached even after adding the song ID extracted in step S502 to the DL library 35L (step S503 No), the narrowing unit 13 adds the song ID extracted in step S502 to the DL library 35L (step S504).

[0108] Then, the narrowing unit 13 sorts the remaining song IDs included in the cloud library 11L that have not been extracted in step S502 in order of most recent last DJ edit date and time (step S505).

[0109] Then, the narrowing unit 13 extracts song IDs whose last DJ edit date and time is within a threshold Th2 from the list of song IDs sorted in order of most recent last DJ edit date and time in step S505 (step S506).

[0110] Then, if the target value, for example, 100 or more songs, is not reached even after adding the song IDs extracted in step S506 to the DL library 35L (step S507 No), the narrowing unit 13 adds the song IDs extracted in step S506 to the DL library 35L (step S508).

[0111] Next, the narrowing unit 13 sorts the remaining song IDs included in the cloud library 11L that have not been extracted in step S506 in descending order of import date and time (step S509).

[0112] Then, the narrowing-down unit 13 extracts song IDs whose import dates and times are within a threshold Th3 from the list of song IDs sorted in order of most recent import dates and times in step S509 (step S510).

[0113] Then, if the target value, for example, 100 or more songs, is not reached even after adding the song IDs extracted in step S510 to the DL library 35L (step S511 No), the narrowing unit 13 adds the song IDs extracted in step S510 to the DL library 35L (step S512).

[0114] Next, the narrowing-down unit 13 relaxes the condition settings used for comparison with the operation items in the narrowing-down conditions 1 to 3, i.e., the settings of the thresholds Th1, Th2, and Th3 (step S513). For example, the condition settings can be relaxed by extending the periods of the thresholds Th1, Th2, and Th3 by adding a predetermined value, for example, three months, to the thresholds Th1, Th2, and Th3 corresponding to the periods going back from the current date and time.

[0115] Thereafter, the process proceeds to step S501, and the processes from step S501 to step S513 are repeated until any one of the conditions of step S503 Yes, step S507 Yes, or step S511 Yes is satisfied.

[0116] On the other hand, if the target value, for example, 100 or more songs, is reached by adding the song IDs extracted in step S502, step S506, or step S510 to the DL library 35L (Yes in step S503, Yes in step S507, or Yes in step S511), the narrowing-down unit 13 executes the following process: The narrowing-down unit 13 adds the song IDs extracted in step S502, step S506, or step S510, as many as reach the target value, to the DL library 35L (step S514), and ends the process.

[0117] By carrying out the series of processes from step S501 to step S514, songs that satisfy the above three narrowing conditions in an OR condition can be added to the DL library 35L until the number of songs corresponding to the target value is reached.

[0118] <Application Example 2> In addition, in the above embodiment 1, an example was given in which songs that satisfy multiple filtering conditions are narrowed down using an AND condition or an OR condition, but it is also possible to set a target value for each filtering condition and then extract songs that satisfy each filtering condition in parallel.

[0119] For example, the target value for filtering condition 1, the last DJ performance date and time, is 200 songs, the target value for filtering condition 2, the last DJ edit date and time, is 100 songs, and the target value for filtering condition 3, the import date and time, is 50 songs.

[0120] In this case, the narrowing down unit 13 extracts 200 songs in descending order starting from the song with the most recent last DJ performance date and time, extracts 100 songs in descending order starting from the song with the most recent last DJ edit date and time, and extracts 50 songs in descending order starting from the song with the most recent import date and time.

[0121] By narrowing down the search results in this way, it is possible to extract songs that satisfy each of the narrowing down conditions evenly, without placing too much emphasis on the narrowing down conditions of a specific operation item.

[0122] <Application Example 3> In addition, in the above-mentioned first embodiment, an example was given in which various DJ editing operations such as memory cues, loops, hot cues, beat grids, and BPMs are grouped together and narrowed down as a DJ editing operation, but it is also possible to distinguish between these and narrow down the operations.

[0123] For example, the narrowing-down unit 13 can set priorities (priorities) among multiple DJ editing operations. For example, the priorities can be set in descending order of priority, such as hot cues, memory cues, beat grids, BPM, and loops. The narrowing-down unit 13 may narrow down songs that satisfy the narrowing-down conditions for each of these DJ editing operations using an AND condition or an OR condition.

[0124] In the first embodiment, the narrowing down by the narrowing down unit 13 is performed on demand after the reception of a download request, but the timing at which the narrowing down is performed is not limited to this. For example, the narrowing down by the narrowing down unit 13 may be performed in advance before the reception of a download request.

[0125] That is, when the cloud library 11L is narrowed down after a download request is received, the time required for narrowing down the cloud library 11L increases as the number of songs included in the cloud library 11L increases. In other words, depending on the number of songs included in the cloud library 11L, in addition to the time required for transmitting the DL library 35L from the server device 10 to the audio device 30, the non-negligible time required for narrowing down the cloud library 11L may be added to the download time.

[0126] From this perspective, the narrowing-down unit 13 can narrow down the cloud library 11L after the update in advance every time the cloud library 11L is updated, for example, every time step S04 shown in FIG. 1 is executed. This eliminates the need to narrow down the cloud library 11L when a download request is received, and therefore reduces the time required for narrowing down the cloud library 11L from the download time from when a download request is made until the download is completed. As a result, the download time can be reduced.

[0127] At this time, the narrowing unit 13 can set the size of the DL library 35L to be transmitted from the server device 10 to the audio device 30 to the upper limit threshold of the storage capacity or free space of the audio device 30, for example, the target value of the narrowing setting file shown in Fig. 4. This can prevent the audio device 30's storage capacity from being exceeded, eliminating the need to perform retry processes such as re-narrowing the cloud library 11L or re-downloading the DL library 35L.

[0128] <System> The processing procedures, control procedures, specific names, various data, and parameters shown in the above documents and drawings may be changed as desired unless otherwise specified. For example, one or more of the request unit 33, download unit 34, library update unit 36, upload unit 37, playback reception unit 38, and playback unit 39 of the audio device 30 may be configured as separate devices. Furthermore, one or more of the narrowing unit 13, library transmission unit 14, library update unit 15, and music transmission unit 16 of the server device 10 may be configured as separate devices.

[0129] Furthermore, each component of the illustrated device is a functional concept and does not necessarily have to be physically configured as illustrated. In other words, the specific form of distribution and integration of the functional units of the device is not limited to that shown. In other words, all or part of the device can be functionally or physically distributed and integrated in any unit depending on various loads, usage conditions, etc. Note that each component may also be a physical configuration.

[0130] Furthermore, all or any part of the processing performed by the illustrated device may be realized by a program executed by a hardware processor such as an MPU (Micro-Processing Unit) or a CPU (Central Processing Unit), or may be realized as hardware using wired logic.

[0131] <Hardware> Next, an example of the hardware configuration of the audio device described in the above embodiment will be described. Fig. 11 is a diagram showing an example of the hardware configuration. As shown in Fig. 11, the audio device 30 has a communication device 30a, a storage device 30b, a memory 30c, and a processor 30d. Note that the components shown in Fig. 11 may be connected to each other via a bus or the like.

[0132] The communication device 30a is a network interface card, etc. The storage device 30b is a storage device such as a hard disk drive (HDD) or a solid state drive (SSD). For example, the storage device 30b stores programs and databases that operate the functions shown in Figures 8 to 10.

[0133] The processor 30d reads out a program that executes the same processing as the processing unit shown in FIG. 2 from the storage device 30b or the like and loads it into the memory 30c, thereby operating a process that executes the functions described in FIG.

[0134] Such a process realizes the same functions as the processing units of the audio device 30. For example, the processor 30d reads from the storage device 30b or the like a program having the same functions as the request unit 33, the download unit 34, the library update unit 36, the upload unit 37, the playback acceptance unit 38, the playback unit 39, etc. Then, the processor 30d executes a process that executes the same processing as the request unit 33, the download unit 34, the library update unit 36, the upload unit 37, the playback acceptance unit 38, the playback unit 39, etc.

[0135] In this way, the audio device 30 operates as an information processing device that executes a download method by reading and executing a program. The audio device 30 can also realize the same functions as the above-described embodiment by reading the program from a recording medium using a media reader and executing the read program. Note that the program in these other embodiments is not limited to being executed by the audio device 30. For example, the present invention can also be applied in a similar manner to cases where another computer or server executes the program, or where these execute the program in cooperation with each other.

[0136] The above program can be distributed via a network such as the Internet. The above program can also be recorded on any recording medium and executed by a computer by reading it from the recording medium. For example, the recording medium can be a hard disk, a flexible disk (FD), a CD-ROM, a magneto-optical disk (MO), a digital versatile disk (DVD), or the like.

[0137] REFERENCE SIGNS LIST 1 Library providing system 10 Server device 11 Library storage unit 12 Music storage unit 13 Narrowing unit 14 Library transmission unit 15 Library update unit 16 Music transmission unit 30 Sound device 31 Operation unit 32 Audio output unit 33 Request unit 34 Download unit 35 Library storage unit 36 ​​Library update unit 37 Upload unit 38 Playback reception unit 39 Playback unit

Claims

1. A request section that requests the download of the first library stored in cloud storage, A download unit downloads a second library, which is a list of songs included in the first library from a server device on the cloud, based on the operation history attached as metadata to the songs. An acoustic device characterized by having the following features.

2. The sound device according to claim 1, characterized in that the first library is narrowed down on the condition that the first library exceeds a predetermined capacity.

3. The sound device according to claim 2, characterized in that the predetermined capacity is set based on the storage capacity of the sound device.

4. The sound device according to claim 1, characterized in that the second library includes songs from the first library that satisfy the filtering conditions related to the operation items included in the operation history.

5. The sound device according to claim 1, characterized in that the operation history includes one or more operation items from among the operation of editing the music, the operation of DJing using the music, and the operation of importing the music.

6. The sound device according to claim 1, further comprising an upload unit that, when it receives an operation on a song included in the second library, uploads the operation history corresponding to the operation to the cloud storage.

7. The sound device according to any one of claims 1 to 6, characterized in that the second library is narrowed down based on the operation history when the first library is updated.

8. A filtering unit that narrows down the list of songs contained in a first library stored in cloud storage based on the operation history attached as metadata to the songs, A transmission unit that transmits the second library obtained as a result of the filtering by the filtering unit, A server device characterized by having the following features.

9. The sound equipment is A request section that requests the download of the first library stored in cloud storage, A download unit downloads a second library, which is a list of songs included in the first library from a server device on the cloud, based on the operation history attached as metadata to the songs. It has, The aforementioned server device on the cloud, A filtering unit that narrows down the list of songs included in the first library based on the operation history attached as metadata to the songs, A transmitting unit that transmits the second library obtained as a result of the narrowing down by the aforementioned narrowing unit to the sound device, A library provisioning system characterized by having the following features.

10. Request to download the first library stored in cloud storage, The server device on the cloud downloads a second library, which is a list of songs included in the first library, narrowed down based on the operation history attached as metadata to the songs. A download program characterized by having an audio device perform the processing.