Patent Grant
9832516
The invention relates generally to providing interactive multimedia content over multiple devices, and more particularly to systems and methods for managing the interaction of multiple input and output devices with a seamless multimedia presentation having selectably presentable content segments.
Over the past decade there has been an exponential growth in the prevalence of streaming media in the lives of the general public. Users frequently listen to streaming music on Internet radio stations such as Pandora, and watch streaming television shows, movies, and video clips on websites such as Hulu, Netflix, and YouTube. Interactive streaming multimedia content, though less common, is also available. Existing forms of interactive videos allow a viewer to make choices on how to proceed through predefined video paths; however, this functionality is accomplished using separate video segments that are jumped to upon selection, resulting in a noticeable disconnect in audio and video between consecutive segments. Further, these forms of interactive media rely on a single device for receiving user interactions and playing the resulting audio and video for the user. Accordingly, users would benefit from systems and methods for interacting with selectably presentable multimedia content through multiple input and/or output devices.
Methods and systems are disclosed for multiple device control and interaction with selectably presentable media content, such as a segmented video presentation that, as it is assembled in real-time based on viewer choices, is seamlessly played for the viewers, such that the video appears to be a single, linear presentation without noticeable gaps, jumps, or delays. Various devices may be used as output devices to view the multimedia content, and/or as input devices to interact with and make choices affecting playback of the content.
In one aspect, a system for multiple device interaction with selectably presentable multimedia content includes an output engine, an input engine, a manager, and a memory that stores selectably presentable multimedia content segments. Each content segment represents a predefined portion of one or more content paths. The output engine, executing on a first device, receives a subset of the content segments, assembles them into a seamless multimedia presentation that is one of the content paths, and plays the assembled multimedia presentation. The input engine, executing on a second device, receives user interactions associated with the multimedia presentation, and the manager coordinates the multimedia presentation among multiple devices based on the user interactions.
At least one of the content segments may include a predefined decision period during which a user may select, as that content segment is playing, a subsequent content segment to be played immediately following the conclusion or selection of the playing content segment.
In one embodiment, the input engine presents to a user, during a predefined decision period as a content segment is playing, visual representations of two or more alternative content segments from which a subsequent content segment may be selected. The input engine may also present to the user, upon reaching the predefined decision period, a visual representation of the time left to select an alternative content segment.
In some implementations, there are multiple input engines, each configured to execute on a different device. Each input engine may provide interactive options to a user based on a characteristic of a device user and/or a device.
In another embodiment, there are multiple output engines, each configured to execute on a different device. The output engines may play the assembled multimedia presentation at the same time, in accordance with a common timeline. Each assembled multimedia presentation may include the same set of content segments, causing the output engines to play the same multimedia presentation. Alternatively, some of the assembled multimedia presentations may include different content segments, thereby causing those output engines to play different multimedia presentations.
In various embodiments, the manager is configured to execute on the first device, the second device, and/or a third device. The manager may include an event analyzer that evaluates user interactions received from the input engine and, based on the evaluation, selects content segments to provide to the output engine.
In a further implementation, to coordinate the multimedia presentation, the devices are synchronized to a common timeline. The input engine may receive user interactions simultaneously with playback of the multimedia presentation by the output engine.
In another aspect, a method for multiple device interaction with selectably presentable multimedia content includes the step of storing selectably presentable multimedia content segments, with each content segment representing a predefined portion of one or more content paths. An output engine, executing on a first device, receives a subset of the content segments, assembles them into a seamless multimedia presentation that is one of the content paths, and plays the assembled multimedia presentation. An input engine, executing on a second device, receives user interactions associated with the multimedia presentation, and a manager coordinates the multimedia presentation among multiple devices based on the user interactions.
At least one of the content segments may include a predefined decision period during which a user may select, as that content segment is playing, a subsequent content segment to be played immediately following the conclusion or selection of the playing content segment.
In one embodiment, the input engine presents to a user, during a predefined decision period as a content segment is playing, visual representations of two or more alternative content segments from which a subsequent content segment may be selected. The input engine may also present to the user, upon reaching the predefined decision period, a visual representation of the time left to select an alternative content segment.
In some implementations, there are multiple input engines, each configured to execute on a different device. Each input engine may provide interactive options to a user based on a characteristic of a device user and/or a device.
In another embodiment, there are multiple output engines, each configured to execute on a different device. The output engines may play the assembled multimedia presentation at the same time, in accordance with a common timeline. Each assembled multimedia presentation may include the same set of content segments, causing the output engines to play the same multimedia presentation. Alternatively, some of the assembled multimedia presentations may include different content segments, thereby causing those output engines to play different multimedia presentations.
In various embodiments, the manager is configured to execute on the first device, the second device, and/or a third device. The manager may include an event analyzer that evaluates user interactions received from the input engine and, based on the evaluation, selects content segments to provide to the output engine.
In a further implementation, to coordinate the multimedia presentation, the devices are synchronized to a common timeline. The input engine may receive user interactions simultaneously with playback of the multimedia presentation by the output engine.
Other aspects and advantages of the invention will become apparent from the following drawings, detailed description, and claims, all of which illustrate the principles of the invention, by way of example only
A more complete appreciation of the invention and many attendant advantages thereof will be readily obtained as the same becomes better understood by reference to the following detailed description when considered in connection with the accompanying drawings. In the drawings, like reference characters generally refer to the same parts throughout the different views. Further, the drawings are not necessarily to scale, with emphasis instead generally being placed upon illustrating the principles of the invention.
Described herein are various embodiments of methods and supporting systems for managing the interaction of multiple input and output devices with a seamless multimedia presentation having selectably presentable content segments. The disclosed techniques may be used in conjunction with seamlessly assembled and selectably presentable multimedia content, such as that described in U.S. patent application Ser. No. 13/033,916, filed Feb. 24, 2011, and entitled “System and Method for Seamless Multimedia Assembly,” the entirety of which is incorporated by reference herein.
Selectably presentable multimedia content may include, for example, one or more predefined, separate multimedia content segments that are combined to create a continuous, seamless presentation such that there are no noticeable gaps, jumps, freezes, or other visual or audible interruptions to video or audio playback between segments. In addition to the foregoing, “seamless” may refer to a continuous playback of content that gives the viewer the appearance of watching a single, linear multimedia presentation. In some instances, the viewer is permitted to make choices or otherwise interact in real-time at decision points or during decision periods interspersed throughout the multimedia content. Decision points and/or decision periods may occur at any time and in any number during a multimedia segment, including at or near the end. Decision points and/or periods may be predefined, occurring at fixed points or during fixed periods in the multimedia content segments. Based at least in part on the viewer's choices, one or more corresponding multimedia segment(s) associated with the choices may be presented to the viewer.
The chosen multimedia segment(s) may be presented immediately following a currently playing segment, or may be shown after other segments are played. Further, the chosen multimedia segment(s) may be presented to the viewer immediately after selection, after a fixed or random delay, at the end of a decision period, and/or at the end of the currently playing segment. Two or more combined segments form a seamless multimedia content path, and there may be multiple paths that a viewer can take to experience a complete, start-to-finish, seamless presentation. Further, one or more multimedia segments may be shared among intertwining paths while still ensuring a seamless transition from a previous segment and to the next segment. The content paths may be predefined, with fixed sets of possible transitions in order to ensure seamless transitions among segments.
Traversal of the multimedia content along a content path may be performed by selecting among options that appear on and/or around the video while the video is playing. In some embodiments, these options are presented to viewers at a decision point and/or during a decision period in a content segment. The display may hover and then disappear when the decision period ends or when an option has been selected. Further, a countdown or other visual, aural, or other sensory indicator may be presented during playback of content segment to inform the viewer of the point by which he must make his selection. For example, the countdown may indicate when the decision period will end.
The segment that is played after a currently playing segment may be determined based on the option selected. Each option may result in a different video and audio segment being played. As previously mentioned, the transition to the next segment may occur immediately upon selection, at the end of the current segment, or at some other predefined or random point. Notably, the transition between content segments may be seamless. In other words, the audio and video may continue playing regardless of whether a segment selection is made, and no noticeable gaps appear in audio or video playback between any connecting segments. In some instances, the video continues on to another segment after a certain amount of time if none is chosen, or may continue playing in a loop.
In one example, the multimedia content is a music video in which the viewer selects options upon reaching segment decision points to determine subsequent content to be played. First, a video introduction segment is played for the viewer. Prior to the end of the segment, a decision point is reached at which the viewer may select the next segment to be played from a listing of choices. In this case, the viewer is presented with a choice as to who will sing the first verse of the song: a tall, female performer, or a short, male performer. The viewer is given an amount of time to make a selection (i.e., a decision period), after which, if no selection is made, a default segment will be automatically selected. The default may be a predefined or random selection. Of note, the media content continues to play during the time the viewer is presented with the choices. Once a choice is selected (or the decision period ends), a seamless transition occurs to the next segment, meaning that the audio and video continue on to the next segment as if there were no break between the two segments and the user cannot visually or audibly detect the transition. As the music video continues, the viewer is presented with other choices at other decisions points, depending on which path of choices is followed. Ultimately, the viewer arrives at a final segment, having traversed a complete multimedia content path.
Although the techniques described herein relate primarily to audio and video playback, the invention is equally applicable to various streaming and non-streaming media, including animation, video games, interactive media, and other forms of content usable in conjunction with the present systems and methods. Further, there may be more than one audio, video, and/or other media content stream played in synchronization with other streams. Streaming media may include, for example, multimedia content that is continuously presented to a viewer while it is received from a content delivery source, such as a remote video server. If a source media file is in a format that cannot be streamed and/or does not allow for seamless connections between segments, the media file may be transcoded or converted into a format supporting streaming and/or seamless transitions.
Referring to
A single device may perform both input and output functions. For example, a smartphone may allow a user to provide input using a touchscreen, while viewing the multimedia presentation on the display screen of the phone. Alternatively, a single device may have both input and output capabilities, but may only be used for either input or output. For example, the smartphone may be used as an input device to interact with a video that is being played on a television.
Referring now to
Referring again to
The Manager 110, input engine(s) 210 and output engine(s) 230 may be distributed among the input and output devices 102, 106. In some implementations, however, the Manager 110 is stored on and/or executable by a separate system, such as a server in communication with the input and output devices 102, 106. As depicted in
Other configurations are also possible. For example, in other embodiments, the Manager 110 may include multiple components that may be distributed among the input devices 102, output devices 106, and/or other systems or devices. There may also be more than one Manager 110, each of which may work independently or in synchronization with one or more of the other management components.
The Manager 110, depicted in further detail in
The Manager 110 may also be responsible for session initialization. For example, when a session begins (e.g., prior to or as a multimedia presentation begins playback), each device (input and/or output) establishes communication with the Manager 110 to inform the Manager 110 that the respective device intends to participate in the session. Each device may also indicate whether it will be acting as an input device, an output device, or both. Upon successfully initializing the session, the Manager 110 has knowledge of the number and type of devices participating in the session, the devices that will act as input and/or output devices, and various information associated with participating users, such as login name, IP address, location, social networking account user name, and the like. At this point, each device may be permitted to engage in unidirectional or bidirectional communication with the Manager 110.
In one embodiment, the Manager 110 includes a Project Configuration Manager 405, an Event Analyzer 410, an Event Distributer 415, and a Choice Manager 420.
The Project Configuration Manager 405 reads from a project configuration file 407 that stores the defined content path structure of the multimedia presentation, e.g., how the multimedia content segments may be linked together in various manners to form one or more content paths (in some embodiments, a video tree). The configuration file 407 may further specify which audio, video, and/or other media files correspond to each content segment, i.e., which audio, video, and/or other media should be retrieved when the Manager 110 determines that a particular content segment should be played. Additionally, the configuration file 407 may indicate the interface elements that should be displayed or otherwise presented to users, as well as the when the elements should be displayed.
In some embodiments, the configuration file 407 is also used in determining which media files should be loaded or buffered prior to being played (or potentially played). Because decision periods may occur near the end of a segment, it may be necessary to begin transfer of one or more of the potential next segments to viewers prior to a selection being made. For example, if a viewer is approaching a decision point with three possible next segments for selection, all three potential segments may be loaded to ensure a smooth transition upon conclusion of the current segment. Intelligent buffering of the video, audio, and/or other media content may be performed as described in U.S. patent application Ser. No. 13/437,164, filed Apr. 2, 2012, and entitled “Systems and Methods for Loading More Than One Video Content at a Time,” the entirety of which is incorporated by reference herein.
As earlier indicated, the Project Configuration Manager 405 may reference the configuration file 407 to determine which interface elements should be displayed to viewers. The configuration file 407 may further indicate the specific timings for which actions may be taken with respect to the interface elements (e.g., when a particular element is active and can be interacted with). The interface elements may include, for example, playback controls (pause, stop, play, seek, etc.), segment option selectors (e.g., buttons, images, text, animations, video thumbnails, and the like, that a viewer may interact with during decision periods, the selection of which results in a particular multimedia segment being seamlessly played following the conclusion of the current segment), timers (e.g., a clock or other graphical or textual countdown indicating the amount of time remaining to select an option or next segment, which, in some cases, may be the amount of time remaining until the current segment will transition to the next segment), links, popups, an index (for browsing and/or selecting other multimedia content to view or listen to), and/or a dynamic progress bar such as that described in U.S. patent application Ser. No. 13/622,795, filed Sep. 19, 2012, and entitled “Progress Bar for Branched Videos,” the entirety of which is incorporated by reference herein. In addition to visual elements, sounds or other sensory elements may be presented. For example, a timer may have a “ticking” sound synchronized with the movement of a clock hand. The interactive interface elements may be shared among multimedia segments or may be unique to one or more of the segments.
In one implementation, the Event Analyzer 410 evaluates data received from one or more input engines that are participating in a session and, based on the evaluation, determines how the multimedia presentation should continue. For example, referring again to the interactive music video discussed above, the data received from the input engines may indicate the selection of a particular singer to continue the song. The choice may be associated with a particular algorithm that the Event Analyzer 410 uses to determine the behavior of the multimedia presentation. If the choice is associated with a voting mechanism, the Event Analyzer 410 will determine the singer having the most votes and, in response, the Manager 110 may direct any output engines in the session to seamlessly transition to playing the content segment associated with the highest-voted singer. Other algorithms are possible, such as a bidding algorithm in which an option requested by a highest bidder is presented to viewers.
The Event Analyzer 410 may evaluate other types of user interactions. For example, the Manager 110 may direct all output engines to pause playback if a pause event is received from any input engine. In other embodiments, users are able to send messages or chat with each other, or cause text, images, or sounds to be output to one or more other output engines via the Manager 110. Messages may include, for example, suggested content segments for selection, allowing viewers to “lobby” for particular selections from among those available for subsequent playback. One skilled in the art will appreciate the various interactions received by the Event Analyzer 410 that may affect playback of the multimedia presentation.
In one embodiment, the Event Distributer 415 manages distribution of instructions, messages, updates, and other data to the output engines participating in a session. The Event Distributer 415 informs each output engine how to proceed with playback of the multimedia presentation. The instructions sent by the Event Distributer 415 may be based on prior user interactions received and evaluated by the Event Analyzer 410. Notably, the Event Distributer 415 may provide different instructions to different output engines depending on characteristics associated with a user or device. In one example, an interactive video presents male and female viewers with the option of having a character in the video spend the night studying or go out for entertainment. Upon a determination by the Manager 110 that the majority of the viewers have voted for the character to seek entertainment, the Event Distributer 415 sends instructions to output engines associated with male viewers to play a segment in which the character attends a sports game. For female viewers, the Event Distributer 415 instead sends instructions to cause playback of a segment in which the character sees a movie. The Event Distributor 415 may also send events input engines; e.g., the Event Distributer 415 may send synchronizing events to the input engines 210 and/or provide instructions on what interface elements should be presented to users.
Referring still to
As described above, the Event Distributor 415 may provide different instructions to input output engines. In some embodiments, these instructions are based on instructions from the Choice Manager 420. For example, referring again to the study-or-party interactive video described above, the majority of viewers may vote for the character to head to the library. These votes (interactions) are received from the input devices at the Event Analyzer 410 component of the Manager 110, which determines, based on a voting algorithm, that the winning selection is that the character should study. This determination of the winning selection is received by the Choice Manager 420, which may examine the content path structure provided by the Project Configuration Manager 405 to determine which content segment should be played after the current content segment, given that the character should be shown studying. Upon determining the correct segment to play (which may include different segments for different devices and/or users, as indicated above), the Choice Manager 420 informs the Event Distributor 415 of the next segment to be played or action that should be taken, and the Event Distributor 415 communicates to the output engines 230 (and/or input engines 210) the instructions necessary for the next segment/action to take effect.
Each device that enables a user to interact with a multimedia presentation as described herein may include an input engine 210, as depicted in
In one embodiment, an input engine 210 includes a Project Configuration Manager 505, External Assets Manager 515, and Choice Manager 520. Similar to the Project Configuration Manager 405 described with respect to the Manager 110, the Project Configuration Manager 505 in the input engine 210 may read from a project configuration file 507 that defines the content path structure of the multimedia presentation, e.g., how the multimedia content segments may be linked together in various manners to form one or more content paths (in some embodiments, a video tree). The configuration file 507 may further specify which audio, video, and/or other media files correspond to each content segment, and may indicate the interface elements that should be displayed or otherwise presented to users, as well as when the elements should be displayed. In some embodiments, the configuration file 507 is substantially similar or identical to the project configuration file 407 utilized by the Manager 110. The configuration file 507 may be stored on the device associated with the input engine 210, or the file 507 may be remotely accessed by the Project Configuration Manager 505.
The External Assets Manager 515 component of the input engine 210 manages assets 550 associated with a multimedia presentation, including user interface elements such as segment choice buttons/thumbnails, splash screens, timers, playback control buttons, and other visual and/or audio interactive or display elements. Upon direction from the Choice Manager 520, the External Assets Manager 515 sends the assets for display/playback in accordance with the timeline of the multimedia presentation.
The input engine 210 may also include a Choice Manager 520, which receives user interactions (e.g., mouse clicks, keyboard presses, touchpad presses, etc.) that may be translated into actions associated with the multimedia presentation (e.g., segment selections, playback controls, etc.) and provides them to the Manager 110, which processes the actions as described above. In addition to receiving user interactions, the Choice Manager 520 may receive other events or data, such as video and/or audio recorded previously or in real-time by the user, images, text (e.g., real-time chat) or other data uploads, such as information associated with the device user (e.g., user name, avatar, social networking account information, demographics, etc.), or device itself (e.g., GPS location, device type, device model, etc.). The events, actions, and/or data may be provided to the Choice Manager 520 automatically, or as a result of an action taken by the user.
The input engine 210 may also receive events from the Manager 110. For example, the Event Distributor 415 may send synchronizing events to the input engine 210 and/or provide instructions on what interface elements should be presented to the user and when they should be presented, in accordance with a common presentation timeline. Taking into account events received from the Manager 110 as well as the path structure of the multimedia content received from the Project configuration Manager 505, the Choice Manager 520 informs the External Assets Manager 510 of the interface elements that should be presented to the user and the timing of the presentation.
In some embodiments, the Choice Manager 520 instructs the External Assets Manager 510 to present interface elements based on information associated with the device and/or device user. For example, in one example of the present invention, a group of viewers in a movie theater can use their mobile devices (e.g., smartphones, tablets, etc.) to vote on how a currently playing movie should proceed. In this instance, the Choice Manager 520 receives data from each participating mobile device indicating whether it is, e.g., an Android® smartphone, or an Apple® iPad® tablet. When a point in the movie timeline is reached where user interface elements are to be presented to the users, the Choice Manager 520 may direct the External Assets Manager 510 to provide customized interface elements to each user's device based on the properties of the device, e.g., different graphical themes that correlate with the design of the device.
In some embodiments, the input engine 210 also includes functionality to cause media to be presented on an input device, similar to the functionality provided by the output engine 230, further described below. For example, the input engine 210 may cause an input device to play the same audio, video, and/or other media as is simultaneously presented on one or more output devices participating in the same session. In another example, the input engine 210 may cause personalized media content to be played on an associated input device, such as audio, video, imagery, or other content based on a particular user, the user's device, and/or interactions or content segment selections made by the user. For example, if there is one device used for output but there are multiple input devices, the present system may display global video (i.e., video common to all users) with global data on the screen, while simultaneously providing each user with individualized video, data, and selection options. The foregoing example may operate with multiple output devices as well (e.g., multiple screens showing a globally-presented video). Individualized content may include customized ending options; for example, at the end of the multimedia presentation, each user may be provided with one of multiple possible endings and/or an individualized ending. Such an ending may include displaying a winner, comparing the performance of the user to other users, and so on.
Each device that enables a user to view, listen to, or engage in other sensory perception with, a multimedia presentation as described herein may include an output engine 230, as depicted in
In one embodiment, each output engine 230 includes a Project Configuration Manager 605, External Assets Manager 615, Choice Manager 620, Loading Manager 635, Video Parser, 645, and Video Bytes Appender 655. Similar to the Project Configuration Managers 405 and 505 described with respect to the Manager 110 and input engine 210, the Project Configuration Manager 605 in the output engine 230 may read from a project configuration file 607 that defines the content path structure of the multimedia presentation, e.g., how the multimedia content segments may be linked together in various manners to form one or more content paths (in some embodiments, a video tree). The configuration file 607 may further specify which audio, video, and/or other media files correspond to each content segment, and may indicate the interface elements that should be displayed or otherwise presented to users, as well as when the elements should be displayed. In some embodiments, the configuration file 607 is substantially similar or identical to the project configuration file 507 utilized by the input engine 210 and/or the project configuration file 407 utilized by the Manager 110. The configuration file 607 may be stored on the device associated with the output engine 230, or the file 607 may be remotely accessed by the Project Configuration Manager 605.
The External Assets Manager 615 component of the output engine 230 manages and retrieves assets 670 associated with a multimedia presentation, such as audio, video, and/or other media files, as well as user interface elements such as segment choice buttons/thumbnails, splash screens, timers, playback control buttons, and other visual and/or audio interactive or display elements. The External Assets Manager 615 may cause the same or similar interface elements to be shown on an output device as are shown on an input device. In some embodiments, the External Assets Manager 615 causes the display of real-time status messages or other indications of activities performed on input devices; e.g., how many and/or which users voted for a particular option, information about users (photo, Facebook user name, etc.), the options selected by the users, and so on. Upon direction from the Choice Manager 620, the External Assets Manager 615 may send the assets for display/playback in accordance with the timeline of the multimedia presentation.
The Loading Manager 635 manages the downloading of streaming media according to a loading logic. In one embodiment, the Loading Manager 635 receives the media content path structure from the Project Configuration Manager 605 and events from the Choice Manager 620 and, based on the path structure and events, determines which media segments to download and/or buffer (if the segments are remotely stored). For example, if the Choice Manager informs the Loading Manager 635 that a particular segment A will be played at an upcoming point in the timeline, the Loading Manager 635 may intelligently request for download, in advance of playback or notification of potential playback, additional media segments X, Y and Z that may be played following segment A. The downloading may occur even if fewer than all of X, Y, Z will be played (e.g., if X, Y and Z are potential segment choices branching off segment A).
In some embodiments, the Loading Manager 635 ceases or cancels downloading of content segments or other media if it determines that it is no longer possible for a particular media content segment (or other content) to be presented on a currently traversed media path. Referring to the above example, a user may select, via an input engine 210, segment Y as the next segment to be played. The selection may be relayed to the Manager 110, which processes the selection and notifies the Choice Manager 620 output engine 230. The Choice Manager 620 may then inform the Loading Manager 635 of the selection event and, based on the Loading Manager's 635 knowledge of the content path structure of the multimedia presentation, the Loading Manager 635 may stop active downloads or dequeue pending downloads of content segments no longer reachable now that segment Y has been selected.
The output engine 230 may also include Video Parser 645 and Video Bytes Appender 655 modules. In one embodiment, the Video Parser 645 receives media content from the Loading Manager 635 and analyzes and/or modifies the raw video or other media content, for example, to concatenate two separate media streams into a single timeline. The Video Parser 645 may also insert cue points and other event markers, such as junction events, into media streams. The Video Bytes Appender 655 processes media content output by the Video Parser 645. For instance, the Video Bytes Appender 655 may form one or more streams of bytes from multiple video, audio or other media streams, and feed the formed streams such that there is seamless playback of the combined media content. The Video Bytes Appender 655 may be directed by the Choice Manager 620 to stream media in synchronization with other modules of the output engine 230, such as the External Assets Manager 615.
Referring still to
In some implementations, the input engines 210 and/or output engines 230 participating in a playback session of a multimedia presentation track data regarding user interactions, users, and/or devices and provide the data to the Manager 110 for the collection of various analytics. Collected analytics may include, but are not limited to: the number, type, and/or location of a device; user data, such as login information, name, address, age, sex, and the like; user interactions, such as button/touchpad presses, mouse clicks, mouse/touchpad movements, interaction timings, and the like; decisions made by users or automatically (e.g., content segment user choice or default selection); and content paths followed in the presentation content structure. The analytics may include those described in U.S. patent application Ser. No. 13/034,645, entitled “System and Method for Data Mining within Interactive Multimedia,” and filed Feb. 24, 2011, the entirety of which is incorporated by reference herein. Those skilled in the art will appreciate the various analytics available for collection and analysis in the present system.
The present invention may be used in a variety of applications, including but not limited to the scenarios described herein. In one exemplary embodiment, a user watches selectably presentable video content on his television (which includes an output engine 230) and can direct the path of the video by interacting with his smartphone or tablet (which includes an input engine 210). In this example, the Manager 110 may be integrated or collocated with the output engine 230 (see
In another embodiment, multiple users view an interactive movie in a movie theater and vote or bid to direct its path. In this case, the output engine 230 may be stored on or executable by the movie theater projection system, with the projection screen acting as a display, and each user in the audience may have a smartphone, tablet, or other mobile or fixed device having an input engine 210 that receives user interactions and forwards them to the Manager 110, which may be separate from or collocated with the output engine 230 (see
In another exemplary implementation, an interactive game show is presented on a television (having an output engine 230), with multiple participants interacting through suitable respective input devices 102 (having input engines 210). Questions are presented to the participants on the television, and answers are collected by the Manager 110 via the input devices. The Manager 110 directs the flow of the game show content based on the participant interactions. The Manager 110 may be collocated with or separate from the output engine 230 (see
In one application, a multimedia presentation includes selectably presentable content segments forming various paths of a video storyline that can be traversed and interacted with by viewers. In this example, there may be multiple input devices 102 having input engines 210 and multiple output devices 106 having output engines 230, each of which interacts with a separately located Manager 110 (see
In another example using the configuration of
One skilled in the art will recognize the various forms in which the systems and methods described herein may be implemented. The functions provided by the Manager 110, input engines 210, output engines 230, and/or other components may be implemented in any appropriate hardware or software. If implemented as software, the invention may execute on a system capable of running a commercial operating system such as the Microsoft Windows® operating systems, the Apple OS X® operating systems, the Apple iOS® platform, the Google Android™ platform, the Linux® operating system and other variants of UNIX® operating systems, and the like.
Some or all of the described functionality may be implemented in a media player and/or other software downloaded to or existing on the viewer's device. Some of the functionality may exist remotely; for example, management functions may be performed on one or more remote servers. In some embodiments, the viewer's device serves only to provide output and input functionality, with the remainder of the processes being performed remotely.
The local and/or remote software may be implemented on hardware such as a smart or dumb terminal, network computer, personal digital assistant, wireless device, smartphone, tablet, television, gaming device, music player, mobile telephone, laptop, palmtop, wireless telephone, information appliance, workstation, minicomputer, mainframe computer, or other computing device, that is operated as a general purpose computer or a special purpose hardware device that can execute the functionality described herein. The software may be implemented on a general purpose computing device in the form of a computer including a processing unit, a system memory, and a system bus that couples various system components including the system memory to the processing unit.
The described systems may include a plurality of software processing modules stored in a memory and executed on a processor in the manner described herein. The program modules may be in the form of any or more suitable programming languages, which are converted to machine language or object code to allow the processor or processors to read the instructions. The software may be in the form of a standalone application, implemented in any suitable programming language or framework.
Method steps of the techniques described herein can be performed by one or more programmable processors executing a computer program to perform functions of the invention by operating on input data and generating output. Method steps can also be performed by, and apparatus of the invention can be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). Modules can refer to portions of the computer program and/or the processor/special circuitry that implements that functionality.
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. One or more memories may store media assets (e.g., audio, video, graphics, interface elements, and/or other media files), configuration files, and/or instructions that, when executed by a processor, form the modules, engines, and other components described herein and perform the functionality associated with the components. The processor and the memory can be supplemented by, or incorporated in special purpose logic circuitry.
In various embodiments, the devices include a web browser, client software, or both. The web browser allows the client to request a web page or other downloadable program, applet, or document (e.g., from the server(s)) with a web page request. One example of a web page is a data file that includes computer executable or interpretable information, graphics, sound, text, and/or video, that can be displayed, executed, played, processed, streamed, and/or stored and that can contain links, or pointers, to other web pages. In one embodiment, a user of the client manually requests a web page from the server. Alternatively, the device automatically makes requests with the web browser. Examples of commercially available web browser software are Microsoft® Internet Explorer®, Mozilla® Firefox®, and Apple Safari®.
In some embodiments, the devices include client software. The client software provides functionality to the device that provides for the implementation and execution of the features described herein. The client software may be implemented in various forms, for example, it may be in the form of a web page, widget, and/or Java, JavaScript, .Net, Silverlight, Flash, and/or other applet or plug-in that is downloaded to the device and runs in conjunction with the web browser. The client software and the web browser may be part of a single client-server interface; for example, the client software can be implemented as a “plug-in” to the web browser or to another framework or operating system. Any other suitable client software architecture, including but not limited to widget frameworks and applet technology may also be employed with the client software.
A communications network may connect the devices with one or more servers and/or with each other. The communication may take place via any media such as standard telephone lines, LAN or WAN links (e.g., T1, T3, 56 kb, X.25), broadband connections (ISDN, Frame Relay, ATM), wireless links (802.11, Bluetooth, GSM, CDMA, etc.), and so on. The network may carry TCP/IP protocol communications, and HTTP/HTTPS requests made by a web browser, and the connection between the clients and servers can be communicated over such TCP/IP networks. The type of network is not a limitation, however, and any suitable network may be used.
It should also be noted that embodiments of the present invention may be provided as one or more computer-readable programs embodied on or in one or more articles of manufacture. The article of manufacture may be any suitable hardware apparatus, such as, for example, a floppy disk, a hard disk, a CD-ROM, a CD-RW, a CD-R, a DVD-ROM, a DVD-RW, a DVD-R, a flash memory card, a PROM, a RAM, a ROM, or a magnetic tape. In general, the computer-readable programs may be implemented in any programming language. The software programs may be further translated into machine language or virtual machine instructions and stored in a program file in that form. The program file may then be stored on or in one or more of the articles of manufacture.
Certain embodiments of the present invention were described above. It is, however, expressly noted that the present invention is not limited to those embodiments, but rather the intention is that additions and modifications to what was expressly described herein are also included within the scope of the invention. Moreover, it is to be understood that the features of the various embodiments described herein were not mutually exclusive and can exist in various combinations and permutations, even if such combinations or permutations were not made express herein, without departing from the spirit and scope of the invention. In fact, variations, modifications, and other implementations of what was described herein will occur to those of ordinary skill in the art without departing from the spirit and the scope of the invention. As such, the invention is not to be defined only by the preceding illustrative description.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5568602 | Callahan et al. | Oct 1996 | A |
| 5607356 | Schwartz | Mar 1997 | A |
| 5636036 | Ashbey | Jun 1997 | A |
| 5734862 | Kulas | Mar 1998 | A |
| 5818435 | Kozuka et al. | Oct 1998 | A |
| 6122668 | Teng et al. | Sep 2000 | A |
| 6128712 | Hunt et al. | Oct 2000 | A |
| 6191780 | Martin et al. | Feb 2001 | B1 |
| 6222925 | Shiels et al. | Apr 2001 | B1 |
| 6298482 | Seidman et al. | Oct 2001 | B1 |
| 6728477 | Watkins | Apr 2004 | B1 |
| 6801947 | Li | Oct 2004 | B1 |
| 7155676 | Land et al. | Dec 2006 | B2 |
| 7310784 | Gottlieb et al. | Dec 2007 | B1 |
| 7379653 | Yap et al. | May 2008 | B2 |
| 7444069 | Bernsley | Oct 2008 | B1 |
| 7627605 | Lamere et al. | Dec 2009 | B1 |
| 7917505 | van Gent et al. | Mar 2011 | B2 |
| 8065710 | Malik | Nov 2011 | B2 |
| 8190001 | Bernsley | May 2012 | B2 |
| 8276058 | Gottlieb et al. | Sep 2012 | B2 |
| 8281355 | Weaver et al. | Oct 2012 | B1 |
| 8600220 | Bloch et al. | Dec 2013 | B2 |
| 8650489 | Baum et al. | Feb 2014 | B1 |
| 8860882 | Bloch et al. | Oct 2014 | B2 |
| 8977113 | Rumteen et al. | Mar 2015 | B1 |
| 9009619 | Bloch et al. | Apr 2015 | B2 |
| 9021537 | Funge et al. | Apr 2015 | B2 |
| 9190110 | Bloch | Nov 2015 | B2 |
| 9257148 | Bloch et al. | Feb 2016 | B2 |
| 9271015 | Bloch et al. | Feb 2016 | B2 |
| 20020091455 | Williams | Jul 2002 | A1 |
| 20020105535 | Wallace et al. | Aug 2002 | A1 |
| 20020106191 | Betz et al. | Aug 2002 | A1 |
| 20020120456 | Berg et al. | Aug 2002 | A1 |
| 20020177914 | Chase | Nov 2002 | A1 |
| 20030159566 | Sater et al. | Aug 2003 | A1 |
| 20030183064 | Eugene et al. | Oct 2003 | A1 |
| 20030184598 | Graham | Oct 2003 | A1 |
| 20030221541 | Platt | Dec 2003 | A1 |
| 20040138948 | Loomis | Jul 2004 | A1 |
| 20040172476 | Chapweske | Sep 2004 | A1 |
| 20050019015 | Ackley et al. | Jan 2005 | A1 |
| 20050055377 | Dorey et al. | Mar 2005 | A1 |
| 20050091597 | Ackley | Apr 2005 | A1 |
| 20050102707 | Schnitman | May 2005 | A1 |
| 20060028951 | Tozun et al. | Feb 2006 | A1 |
| 20060064733 | Norton et al. | Mar 2006 | A1 |
| 20060150072 | Salvucci | Jul 2006 | A1 |
| 20060155400 | Loomis | Jul 2006 | A1 |
| 20060200842 | Chapman et al. | Sep 2006 | A1 |
| 20060224260 | Hicken et al. | Oct 2006 | A1 |
| 20070024706 | Brannon et al. | Feb 2007 | A1 |
| 20070033633 | Andrews et al. | Feb 2007 | A1 |
| 20070118801 | Harshbarger et al. | May 2007 | A1 |
| 20070157261 | Steelberg et al. | Jul 2007 | A1 |
| 20070162395 | Ben-Yaacov et al. | Jul 2007 | A1 |
| 20070239754 | Schnitman | Oct 2007 | A1 |
| 20080021874 | Dahl et al. | Jan 2008 | A1 |
| 20080022320 | Ver Steeg | Jan 2008 | A1 |
| 20080031595 | Cho | Feb 2008 | A1 |
| 20080086754 | Chen et al. | Apr 2008 | A1 |
| 20080091721 | Harboe et al. | Apr 2008 | A1 |
| 20080092159 | Dmitriev et al. | Apr 2008 | A1 |
| 20080148152 | Blinnikka et al. | Jun 2008 | A1 |
| 20080276157 | Kustka et al. | Nov 2008 | A1 |
| 20080300967 | Buckley et al. | Dec 2008 | A1 |
| 20080301750 | Silfvast et al. | Dec 2008 | A1 |
| 20080314232 | Hansson et al. | Dec 2008 | A1 |
| 20090022015 | Harrison | Jan 2009 | A1 |
| 20090024923 | Hartwig et al. | Jan 2009 | A1 |
| 20090055880 | Batteram et al. | Feb 2009 | A1 |
| 20090063681 | Ramakrishnan et al. | Mar 2009 | A1 |
| 20090116817 | Kim et al. | May 2009 | A1 |
| 20090199697 | Lehtiniemi et al. | Aug 2009 | A1 |
| 20090228572 | Wall et al. | Sep 2009 | A1 |
| 20090320075 | Marko | Dec 2009 | A1 |
| 20100017820 | Thevathasan et al. | Jan 2010 | A1 |
| 20100042496 | Wang et al. | Feb 2010 | A1 |
| 20100077290 | Pueyo | Mar 2010 | A1 |
| 20100146145 | Tippin et al. | Jun 2010 | A1 |
| 20100153512 | Balassanian et al. | Jun 2010 | A1 |
| 20100161792 | Palm et al. | Jun 2010 | A1 |
| 20100167816 | Perlman et al. | Jul 2010 | A1 |
| 20100186579 | Schnitman | Jul 2010 | A1 |
| 20100262336 | Rivas et al. | Oct 2010 | A1 |
| 20100268361 | Mantel et al. | Oct 2010 | A1 |
| 20100278509 | Nagano et al. | Nov 2010 | A1 |
| 20100287033 | Mathur | Nov 2010 | A1 |
| 20100287475 | van Zwol et al. | Nov 2010 | A1 |
| 20100293455 | Bloch | Nov 2010 | A1 |
| 20100332404 | Valin | Dec 2010 | A1 |
| 20110007797 | Palmer et al. | Jan 2011 | A1 |
| 20110010742 | White | Jan 2011 | A1 |
| 20110026898 | Lussier et al. | Feb 2011 | A1 |
| 20110041059 | Amarasingham et al. | Feb 2011 | A1 |
| 20110096225 | Candelore | Apr 2011 | A1 |
| 20110126106 | Ben Shaul et al. | May 2011 | A1 |
| 20110131493 | Dahl | Jun 2011 | A1 |
| 20110138331 | Pugsley et al. | Jun 2011 | A1 |
| 20110191684 | Greenberg | Aug 2011 | A1 |
| 20110197131 | Duffin et al. | Aug 2011 | A1 |
| 20110200116 | Bloch et al. | Aug 2011 | A1 |
| 20110202562 | Bloch et al. | Aug 2011 | A1 |
| 20110246885 | Pantos et al. | Oct 2011 | A1 |
| 20110252320 | Arrasvuori et al. | Oct 2011 | A1 |
| 20110264755 | Salvatore De Villiers | Oct 2011 | A1 |
| 20120005287 | Gadel et al. | Jan 2012 | A1 |
| 20120017141 | Eelen et al. | Jan 2012 | A1 |
| 20120094768 | McCaddon et al. | Apr 2012 | A1 |
| 20120110620 | Kilar et al. | May 2012 | A1 |
| 20120198412 | Creighton et al. | Aug 2012 | A1 |
| 20120308206 | Kulas | Dec 2012 | A1 |
| 20130046847 | Zavesky et al. | Feb 2013 | A1 |
| 20130054728 | Amir et al. | Feb 2013 | A1 |
| 20130055321 | Cline et al. | Feb 2013 | A1 |
| 20130259442 | Bloch et al. | Oct 2013 | A1 |
| 20130282917 | Reznik et al. | Oct 2013 | A1 |
| 20140040280 | Slaney et al. | Feb 2014 | A1 |
| 20140078397 | Bloch et al. | Mar 2014 | A1 |
| 20140082666 | Bloch et al. | Mar 2014 | A1 |
| 20140129618 | Panje et al. | May 2014 | A1 |
| 20140178051 | Bloch et al. | Jun 2014 | A1 |
| 20140270680 | Bloch et al. | Sep 2014 | A1 |
| 20140282013 | Amijee | Sep 2014 | A1 |
| 20140380167 | Bloch et al. | Dec 2014 | A1 |
| 20150067723 | Bloch et al. | Mar 2015 | A1 |
| 20150104155 | Bloch et al. | Apr 2015 | A1 |
| 20150179224 | Bloch et al. | Jun 2015 | A1 |
| 20150181301 | Bloch et al. | Jun 2015 | A1 |
| 20150199116 | Bloch et al. | Jul 2015 | A1 |
| 20150293675 | Bloch et al. | Oct 2015 | A1 |
| 20150294685 | Bloch et al. | Oct 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 10053720 | Apr 2002 | DE |
| 1033157 | Sep 2000 | EP |
| 2104105 | Sep 2009 | EP |
| 2359916 | Sep 2001 | GB |
| 2428329 | Jan 2007 | GB |
| 2008005288 | Jan 2008 | JP |
| WO-2000059224 | Oct 2000 | WO |
| WO-2007062223 | May 2007 | WO |
| WO-2007138546 | Dec 2007 | WO |
| WO-2008001350 | Jan 2008 | WO |
| WO-2008057444 | May 2008 | WO |
| WO-2008052009 | May 2008 | WO |
| WO-2009137919 | Nov 2009 | WO |
| Entry |
|---|
| U.S. Appl. No. 12/706,721 Published as US2010/0293455, System and Method for Assembling a Recorded Composition, filed Feb. 17, 2010. |
| U.S. Appl. No. 13/622,780, Systems and Methods for Constructing Multimedia Content Modules, filed Sep. 19, 2012. |
| U.S. Appl. No. 13/622,795, Progress Bar for Branched Videos, filed Sep. 19, 2012. |
| U.S. Appl. No. 13/838,830, Systems and Methods for Synchronization of Selectably Presentable Media Streams, filed Mar. 15, 2013. |
| U.S. Appl. No. 14/107,600, Methods and Systems for Unfolding Pre-Roll, filed Dec. 16, 2013. |
| U.S. Appl. No. 14/139,996, Methods and Systems for In-Video Library, filed Dec. 24, 2013. |
| U.S. Appl. No. 12/706,721, the Office Actions dated Apr. 26, 2012, Aug. 17, 2012, Mar. 28, 2013, Jun. 20, 2013 and Jan. 3, 2014. |
| U.S. Appl. No. 13/033,916, the Office Actions dated Jun. 7, 2013 and Jan. 2, 2014. |
| U.S. Appl. No. 13/034,645, the Office Actions dated Jul. 23, 2012 and Mar. 21, 2013. |
| U.S. Appl. No. 13/622,780, the Office Action dated Jan. 16, 2014. |
| U.S. Appl. No. 13/622,780 Published as US2014/0078397, Systems and Methods for Constructing Multimedia Content Modules, filed Sep. 19, 2012. |
| U.S. Appl. No. 13/622,795 Published as US2014/0082666, Progress Bar for Branched Videos, filed Sep. 19, 2012. |
| U.S. Appl. No. 12/706,721, the Office Actions dated Apr. 26, 2012, Aug. 17, 2012, Mar. 28, 2013, Jun. 20, 2013, and Jan. 3, 2014. |
| An ffmpeg and SDL Tutorial, “Tutorial 05: Synching Video,” Retrieved from internet on Mar. 15, 2013: <http://drancier.com/ffmpeg/tutoria105.html>, (4 pages). |
| Archos Gen 5 English User Manual Version 3.0, Jul. 26, 2007, pp. 1-81. |
| International Search Report for International Patent Application PCT/IL2012/000080 dated Aug. 9, 2012 (4 pages). |
| International Search Report for International Patent Application PCT/IL2012/000081 dated Jun. 28, 2012 (4 pages). |
| International Search Report for International Patent Application PCT/IL2010/000362 dated Aug. 25, 2010 (2 pages). |
| Supplemental European Search Report for EP10774637.2 (PCT/IL2010/000362) dated Jun. 20, 2012 (6 pages). |
| Labs.byHook: “Ogg Vorbis Encoder for Flash: Alchemy Series Part 1,” [Online] Internet Article, Retrieved on Jun. 14, 2012 from the Internet: URL:http://labs.byhook.com/2011/02/15/ogg-vorbis-encoder-for-flash-alchemy-series-part-1/, 2011, (pp. 1-8). |
| Yang, H, et al., “Time Stamp Synchronization in Video Systems,” Teletronics Technology Corporation, <http://www.ttcdas.com/products/daus encoders/pdf/ tech papers/tp 2010 time stamp video system.pdf>, Abstract, (8 pages). |
| Barlett, Mitch, “iTunes 11: How to Queue Next Song,” Technipages, Oct. 6, 2008, pp. 1-8, retrieved on Dec. 26, 2013 from the internet http://www.technipages.com/itunes-queue-next-song.html. |
| Gregor Miller et al. “MiniDiver: A Novel Mobile Media Playback Interface for Rich Video Content on an iPhoneTM”, Entertainment Computing A ICEC 2009, Sep. 3, 2009, pp. 98-109. |
| International Search Report and Writton Opinion for International Patent Application PCT/IB2013/001000 dated Jul. 31, 2013 (12 pages). |
| Sodagar, I., (2011) “The MPEG-DASH Standard for Multimedia Streaming Over the Internet”, IEEE Multimedia, IEEE Service Center, New York, NY US, vol. 18, No. 4, pp. 62-67. |
| Supplemental European Search Report for EP13184145 dated Jan. 30, 2014 (6 pages). |
| U.S. Appl. No. 12/706,721 9,190,110 Published as US2010/0293455, System and Method for Assembling a Recorded Composition, filed Feb. 17, 2010. |
| U.S. Appl. No. 13/033,916 Published as US2011/0200116, System and Method for Seamless Multimedia Assembly, filed Feb. 24, 2011. |
| U.S. Appl. No. 13/034,645 Published as US2011/0202562, System and Method for Data Mining Within Interactive Multimedia, filed Feb. 24, 2011. |
| U.S. Appl. No. 14/884,285, System and Method for Assembling a Recorded Composition, filed Oct. 15, 2015. |
| U.S. Appl. No. 13/437,164 8,600,220 Published as US2013/0259442 Systems and Methods for Loading More Than One Video Content at a Time, filed Apr. 2, 2012. |
| U.S. Appl. No. 14/069,694 9,271,015 Published as US2014/0178051, Systems and Methods for Loading More Than One Video Content at a Time, filed Nov. 1, 2013. |
| U.S. Appl. No. 13/622,780 8,860,882 Published as US2014/0078397, Systems and Methods for Constructing Multimedia Content Modules, filed Sep. 19, 2012. |
| U.S. Appl. No. 13/622,795 9,009,619 Published as US2014/0082666, Progress Bar for Branched Videos, filed Sep. 19, 2012. |
| U.S. Appl. No. 14/639,579 Published as US2015/0199116, Progress Bar for Branched Videos, filed Mar. 5, 2015. |
| U.S. Appl. No. 13/838,830 9,257,148 Published as US2014/0270680, System and Method for Synchronization of Selectably Presentable Media Streams, filed Mar. 15, 2013. |
| U.S. Appl. No. 14/984,821, System and Method for Synchronization of Selectably Presentable Media Streams, filed Dec. 30, 2015. |
| U.S. Appl. No. 14/107,600 Published as US2015/0067723, Methods and Systems for Unfolding Video Pre-Roll, filed Dec. 16, 2013. |
| U.S. Appl. No. 14/335,381 Published as US2015/0104155, Systems and Methods for Real-Time Pixel Switching, filed Jul. 18, 2014. |
| U.S. Appl. No. 14/139,996 Published as US2015/0181301, Methods and Systems for In-Video Library, filed Dec. 24, 2013. |
| U.S. Appl. No. 14/140,007 Published as US2015/0179224, Methods and Systems for Seeking to Non-Key Frames, filed Dec. 24, 2013. |
| U.S. Appl. No. 14/249,627 Published as US2015/0294685, Systems and Methods for Creating Linear Video From Branched Video, filed Apr. 10, 2014. |
| U.S. Appl. No. 14/249,665 Published as US2015/0293675, Dynamic Timeline For Branched Video, filed Apr. 10, 2014. |
| U.S. Appl. No. 14/509,700, Systems and Methods for Dynamic Video Bookmarking, filed Oct. 8, 2014. |
| U.S. Appl. No. 14/534,626, Systems and Methods for Parallel Track Transitions, filed Nov. 6, 2014. |
| U.S. Appl. No. 14/700,845, Systems and Methods for Nonlinear Video Playback Using Linear Real-Time Video Players, filed Apr. 30, 2015. |
| U.S. Appl. No. 14/700,862, Systems and Methods for Seamless Media Creation, filed Apr. 30, 2015. |
| U.S. Appl. No. 14/835,857, Systems and Methods for Adaptive and Responsive Video, filed Aug. 26, 2015. |
| U.S. Appl. No. 14/978,464, Intelligent Buffering of Large-Scale Video, filed Dec. 22, 2015. |
| U.S. Appl. No. 14/978,491, Seamless Transitions In Large-Schale Vidoe, filed Dec. 22, 2015. |
| U.S. Appl. No. 15/085,209, Media Stream Rate Synchronization, filed Mar. 30, 2016. |
| Number | Date | Country | |
|---|---|---|---|
| 20140380167 A1 | Dec 2014 | US |
