US20130033971A1 - System and Method for Managing and Distributing Audio Recordings - Google Patents
System and Method for Managing and Distributing Audio Recordings Download PDFInfo
- Publication number
- US20130033971A1 US20130033971A1 US13/198,977 US201113198977A US2013033971A1 US 20130033971 A1 US20130033971 A1 US 20130033971A1 US 201113198977 A US201113198977 A US 201113198977A US 2013033971 A1 US2013033971 A1 US 2013033971A1
- Authority
- US
- United States
- Prior art keywords
- audio
- website
- audio clip
- clip
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/258—Client or end-user data management, e.g. managing client capabilities, user preferences or demographics, processing of multiple end-users preferences to derive collaborative data
- H04N21/25866—Management of end-user data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/27—Server based end-user applications
- H04N21/274—Storing end-user multimedia data in response to end-user request, e.g. network recorder
- H04N21/2743—Video hosting of uploaded data from client
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/41—Structure of client; Structure of client peripherals
- H04N21/414—Specialised client platforms, e.g. receiver in car or embedded in a mobile appliance
- H04N21/4143—Specialised client platforms, e.g. receiver in car or embedded in a mobile appliance embedded in a Personal Computer [PC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/45—Management operations performed by the client for facilitating the reception of or the interaction with the content or administrating data related to the end-user or to the client device itself, e.g. learning user preferences for recommending movies, resolving scheduling conflicts
- H04N21/462—Content or additional data management, e.g. creating a master electronic program guide from data received from the Internet and a Head-end, controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabilities
- H04N21/4622—Retrieving content or additional data from different sources, e.g. from a broadcast channel and the Internet
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/47—End-user applications
- H04N21/475—End-user interface for inputting end-user data, e.g. personal identification number [PIN], preference data
- H04N21/4753—End-user interface for inputting end-user data, e.g. personal identification number [PIN], preference data for user identification, e.g. by entering a PIN or password
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/61—Network physical structure; Signal processing
- H04N21/6106—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network
- H04N21/6125—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network involving transmission via Internet
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/81—Monomedia components thereof
- H04N21/8106—Monomedia components thereof involving special audio data, e.g. different tracks for different languages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/81—Monomedia components thereof
- H04N21/8166—Monomedia components thereof involving executable data, e.g. software
- H04N21/8173—End-user applications, e.g. Web browser, game
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/85—Assembly of content; Generation of multimedia applications
- H04N21/858—Linking data to content, e.g. by linking an URL to a video object, by creating a hotspot
- H04N21/8586—Linking data to content, e.g. by linking an URL to a video object, by creating a hotspot by using a URL
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/251—Learning process for intelligent management, e.g. learning user preferences for recommending movies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/83—Generation or processing of protective or descriptive data associated with content; Content structuring
- H04N21/835—Generation of protective data, e.g. certificates
- H04N21/8352—Generation of protective data, e.g. certificates involving content or source identification data, e.g. Unique Material Identifier [UMID]
Definitions
- the present invention relates to the field of management and distribution of audio recordings and, in particular, to systems, methods and computer program products for recording, playing back, responding to and sharing audio clips on the Internet.
- the system includes an audio management server that stores and distributes audio clips, such as voice, music, sounds, and other recordings made by system users.
- the audio clips can be recorded by system users directly through a central website hosted by the server.
- the audio clips can be recorded on various third-party websites, such as blogs, social networking sites, celebrity sites and the like, using audio web widgets provided by the audio management server.
- audio clips can be recorded using an application for a smart phone, tablet computer or other portable electronic device provided by the audio management server.
- a method for recording, playing back, responding to and sharing audio clips involves the audio server receiving from a first third-party website a request by a website visitor to record an audio clip.
- the audio management server provides to the first website an audio widget operable to record, play back, respond to and share audio clips.
- the audio widget records an audio clip from a website visitor, assigns a unique identifier to the recorded audio clip and a unique identifier of the first website, and returns this information to the audio server.
- the server stores the received information in a database.
- the server then provides to the audio widget a link to be posted on the first website for accessing the recorded audio clip through the audio widget.
- the server receives from the audio widget on the first website a request by the website visitor to share the audio clip on a second third-party website, the server posts on the second website the link or the audio widget for accessing the recorded audio clip through the first website where the audio clip was recorded.
- a method for recording; playing back, responding to and sharing audio clips comprises the audio management server storing an audio clip recorded on a first third-party website. The server then posts on a second third-party website a link for accessing the audio clip.
- the server determines if the playback request came from the first third-party website or the second third-party website. If the request came from the first third-party website where the audio clip was recorded, the server provides to the first third-party website the requested audio clip and an audio widget operable to play back, respond to and share the requested audio clip. If the request came from the second third-party website, the server redirects the website visitor to the first website where the audio clip was recorded for playback of the audio clip on the first website using the audio widget of the first third-party website.
- a method for recording, playing back, responding to and sharing audio clips comprises the audio management server receiving from a second website a request by a website visitor to play back a first audio clip, which was recorded on a first website and whose link was posted on the second website.
- the server redirects the visitor to the first website where the audio clip was recorded and provides to the first website the requested first audio clip and an audio widget operable to play back, respond to and share the first audio clip.
- the server receives from the first third-party website a request by the website visitor to record a second audio clip in response to the first audio clip, the server instructs the audio widget on the first website to record the second audio clip.
- the server posts on the first and second third-party websites links for accessing the first and second audio clip and/or the audio widgets for playing back, responding to and sharing the audio clips.
- FIG. 1 illustrates a schematic diagram of the audio management system in accordance with one example embodiment.
- FIG. 2 illustrates one example embodiment of the audio widget.
- FIG. 3 illustrates an exemplary interface of the audio management application.
- FIG. 4 illustrates another exemplary interface of the audio management application.
- FIGS. 5A and B illustrate a flow chart of a method of operation of the audio management system in accordance with one example embodiment.
- FIGS. 6A and B illustrate a flow chart of another method of operation of the audio management system in accordance with another example embodiment.
- FIGS. 7A and B illustrate a flow chart of yet another method of operation of the audio management system in accordance with another example embodiment.
- FIG. 8 illustrates a schematic diagram of a computer system in accordance with one example embodiment.
- Example embodiments of the present invention are described herein in the context of systems, methods and computer program products for recording, playing back, responding to and sharing of audio clips through a plurality of third-party websites.
- Those of ordinary skill in the art will realize that the following description is illustrative only and is not intended to be in any way limiting. Other embodiments will readily suggest themselves to those skilled in the art having the benefit of this disclosure.
- FIG. 1 illustrates one exemplary embodiment of a system for managing and distributing audio recordings.
- the system 100 comprises a computer server 110 with an audio management application 120 deployed thereon, an audio content database 130 , and a user account database 140 .
- the system 100 is accessible via the Internet 150 by visitors 163 , 165 and 175 of third-party websites 160 and 170 , which may interact with the audio management application 120 via application program interfaces (APIs) 121 and 121 .
- a third-party website includes a website owned/operated by an individual or company unaffiliated with owner/operator of system 100 , but which may be registered with system 100 .
- system 100 may be directly accessed by registered user 185 and 195 through a central website 125 provide by application 120 hosted by the audio management server 110 .
- server 110 may comprise a single server or a group of servers.
- system 100 may employ cloud servers, whereby the number of servers 110 may be scalable and may differ at any given time, depending on the number of users and/or visitors who are utilizing the system 100 at different time points.
- the audio management application 120 may be implemented as a stand-alone application for use on a portable communication device, such as a smart phone or a tablet computer.
- the application 120 will utilize device's wireless or cellular network interface to communicate with the audio management server 110 .
- the application 120 will include substantially the same functionality as in the embodiments of the web-based application 120 described above.
- the application 120 may be configured to perform the functions of recording audio clips on the portable communication device, playback of the recorded audio clips, storage of the audio clips on the server 110 , retrieval of audio clips and responses to the audio clips from the server 110 , recording of response audio clips, and sharing of audio clips on various third-party websites.
- Other functionality of the application 120 for portable communication devices may include, but not limited to customization of audio web widgets posted on third-party websites, geo tagging of the recorded audio clips or response audio clips, attachment of photos to the audio clips, etc.
- an audio management application 120 provides a central website 125 , accessible via a Web browser to registered system users 185 and 195 . Access to the website 125 may be controlled, so that the user must log in or be otherwise authenticated as being authorized to use the application 120 .
- the application 120 allows registered users 185 and 195 to record audio clips, playing back the recorded clips, share the recorded audio clips through various social networking sites, such as Facebook® and Twitter®, email the recorded audio clips to others, listen to audio responses recorded by others, and record responses to the audio clips through the website 125 .
- the application 120 also allows registered users 185 and 195 to review statistical information about the number of times the user-recorded audio clips were played back and the source websites from which the audio clips were accessed for playback.
- the audio management system 100 maintains an audio content database 130 and a user account database 140 .
- the audio content database 130 stores all recorded audio clips along with a unique identifier of each audio clip and identifier of the source website (e.g., website's URL) where the clip was recorded.
- the audio clips can be stored in MP3 format or other known digital audio encoding format.
- the audio content database 130 may also stores additional metadata associated with the audio clips including, but not limited to, the descriptive name of the clip, duration of clip, text comments associated with the clip, photos or other images associated with the clip and other metadata.
- the audio content database 130 may also store, for each audio clip, a list of identifiers of related audio clips, e.g., one or more audio clips recorded in response to the original audio clip. In this manner, the server 110 can reconstruct an audio conversation thread between users.
- the user account database 140 stores a plurality of user accounts of registered users 185 and 195 .
- Each user account may include user's name and logging information.
- Each user account further contains a list of identifiers of audio clips recorded by the user, identifier of a source website (e.g., website's URL) where each clip was recorded, identifiers of the websites (e.g., websites' URLs) where the audio clips were shared, information about the number of times each audio clip was played back, identifiers of websites from which the audio clips were accessed.
- the following list is not inclusive and there may be other items of information stored in the user account database 140 .
- the user account may also store user-provided customization data for audio widgets used for recording, playing back, responding to and sharing audio clips on third-party websites 160 and 170 , as will be described in a greater detail below.
- the non-audio related metadata described above, such as text comments, photos and images, associated with the audio clips may be stored in the user account database 140 instead of the audio content database 130 .
- the user account may store login information for other websites, such as Facebook® and Twitter®, through which the user may wish to share the recorded audio clips.
- the recording, playback, responding to and sharing of audio clips on third-party websites 160 or 170 may be implemented using an audio web widget 161 or 171 provided by the audio management server 110 in accordance with one example embodiment.
- An audio widget may be implemented as a stand-alone web application or script provided by the server 110 that can be embedded into third-party websites by a website owner/developer.
- the audio widget may be provided as a downloadable web application or script implemented using Web technologies, such as JavaScript, Flash, HTML and CSS.
- the owner of the third-party website 160 may post on its site a link (e.g., an HTML button), which, when activated by a website visitor 163 , would instruct the visitor's Web browser to retrieve from the audio management server 110 an audio widget 161 for recording, playback, responding to and sharing of audio clips on the website 160 .
- the audio widget 161 may be activated as a pop-up widget or an inline widget anywhere on the website 160 .
- FIG. 2 depicts one example embodiment of the audio widget provided by the audio management server 110 .
- Audio widget 200 may be downloaded/activated when a website visitor 163 clicks “record blurt” button 205 posted on the third-party website 160 .
- the audio widget 200 may have a multi-modular format with each module 210 - 240 performing one or more different functions. The modules may be closed by the user or automatically when it is no longer needed. Modules 210 and 220 may be used to record a new audio clip. Module 215 provides a record button 215 for recording a new audio clip. The duration of the recording may be limited to 30 seconds or different duration.
- Pressing of the record button 210 activates Wowza® Media Server or another application capable of recording/playback of streaming audio from the visitor's computer microphone in real-time.
- the recording may be stopped using stop button 225 .
- the widget 200 may encapsulate the recorded audio clip in a FLV container and transcode it into MP3 format.
- the widget 200 then uses APIs 121 and 121 to send the audio clip to the server 110 for storage in the database 130 .
- the audio management server 110 assigns a unique identifier to the new audio clip, stores the audio clip in the audio content database 130 , and returns to the audio widget 200 a link 235 for accessing the audio clip for playback.
- the audio clip may be played back using players 233 of module 230 .
- the audio clip link 235 may include a URL of the server 130 (e.g., http://blurts.com) and the unique identifier of the audio clip (e.g., abc121).
- the server 110 may automatically post the audio clip link 235 on the website 160 , so when the visitor 163 leaves the website 160 and a new visitor 165 subsequently visits the website 160 , the audio clip link 235 will be displayed on the website 160 .
- the visitor 165 may play back, respond to and share the audio clip associated with link 235 using module 240 of the embedded audio widget 200 . If the audio widget 200 is not embedded on the website 160 , it may be loaded by the visitor's Web browser when the visitor 165 clicks on the audio clip link 235 posted on the website 160 .
- the audio widget 200 also allows the website visitor 163 to store the recorded audio clip into his/her account on the audio management server 110 .
- the website visitor 163 is a registered user of the audio management application 120 , or wishes to become one, the visitor may login into his/her user account, or open a new account, by pressing “account” button 231 of the widget 200 and entering user name and login information.
- the widget 200 will pass this information through APIs 121 and 121 to the audio management application 120 .
- the application 120 will use the received information to identify visitor's user account in the database 140 and update it with information about newly recorded audio clip. This information may include, but not limited to, the assigned identifier of the audio clip and an identifier of the website 160 where the audio clip was recorded. If the visitor 163 does not register with or have a user account on the server 110 , the recorded audio clip may be saved anonymous by the audio management server 110 according to one embodiment.
- the audio widget 200 also allows visitors to share the recorded audio clips through various Web platforms, such as popular social networking sites, and the like.
- the audio widget 200 opens a menu of third-party platforms with which the audio clip can be shared.
- the available Web platforms include, but not limited to: Facebook®, Twitter®, LinkedIn®, MySpace®, Google+®, Flickr® and the like.
- the visitor 163 may select one or more websites 170 for sharing the audio clip and provide the required website login information. If the visitor 163 is already registered with the server 110 , the server will retrieve from the visitor's user account in the database 140 the required login information for the selected website 170 . This information may have been previously provided by the user during the registration process. The server 110 will then post on the selected website 170 , directly or using a third-party service, the audio clip link 235 for accessing the audio clip from the audio management server 110 .
- the system 100 allows a visitor 175 of the website 170 to play back, respond to and further share the audio clip.
- the visitors' Web browser sends an HTML request to the audio management server 110 to retrieve the audio clip associated with the link.
- the server 110 retrieves a unique identifier of the audio clip from the link 235 and uses it to identify the associate audio clip.
- the server 110 also compares an identifier of the website from which the request for the audio clip came from with the identifier of the website where the audio clip was recorded, which is stored in the audio content database 130 .
- server 110 will determine that two website identifiers are different. When the two website identifiers are different, the server 110 is configured to redirect the visitor's Web browser to the website 160 wherein the clip was recorded. Once on the website 160 , the server 110 activates the audio widget 200 , which in turn loads the requested audio clip for playback using player 243 of the module 240 to the visitor 175 .
- the audio widget 200 also allows website visitor 175 (or visitor 165 ) to record their own second audio clip in response to the first audio clip recorded by visitor 163 .
- the visitor may press “blurt-back” button 245 , which activates modules 210 and 220 for recording and storing a second audio clip. Functionality of these modules has been described above.
- a registered visitor 175 may store the recorded audio clip into his/her account on the audio management server 110 , as described above.
- the server 100 associates the identifier of the second audio clip with the identifier of the second audio clip in the database 130 to indicate that the second audio clip relates to the first audio clip, whereby reconstructing an audio conversation thread among multiple system users.
- the visitor 175 or any other visitor of the website 160 may view and play back the entire audio conversation thread comprising multiple audio clips recorded by various visitors of website 160 or other websites where the audio clip was shared.
- the visitor 175 can press “blurt-backs” button 247 of the module 240 of the audio widget 200 in response to which the widget retrieves from the server 100 information about all audio clips related to (e.g., recorded in response to) the first audio clip or any other clip in the audio conversation thread.
- the audio widget 200 may than generate a copy of module 240 for each related audio clip in the given audio conversation thread.
- the module 240 may indicated the name of the user who recorded the clip (or anonymous user if the audio clip was recorded by an unregistered visitor), the date and time when the audio clip was recorded, and an identifier of the website where the clip was recorded or from which the visitor who recorded the clip was redirected from.
- the visitor 175 may then play back each audio clip one at a time using player 243 of the module 240 of the widget 200 .
- the visitor 175 may share any one of the related audio clips through various Web platforms, such as popular social networking sites and the like.
- the visitor 175 may press “share” button 237 in the module 240 and the audio widget 200 will opens a menu of third-party Web platforms on which the audio clip can be shared.
- the available Web platforms include, but not limited to: Facebook®, Twitter®, LinkedIn®, MySpace®, Google+®, Flickr® and others.
- the visitor 175 may then select one or more websites 170 for sharing the audio clip and provide the required website login information.
- the server 110 will then post an audio clip link 235 on the selected website 170 .
- FIG. 3 depicts an exemplary user account interface of the central website 125 .
- the interface 300 includes information about each audio conversation thread initiated by the user of said account.
- Section 310 shows the original audio clip recorded by the user and various associated metadata, such as title, time and date of recoding, audio clip link, duration of the clip, and the number of times the clip was shared and where.
- Section 320 shows a list of audio responses associated with the original audio clip as well as various information about the audio response, including but not limited to the title of each clip, time and date of recoding, audio clip link, duration of the clip, the number of times the clip was shared and where, and the names of users who recorded the response clips.
- FIG. 4 depicts another exemplary user account interface of the central website 125 provided by of the application 120 .
- This interface 400 shows statistical information about audio clip 405 and associated audio conversation thread.
- section 410 shows a list of listening sources, i.e., the URLs of websites where audio clip 405 was played back or was redirected for playback from.
- Pie chart 420 shows the number of times that audio clip 405 was played back.
- Time chart 430 tracks the number of listens of clip 405 over time.
- the collected statistical information is not limited to the above-described and may include other types of information about audio clips and the associated audio conversation thread. In addition, other graphical or numerical forms may be used to represent the collected statistical data.
- the audio management server 110 may perform a speech-to-text conversion of the stored audio clips for data mining or other purposes. For example, the server 110 may analyze the text of an individual audio clips or the entire audio conversation thread to determine its subject matter. This information may be used to determine interests and views of the user who recorded the original clip as well as to identify other users who contributed to the audio conversation thread, and therefore share similar interests or views. In addition, this information may be used to monetize the audio management system by inserting contextual ads into the audio widget 200 when it plays back a particular audio clip.
- the audio management server 110 may insert an advertisement of a major consumer electronics retailer with a discount or sale offer on the discussed gaming console.
- the users of the audio management system 100 may monetize their audio clips by charging listeners for each playback of the audio clip.
- a celebrity person may register with the audio management system 100 and record using the central website 125 a short statement, announcement or message to his/her fans, and share the recorded audio clip on his/her Facebook® or Twitter® webpage.
- the server 110 would allow the celebrity to assign a monetary value (e.g., $0.10) for each listen of the audio clip.
- the audio widget 200 and server 110 may be configured to use PayPal® or other online money transfer system to collect payments from listeners and transfer the money to the celebrity's account. If the celebrity has a large number of Facebook or Twitter followers, the celebrity may collect substantial amount of money from the fans who listened to his/her audio clips.
- the celebrity may embed the audio widget 200 on his personal website, record the audio clips on his personal website, and post the clips on his/her Facebook® or Twitter® webpages.
- the fans will click on the audio clip link, they will be redirected to celebrity's personal website, thereby driving visitor traffic to celebrity's website.
- FIGS. 5A and B depict a flow chart of a method of operation of the audio management system in accordance with one example embodiment.
- the audio management server receives from a first website a request by a first website visitor to record an audio clip on the first website.
- the server provides to the first website an audio widget operable to record, play back, respond to and share audio clips.
- the audio widget records an audio clip from the first website visitor.
- the widget requests the visitor to provide login information for the user account on the server.
- the audio widget sends the recorded audio clip and visitor's log information to the server.
- the server receives the audio clip, assigns a unique identifier to the audio clip, stores the audio clip in the audio content database, and generates a link to the audio clip.
- the link comprises an identifier of the audio server and unique identifier of the audio clip.
- the server also access user account using the provided login information, and stores the audio clip identifier and a first website identifier in the user account. If the visitor did not provide account login information, the audio clip may be stored unanimously.
- the server provides to the audio widget an audio clip link to be posted on the first website for accessing the audio clip through the audio widget.
- the server receives from the audio widget on the first website a request by the first website visitor to share the recorded audio clip on a second website.
- the server retrieves from the user account login information for the second website or requests the first website visitor to provide the required login information.
- the server posts on the second website the audio clip link or the audio widget for recording, playback, responding to and sharing of the audio clip.
- the server stores in the user account an identifier of the second website where the audio clip was posted.
- the server receives from the second website a request by a second website visitor to play back the audio clip whose link is posted on the second website.
- the server redirects the visitor to the first website where the audio clip was recorded.
- the server provides the requested audio clip to the audio widget on the first website for playback of the clip to the second website visitor.
- FIGS. 6A and B depict a flow chart of another method of operation of the audio management system in accordance with another example embodiment.
- the audio management server stores a first audio clip recorded on a first website.
- the server generates a link for accessing the first audio clip from the audio server.
- the server posts on the second website the audio clip link for accessing the first audio clip.
- the server receives a request by a website visitor to play back the first audio clip.
- the server determines from the request an identifier of the website where the request came from.
- the server compares the website identifier with the first website wherein the clip was recorded.
- the server determines if the playback request came from the first website or the second website. If the request came from the second website, at step 640 , the server redirects the website visitor to the first website where the first audio clip was recorded for playback of the first audio clip on the first website. If the request came from the first website or the visitor has been just redirected to the first website, at step 645 , the server provides to the first website the first audio clip and an audio widget that enables the visitor to play back, respond to and share the first audio clip on the first website.
- the server identifies a user of the audio server who recorded the first audio clip.
- the server accesses the user account, updates a playback counter associated with the first audio clip, and stores an identifier of the second website in the user account.
- the server receives from the website visitor a request to record a second audio clip in response to the first audio clip recorded on the first website and instructs the audio widget on the first website to record the second audio clip.
- the server posts on the first and second websites audio clip links for accessing the second audio clip.
- the server receives from the website visitor a request to record a third audio clip in response to the second audio clip recorded on the first website.
- the server provides audio widget for recording the third audio clip of the first website.
- the server posts on the first and second websites audio clip links for accessing the third audio clip recorded on the first website.
- FIGS. 7A and B depict a flow chart of yet another method of operation of the audio management system in accordance with another example embodiment.
- the audio management server receives from a second website a request by a website visitor to play back a first audio clip, which was recorded on a first website and whose link was posted on the second website.
- the server redirects the visitor to the first website where the audio clip was recorded.
- the server provides to the first website the requested first audio clip and an audio widget operable to play back, respond to and share the first audio clip.
- the server receives from the first website a request by a website visitor to record a second audio clip in response to the first audio clip.
- the audio widget on the first website records the second audio clip.
- the server posts on the first and second websites audio clip links for accessing the first and second audio clips or the audio widgets for playing back, responding to and sharing the first and second audio clips.
- the server determines whether the first and second audio clips were recorded by the same or different website visitors. If it is determined at step 740 that the clips were recorded by the same visitor, at step 745 , the server stores in the user account of said visitor the identifier of the first audio clip and an identifier of the first website, the identifier of the second audio clip and an identifier of the second website, and the indicator that the second audio clip was recorded in response to the first audio clip.
- the server stores in the user account of the first website visitor who recorded the first audio clip the identifier of the first audio clip, an identifier of the first website, the identifier of the second audio clip, and the indicator that the second audio clip was recorded in response to the first audio clip.
- the server stores in the user account of the second website visitor who recorded the second audio clip the identifier of the second audio clip, an identifier of the second website, the identifier of the first audio clip, and the indicator that the second audio clip was recorded in response to the first audio clip.
- FIG. 8 depicts one example embodiment of a computer system 5 , which could be used to implement the audio management server 110 of the audio management system 100 .
- computer system 5 may include one or more processors 15 , memory 20 , one or more hard disk drive(s) 30 , optical drive(s) 35 , serial port(s) 40 , graphics card 45 , audio card 50 and network card(s) 55 connected by system bus 10 .
- System bus 10 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus and a local bus using any of a variety of known bus architectures.
- Processor 15 may include one or more Intel® Core 2 Quad 2.33 GHz processors or other type of microprocessor.
- System memory 20 may include a read-only memory (ROM) 21 and random access memory (RAM) 23 .
- Memory 20 may be implemented as in DRAM (dynamic RAM), EPROM, EEPROM, Flash or other type of memory architecture.
- ROM 21 stores a basic input/output system 22 (BIOS), containing the basic routines that help to transfer information between the components of computer system 5 , such as during start-up,
- BIOS basic input/output system 22
- RAM 23 stores operating system 24 (OS), such as Windows® XP Professional or other type of operating system, that is responsible for management and coordination of processes and allocation and sharing of hardware resources in computer system 5 .
- OS operating system 24
- Memory 20 also stores applications and programs 25 , such as services 306 .
- Memory 20 also stores various runtime data 26 used by programs 25 .
- Computer system 5 may further include hard disk drive(s) 30 , such as SATA magnetic hard disk drive (HDD), and optical disk drive(s) 35 for reading from or writing to a removable optical disk, such as a CD-ROM, DVD-ROM or other optical media.
- Hard disk drive(s) 30 such as SATA magnetic hard disk drive (HDD)
- optical disk drive(s) 35 for reading from or writing to a removable optical disk, such as a CD-ROM, DVD-ROM or other optical media.
- Drives 30 and 35 and their associated computer-readable media provide non-volatile storage of computer readable instructions, data structures, applications and program modules/subroutines that implement algorithms and methods disclosed herein.
- exemplary computer system 5 employs magnetic and optical disks
- other types of computer readable media that can store data accessible by a computer system 5 , such as magnetic cassettes, flash memory cards, digital video disks, RAMs, ROMs, EPROMs and other types of memory may also be used in alternative embodiments of the computer system.
- Computer system 5 further includes a plurality of serial ports 40 , such as Universal Serial Bus (USB), for connecting data input device(s) 75 , such as keyboard, mouse, touch pad and other.
- Serial ports 40 may be also be used to connect data output device(s) 80 , such as printer, scanner and other, as well as other peripheral device(s) 85 , such as external data storage devices and the like.
- System 5 may also include graphics card 45 , such as nVidia® GeForce® GT 240M or other video card, for interfacing with a monitor 60 or other video reproduction device.
- System 5 may also include an audio card 50 for reproducing sound via internal or external speakers 65 .
- system 5 may include network card(s) 55 , such as Ethernet, WiFi, GSM, Bluetooth or other wired, wireless, or cellular network interface for connecting computer system 5 to network 70 , such as the Internet.
- the algorithms and methods described herein may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or code on a non-transitory computer-readable medium.
- Computer-readable medium includes both computer storage and communication medium that facilitates transfer of a computer program from one place to another.
- a storage medium may be any available media that can be accessed by a computer.
- such computer-readable medium can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
- any connection may be termed a computer-readable medium.
- a computer-readable medium For example, if software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
- DSL digital subscriber line
Abstract
Disclosed are system, methods and computer program products for recording, playing back, responding to and sharing audio recordings. In one example embodiment, the system includes an audio management server that stores and distributes through various third-party websites audio clips, such as voice, music, sounds, and other recordings made by system users. The audio clips can be recorded by system users directly through a central website hosted by the server. Alternatively, the audio clips can be recorded on various third-party websites using audio widgets provided by the audio management server. In addition, the recorded audio clips can be shared on various other third-party websites, such as blogs, social networking sites, celebrity sites and the like, using the audio widget provided by the server.
Description
- The present invention relates to the field of management and distribution of audio recordings and, in particular, to systems, methods and computer program products for recording, playing back, responding to and sharing audio clips on the Internet.
- The popularity of the Internet and World Wide Web has spurred the growth in the number of online blogs, chats, social networking sites, celebrity sites and other types of websites that facilitate communication between website visitors. Typically, visitors can post text, graphics and video content, view content posted by other visitors and comment on the content posted on these websites. However, visitors' comments are typically limited to text or simple graphics due to limitations of the current Web technologies. In particular, currently-available systems do not efficiently allow visitors to record audio comments associated with content published on the website, share the recorded audio comments with other website visitors, respond in audio form to the recorded audio comments, and publish the recorded audio comments on other Web platforms, thereby fueling further discourse. Accordingly, there is a need for a new system for management and distribution of audio comments on the Web.
- Disclosed are system, methods and computer program products for recording, playing back, responding to and sharing audio comments or clips on the Internet. In one example embodiment, the system includes an audio management server that stores and distributes audio clips, such as voice, music, sounds, and other recordings made by system users. In one example embodiment, the audio clips can be recorded by system users directly through a central website hosted by the server. In another example embodiment, the audio clips can be recorded on various third-party websites, such as blogs, social networking sites, celebrity sites and the like, using audio web widgets provided by the audio management server. Yet in another embodiment, audio clips can be recorded using an application for a smart phone, tablet computer or other portable electronic device provided by the audio management server.
- In one example embodiment, a method for recording, playing back, responding to and sharing audio clips involves the audio server receiving from a first third-party website a request by a website visitor to record an audio clip. The audio management server provides to the first website an audio widget operable to record, play back, respond to and share audio clips. The audio widget records an audio clip from a website visitor, assigns a unique identifier to the recorded audio clip and a unique identifier of the first website, and returns this information to the audio server. The server stores the received information in a database. The server then provides to the audio widget a link to be posted on the first website for accessing the recorded audio clip through the audio widget. If the server receives from the audio widget on the first website a request by the website visitor to share the audio clip on a second third-party website, the server posts on the second website the link or the audio widget for accessing the recorded audio clip through the first website where the audio clip was recorded.
- In another example embodiment, a method for recording; playing back, responding to and sharing audio clips comprises the audio management server storing an audio clip recorded on a first third-party website. The server then posts on a second third-party website a link for accessing the audio clip. When the server receives a request by a website visitor to play back the audio clip, the server determines if the playback request came from the first third-party website or the second third-party website. If the request came from the first third-party website where the audio clip was recorded, the server provides to the first third-party website the requested audio clip and an audio widget operable to play back, respond to and share the requested audio clip. If the request came from the second third-party website, the server redirects the website visitor to the first website where the audio clip was recorded for playback of the audio clip on the first website using the audio widget of the first third-party website.
- In another example embodiment, a method for recording, playing back, responding to and sharing audio clips comprises the audio management server receiving from a second website a request by a website visitor to play back a first audio clip, which was recorded on a first website and whose link was posted on the second website. The server redirects the visitor to the first website where the audio clip was recorded and provides to the first website the requested first audio clip and an audio widget operable to play back, respond to and share the first audio clip. When the server receives from the first third-party website a request by the website visitor to record a second audio clip in response to the first audio clip, the server instructs the audio widget on the first website to record the second audio clip. The server then posts on the first and second third-party websites links for accessing the first and second audio clip and/or the audio widgets for playing back, responding to and sharing the audio clips.
- The above simplified summary of example embodiments serves to provide a basic understanding of the invention. This summary is not an extensive overview of all contemplated aspects of the invention, and is intended to neither identify key or critical elements of all embodiments nor delineate the scope of any or all embodiments. Its sole purpose is to present one or more embodiments in a simplified form as a prelude to the more detailed description of the invention that follows. To the accomplishment of the foregoing, the one or more embodiments comprise the features described and particularly pointed out in the claims.
- The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more example embodiments of the invention and, together with the detailed description serve to explain their principles and implementations.
- In the drawings:
-
FIG. 1 illustrates a schematic diagram of the audio management system in accordance with one example embodiment. -
FIG. 2 illustrates one example embodiment of the audio widget. -
FIG. 3 illustrates an exemplary interface of the audio management application. -
FIG. 4 illustrates another exemplary interface of the audio management application. -
FIGS. 5A and B illustrate a flow chart of a method of operation of the audio management system in accordance with one example embodiment. -
FIGS. 6A and B illustrate a flow chart of another method of operation of the audio management system in accordance with another example embodiment. -
FIGS. 7A and B illustrate a flow chart of yet another method of operation of the audio management system in accordance with another example embodiment. -
FIG. 8 illustrates a schematic diagram of a computer system in accordance with one example embodiment. - Example embodiments of the present invention are described herein in the context of systems, methods and computer program products for recording, playing back, responding to and sharing of audio clips through a plurality of third-party websites. Those of ordinary skill in the art will realize that the following description is illustrative only and is not intended to be in any way limiting. Other embodiments will readily suggest themselves to those skilled in the art having the benefit of this disclosure. Reference will now be made in detail to implementations of the example embodiments of the invention as illustrated in the accompanying drawings. The same reference indicators will be used to the extent possible throughout the drawings and the following description to refer to the same or like items.
-
FIG. 1 illustrates one exemplary embodiment of a system for managing and distributing audio recordings. Thesystem 100 comprises acomputer server 110 with anaudio management application 120 deployed thereon, anaudio content database 130, and auser account database 140. In one embodiment, thesystem 100 is accessible via the Internet 150 byvisitors party websites audio management application 120 via application program interfaces (APIs) 121 and 121. A third-party website includes a website owned/operated by an individual or company unaffiliated with owner/operator ofsystem 100, but which may be registered withsystem 100. In another embodiment, thesystem 100 may be directly accessed by registereduser central website 125 provide byapplication 120 hosted by theaudio management server 110. In one example embodiment, theserver 110 may comprise a single server or a group of servers. In another embodiment, thesystem 100 may employ cloud servers, whereby the number ofservers 110 may be scalable and may differ at any given time, depending on the number of users and/or visitors who are utilizing thesystem 100 at different time points. - In one example embodiment, the
audio management application 120 may be implemented as a stand-alone application for use on a portable communication device, such as a smart phone or a tablet computer. In this case, theapplication 120 will utilize device's wireless or cellular network interface to communicate with theaudio management server 110. In this embodiment, theapplication 120 will include substantially the same functionality as in the embodiments of the web-basedapplication 120 described above. In particular, theapplication 120 may be configured to perform the functions of recording audio clips on the portable communication device, playback of the recorded audio clips, storage of the audio clips on theserver 110, retrieval of audio clips and responses to the audio clips from theserver 110, recording of response audio clips, and sharing of audio clips on various third-party websites. Other functionality of theapplication 120 for portable communication devices may include, but not limited to customization of audio web widgets posted on third-party websites, geo tagging of the recorded audio clips or response audio clips, attachment of photos to the audio clips, etc. - In one example embodiment, an
audio management application 120 provides acentral website 125, accessible via a Web browser to registeredsystem users website 125 may be controlled, so that the user must log in or be otherwise authenticated as being authorized to use theapplication 120. In one example embodiment, theapplication 120 allows registeredusers website 125. In other example embodiments, theapplication 120 also allows registeredusers - To effectuate the above functions, the
audio management system 100 maintains anaudio content database 130 and auser account database 140. In one example embodiment, theaudio content database 130 stores all recorded audio clips along with a unique identifier of each audio clip and identifier of the source website (e.g., website's URL) where the clip was recorded. The audio clips can be stored in MP3 format or other known digital audio encoding format. In another example embodiment, theaudio content database 130 may also stores additional metadata associated with the audio clips including, but not limited to, the descriptive name of the clip, duration of clip, text comments associated with the clip, photos or other images associated with the clip and other metadata. In one example embodiment, theaudio content database 130 may also store, for each audio clip, a list of identifiers of related audio clips, e.g., one or more audio clips recorded in response to the original audio clip. In this manner, theserver 110 can reconstruct an audio conversation thread between users. - In one example embodiment, the
user account database 140 stores a plurality of user accounts of registeredusers user account database 140. For example, the user account may also store user-provided customization data for audio widgets used for recording, playing back, responding to and sharing audio clips on third-party websites user account database 140 instead of theaudio content database 130. Yet in another example, the user account may store login information for other websites, such as Facebook® and Twitter®, through which the user may wish to share the recorded audio clips. - As indicated above, the recording, playback, responding to and sharing of audio clips on third-
party websites audio web widget audio management server 110 in accordance with one example embodiment. An audio widget may be implemented as a stand-alone web application or script provided by theserver 110 that can be embedded into third-party websites by a website owner/developer. Alternatively, the audio widget may be provided as a downloadable web application or script implemented using Web technologies, such as JavaScript, Flash, HTML and CSS. In the latter case, the owner of the third-party website 160 may post on its site a link (e.g., an HTML button), which, when activated by awebsite visitor 163, would instruct the visitor's Web browser to retrieve from theaudio management server 110 anaudio widget 161 for recording, playback, responding to and sharing of audio clips on thewebsite 160. Theaudio widget 161 may be activated as a pop-up widget or an inline widget anywhere on thewebsite 160. -
FIG. 2 depicts one example embodiment of the audio widget provided by theaudio management server 110.Audio widget 200 may be downloaded/activated when awebsite visitor 163 clicks “record blurt”button 205 posted on the third-party website 160. In one example embodiment, theaudio widget 200 may have a multi-modular format with each module 210-240 performing one or more different functions. The modules may be closed by the user or automatically when it is no longer needed.Modules Module 215 provides arecord button 215 for recording a new audio clip. The duration of the recording may be limited to 30 seconds or different duration. Pressing of therecord button 210 activates Wowza® Media Server or another application capable of recording/playback of streaming audio from the visitor's computer microphone in real-time. The recording may be stopped usingstop button 225. Thewidget 200 may encapsulate the recorded audio clip in a FLV container and transcode it into MP3 format. Thewidget 200 then usesAPIs server 110 for storage in thedatabase 130. - In one example embodiment, the
audio management server 110 assigns a unique identifier to the new audio clip, stores the audio clip in theaudio content database 130, and returns to the audio widget 200 alink 235 for accessing the audio clip for playback. The audio clip may be played back usingplayers 233 ofmodule 230. In one example embodiment, theaudio clip link 235 may include a URL of the server 130 (e.g., http://blurts.com) and the unique identifier of the audio clip (e.g., abc121). In one example embodiment, theserver 110 may automatically post the audio clip link 235 on thewebsite 160, so when thevisitor 163 leaves thewebsite 160 and anew visitor 165 subsequently visits thewebsite 160, theaudio clip link 235 will be displayed on thewebsite 160. Thevisitor 165 may play back, respond to and share the audio clip associated withlink 235 usingmodule 240 of the embeddedaudio widget 200. If theaudio widget 200 is not embedded on thewebsite 160, it may be loaded by the visitor's Web browser when thevisitor 165 clicks on the audio clip link 235 posted on thewebsite 160. - In one example embodiment, the
audio widget 200 also allows thewebsite visitor 163 to store the recorded audio clip into his/her account on theaudio management server 110. In particular, if thewebsite visitor 163 is a registered user of theaudio management application 120, or wishes to become one, the visitor may login into his/her user account, or open a new account, by pressing “account”button 231 of thewidget 200 and entering user name and login information. Thewidget 200 will pass this information throughAPIs audio management application 120. Theapplication 120 will use the received information to identify visitor's user account in thedatabase 140 and update it with information about newly recorded audio clip. This information may include, but not limited to, the assigned identifier of the audio clip and an identifier of thewebsite 160 where the audio clip was recorded. If thevisitor 163 does not register with or have a user account on theserver 110, the recorded audio clip may be saved anonymous by theaudio management server 110 according to one embodiment. - In another example embodiment, the
audio widget 200 also allows visitors to share the recorded audio clips through various Web platforms, such as popular social networking sites, and the like. In particular, when thevisitor 163 presses “share”button 237, theaudio widget 200 opens a menu of third-party platforms with which the audio clip can be shared. The available Web platforms include, but not limited to: Facebook®, Twitter®, LinkedIn®, MySpace®, Google+®, Flickr® and the like. Thevisitor 163 may select one ormore websites 170 for sharing the audio clip and provide the required website login information. If thevisitor 163 is already registered with theserver 110, the server will retrieve from the visitor's user account in thedatabase 140 the required login information for the selectedwebsite 170. This information may have been previously provided by the user during the registration process. Theserver 110 will then post on the selectedwebsite 170, directly or using a third-party service, the audio clip link 235 for accessing the audio clip from theaudio management server 110. - Once the
audio clip link 235 is posted on anotherwebsite 170, such as Facebook®, Twitter® or other social networking site, thesystem 100 allows avisitor 175 of thewebsite 170 to play back, respond to and further share the audio clip. In particular, when thevisitor 175 clicks on the audio clip link 235 posted on thewebsite 170, the visitors' Web browser sends an HTML request to theaudio management server 110 to retrieve the audio clip associated with the link. In response, theserver 110 retrieves a unique identifier of the audio clip from thelink 235 and uses it to identify the associate audio clip. Theserver 110 also compares an identifier of the website from which the request for the audio clip came from with the identifier of the website where the audio clip was recorded, which is stored in theaudio content database 130. In the given example, the audio clip was recorded onwebsite 160 and the request for the audio clip came fromwebsite 170. Therefore,server 110 will determine that two website identifiers are different. When the two website identifiers are different, theserver 110 is configured to redirect the visitor's Web browser to thewebsite 160 wherein the clip was recorded. Once on thewebsite 160, theserver 110 activates theaudio widget 200, which in turn loads the requested audio clip forplayback using player 243 of themodule 240 to thevisitor 175. - In one example embodiment, the
audio widget 200 also allows website visitor 175 (or visitor 165) to record their own second audio clip in response to the first audio clip recorded byvisitor 163. In particular, once thevisitor 175 listened to the first audioclip using module 240 of theaudio widget 200, the visitor may press “blurt-back”button 245, which activatesmodules audio content database 130, a registeredvisitor 175 may store the recorded audio clip into his/her account on theaudio management server 110, as described above. In addition, theserver 100 associates the identifier of the second audio clip with the identifier of the second audio clip in thedatabase 130 to indicate that the second audio clip relates to the first audio clip, whereby reconstructing an audio conversation thread among multiple system users. - Yet in another example embodiment, the
visitor 175 or any other visitor of thewebsite 160 may view and play back the entire audio conversation thread comprising multiple audio clips recorded by various visitors ofwebsite 160 or other websites where the audio clip was shared. In particular, thevisitor 175 can press “blurt-backs”button 247 of themodule 240 of theaudio widget 200 in response to which the widget retrieves from theserver 100 information about all audio clips related to (e.g., recorded in response to) the first audio clip or any other clip in the audio conversation thread. Theaudio widget 200 may than generate a copy ofmodule 240 for each related audio clip in the given audio conversation thread. For each audio clip, themodule 240 may indicated the name of the user who recorded the clip (or anonymous user if the audio clip was recorded by an unregistered visitor), the date and time when the audio clip was recorded, and an identifier of the website where the clip was recorded or from which the visitor who recorded the clip was redirected from. Thevisitor 175 may then play back each audio clip one at atime using player 243 of themodule 240 of thewidget 200. - Yet in another embodiment, the
visitor 175 may share any one of the related audio clips through various Web platforms, such as popular social networking sites and the like. In particular, thevisitor 175 may press “share”button 237 in themodule 240 and theaudio widget 200 will opens a menu of third-party Web platforms on which the audio clip can be shared. As indicated above, the available Web platforms include, but not limited to: Facebook®, Twitter®, LinkedIn®, MySpace®, Google+®, Flickr® and others. Thevisitor 175 may then select one ormore websites 170 for sharing the audio clip and provide the required website login information. Theserver 110 will then post an audio clip link 235 on the selectedwebsite 170. In this manner, by sharing links to the first audio clip recorded onwebsite 160 to other websites, the visitor traffic from those websites is driven to thewebsite 160, where through multiple audio responses to the first audio clip, a single audio clip grows into an audio conversation thread consisting of numerous audio clips recorded by different visitors. - As mentioned above, the information about audio conversation threads is collected by the
audio management application 120 and stored in the accounts of registered users. This information may be accessed by a registered system user through thecentral website 125 provided by theapplication 120.FIG. 3 depicts an exemplary user account interface of thecentral website 125. Theinterface 300 includes information about each audio conversation thread initiated by the user of said account.Section 310 shows the original audio clip recorded by the user and various associated metadata, such as title, time and date of recoding, audio clip link, duration of the clip, and the number of times the clip was shared and where.Section 320 shows a list of audio responses associated with the original audio clip as well as various information about the audio response, including but not limited to the title of each clip, time and date of recoding, audio clip link, duration of the clip, the number of times the clip was shared and where, and the names of users who recorded the response clips. -
FIG. 4 depicts another exemplary user account interface of thecentral website 125 provided by of theapplication 120. Thisinterface 400 shows statistical information aboutaudio clip 405 and associated audio conversation thread. For example,section 410 shows a list of listening sources, i.e., the URLs of websites whereaudio clip 405 was played back or was redirected for playback from.Pie chart 420 shows the number of times thataudio clip 405 was played back.Time chart 430 tracks the number of listens ofclip 405 over time. The collected statistical information is not limited to the above-described and may include other types of information about audio clips and the associated audio conversation thread. In addition, other graphical or numerical forms may be used to represent the collected statistical data. - In one example embodiment, the
audio management server 110 may perform a speech-to-text conversion of the stored audio clips for data mining or other purposes. For example, theserver 110 may analyze the text of an individual audio clips or the entire audio conversation thread to determine its subject matter. This information may be used to determine interests and views of the user who recorded the original clip as well as to identify other users who contributed to the audio conversation thread, and therefore share similar interests or views. In addition, this information may be used to monetize the audio management system by inserting contextual ads into theaudio widget 200 when it plays back a particular audio clip. Thus, for example, if an audio conversation thread published onwebsite 160 discusses a new model of a gaming console, and the audio conversation thread between several website visitors indicates that these visitors are interested in purchasing the discussed gaming console, theaudio management server 110 may insert an advertisement of a major consumer electronics retailer with a discount or sale offer on the discussed gaming console. - Yet in one example embodiment, the users of the
audio management system 100 may monetize their audio clips by charging listeners for each playback of the audio clip. For example, a celebrity person may register with theaudio management system 100 and record using the central website 125 a short statement, announcement or message to his/her fans, and share the recorded audio clip on his/her Facebook® or Twitter® webpage. Theserver 110 would allow the celebrity to assign a monetary value (e.g., $0.10) for each listen of the audio clip. Theaudio widget 200 andserver 110 may be configured to use PayPal® or other online money transfer system to collect payments from listeners and transfer the money to the celebrity's account. If the celebrity has a large number of Facebook or Twitter followers, the celebrity may collect substantial amount of money from the fans who listened to his/her audio clips. In another example embodiment, the celebrity may embed theaudio widget 200 on his personal website, record the audio clips on his personal website, and post the clips on his/her Facebook® or Twitter® webpages. When the fans will click on the audio clip link, they will be redirected to celebrity's personal website, thereby driving visitor traffic to celebrity's website. -
FIGS. 5A and B depict a flow chart of a method of operation of the audio management system in accordance with one example embodiment. Atstep 505, the audio management server receives from a first website a request by a first website visitor to record an audio clip on the first website. Atstep 510, the server provides to the first website an audio widget operable to record, play back, respond to and share audio clips. Atstep 515, the audio widget records an audio clip from the first website visitor. Atstep 520, the widget requests the visitor to provide login information for the user account on the server. Atstep 525, the audio widget sends the recorded audio clip and visitor's log information to the server. Atstep 530, the server receives the audio clip, assigns a unique identifier to the audio clip, stores the audio clip in the audio content database, and generates a link to the audio clip. In one example embodiment, the link comprises an identifier of the audio server and unique identifier of the audio clip. The server also access user account using the provided login information, and stores the audio clip identifier and a first website identifier in the user account. If the visitor did not provide account login information, the audio clip may be stored unanimously. - At
step 535, the server provides to the audio widget an audio clip link to be posted on the first website for accessing the audio clip through the audio widget. Atstep 540, the server receives from the audio widget on the first website a request by the first website visitor to share the recorded audio clip on a second website. Atstep 545, the server retrieves from the user account login information for the second website or requests the first website visitor to provide the required login information. Atstep 550, the server posts on the second website the audio clip link or the audio widget for recording, playback, responding to and sharing of the audio clip. Atstep 555, the server stores in the user account an identifier of the second website where the audio clip was posted. Atstep 560, the server receives from the second website a request by a second website visitor to play back the audio clip whose link is posted on the second website. Atstep 565, the server redirects the visitor to the first website where the audio clip was recorded. Atstep 570, the server provides the requested audio clip to the audio widget on the first website for playback of the clip to the second website visitor. -
FIGS. 6A and B depict a flow chart of another method of operation of the audio management system in accordance with another example embodiment. Atstep 605, the audio management server stores a first audio clip recorded on a first website. Atstep 610, the server generates a link for accessing the first audio clip from the audio server. Atstep 615, the server posts on the second website the audio clip link for accessing the first audio clip. Atstep 620, the server receives a request by a website visitor to play back the first audio clip. Atstep 625, the server determines from the request an identifier of the website where the request came from. Atstep 630, the server compares the website identifier with the first website wherein the clip was recorded. Atstep 635, the server determines if the playback request came from the first website or the second website. If the request came from the second website, atstep 640, the server redirects the website visitor to the first website where the first audio clip was recorded for playback of the first audio clip on the first website. If the request came from the first website or the visitor has been just redirected to the first website, atstep 645, the server provides to the first website the first audio clip and an audio widget that enables the visitor to play back, respond to and share the first audio clip on the first website. - At
step 650, after the playback of the first audio clip on the first website, the server identifies a user of the audio server who recorded the first audio clip. Atstep 655, the server accesses the user account, updates a playback counter associated with the first audio clip, and stores an identifier of the second website in the user account. Atstep 660, the server receives from the website visitor a request to record a second audio clip in response to the first audio clip recorded on the first website and instructs the audio widget on the first website to record the second audio clip. Atstep 665, the server posts on the first and second websites audio clip links for accessing the second audio clip. Atstep 670, the server receives from the website visitor a request to record a third audio clip in response to the second audio clip recorded on the first website. Atstep 675, the server provides audio widget for recording the third audio clip of the first website. Atstep 680, the server posts on the first and second websites audio clip links for accessing the third audio clip recorded on the first website. -
FIGS. 7A and B depict a flow chart of yet another method of operation of the audio management system in accordance with another example embodiment. Atstep 705, the audio management server receives from a second website a request by a website visitor to play back a first audio clip, which was recorded on a first website and whose link was posted on the second website. Atstep 710, the server redirects the visitor to the first website where the audio clip was recorded. Atstep 715, the server provides to the first website the requested first audio clip and an audio widget operable to play back, respond to and share the first audio clip. Atstep 720, the server receives from the first website a request by a website visitor to record a second audio clip in response to the first audio clip. Atstep 725, the audio widget on the first website records the second audio clip. Atstep 730, the server posts on the first and second websites audio clip links for accessing the first and second audio clips or the audio widgets for playing back, responding to and sharing the first and second audio clips. - At
step 735, the server determines whether the first and second audio clips were recorded by the same or different website visitors. If it is determined atstep 740 that the clips were recorded by the same visitor, at step 745, the server stores in the user account of said visitor the identifier of the first audio clip and an identifier of the first website, the identifier of the second audio clip and an identifier of the second website, and the indicator that the second audio clip was recorded in response to the first audio clip. If the first and second audio clips were recorded by different visitors, atstep 750, the server stores in the user account of the first website visitor who recorded the first audio clip the identifier of the first audio clip, an identifier of the first website, the identifier of the second audio clip, and the indicator that the second audio clip was recorded in response to the first audio clip. Atstep 755, the server stores in the user account of the second website visitor who recorded the second audio clip the identifier of the second audio clip, an identifier of the second website, the identifier of the first audio clip, and the indicator that the second audio clip was recorded in response to the first audio clip. -
FIG. 8 depicts one example embodiment of acomputer system 5, which could be used to implement theaudio management server 110 of theaudio management system 100. As shown,computer system 5 may include one ormore processors 15,memory 20, one or more hard disk drive(s) 30, optical drive(s) 35, serial port(s) 40,graphics card 45,audio card 50 and network card(s) 55 connected by system bus 10. System bus 10 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus and a local bus using any of a variety of known bus architectures.Processor 15 may include one or moreIntel® Core 2 Quad 2.33 GHz processors or other type of microprocessor. -
System memory 20 may include a read-only memory (ROM) 21 and random access memory (RAM) 23.Memory 20 may be implemented as in DRAM (dynamic RAM), EPROM, EEPROM, Flash or other type of memory architecture.ROM 21 stores a basic input/output system 22 (BIOS), containing the basic routines that help to transfer information between the components ofcomputer system 5, such as during start-up,RAM 23 stores operating system 24 (OS), such as Windows® XP Professional or other type of operating system, that is responsible for management and coordination of processes and allocation and sharing of hardware resources incomputer system 5.Memory 20 also stores applications andprograms 25, such as services 306.Memory 20 also storesvarious runtime data 26 used byprograms 25. -
Computer system 5 may further include hard disk drive(s) 30, such as SATA magnetic hard disk drive (HDD), and optical disk drive(s) 35 for reading from or writing to a removable optical disk, such as a CD-ROM, DVD-ROM or other optical media.Drives exemplary computer system 5 employs magnetic and optical disks, it should be appreciated by those skilled in the art that other types of computer readable media that can store data accessible by acomputer system 5, such as magnetic cassettes, flash memory cards, digital video disks, RAMs, ROMs, EPROMs and other types of memory may also be used in alternative embodiments of the computer system. -
Computer system 5 further includes a plurality ofserial ports 40, such as Universal Serial Bus (USB), for connecting data input device(s) 75, such as keyboard, mouse, touch pad and other.Serial ports 40 may be also be used to connect data output device(s) 80, such as printer, scanner and other, as well as other peripheral device(s) 85, such as external data storage devices and the like.System 5 may also includegraphics card 45, such as nVidia® GeForce® GT 240M or other video card, for interfacing with amonitor 60 or other video reproduction device.System 5 may also include anaudio card 50 for reproducing sound via internal orexternal speakers 65. In addition,system 5 may include network card(s) 55, such as Ethernet, WiFi, GSM, Bluetooth or other wired, wireless, or cellular network interface for connectingcomputer system 5 to network 70, such as the Internet. - In various embodiments, the algorithms and methods described herein may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or code on a non-transitory computer-readable medium. Computer-readable medium includes both computer storage and communication medium that facilitates transfer of a computer program from one place to another. A storage medium may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable medium can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection may be termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
- In the interest of clarity, not all of the routine features of the embodiments are disclosed. It will be appreciated that in the development of any actual implementation of the invention, numerous implementation-specific decisions must be made in order to achieve the developer's specific goals, and that these specific goals will vary from one implementation to another and from one developer to another. It will be appreciated that such a development effort might be complex and time-consuming, but would nevertheless be a routine undertaking of engineering for those of ordinary skill in the art having the benefit of this disclosure.
- Furthermore, it is to be understood that the phraseology or terminology used herein is for the purpose of description and not of limitation, such that the terminology or phraseology of the present specification is to be interpreted by the skilled in the art in light of the teachings and guidance presented herein, in combination with the knowledge of the skilled in the relevant art(s). Moreover, it is not intended for any term in the specification or claims to be ascribed an uncommon or special meaning unless explicitly set forth as such.
- The various embodiments disclosed herein encompass present and future known equivalents to the known components referred to herein by way of illustration. Moreover, while embodiments and applications have been shown and described, it would be apparent to those skilled in the art having the benefit of this disclosure that many more modifications than mentioned above are possible without departing from the inventive concepts disclosed herein.
Claims (18)
1. A method for recording, playing back, responding to and sharing audio clips comprising:
providing to a first third-party website an audio widget that allows website visitors to record, play back, respond to and share audio clips;
receiving from the audio widget an audio clip recorded by a first website visitor and an identifier of the first third-party website where the audio clip was recorded;
storing information received from the audio widget in an audio server;
posting on the first third-party website at least one of a link to the audio clip and the audio widget operable to play back, respond to and share the audio clip;
receiving from the audio widget on the first third-party website a request by the website visitor to share the audio clip on a second third-party website; and
posting on the second third-party website at least one of the link to the audio clip and the audio widget operable to play back, respond to and share the audio clip.
2. The method of claim 1 further comprising:
receiving from the second third-party website a request by a second website visitor to play back the audio clip, wherein the request includes the link to the audio clip; and
redirecting the second website visitor to the first third-party website where the second website visitor can play back the audio clip using the audio widget.
3. The method of claim 2 , wherein storing information received from the audio widget in an audio server further comprises:
assigning by the audio server a unique identifier to the audio clip; and
generating by the audio server a link to the audio clip, the link comprising an identifier of the audio server and the unique identifier of the audio clip.
4. The method of claim 3 , wherein storing information received from the audio widget in the audio server further comprises:
requesting the first website visitor to provide login information to the audio server, the login information including first website visitor's username and password;
if the first website visitor provides the requested login information,
accessing a user account of said first website visitor in the audio server; and
storing in the user account the unique identifier of the audio clip and the identifier of the first third-party website; and
if the first website visitor does not provide the requested login information,
unanimously storing on the audio server the unique identifier of the audio clip and the identifier of the first third-party website.
5. The method of claim 1 , wherein receiving from the first third-party website a request to share the audio clip on a second third-party website further comprises:
requesting the first website visitor to provide a login information for the second third-party website, the login information including visitor's username and password; and
if the first website visitor provides the requested login information, posting on the second third-party website the link to the audio clip.
6. The method of claim 4 further comprising:
receiving by the audio server a request to display user account statistics data;
collecting statistics data from the user account, the statistics data includes one or more of a list of all audio clips recorded by the account user, a list of third-party websites where the audio clips were posted, the number of times each audio clip was played back; and
displaying the collected statistics data in a user interface of the audio server.
7. A method for recording, playing back, responding to and sharing audio clips comprising:
storing in an audio server a first audio clip recorded on a first third-party website;
posting on a second third-party website a link for accessing the first audio clip;
receiving a request from a website visitor to play back the first audio clip, wherein the request includes a link to the first audio clip on the audio server;
determining if the playback request came from the first or second third-party website;
if the playback request came from the first third-party website where the first audio clip was recorded, providing to the first third-party website the first audio clip and an audio widget operable to play back, respond to and share the first audio clip; and
if the playback request came from the second third-party website, redirecting the website visitor to the first third-party website and providing to the first third-party website the first audio clip and the audio widget operable to play back, respond to and share the audio clip.
8. The method of claim 7 , wherein storing in an audio server a first audio clip further comprises:
assigning by the audio server a unique identifier to the first audio clip; and
generating by the audio server a link to the first audio clip, the link comprising an identifier of the audio server and the unique identifier of the first audio clip.
9. The method of claim 7 , wherein determining if the playback request came from the first or second third-party website further comprises:
determining from the playback request a website which sent the playback request; and
comparing said website with the first website where the first audio clip was recorded.
10. The method of claim 7 , wherein, after the playback of the audio clip on the first website,
identifying a user of the audio server who recorded the first audio clip;
accessing a user account of the identified user in the audio server;
updating in the user account a playback counter associated with the first audio clip; and
if the playback request came from the second third-party website, storing in the user account an identifier of the second third-party website.
11. The method of claim 7 further comprising:
receiving from the website visitor a request to record a second audio clip in response to the first audio clip recorded on the first third-party website;
recording the second audio clip using the audio player widget of the first website; and
posting on the first and second third-party websites links to the second audio clip.
12. The method of claim 11 further comprising:
receiving from the website visitor a request to record a third audio clip in response to the second clip recorded on the first third-party website;
recording the third audio clip using the audio widget of the first website; and
posting on the first and second third-party websites links to the third audio clip.
13. A method for recording, playing back, responding to and sharing audio clips comprising:
receiving from a second third-party website a request by a website visitor to play back a first audio clip recorded on a first third-party website;
redirecting the website visitor to the first third-party website;
providing to the first website the requested first audio clip and an audio widget operable to play back, respond to and share the first audio clip;
receiving from the first third-party website a request by the website visitor to record a second audio clip in response to the first audio clip;
recording the second audio clip using the audio widget on the first third-party website;
posting on the first and second third-party websites at least one of links to the first and second audio clip and audio widgets for playback, responding to and sharing of said audio clips.
14. The method of claim 13 further comprising:
storing in an audio server (i) the first audio clip and a unique identifier of the first audio clip (ii) the second audio clip and a unique identifier of the second audio clip; and (iii) an indicator that the second audio clip was recorded in response to the first audio clip.
15. The method of claim 13 further comprising:
determining whether the first and second audio clips were recorded by the same or different website visitors.
16. The method of claim 15 , wherein, if the first and second audio clips were recorded by the same website visitor, the method further comprises:
identifying said website visitor in user account records of an audio server;
accessing a user account of said website visitor in the audio server; and
storing in the user account (i) the identifier of the first audio clip and an identifier of the first third-party website; (ii) the identifier of the second audio clip and an identifier of the second third-party website; and (iii) the indicator that the second audio clip was recorded in response to the first audio clip.
17. The method of claim 15 , wherein, if the first and second audio clips were recorded by different website visitors, the method further comprises:
identifying a first website visitor who recorded the first audio clip;
accessing a first user account of the first website visitor in the audio server;
storing in the first user account the identifier of the first audio clip, an identifier of the first website, the identifier of the second audio clip, and the indicator that the second audio clip was recorded in response to the first audio clip; and
identifying a second website visitor who recorded the second audio clip;
accessing a second user account of the second website visitor in the audio server;
storing in the second user account the identifier of the second audio clip, an identifier of the second website, the identifier of the first audio clip, and the indicator that the second audio clip was recorded in response to the first audio clip.
18. The method of claim 13 further comprising:
receiving from the website visitor a request to display one or more second audio clips recorded in response to the first audio clip;
identifying in the audio server at least one second audio clip recorded in response to the first audio clip by at least one second website visitor; and
displaying a list of one or more second audio clips to the website visitor.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/198,977 US20130033971A1 (en) | 2011-08-05 | 2011-08-05 | System and Method for Managing and Distributing Audio Recordings |
US13/236,396 US8452887B1 (en) | 2011-08-05 | 2011-09-19 | System and method for managing and distributing audio recordings |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/198,977 US20130033971A1 (en) | 2011-08-05 | 2011-08-05 | System and Method for Managing and Distributing Audio Recordings |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/236,396 Continuation US8452887B1 (en) | 2011-08-05 | 2011-09-19 | System and method for managing and distributing audio recordings |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130033971A1 true US20130033971A1 (en) | 2013-02-07 |
Family
ID=47626878
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/198,977 Abandoned US20130033971A1 (en) | 2011-08-05 | 2011-08-05 | System and Method for Managing and Distributing Audio Recordings |
US13/236,396 Expired - Fee Related US8452887B1 (en) | 2011-08-05 | 2011-09-19 | System and method for managing and distributing audio recordings |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/236,396 Expired - Fee Related US8452887B1 (en) | 2011-08-05 | 2011-09-19 | System and method for managing and distributing audio recordings |
Country Status (1)
Country | Link |
---|---|
US (2) | US20130033971A1 (en) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140214628A1 (en) * | 2013-01-31 | 2014-07-31 | Wal-Mart Stores, Inc. | Gesture-Based Product Wishlist And Shared Social Networking |
US20140289626A1 (en) * | 2013-03-15 | 2014-09-25 | Cloudeck Inc. | Cloud based audio recording system |
US20150106713A1 (en) * | 2013-10-11 | 2015-04-16 | Aol Inc. | Systems and methods for generating and managing audio content |
US20160034684A1 (en) * | 2014-08-01 | 2016-02-04 | Okta, Inc. | Automated Password Generation and Change |
WO2016018724A1 (en) * | 2014-07-30 | 2016-02-04 | Alibaba Group Holding Limited | Extending content sources |
US20170357380A1 (en) * | 2016-02-11 | 2017-12-14 | Hyperkey, Inc. | Content Sharing Logging |
CN109074207A (en) * | 2016-02-11 | 2018-12-21 | 海佩吉公司 | social keyboard |
EP3540603A4 (en) * | 2016-11-11 | 2019-09-25 | Sony Mobile Communications Inc. | Reproduction terminal and reproduction method |
US20190304483A1 (en) * | 2017-09-29 | 2019-10-03 | Axwave, Inc. | Using selected groups of users for audio enhancement |
US20190303400A1 (en) * | 2017-09-29 | 2019-10-03 | Axwave, Inc. | Using selected groups of users for audio fingerprinting |
US10523615B1 (en) * | 2018-07-17 | 2019-12-31 | Kiaran Sim | Method that allows a publisher's website to allow registered users to upload audio and video content on the publisher's website |
US10701018B2 (en) * | 2015-08-27 | 2020-06-30 | Mobilitie, Llc | System and method for customized message delivery |
US10976923B2 (en) | 2016-02-11 | 2021-04-13 | Hyperkey, Inc. | Enhanced virtual keyboard |
CN112836087A (en) * | 2021-01-26 | 2021-05-25 | 湖南快乐阳光互动娱乐传媒有限公司 | Video attribute information acquisition method and device |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10296561B2 (en) | 2006-11-16 | 2019-05-21 | James Andrews | Apparatus, method and graphical user interface for providing a sound link for combining, publishing and accessing websites and audio files on the internet |
US9361295B1 (en) | 2006-11-16 | 2016-06-07 | Christopher C. Andrews | Apparatus, method and graphical user interface for providing a sound link for combining, publishing and accessing websites and audio files on the internet |
US9380410B2 (en) | 2011-04-04 | 2016-06-28 | Soundlink, Inc. | Audio commenting and publishing system |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090164902A1 (en) * | 2007-12-19 | 2009-06-25 | Dopetracks, Llc | Multimedia player widget and one-click media recording and sharing |
US20100268779A1 (en) * | 2009-04-15 | 2010-10-21 | Sling Media, Inc. | Sharing of audio/visual content with a selected user |
US20110231887A1 (en) * | 2010-03-10 | 2011-09-22 | West R Michael Peters | Methods and systems for audio-video clip sharing for internet-delivered television programming |
Family Cites Families (42)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6505160B1 (en) | 1995-07-27 | 2003-01-07 | Digimarc Corporation | Connected audio and other media objects |
US6804806B1 (en) | 1998-10-15 | 2004-10-12 | At&T Corp. | Method of delivering an audio or multimedia greeting containing messages from a group of contributing users |
US7178106B2 (en) | 1999-04-21 | 2007-02-13 | Sonic Solutions, A California Corporation | Presentation of media content from multiple media sources |
US7702403B1 (en) | 1999-08-31 | 2010-04-20 | Stephen Christopher Gladwin | Structure and method for selecting, controlling and sending internet-based or local digital audio to an AM/FM radio or analog amplifier |
WO2001025948A1 (en) | 1999-10-05 | 2001-04-12 | Zapmedia, Inc. | System and method for distributing media assets to user devices and managing user rights of the media assets |
US6496802B1 (en) | 2000-01-07 | 2002-12-17 | Mp3.Com, Inc. | System and method for providing access to electronic works |
US6385306B1 (en) | 2000-03-02 | 2002-05-07 | John Francis Baxter, Jr. | Audio file transmission method |
US20010042048A1 (en) | 2000-05-15 | 2001-11-15 | The Regents Of The University Of California | Method and apparatus for electronically distributing audio recordings |
US6423892B1 (en) | 2001-01-29 | 2002-07-23 | Koninklijke Philips Electronics N.V. | Method, wireless MP3 player and system for downloading MP3 files from the internet |
JP2002244928A (en) | 2001-02-16 | 2002-08-30 | Pioneer Electronic Corp | Digital information storage system and digital information delivery system |
US20020128067A1 (en) | 2001-03-09 | 2002-09-12 | Victor Keith Blanco | Method and apparatus for creating and playing soundtracks in a gaming system |
AU2002316435B2 (en) | 2001-06-27 | 2008-02-21 | Skky, Llc | Improved media delivery platform |
JP2003044739A (en) | 2001-07-27 | 2003-02-14 | Kinya Kuriyama | Method and program for distributing contents |
JP3823929B2 (en) | 2002-05-17 | 2006-09-20 | ソニー株式会社 | Information processing apparatus, information processing method, content distribution apparatus, content distribution method, and computer program |
US20040162878A1 (en) | 2002-11-22 | 2004-08-19 | Lewis Michael Pescatello | System and method to facilitate real-time communications and content sharing among users over a network |
WO2004097599A2 (en) | 2003-04-28 | 2004-11-11 | Sony Pictures Entertainment Inc. | Rich media publishing |
US20040252814A1 (en) | 2003-06-13 | 2004-12-16 | Eakin William J. | System and method of voice message recording and delivery |
US20060008256A1 (en) | 2003-10-01 | 2006-01-12 | Khedouri Robert K | Audio visual player apparatus and system and method of content distribution using the same |
US7447775B1 (en) * | 2003-11-07 | 2008-11-04 | Cisco Technology, Inc. | Methods and apparatus for supporting transmission of streaming data |
US7478059B2 (en) | 2003-12-29 | 2009-01-13 | Robert W. Crocitto | System and method for content distribution and commerce on a peer-to-peer network |
JP2005351994A (en) | 2004-06-08 | 2005-12-22 | Sony Corp | Contents distribution server, contents distributing method and program |
JP2006011535A (en) | 2004-06-22 | 2006-01-12 | Sony Corp | Contents transfer device, contents transfer method, and computer program |
US7370063B2 (en) | 2005-02-17 | 2008-05-06 | Andy Vilcauskas | Audio distribution system |
US7647128B2 (en) | 2005-04-22 | 2010-01-12 | Microsoft Corporation | Methods, computer-readable media, and data structures for building an authoritative database of digital audio identifier elements and identifying media items |
US8302030B2 (en) | 2005-09-14 | 2012-10-30 | Jumptap, Inc. | Management of multiple advertising inventories using a monetization platform |
US7555715B2 (en) | 2005-10-25 | 2009-06-30 | Sonic Solutions | Methods and systems for use in maintaining media data quality upon conversion to a different data format |
US7900818B2 (en) | 2005-11-14 | 2011-03-08 | Packetvideo Corp. | System and method for accessing electronic program guide information and media content from multiple locations using mobile devices |
US20070174772A1 (en) | 2006-01-12 | 2007-07-26 | Gorman Jerome S | Method and system for integrated network multimedia distribution |
US20090286560A1 (en) | 2006-01-13 | 2009-11-19 | Michael John Willis | System and method for mobile content generation |
US8285595B2 (en) | 2006-03-29 | 2012-10-09 | Napo Enterprises, Llc | System and method for refining media recommendations |
US20080091606A1 (en) | 2006-10-12 | 2008-04-17 | William Grecia | Proprietary encapsulated session container with embedded features for a post transferred option for electronic commerce along with a system for distribution and user access |
US20080147558A1 (en) | 2006-10-24 | 2008-06-19 | Robert Korbin Kraus | Method and system for providing prospective licensees and/or purchasers with access to licensable media content |
US7937451B2 (en) | 2007-01-08 | 2011-05-03 | Mspot, Inc. | Method and apparatus for transferring digital content from a computer to a mobile handset |
US7890854B2 (en) | 2007-05-31 | 2011-02-15 | Realnetworks, Inc. | Web media asset identification system and method |
JP5141195B2 (en) | 2007-11-09 | 2013-02-13 | ソニー株式会社 | Information processing apparatus, music distribution system, music distribution method, and computer program |
US7979447B2 (en) | 2008-01-18 | 2011-07-12 | Sony Corporation | Method and apparatus for use in providing information to accessing content |
US8467402B2 (en) | 2008-09-10 | 2013-06-18 | Miselu, Inc. | Digital audio communication system |
CN101686222A (en) | 2008-09-27 | 2010-03-31 | 中兴通讯股份有限公司 | Media resource system and method for providing media resources |
US20110078053A1 (en) | 2008-12-13 | 2011-03-31 | Yang Pan | System and method for distribution of media assets from media delivery unit to handheld media player |
US20100306859A1 (en) | 2009-05-29 | 2010-12-02 | Hank Risan | Secure media copying and/or playback in a usage protected frame-based work |
WO2011014772A1 (en) | 2009-07-31 | 2011-02-03 | Citizenglobal Inc. | Systems and methods for content aggregation, editing and delivery |
US20110072350A1 (en) | 2009-09-21 | 2011-03-24 | Walter Bachtiger | Systems and methods for recording and sharing audio files |
-
2011
- 2011-08-05 US US13/198,977 patent/US20130033971A1/en not_active Abandoned
- 2011-09-19 US US13/236,396 patent/US8452887B1/en not_active Expired - Fee Related
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090164902A1 (en) * | 2007-12-19 | 2009-06-25 | Dopetracks, Llc | Multimedia player widget and one-click media recording and sharing |
US20100268779A1 (en) * | 2009-04-15 | 2010-10-21 | Sling Media, Inc. | Sharing of audio/visual content with a selected user |
US20110231887A1 (en) * | 2010-03-10 | 2011-09-22 | West R Michael Peters | Methods and systems for audio-video clip sharing for internet-delivered television programming |
Cited By (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140214628A1 (en) * | 2013-01-31 | 2014-07-31 | Wal-Mart Stores, Inc. | Gesture-Based Product Wishlist And Shared Social Networking |
US20140289626A1 (en) * | 2013-03-15 | 2014-09-25 | Cloudeck Inc. | Cloud based audio recording system |
US20150106713A1 (en) * | 2013-10-11 | 2015-04-16 | Aol Inc. | Systems and methods for generating and managing audio content |
US11100161B2 (en) * | 2013-10-11 | 2021-08-24 | Verizon Media Inc. | Systems and methods for generating and managing audio content |
EP3175369A4 (en) * | 2014-07-30 | 2018-03-14 | Alibaba Group Holding Limited | Extending content sources |
TWI690895B (en) * | 2014-07-30 | 2020-04-11 | 開曼群島商釘釘控股(開曼)有限公司 | Method and system for expanding content source in social application, user end and server |
WO2016018724A1 (en) * | 2014-07-30 | 2016-02-04 | Alibaba Group Holding Limited | Extending content sources |
CN105450496A (en) * | 2014-07-30 | 2016-03-30 | 阿里巴巴集团控股有限公司 | A method and system for expanding content sources in social applications, a client and a server |
US20160034684A1 (en) * | 2014-08-01 | 2016-02-04 | Okta, Inc. | Automated Password Generation and Change |
US9916437B2 (en) * | 2014-08-01 | 2018-03-13 | Okta, Inc. | Automated password generation and change |
US9852286B2 (en) * | 2014-08-01 | 2017-12-26 | Okta, Inc. | Automated password generation and change |
US10762191B2 (en) * | 2014-08-01 | 2020-09-01 | Okta, Inc. | Automated password generation and change |
US20160036806A1 (en) * | 2014-08-01 | 2016-02-04 | Okta, Inc. | Automated Password Generation and Change |
US10169569B2 (en) * | 2014-08-01 | 2019-01-01 | Okta, Inc. | Automated password generation and change |
US20190095609A1 (en) * | 2014-08-01 | 2019-03-28 | Okta, Inc. | Automated password generation and change |
US10701018B2 (en) * | 2015-08-27 | 2020-06-30 | Mobilitie, Llc | System and method for customized message delivery |
CN109074207A (en) * | 2016-02-11 | 2018-12-21 | 海佩吉公司 | social keyboard |
US9939962B2 (en) * | 2016-02-11 | 2018-04-10 | Hyperkey, Inc. | Enhanced keyboard including multiple application execution |
US10768810B2 (en) | 2016-02-11 | 2020-09-08 | Hyperkey, Inc. | Enhanced keyboard including multiple application execution |
US10976923B2 (en) | 2016-02-11 | 2021-04-13 | Hyperkey, Inc. | Enhanced virtual keyboard |
US20170357380A1 (en) * | 2016-02-11 | 2017-12-14 | Hyperkey, Inc. | Content Sharing Logging |
EP3540603A4 (en) * | 2016-11-11 | 2019-09-25 | Sony Mobile Communications Inc. | Reproduction terminal and reproduction method |
US11298080B2 (en) | 2016-11-11 | 2022-04-12 | Sony Mobile Communications Inc. | Reproduction terminal and reproduction method |
US20190304483A1 (en) * | 2017-09-29 | 2019-10-03 | Axwave, Inc. | Using selected groups of users for audio enhancement |
US20190303400A1 (en) * | 2017-09-29 | 2019-10-03 | Axwave, Inc. | Using selected groups of users for audio fingerprinting |
US10523615B1 (en) * | 2018-07-17 | 2019-12-31 | Kiaran Sim | Method that allows a publisher's website to allow registered users to upload audio and video content on the publisher's website |
US20200028811A1 (en) * | 2018-07-17 | 2020-01-23 | Jennifer Dyer | Method that allows a publisher?s website to allow registered users to upload audio and video content on the publisher?s web83-4 |
CN112836087A (en) * | 2021-01-26 | 2021-05-25 | 湖南快乐阳光互动娱乐传媒有限公司 | Video attribute information acquisition method and device |
Also Published As
Publication number | Publication date |
---|---|
US8452887B1 (en) | 2013-05-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8452887B1 (en) | System and method for managing and distributing audio recordings | |
US9218413B2 (en) | Venue-related multi-media management, streaming, online ticketing, and electronic commerce techniques implemented via computer networks and mobile devices | |
US8935279B2 (en) | Venue-related multi-media management, streaming, online ticketing, and electronic commerce techniques implemented via computer networks and mobile devices | |
US10007893B2 (en) | Methods for online collaboration | |
US9516122B1 (en) | Media player social network integration | |
US8856170B2 (en) | Bandscanner, multi-media management, streaming, and electronic commerce techniques implemented over a computer network | |
CN103827912B (en) | Network-based music partner system and method | |
US8962964B2 (en) | Methods for online collaborative composition | |
US20170185981A1 (en) | Methods for Online Media Collaboration and Licensing | |
US20140258553A1 (en) | Multi-media management and streaming techniques implemented over a computer network | |
US20130086185A1 (en) | Systems and methods for a multimedia social networking system | |
CA3125630C (en) | Methods and systems for analyzing user preferences to dynamically identify remotely located media for local access | |
US20150213491A1 (en) | Method and system for optimizing communication about entertainment | |
US20130297467A1 (en) | Method and system for accounting for download transactions and social network interaction | |
JP6312564B2 (en) | Information processing apparatus, control method, and control program | |
US10719838B2 (en) | Generating event recommendations based upon media consumption | |
JP6500141B2 (en) | Information processing apparatus, control method, and control program | |
USRE48375E1 (en) | Method for real time distribution of dealership generated data and media originating from a retail environment | |
US9721270B2 (en) | Integrating communications services with personalized social networks | |
van Rensburg | Interpreting music consumption data published by the music industry to inform the career choices of music graduates | |
US20220343361A1 (en) | System and method for offering bounties to a user in real-time | |
KR20130090007A (en) | System and method for providing social network service account mining information for surporting social network service action | |
KR20120080891A (en) | Method and system for co-working between music service and sns service | |
KR20140062631A (en) | System and method for providing social network service analysis information using 64 category |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: VOICE PORTRAITS, INC., NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:STIER, JEFFREY;REEL/FRAME:030147/0743 Effective date: 20130321 |
|
AS | Assignment |
Owner name: VOICE PORTRAITS, INC., NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:STIER, JEFFREY;REEL/FRAME:030210/0748 Effective date: 20130321 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |