Pre-release of recordings for digital streaming platforms

A computer system is provided for implementing a pre-release of a recording at a distribution platform. The computer system includes a processor coupled to a storage system that stores instructions, which, upon execution by the processor, cause the processor to present a release interface for the recording. The release interface includes graphical controls element for confirming the pre-release of the recording, for selecting a release date, and for selecting a pre-release date. The instructions further cause the processor to receive information describing a confirmation of the pre-release of the recording, a selected release date, and a selected pre-release date. The instructions further cause the processor to provide a truncated version of the recording for the pre-release of the recording. The instructions further cause the processor to transmit the truncated version of the recording to a digital streaming platform.

BACKGROUND

Digital streaming platforms (DSPs) provide on-demand online entertainment for their users, typically through a subscription model. As an alternative to file downloading, the user can stream media content such as video and audio data in real-time and start playing the video or audio before the entire file has been transmitted. DSPs provide a platform for artists to exhibit and promote their works while earning income through various licensing and royalties arrangements.

SUMMARY

A computer system is provided for implementing a pre-release of a recording at a distribution platform. The computer system includes a processor coupled to a storage system that stores instructions, which, upon execution by the processor, cause the processor to present a release interface for the recording. The release interface includes a first graphical control element having options for confirming the pre-release of the recording, a second graphical control element having options for selecting a release date, and a third graphical control element having options for selecting a pre-release date. The instructions further cause the processor to receive information describing a confirmation of the pre-release of the recording, a selected release date, and a selected pre-release date. The instructions further cause the processor to provide a truncated version of the recording for the pre-release of the recording. The instructions further cause the processor to transmit the truncated version of the recording to a digital streaming platform, wherein the transmitted truncated version of the recording includes metadata describing the selected pre-release date.

DETAILED DESCRIPTION

Artists have many different avenues and channels in which to release their recordings. Generally, artists tend to release their recordings on multiple platforms to reach a larger audience. For example, an artist releasing a music track on streaming platforms will typically release it on multiple DSPs at the same time for widespread exposure. However, simultaneous widespread release of the music track limits the marketing and advertising opportunities available. As with most musical works, developing momentum in the promotion of an upcoming music track can have a significant impact on its popularity at the time of release. As such, the artist can choose to pre-release a truncated version of their music track to drive publicity of their work before a full release date.

The present disclosure provides systems and methods for a release interface enabling users, such as artists and distributors, to offer a pre-release of their recordings on a digital streaming platform. Pre-releases of recordings provide a channel for artists to distinguish and promote their work on DSPs that are saturated with other content by offering a sampling of their recording to the public before the full release date of said recording. A pre-release can be offered in the form of a truncated version of the recording released before a full release of the recording in its entirety.

Release interfaces in accordance with the present disclosure include an option for users to decide whether to offer a pre-release. A release interface can be implemented during an initial scheduling of the recording. For example, in addition to an option for users to decide whether to offer a pre-release, the interface can include options for a user to select the full release date and time of their recording. The release interface can further include options for users to select the pre-release date and time. Various constraints on the selections can be implemented. For example, selection of the release date can be limited to dates after the current date. These and other pre-release implementations are discussed below in further detail.

FIG.1is a diagram schematically illustrating an example system100for implementing pre-releases of recordings. The system100includes a plurality of client computing devices102in communication with a distribution platform device104through a communication network106. The system100further includes at least one digital streaming platform device108in communication with the distribution platform device104. In some implementations, the distribution platform device104and the digital streaming platform device108are located on the same platform. The distribution platform device104is implemented to present a release interface for recordings to the client computing devices102for display. The release interface includes various graphical control elements, including a graphical control element having options for confirming a pre-release of the recording. Graphical control elements for collecting other various information can be implemented in the release interface. For example, the release interface can further include graphical control elements having options for selecting a release date, a release time, a pre-release date, a pre-release time, etc. Upon receiving input information from a client computing device102confirming the pre-release of a recording, the distribution platform device104provides a truncation of the recording, which is then transmitted to the digital streaming platform device108for publishing.

Each of the client computing devices102can represent various forms of processing devices. Example processing devices can include a desktop computer, a laptop computer, a handheld computer, a tablet computer, a personal digital assistant, a smart phone, a game console, or a combination of any these data processing devices or other data processing devices. The distribution platform device104and the digital streaming platform device108can represent various forms of servers including, but not limited to a web server, an application server, a proxy server, a network server, or a server farm. The computing devices102,104,108can communicate through wired connections or wirelessly (e.g., through communication network106). The system100can be a distributed client/server system that spans one or more networks such as the communication network106.

FIG.2is a diagram schematically illustrating an example computing system200having a computing device202configured to implement pre-releases of recordings, which may be utilized to implement the distribution platform device104ofFIG.1. The computing device202includes a processor204(e.g., central processing units, or “CPUs”) and memory206(e.g., volatile and non-volatile memory) operatively coupled to each other. The memory206stores a pre-release program208, which contains instructions for the various software modules described herein for execution by the processor204. The memory206also stores data210for use by the pre-release program208and its software modules.

Upon execution by the processor204, the instructions stored in the pre-release program208cause the processor204to implement a release interface module212to present a release interface214to an external computing device (not shown) for display. For example, the release interface212can be presented to a client computing device such as those described inFIG.1. In some implementations, the release interface214is retrieved from data210stored in memory206. The release interface212includes a plurality of graphical control elements for a user of the external computing device to select and determine various attributes related to the recording to be released. For example, the release interface212can include graphical control elements having options for confirming a pre-release of the recording. The release interface212can also include graphical control elements having options for selecting the release date, release time, pre-release date, pre-release time, etc.

The computing device202is configured to receive information describing selected options of the graphical control elements from the external computing device. The computing device202receives information describing at least a confirmation of the pre-release of the recording, a selected release date, and a selected pre-release date. In some implementations, the computing device202receives information describing a selected release time and a selected pre-release time. In response to a confirmation of the pre-release of the recording, the pre-release program208implements a truncation module216to provide a truncated version of the recording218.

The truncation module216can be implemented in various ways to provide the truncated version of the recording218. For example, the truncation module216can provide the truncated version of the recording by receiving an uploaded file of a truncated recording. In some implementations, the truncation module216provides a data file of the recording and generates the truncated version of the recording using the provided data file of the recording. A data file of the recording can be provided through various means, including receiving an upload of the recording by the user of the external computing device.

The truncated version of the recording218may be generated manually. For example, the administrator of the computing system200can manually generate a truncated version of the recording218by trimming the provided data file of the recording. The truncated version of the recording218may also be generated or through automatic means. One example process for generating a truncated version of the recording218includes providing a graphical control element having options for selecting at least one truncation point. In such cases, the received information from the external computing device includes at least one selected truncation point. The truncation point(s) can describe the time point(s) in the recording at which to trim the recording. The truncation module216utilizes the provided data file of the recording and the received information describing the truncation point(s) to generate a truncated version of the recording218.

Another example process includes the use of deep learning and neural networks. For example, the truncation module216can provide a neural network that has been trained to select a section of a provided recording based on different criteria. In some implementations, the neural network is trained to select a section of a chorus to a music track. In other implementations, the neural network is trained to select a section based on various music theory elements. For example, the neural network can be trained to detect certain pitches, rhythms, melodies, etc. Different neural network types can be utilized, including convolutional neural networks (CNNs), recurrent neural networks (RNNs), bi-directional long short term memory (LSTM) RNNs, encoder-decoder transformers, encoder-only transformers, Siamese networks, etc.

After the truncated version of the recording218is provided, the pre-release program208is configured to transmit the truncated version of the recording218to an external system for publishing. For example, the truncated version of the recording218can be transmitted to one or more digital streaming platforms for publishing.

