The present invention relates generally to systems and methods for identifying a set of characters. More particularly, the present invention relates to identifying a set of characters in one or more media files.
As higher volumes of data are able to be stored and transmitted within and across computer systems, media files (e.g., audio files, video files, audio/video files, etc.) have become a daily part of our lives. The rise of MP3 players and websites such as YouTube® are examples of how media files have become ingrained in our society. Media files often contain human speech, such as the sung lyrics of a song or human dialogue in a video. Current users of media files may have no convenient way of being notified when a media file contains particular characters or words. In addition, current systems may not be able to identify user-defined characters or words in a playing media file. For example, a user may want to know whether a media file playing on his or her computer or other device contains a particular phrase, but current systems may not be able to identify such user-defined phases or provide notification to the user when the phrase is found in the media file.
The illustrative embodiments described herein are directed to a data processing system and, in particular, to systems and methods for notifying a user when a set of characters are identified in a media file. In one embodiment, a method includes receiving a set of characters inputted by the user of a computing device, playing the media file, transcribing the media file to form a transcription, and determining whether the transcription of the media file includes the set of characters. The method also includes initiating a notification prompt on a graphical user interface of the computing device in response to determining that the media file includes the set of characters.
In another embodiment, a system for notifying a user when a set of words is identified in a media file includes a transcription module to transcribe the media file to form a transcription, and an identification module to identify a segment of the media file that includes a user-defined set of words. The identification module uses the transcription to identify the segment of the media file that includes the user-defined set of words. The system also includes a notification module to notify the user in response to identifying the segment of the media file that includes the user-defined set of words.
In another embodiment, a computing device includes a bus system and a memory connected to the bus system. The memory includes a set of instructions. The data processing system includes a processing unit connected to the bus system. The processing unit executes the set of instructions to receive a set of characters inputted by a user of a computing device, play a media file, and transcribe the media file to form a transcription. The processing unit also executes the set of instructions to identify a beginning time point of a segment of the media file containing the set of characters. The transcription is used to identify the beginning time point. The processing unit also executes the set of instructions to identify an ending time point of the segment of the media file containing the set of characters. The transcription is used to identify the ending time point. The processing unit also executes the set of instructions to store the beginning time point and the ending time point in the memory.
Referring to
In one embodiment, the character identification and notification system 100 initiates an entry prompt 112 on the graphical user interface 104, and a user 114 inputs the characters 108 in a query field 116 on the entry prompt 112. The entry prompt 112 is shown in
In one embodiment, the character identification and notification system 100 includes a transcription module 126 that transcribes the media file 110 by converting speech, or audio, in the media file 110 into text. The transcription module 126 may include, or work with, a speech-to-text application 128. In one non-limiting example, the speech-to-text application 128 may originate from an outside, or third-party, source, such as Nuance's Dragon® NaturallySpeaking® speech recognition software, YouTube®, or any other voice recognition software or software source.
In one embodiment, a media player 130 plays the media file 110 as the transcription module 126 transcribes the media file 110. By way of specific example, if the computing device 102 is an MP3 player and the media file 110 is an MP3 file, the media player 130 may play the MP3 file while the transcription module 126 transcribes the MP3 file. As described below, the user 114 may be notified as to whether the currently playing media file 110 contains the characters 108.
In another embodiment, the transcription module 126 transcribes any or all of the media files contained in the media database 118 regardless of whether the media files contained in the media database are being played by the media player 130. This embodiment may be used, for example, when the user 114 desires to know whether or not the media contained in the media database 118 includes the characters 108. Thus, the user 114 is able to know whether or not the media in the media database 118 includes the characters 108 even if the media contained in the media database 118 is not currently playing.
The transcription module 126 transcribes the media file 110 to form a transcription 132 of the media file 110. The character identification and notification system 100 includes an identification module 134, which uses the transcription 132 of the media file 110 to determine whether the media file 110 includes the characters 108. In one embodiment, the identification module 134 determines whether the transcription 132 includes the characters 108. In another embodiment, the identification module 134 uses the transcription 132 to identify one or more segments of the media file 110 that include the characters 108. The identification module 134 may also identify a beginning time point and ending time point for each of the segments identified that includes the characters 108.
An example of identifying one or more segments of the media file 110 that contain the characters 108 is shown with particular reference to
In one embodiment, the identification module 134 identifies a beginning time point 144, 148 and an ending time point 146, 150 of each segment in the media file 110 in which the characters 108 occur. The beginning time point 144, 148 and the ending time point 146, 150 may be stored in a memory, and may be referenced at a later time. In one non-limiting example, the beginning and ending time points 144, 146, 148, 150 are expressed as elapsed, or remaining, times within the total time span of the media file 110. In the example of
Another illustrative embodiment is shown with respect to the first segment 140 in
As discussed above, the identification module 134 may identify the first segment 140 and the second segment 142 at the same time that the media player 130 plays the media file 110. In one embodiment, the identification module 134 may also monitor all media files played thereafter by the media player 130, and determine whether the subsequently-played media files contain the characters 108. Such subsequently-played media files may include any media files that are played after the user 114 submits the characters 108. The identification module 134 may also identify any segments in those subsequently-played media files that contain the characters 108.
In another embodiment, segments of any or all media files in the media database 118 may be identified by the identification module 134 using transcriptions of the media files that are generated by the transcription module 126. In this embodiment, segments may be identified regardless of whether the associated media file is currently playing. In one specific non-limiting example, the user 114 may desire to know whether the characters 108 are included in the media files contained in a particular directory, or storage unit, of his or her computing device 102. In this example, the identification module 134 may identify or report any occurrences of the characters 108 in the media files contained in the directory, as well as the media file segments in which the characters 108 occur.
In one embodiment, upon determining that the media file 110 includes the characters 108, or upon identifying the segment(s) of the media file 110 that include the characters 108, a notification module 158 may notify the user 114. For example, the notification module 158 may notify the user 114 using an audio or visual alert. In one embodiment, the notification module 158 initiates the notification prompt 106 on the graphical user interface 104. A non-limiting example of the notification prompt 106 is shown in
The notification prompt 106 may also include a play button 160, which causes the computing device 102 to play the identified segment of the media file 110. The notification prompt 106 may also include a download button 162, which causes the character identification and notification system 100 to initiate downloading of the identified segment. Downloading the identified segment may be useful when the entire media file 110, but no segments thereof, is included on the media database 118. The download function may also be useful when the media database 118 or the media file 110 are not stored on the computing device 102, and are instead located at a remote location, such as across the Internet. In one example, the user 114 may download the first segment 140 or the second segment 142 instead of, or in addition to, the media file 110. The notification prompt 106 may also include a close button 164, which closes the notification prompt 106.
Although the character identification and notification system 100 is shown to be implemented on the computing device 102, the character identification and notification system 100, as well as the media database 118, may be included on a remote computer and connected to the computing device 102 via a network connection, including over the Internet. In another embodiment, the character identification and notification system 100 is an application that may be downloaded from a server over a wireless network, such as the Internet. Also, the media player 130 may be separate from the character identification and notification system 100, and may be a media player that originates from a third party, such as Microsoft®.
The illustrative embodiments may be used to notify the user 114 when a word or phrase is spoken, or otherwise contained, in his or her songs, movies, or TV episodes. Identifying such user-defined words or phrases can help to identify recurring story lines in the user's media. Identifying such user-defined words or phrases may also link seemingly dissimilar media files, such as when the character identification and notification system 100 identifies a phrase that is normally heard in a particular TV episode in an unrelated song.
Referring to
The process also transcribes the media file to form a transcription (step 205). The process determines if the transcription of the media file includes the set of characters (step 207). If the transcription of the media file does not include the set of characters, the process terminates.
If the process determines that the transcription of the media file includes the set of characters, the process initiates a notification prompt on the graphical user interface of a computing device associated with the user (step 209). The process then terminates
Referring to
The process determines whether the play button has been selected by the user (step 305). If the process determines that the play button has been selected by the user, the process plays the identified segment of the media file (step 307). The process then returns to step 305.
Returning to step 305, if the process determines that the play button has not been selected by the user, the process determines if the download button has been selected by the user (step 309). If the process determines that the download button has been selected by the user, the process downloads the identified segment of the media file (step 311). The process then returns to step 305.
Returning to step 309, if the process determines that the download button has not been selected by the user, the process determines whether the close button has been selected by the user (step 313). If the process determines that the close button has not been selected by the user, the process returns to step 305. If the process determines that the close button has been selected by the user, the process then terminates.
The flowcharts and block diagrams in the different depicted embodiments illustrate the architecture, functionality, and operation of some possible implementations of apparatus, methods and computer program products. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified function or functions. In some alternative implementations, the function or functions noted in the block may occur out of the order noted in the Figures. For example, in some cases, two blocks shown in succession may be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
Referring to
The processor unit 405 serves to execute instructions for software that may be loaded into the memory 407. The processor unit 405 may be a set of one or more processors or may be a multi-processor core, depending on the particular implementation. Further, the processor unit 405 may be implemented using one or more heterogeneous processor systems in which a main processor is present with secondary processors on a single chip. As another illustrative example, the processor unit 405 may be a symmetric multi-processor system containing multiple processors of the same type.
The memory 407, in these examples, may be, for example, a random access memory or any other suitable volatile or non-volatile storage device. The persistent storage 409 may take various forms depending on the particular implementation. For example, the persistent storage 409 may contain one or more components or devices. For example, the persistent storage 409 may be a hard drive, a flash memory, a rewritable optical disk, a rewritable magnetic tape, or some combination of the above. The media used by the persistent storage 409 also may be removable. For example, a removable hard drive may be used for the persistent storage 409. The memory 407 or the persistent storage 409 may be used, for example, to store one or more segments of a media file containing user-definable characters, including the beginning and ending point of such segments.
The communications unit 411, in these examples, provides for communications with other data processing systems or communication devices. In these examples, the communications unit 411 may be a network interface card. The communications unit 411 may provide communications through the use of either or both physical and wireless communication links.
The input/output unit 413 allows for the input and output of data with other devices that may be connected to the computing device 402. For example, the input/output unit 413 may provide a connection for user input through a keyboard and mouse. Further, the input/output unit 413 may send output, such as a processing job, to a processing device. In the case in which the computing device 402 is a cellular phone, the input/output unit 413 may also allow devices to be connected to the cellular phone, such as microphones, headsets, and controllers. The display 415 provides a mechanism to display information to a user, such as a graphical user interface. The display 415 may be the graphical user interface 104 in
Instructions for the operating system and applications or programs are located on the persistent storage 409. These instructions may be loaded into the memory 407 for execution by the processor unit 405. The processes of the different embodiments may be performed by the processor unit 405 using computer-implemented instructions, which may be located in a memory, such as the memory 407. These instructions are referred to as program code, computer-usable program code, or computer-readable program code that may be read and executed by a processor in the processor unit 405. The program code in the different embodiments may be embodied on different physical or tangible computer-readable media, such as the memory 407 or the persistent storage 409.
Program code 417 is located in a functional form on a computer-readable media 419 and may be loaded onto or transferred to the computing device 402 for execution by the processor unit 405. The program code 417 and the computer-readable media 419 form computer program product 421 in these examples. In one embodiment, the computer program product 421 is the character identification and notification system 100 in
In another embodiment, the program code 417 may include computer-usable program code capable of receiving a set of characters inputted by a user of a computing device, playing a media file, and transcribing the media file to form a transcription. The program code 417 may also include computer-usable program code capable of identifying a beginning time point of a segment of the media file containing the set of characters. The transcription may be used to identify the beginning time point. The program code 417 may also include computer-usable program code capable of identifying an ending time point of the segment of the media file containing the set of characters. The transcription may be used to identify the ending time point. The program code 417 may also include computer-usable program code capable of storing the beginning time point and the ending time point in the memory. Any combination of the above-mentioned computer-usable program code may be implemented in the program code 417.
In one example, the computer-readable media 419 may be in a tangible form, such as, for example, an optical or magnetic disc that is inserted or placed into a drive or other device that is part of the persistent storage 409 for transfer onto a storage device, such as a hard drive that is part of the persistent storage 409. In a tangible form, the computer-readable media 419 also may take the form of a persistent storage, such as a hard drive or a flash memory that is connected to the computing device 402. The tangible form of the computer-readable media 419 is also referred to as computer recordable storage media.
Alternatively, the program code 417 may be transferred to the computing device 402 from the computer-readable media 419 through a communication link to the communications unit 411 or through a connection to the input/output unit 413. The communication link or the connection may be physical or wireless in the illustrative examples. The computer-readable media 419 also may take the form of non-tangible media, such as communication links or wireless transmissions containing the program code 417.
The different components illustrated for the computing device 402 are not meant to provide architectural limitations to the manner in which different embodiments may be implemented. The different illustrative embodiments may be implemented in a data processing system including components in addition to or in place of those illustrated for computing device 402. Other components shown in
As one example, a storage device in the computing device 402 is any hardware apparatus that may store data. The memory 407, the persistent storage 409, and the computer-readable media 419 are examples of storage devices in a tangible form.
In another example, a bus system may be used to implement the communications fabric 403 and may be comprised of one or more buses, such as a system bus or an input/output bus. Of course, the bus system may be implemented using any suitable type of architecture that provides for a transfer of data between different components or devices attached to the bus system. Additionally, the communications unit 411 may include one or more devices used to transmit and receive data, such as a modem or a network adapter. Further, a memory may be, for example, the memory 407 or a cache such as found in an interface and memory controller hub that may be present in the communications fabric 403.
The principles of the present invention can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment containing both hardware and software elements. In one embodiment, the invention is implemented in software, which includes but is not limited to, firmware, resident software, microcode, and other computer readable code.
Furthermore, the principles of the present invention can take the form of a computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system. For the purposes of this description, a computer-usable or computer readable medium can be any tangible apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
The previous detailed description is of a small number of embodiments for implementing the invention and is not intended to be limiting in scope. One of skill in this art will immediately envisage the methods and variations used to implement this invention in other areas than those described in detail. The following claims set forth a number of the embodiments of the invention disclosed with greater particularity.
Number | Name | Date | Kind |
---|---|---|---|
2774591 | Uewett | Dec 1956 | A |
3965484 | Matz et al. | May 1976 | A |
4710758 | Mussier et al. | Dec 1987 | A |
4829294 | Iwami et al. | May 1989 | A |
4962475 | Hernandez et al. | Oct 1990 | A |
5337258 | Dennis | Aug 1994 | A |
5367619 | Dipaolo et al. | Nov 1994 | A |
5635683 | McDermott et al. | Jun 1997 | A |
5640577 | Scharmer | Jun 1997 | A |
5774591 | Black et al. | Jun 1998 | A |
5823948 | Ross, Jr. et al. | Oct 1998 | A |
5845255 | Mayaud | Dec 1998 | A |
5963952 | Smith | Oct 1999 | A |
6006240 | Handley | Dec 1999 | A |
6192380 | Light et al. | Feb 2001 | B1 |
6323846 | Westerman et al. | Nov 2001 | B1 |
6728753 | Parasnis et al. | Apr 2004 | B1 |
6910179 | Pennell et al. | Jun 2005 | B1 |
6981001 | Reddick et al. | Dec 2005 | B1 |
7343565 | Ying et al. | Mar 2008 | B2 |
7479949 | Jobs et al. | Jan 2009 | B2 |
7499046 | Wright et al. | Mar 2009 | B1 |
7509588 | Os et al. | Mar 2009 | B2 |
7519223 | Dehlin et al. | Apr 2009 | B2 |
7565139 | Neven et al. | Jul 2009 | B2 |
7657849 | Chaudhri et al. | Feb 2010 | B2 |
7664739 | Farago et al. | Feb 2010 | B2 |
7664991 | Gunda et al. | Feb 2010 | B1 |
7978181 | Westerman | Jul 2011 | B2 |
8140421 | Humphries et al. | Mar 2012 | B1 |
8171030 | Pereira et al. | May 2012 | B2 |
8392430 | Hua et al. | Mar 2013 | B2 |
8494310 | Aona et al. | Jul 2013 | B2 |
8510349 | Duttick | Aug 2013 | B1 |
8515839 | Ma et al. | Aug 2013 | B2 |
8676680 | Humphries et al. | Mar 2014 | B2 |
9405400 | Khafizov et al. | Aug 2016 | B1 |
20030063073 | Geaghan et al. | Apr 2003 | A1 |
20030189552 | Chuang et al. | Oct 2003 | A1 |
20040008363 | Suzuki et al. | Jan 2004 | A1 |
20050012723 | Pallakoff | Jan 2005 | A1 |
20050071423 | Rajaniemi | Mar 2005 | A1 |
20050165881 | Brooks et al. | Jul 2005 | A1 |
20060007177 | McLintock | Jan 2006 | A1 |
20060010098 | Goodnow et al. | Jan 2006 | A1 |
20060010400 | Dehlin et al. | Jan 2006 | A1 |
20060026535 | Hotelling et al. | Feb 2006 | A1 |
20060037051 | McDowell et al. | Feb 2006 | A1 |
20060067053 | Yu et al. | Mar 2006 | A1 |
20060265249 | Follis et al. | Nov 2006 | A1 |
20060287088 | Mashimo et al. | Dec 2006 | A1 |
20070097084 | Niijima | May 2007 | A1 |
20070143312 | Wiseman | Jun 2007 | A1 |
20070174570 | Horii et al. | Jul 2007 | A1 |
20070185727 | Ma et al. | Sep 2007 | A1 |
20070229471 | Kim et al. | Oct 2007 | A1 |
20070250777 | Chen et al. | Oct 2007 | A1 |
20080244453 | Cafer | Oct 2008 | A1 |
20080254869 | Fujimoto et al. | Oct 2008 | A1 |
20080255837 | Kahn | Oct 2008 | A1 |
20080313140 | Pereira et al. | Dec 2008 | A1 |
20090106667 | Lyle et al. | Apr 2009 | A1 |
20090161994 | Sauerwein, Jr. | Jun 2009 | A1 |
20090196475 | Demirli et al. | Aug 2009 | A1 |
20090207154 | Chino | Aug 2009 | A1 |
20090251435 | Westerman et al. | Oct 2009 | A1 |
20090262894 | Shukla et al. | Oct 2009 | A1 |
20090278806 | Duarte et al. | Nov 2009 | A1 |
20090322699 | Hansson | Dec 2009 | A1 |
20100013780 | Ikeda et al. | Jan 2010 | A1 |
20100044121 | Simon et al. | Feb 2010 | A1 |
20100054607 | Aono et al. | Mar 2010 | A1 |
20100058182 | Jung | Mar 2010 | A1 |
20100098339 | Kido | Apr 2010 | A1 |
20100110032 | Kim et al. | May 2010 | A1 |
20100115408 | Mujkic et al. | May 2010 | A1 |
20100162153 | Lau | Jun 2010 | A1 |
20100199285 | Medovich | Aug 2010 | A1 |
20100034476 | Kido | Nov 2010 | A1 |
20110022387 | Hager | Jan 2011 | A1 |
20110069230 | Polumbus et al. | Mar 2011 | A1 |
20110072048 | Hua et al. | Mar 2011 | A1 |
20110113333 | Lee | May 2011 | A1 |
20110125528 | Padate et al. | May 2011 | A1 |
20110161820 | Lee | Jun 2011 | A1 |
20120005034 | Jarman et al. | Jan 2012 | A1 |
20130190056 | Chaudhri et al. | Jul 2013 | A1 |
20130275975 | Masuda et al. | Oct 2013 | A1 |
Entry |
---|
Bonacina et al., “A Web-Based System for Family Health Record”, IEEE, Aug. 23, 2007, pp. 3652-3656. |
Bui et al., “Timeline: Visualizing integrated Patient Records”, IEEE, Jul. 9, 2007, pp. 462-473. |
Fox et al., “Adapting to Network and Client Variation Using Infrastructural Proxies: Lessons and Perspectives”, Aug. 1998, IEEE Personal Communications, Aug. 1998, pp. 10-19. |
Mohan et al., “Adapting Multimedia Internet Content for Universal Access”, IEEE Transactions on Multimedia, vol. 1, No. 1, Mar. 1999, 36 pages. |
Novelli et al., “A Grid-based Infrastructure to Support Multimedia Content Distribution”, 2007, 7 pages. |
Smith et al., “Transcoding Internet Content for Heterogeneous Client Devices”, IEEE, 1998, pp. 599-602. |
Tu et al., “Multiquality Data Replication in Multimedia Databases:”, IEEE Transactions on Knowledge and Data Engineering, vol. 19, No. 5, May 2007, 16 pages. |
Number | Date | Country | |
---|---|---|---|
61317744 | Mar 2010 | US | |
61317827 | Mar 2010 | US | |
61317812 | Mar 2010 | US | |
61317793 | Mar 2010 | US | |
61317741 | Mar 2010 | US | |
61317800 | Mar 2010 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16573991 | Sep 2019 | US |
Child | 17515527 | US | |
Parent | 15202400 | Jul 2016 | US |
Child | 16573991 | US | |
Parent | 12770965 | Apr 2010 | US |
Child | 15202400 | US |