Implementing pre-releases can involve different issues related to the licensing of the recording. Typically, licensing agreements for DSPs involve royalty payouts based on the number of times a music track has been streamed. Pre-releases would complicate this matter. In some cases, separate licenses are implemented for the pre-release and full release. For example, the truncated version of the recording can be licensed separately from the full version of the recording. In such cases, the truncated version can be licensed to a first DSP with a specified pre-release time, and the full version and/or the truncated version can be licensed to one or multiple DSPs, including the first DSP, with a specified release time. A common standard for formatting the metadata of the recording files can be implemented to simplify licensing issues and to promote uniformity across multiple DSPs. For example, the Digital Data Exchange (DDEX) standard format (as defined by Digital Data Exchange, LLC headquartered in New York, USA) can be implemented with the recording and the truncated version of the recording. The DDEX standard defines an approach for the business-to-business communication of information between organizations operating in the digital media supply chain. The approach standardizes the formats in which metadata information, such as credit attribution, is represented in files exchanged between multiple entities, allowing for more effective communications.

Referring back toFIG.2, the truncated version of the recording218can include metadata describing the selected pre-release date. The digital streaming platform(s) receiving the truncated version of the recording218uses the metadata to determine when to publish the truncated version of the recording218. In some implementations, the pre-release program208further transmits the recording in its entirety, where the recording includes metadata describing the selected release date and the digital streaming platform uses such metadata to determine when to publish the recording.

The release interface for recordings can be implemented in many different ways. For example, a graphical user interface can be presented to a user to make selections on various features of the recording, including release date, release time, the offering of a pre-release, etc.FIG.3schematically illustrates an example user interface300for implementing pre-releases of recordings. The user interface300is an interface for providing information on the release of a recording. The user, typically the artist of the recording, make selections to inform the receiving device, such as a distribution platform, on their decisions regarding the release of the recording. For example, the user interface300can include various graphical control elements that allows the user to select from a set of predefined options to provide information to the receiving device. InFIG.3, the user interface300includes options regarding the release date302and the release time304for the recording. Various types of graphical control elements can be implemented. For example, the options for the release date302can be implemented with a date picker. The options for the release time can be implemented with a drop-down list. Various constraints can be enforced to limit the options available for logical consistency. For example, the options for the release date302can be limited to dates after the current date. In other implementations, selection of a release date302before the current date304informs the receiving device to release the recording as early as allowed by the distribution platform's protocols, such as pending a review of the recording and/or a truncated version of the recording.

The user interface300further includes options for the offering of a pre-release306of the recording. InFIG.3, the options for the offering of a pre-release306are implemented using “Yes/No” radio buttons. As shown, the “Yes” option is selected, and the user interface300includes further options for the pre-release date308and pre-release time310. In some implementations, the options for the pre-release date308and pre-release time310are displayed only after the “Yes” radio button for the offering of a pre-release is selected. Similar to the options for the release date302and the release time304, various constraints can be applied to the options for the pre-release date308and pre-release time310. For example, the options for the pre-release date308can be limited to dates before the selected release date302. In other implementations, selection of a pre-release date308before the release date302limits the options for the release date302. In some implementations, the options for selecting the pre-release time preclude options where the selected pre-release date and time is less than twenty-four hours before the selected release date and time.

FIG.4is a flow diagram schematically illustrating an example method400for implementing pre-releases of recordings. At402, the method400includes presenting a release interface for a recording. The release interface includes a first graphical control element having options for confirming the pre-release of the recording, a second graphical control element having options for selecting a release date, and a third graphical control element having options for selecting a pre-release date. Such information can be obtained from various graphical control elements. For example, the release interface can include radio buttons having “Yes/No” options for the user to select whether to offer a pre-release. Other examples include the use of date pickers for the user to select the release date and the pre-release date. In some implementations, the release interface further includes graphical control elements having options for selecting a release time and a pre-release time. In such cases, the release interface can include drop-down lists, or any other graphical control element, for the user to select the release time and the pre-release time. Various constraints can be enforced upon the selections of the dates and times. For example, the pre-release date and time selected can be constrained to at least twenty-four hours before the release date. In some implementations, the options preclude selections where a selected pre-release date is on the same date as or after the selected release date.

At404, the method400includes receiving information describing a confirmation of the pre-release of the recording, a selected release date, and a selected pre-release date. As described above, various constraints can be applied upon the selections. For example, the received information typically describes a selected pre-release date that is before the selected release date. In some implementations, the received information further describes a selected release time and a selected pre-release time, and wherein the truncated version of the recording includes metadata describing the pre-release time

At406, the method400includes providing a truncated version of the recording for the pre-release of the recording. A truncated version of the recording can include various forms. For example, for music tracks, a truncated version can be a shortened clip, such as a fifteen to sixty-second segment of the music track. Clips of other lengths may also be utilized. The recording and the truncated version of the recording can include similar international standard codes for uniquely identifying media recordings, such as the International Standard Recording Code (ISRC) codified as ISO 3901. The recording and the truncated version of the recording can also include different product codes for uniquely identifying a trade item, such as the Universal Product Code (UPC) as set out by international standards.

In some implementations, the truncated version of the recording is provided by the user through an uploaded file. In other implementations, the recording is first provided, and a truncated version of the recording can be generated from the provided recording through manual or automatic means. For example, one example process for generating a truncated version of the recording includes providing a graphical control element having options for selecting at least one truncation point. In such cases, the received information describes at least one selected truncation point. The truncation point(s) can describe the time point(s) in the recording at which to trim the recording. A data file of the recording and the received information describing the truncation point(s) can be used to generate a truncated version of the recording.

Another example includes generating truncated versions of recordings using trained neural networks. Such implementations can include neural networks trained to select a section of the recording based on different criteria. In some implementations, the neural network is trained to select a section of a chorus to a music track. In other implementations, the neural network is trained to select a section based on various music theory elements. For example, the neural network can be trained to detect certain pitches, rhythms, melodies, etc.

At408, the method400includes transmitting the truncated version of the recording to a digital streaming platform, where the transmitted truncated version of the recording includes metadata describing the selected pre-release date.

Referring toFIG.4, the method400can be implemented as an addition to the general process of releasing the recording. For example, the decision to offer a pre-release and the offering of the pre-release can be applied during the general process of releasing the recording.FIG.5is a flow diagram schematically illustrating an example process500of implementing a pre-release within a full release of a recording. At502, the process500includes presenting a release interface for a recording. The release interface can include a graphical control element that allows the user to select from a set of predefined options. In some implementations, the release interface includes graphical control elements that allow the user to select a release date, a release time, an offering of a pre-release, a pre-release date, and a pre-release time. In further implementations, the pre-release date and pre-release time options are not displayed until the option for an offering of a pre-release is affirmed. The options to select a release date and a pre-release date can be implemented using a date picker control element. The options to select a release time and a pre-release time can be implemented using a drop-down list control element. The option to offer a pre-release can be implemented using radio buttons having “Yes/No” options for the user to select whether to offer a pre-release. Various constraints can be enforced upon the selections of the dates and times. For example, the pre-release date and time selected can be constrained to at least twenty-four hours before the release date. In some implementations, the options preclude selections where a selected pre-release date is on the same date as or after the selected release date.

At504, the process500includes receiving information describing the selected options described above. In some implementations, the received information does not describe a release time or a pre-release time. Depending on whether a pre-release is offered, information relating to the pre-release may be missing. For example, the information does not include a pre-release date or a pre-release time if the offering of a pre-release is not selected.

At506, the process500verifies whether the information describes an affirmation of a pre-release of the recording. If a pre-release offering is confirmed, the process500includes, at508, providing a truncated version of the recording. The recording and the truncated version of the recording can include similar international standard codes for uniquely identifying media recordings, such as ISRC codes. The recording and the truncated version of the recording can also include different product codes for uniquely identifying a trade item, such as UPCs.

A recording can first be provided, and a truncated version of the recording can be generated manually or through automatic means. For example, a truncated version of the recording can be generated through the use of graphical control elements for truncation points. Another example includes generating truncated versions of recordings using trained neural networks. In other implementations, the truncated version of the recording is provided by the user through an uploaded file.

If a pre-release offering is confirmed, the process500includes, at510, transmitting the truncated version of the recording to a digital streaming platform for publishing. The truncated version of the recording can include metadata describing the selected pre-release date.

At504, the process500includes transmitting the recording to a digital streaming platform for publishing. The recording can include metadata describing the selected release date. The recording and the truncated version of the recording can be associated under a same data file having metadata describing recording information.

On the client side of the user interface, a process for offering a pre-release can be implemented.FIG.6is a flow diagram schematically illustrating an example process600of offering a pre-release within a full release of a recording to a distribution platform. At602, the process600includes displaying a release interface for a recording. The release interface can include a graphical control element that allows the user to select from a set of predefined options. In some implementations, the release interface includes graphical control elements that allow the user to select a release date, a release time, an offering of a pre-release, a pre-release date, and a pre-release time. In further implementations, the pre-release date and pre-release time options are not displayed until the option for an offering of a pre-release is affirmed.

At604, the process600includes selecting a release date for the recording. The option to select a release date can be implemented using a date picker control element. In some implementations, the process600further includes selecting a release time for the recording. The option to select a release time can be implemented using a drop-down list control element.

At606, the process600includes selecting whether to offer a pre-release of the recording. The option to offer a pre-release can be implemented using radio buttons having “Yes/No” options for the user to select whether to offer a pre-release.

If the user selects to offer the pre-release, the process600includes, at608, selecting a pre-release date for the recording. The option to select a pre-release date can be implemented using a date picker control element. In some implementations, the options preclude selections where a selected pre-release date is on the same date as or after the selected release date. In some implementations, the process600further includes selecting a release time for the recording. The option to select a pre-release release time can be implemented using a drop-down list control element. Various constraints can be applied upon the options. For example, the pre-release date and time selected can be constrained to at least twenty-four hours before the release date. In some implementations, the pre-release date and pre-release time options are not displayed until the option for an offering of a pre-release is affirmed.

If the user selects to offer the pre-release, the process600includes, at610, providing a truncated version of the recording. In some implementations, the user provides the recording to the distribution platform, and the distribution platform uses the recording to generate a truncated version. For example, a truncated version of the recording can be generated through the use of graphical control elements for truncation points. Another example includes generating truncated versions of recordings using trained neural networks. In other implementations, the truncated version of the recording is provided by the user through an uploaded file. In other implementations, the user provides a truncated version of the recording by uploading a file containing a section of the recording to the distribution platform.

At612, the process600includes transmitting information regarding the selections to a distribution platform.

FIG.7schematically shows a non-limiting embodiment of a computing system700that can enact one or more of the methods and processes described above. Computing system700is shown in simplified form. Computing system700may take the form of one or more personal computers, server computers, tablet computers, home-entertainment computers, network computing devices, gaming devices, mobile computing devices, mobile communication devices (e.g., smart phone), and/or other computing devices.

Computing system700includes a logic machine702and a storage machine704. Computing system700may optionally include a display subsystem706, input subsystem708, communication subsystem710, and/or other components not shown inFIG.7.

Storage machine704includes one or more physical devices configured to hold instructions executable by the logic machine702to implement the methods and processes described herein. When such methods and processes are implemented, the state of storage machine704may be transformed—e.g., to hold different data.

When included, display subsystem706may be used to present a visual representation of data held by storage machine704. This visual representation may take the form of a graphical user interface (GUI). As the herein described methods and processes change the data held by the storage machine704, and thus transform the state of the storage machine704, the state of display subsystem706may likewise be transformed to visually represent changes in the underlying data. Display subsystem706may include one or more display devices utilizing virtually any type of technology. Such display devices may be combined with logic machine702and/or storage machine704in a shared enclosure, or such display devices may be peripheral display devices.

The following paragraphs provide additional support for the claims of the subject application. One aspect provides a computer system for implementing a pre-release of a recording at a distribution platform. The computer system comprises a processor coupled to a storage system that stores instructions, which, upon execution by the processor, cause the processor to present a release interface for the recording, where the release interface includes a first graphical control element having options for confirming the pre-release of the recording, a second graphical control element having options for selecting a release date, and a third graphical control element having options for selecting a pre-release date. The instructions further cause the processor to receive information describing a confirmation of the pre-release of the recording, a selected release date, and a selected pre-release date, wherein the selected pre-release date is before the selected release date. The instructions further cause the processor to provide a truncated version of the recording for the pre-release of the recording. The instructions further cause the processor to transmit the truncated version of the recording to a digital streaming platform, wherein the transmitted truncated version of the recording includes metadata describing the selected pre-release date. In this aspect, additionally or alternatively, the instructions further cause the processor to transmit the recording to the digital streaming platform, wherein the transmitted recording includes metadata describing the selected release date. In this aspect, additionally or alternatively, the release interface further includes a fourth graphical control element having options for selecting a release time and a fifth graphical control element having options for selecting a pre-release time. The received information further describes a selected release time and a selected pre-release time. The truncated version of the recording includes metadata describing the pre-release time. In this aspect, additionally or alternatively, the options for selecting the pre-release date preclude options where the selected pre-release date is the same as or after the selected release date. In this aspect, additionally or alternatively, the options for selecting the pre-release time preclude options where the selected pre-release date and time is less than twenty-four hours before the selected release date and time. In this aspect, additionally or alternatively, providing the truncated version of the recording includes receiving an upload of the truncated version of the recording. In this aspect, additionally or alternatively, providing the truncated version of the recording includes providing the recording and generating the truncated version of the recording using a neural network with the provided recording as an input. In this aspect, additionally or alternatively, the release interface further includes a fourth graphical control element having options for selecting at least one truncation point. The received information further describes at least one selected truncation point and providing the truncated version of the recording includes providing the recording and generating the truncated version of the recording using the provided recording and the at least one selected truncation point. In this aspect, additionally or alternatively, the recording and the truncated version of the recording include similar international standard codes for uniquely identifying media recordings and different product codes for uniquely identifying a trade item. In this aspect, additionally or alternatively, the recording and the truncated version of the recording are associated under a same data file having metadata describing recording information.

Another aspect provides a method for implementing a pre-release of a recording at one or more processors of one or more server computing devices of a distribution platform. The method comprises presenting a release interface for the recording, where the release interface includes a first graphical control element having options for confirming the pre-release of the recording, a second graphical control element having options for selecting a release date, and a third graphical control element having options for selecting a pre-release date. The method further comprises receiving information describing a confirmation of the pre-release of the recording, a selected release date, and a selected pre-release date, wherein the selected pre-release date is before the selected release date. The method further comprises providing a truncated version of the recording for the pre-release of the recording. The method further comprises transmitting the truncated version of the recording to a digital streaming platform, wherein the transmitted truncated version of the recording includes metadata describing the selected pre-release date. In this aspect, additionally or alternatively, the method further comprises transmitting the recording to the digital streaming platform, wherein the transmitted recording includes metadata describing the selected release date. In this aspect, additionally or alternatively, the release interface further includes a fourth graphical control element having options for selecting a release time and a fifth graphical control element having options for selecting a pre-release time. The received information further describes a selected release time and a selected pre-release time. The truncated version of the recording includes metadata describing the pre-release time. In this aspect, additionally or alternatively, the options for selecting the pre-release date preclude options where the selected pre-release date is the same as or after the selected release date. In this aspect, additionally or alternatively, the options for selecting the pre-release time preclude options where the selected pre-release date and time is less than twenty-four hours before the selected release date and time. In this aspect, additionally or alternatively, providing the truncated version of the recording includes receiving an upload of the truncated version of the recording. In this aspect, additionally or alternatively, providing the truncated version of the recording includes providing the recording and generating the truncated version of the recording using a neural network with the provided recording as an input. In this aspect, additionally or alternatively, the release interface further includes a fourth graphical control element having options for selecting at least one truncation point. The received information further describes at least one selected truncation point. Providing the truncated version of the recording includes providing the recording and generating the truncated version of the recording using the provided recording and the at least one selected truncation point. In this aspect, additionally or alternatively, the recording and the truncated version of the recording include similar international standard codes for uniquely identifying media recordings and different product codes for uniquely identifying a trade item.

Another aspect provides a method for offering a pre-release of a recording. The method comprises displaying a release interface for the recording, where the release interface includes a first graphical control element having options for confirming the pre-release of the recording, a second graphical control element having options for selecting a release date, and a third graphical control element having options for selecting a pre-release date. The method further comprises transmitting information to a distribution platform, where the information describes a confirmation of the pre-release of the recording, a selected release date, and a selected pre-release date, and where the selected pre-release date is before the selected release date. The method further comprises providing a truncated version of the recording to the distribution platform.