The present disclosure relates generally to video playback and editing and, more particularly, to systems and methods for providing a dynamic timeline for editing non-linear video content.
Existing video editing and post-production software products use a linear, static timeline to represent the progression of a video over time. The timeline is generally associated with a video that has a fixed duration, frame rate, and resolution. Accordingly, rendering the video after editing it results in the creation of a linear, non-interactive video. Branching, non-linear videos, however, cannot be edited using static timelines because such timelines are unable to accurately represent the various video paths that can be interactively traversed during the viewing of these videos. Linear, static timelines do not provide the ability for users to edit, structure, and manipulate multiple interrelated timelines that together result in a navigable, interactive experience.
Systems and methods are presented for providing a dynamic timeline for editing and playing interactive, non-linear video. In one aspect, a dynamic timeline is provided which allows a user to edit a video content structure. The structure includes a plurality of video content paths, each video content path including a plurality of video content segments. The video content segments in a first video content path are visually represented on the dynamic timeline. A selection in the dynamic timeline is received that changes a first video content segment from the first video content path to a second video content segment in an alternative video content path in the video content structure. Subsequently, the dynamic timeline is updated to display visual representations of at least some of the video content segments in the alternative video content path.
In one implementation, the dynamic timeline further includes at least one visual indicator disposed at a branching point of a video content path. The visual indicator can identify a number of alternative video content segments that follow the branching point. The dynamic timeline can also include at least one visual indicator that delineates a decision period in a video content segment.
In another implementation, the dynamic timeline is updated by replacing the visual representations of the video content segments that follow the first video content segment in the first video content path with visual representations of the video content segments that follow the second video content segment in the alternative video content path.
In a further implementation, the dynamic timeline allows for the editing of properties associated with a particular video content segment.
In yet another implementation, a preview of an interactive video based on the video content structure is provided in response to a user interaction with the dynamic timeline. The dynamic timeline can then be updated based on a user interaction with the interactive video preview.
In another aspect, a dynamic timeline system allows a user to edit a video content structure. The structure includes a plurality of video content paths, each video content path including a plurality of video content segments. The video content segments in a first video content path are visually represented on the dynamic timeline. A selection in the dynamic timeline is received that changes a first video content segment from the first video content path to a second video content segment in an alternative video content path in the video content structure. Subsequently, the dynamic timeline is updated to display visual representations of at least some of the video content segments in the alternative video content path.
In one implementation, the dynamic timeline further includes at least one visual indicator disposed at a branching point of a video content path. The visual indicator can identify a number of alternative video content segments that follow the branching point. The dynamic timeline can also include at least one visual indicator that delineates a decision period in a video content segment.
In another implementation, the dynamic timeline is updated by replacing the visual representations of the video content segments that follow the first video content segment in the first video content path with visual representations of the video content segments that follow the second video content segment in the alternative video content path.
In a further implementation, the dynamic timeline allows for the editing of properties associated with a particular video content segment.
In yet another implementation, a preview of an interactive video based on the video content structure is provided in response to a user interaction with the dynamic timeline. The dynamic timeline can then be updated based on a user interaction with the interactive video preview.
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 implementations of methods and supporting systems for editing a video tree using a dynamic timeline. In some implementations, the video tree is formed by nodes that are connected in a branching form, such as in the video tree 100 shown in
The prerecorded video segments in a video tree can be selectably presentable multimedia content and can 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” can refer to a continuous playback of content that gives the user the appearance of watching a single, linear multimedia presentation, as well as a continuous playback of multiple content segments that have smooth audio and/or video transitions (e.g., fadeout/fade-in, linking segments) between two or more of the segments.
In some instances, the user 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 can occur at any time and in any number during a multimedia segment, including at or near the beginning and/or the end of the segment. Decision points and/or periods can be predefined, occurring at fixed points or during fixed periods in the multimedia content segments. Based at least in part on the user's choices made before or during playback of content, one or more subsequent multimedia segment(s) associated with the choices can be presented to the user. In some implementations, the subsequent segment is played immediately and automatically following the conclusion of the current segment, whereas in other implementations, the subsequent segment is played immediately upon the user's interaction with the video, without waiting for the end of the decision period or the segment itself.
If a user does not make a selection at a decision point or during a decision period, a default or random selection can be made by the system. In some instances, the user is not provided with options; rather, the system automatically selects the segments that will be shown based on information that is associated with the user, other users, or other factors, such as the current date. For example, the system can automatically select subsequent segments based on the user's IP address, location, time zone, the weather in the user's location, social networking ID, saved selections, and so on. The system can also automatically select segments based on previous selections made by other users, such as the most popular suggestion or shared selections. The information can also be displayed to the user in the video, e.g., to show the user why an automatic selection is made. As one example, video segments can be automatically selected for presentation based on the geographical location of three different users: a user in Canada will see a twenty-second beer commercial segment followed by an interview segment with a Canadian citizen; a user in the US will see the same beer commercial segment followed by an interview segment with a US citizen; and a user in France is shown only the beer commercial segment.
Multimedia segment(s) selected automatically or by a user can be presented immediately following a currently playing segment, or can be shown after other segments are played. Further, the selected multimedia segment(s) can be presented to the user 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 can be multiple paths that a user can take to experience a complete, start-to-finish, seamless presentation. Further, one or more multimedia segments can be shared among intertwining paths while still ensuring a seamless transition from a previous segment and to the next segment. The content paths can be predefined, with fixed sets of possible transitions in order to ensure seamless transitions among segments. There can be any number of predefined paths, each having any number of predefined multimedia segments. Some or all of the segments can have the same or different playback lengths, including segments branching from a single source segment.
Traversal of the nodes along a content path in a tree can be performed by selecting among options that appear on and/or around the video while the video is playing. In some implementations, these options are presented to users at a decision point and/or during a decision period in a content segment. The display can 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 can be presented during playback of content segment to inform the user of the point by which he must make his selection. For example, the countdown can indicate when the decision period will end, which can be at a different time than when the currently playing segment will end. If a decision period ends before the end of a particular segment, the remaining portion of the segment can serve as a non-interactive seamless transition to one or more other segments. Further, during this non-interactive end portion, the next multimedia content segment (and other potential next segments) can be downloaded and buffered in the background for later playback (or potential playback).
The segment that is played after a currently playing segment can be determined based on an option selected or other interaction with the video. Each available option can result in a different video and audio segment being played. As previously mentioned, the transition to the next segment can 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 can be seamless. In other words, the audio and video can 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 can continue playing in a loop.
In one example, the multimedia content is a music video in which the user selects options upon reaching segment decision points to determine subsequent content to be played. First, a video introduction segment is played for the user. Prior to the end of the segment, a decision point is reached at which the user can select the next segment to be played from a listing of choices. In this case, the user 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 user 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 can be a predefined or random selection. Of note, the media content continues to play during the time the user 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 user is presented with other choices at other decisions points, depending on which path of choices is followed. Ultimately, the user arrives at a final segment, having traversed a complete multimedia content path.
Individual multimedia content segments of selectably-presentable and interactive video such as that described above can be edited similarly to typical linear video. For example, the audio, video, effects, and other components of a content segment can be edited on a linear timeline that represents the playback progression of the content segment over a fixed period of time. All of the content segments in an interactive video tree, however, cannot be placed on a single, static linear timeline without overwhelming or confusing a user (e.g., a video editor). Because there are various paths that a viewer can take through a video tree, and thus different content segments that can be presented within the same timeframe, a static linear timeline cannot easily or accurately represent the possible progressions of the interactive video.
Referring to
The dynamic timeline 200 shown in
The names of the nodes shown in the timeline 200 can be displayed on or around their corresponding visual representations (and/or can appear when selected, when a cursor is hovered over the visual representation, and so on). For example, video segments 202a-202e are respectively titled “Beginning,” “Tall,” “Cheating guy,” Air guitar,” and “Ending.” In this example, the names of the segments 202a-202e descriptively correspond to objects, events, and/or choices in the video segments (e.g., the video starts, a tall guy cheats and plays air guitar, and the video ends). Each segment shown on the dynamic timeline that has a decision period (e.g., a period of time prior to a branching point during which a viewer can make a choice that will determine the viewer's path in the video tree) can have a visual indicator that delineates the decision period. The decision period can be a portion of a video segment shown on the timeline 200 that is highlighted, colored, or otherwise demarcated, such as decision period 225 of segment 202d.
At and/or around the dividing point between two segments, a visual indicator can identify the number of nodes that branch off and/or are otherwise reachable from the first segment. The visual indicator can be, for example, a circled number, as shown by visual indicator 215. Other graphical and/or textual indicators are contemplated, such as Arabic or Roman numerals with various associated shapes, sizes, and colors, icons, graphs, and the like. The branching node visual indicators can be always shown, or can be toggled, appear when a cursor is hovered over a segment or divider, and so on. Other icons or other graphical/textual indicators, such as visual indicator 210, can also be disposed near the dividing points of segments and can represent the type of change leading to a particular segment (e.g., the segment is a direct child node of the previous segment, the segment is jumped-to from the previous segment (which may or may not be in the same path), the two segments are parallel tracks such that they can be alternated between at any time during playback of the segments, and so on). For example, visual indicator 210 represents a direct parent-child node relationship between video segments 202a and 202b in the timeline. Accordingly, as shown in the video tree 100, there is a direct parent-child relationship between nodes 102a and 102b.
In some implementations, a user can manipulate the dynamic timeline 200 in a manner similar to static linear timelines in existing video editing software. For example, there can be a current position indicator 220 on the timeline 200 that can be dragged or otherwise manipulated by a user along the timeline 200 to navigate the video. The user can also jump to any part of the currently edited path by clicking on the corresponding area of the timeline. The current position indicator 220 can represent a current time, current frame, or other position in the video. Upon manipulating the current position indicator 220, the video frame corresponding to the location of the indicator 220 on the timeline 200 can be displayed in a video preview window 205. The user can also playback all or a portion of the video in the video preview window 205 using standard video player controls (e.g., play, rewind, fast-forward, pause, stop). In some implementations, the user can interact with the video playing in the video preview window 205, including selecting choices during decision periods and following different content paths in the video tree. If the user traverses a different path than that currently shown in the timeline 200, the timeline 200 can dynamically update to reflect the current path, as further described below.
In one implementation, a dynamic timeline can be altered by a user in order to play or edit a different content path in a video tree. Referring to
A user can change the timeline 310a to show a different content path (in this example, the path including video segments A1, B1, and C1). In some implementations, the path is changed by selecting a visual indicator 320 that displays the number of branches from the previous segment (e.g., child nodes, jump-to nodes, parallel nodes, etc.). Visual indicator 320 on timeline 410a indicates that there are two possible segments that can follow segment A1. Dynamic timeline 310b illustrates the interface element 330 that appears upon interaction with visual indicator 320. Interface element 330 displays to the user the different segments that can be reached from segment A1 in the video tree 300 (in this case, segments B1 and B2). Upon selection of a different segment than that currently shown, the dynamic timeline can be updated with the segments from the different content path. Thus, in
In one implementation, upon selecting one segment to change, the user is prompted to select each subsequent segment to display (if there is more than one possibility for the segment). In another implementation, the child nodes in the video tree 300 have an ordering or priority, and the first child at each branching point is selected for display (e.g., in dynamic timeline 310c, segment C1 is displayed rather than segment C2). Other methods for automatically selecting the subsequent nodes in a content path for display in a timeline are possible (e.g., random, last child, highest priority, lowest priority, shortest length, longest length, newest, oldest, previous selection, etc.).
Other methods of changing the content path shown in a timeline are also contemplated. For example, the user can interact with other interface elements, such as the dividers between segments and/or the segments themselves. There can also be controls and/or menus separate from the timeline that allow the user to specify a different content path to be shown. The interaction for switching a particular segment can be, for example, a dropdown menu, a graphical representation of options, a keyboard shortcut, a gesture, and/or other suitable interaction.
In one implementation, an individual segment that is displayed on a dynamic timeline can be edited by selecting the segment, dragging a current position cursor to the segment, or other suitable selection method. Video and/or audio assets can be associated with a segment, or the segment can be defined as a placeholder for video and/or audio not yet defined. The length of the segment can be automatically set based on the playback length of associated video and/or audio and/or, in some instances, can be manually set to a desired length. Connections to other segments can be defined, for example, through an interface on the timeline, by dragging and dropping segments on each other, by drawing lines between nodes (e.g., in a tree-view editor), and/or by other suitable methods. Nodes can be defined in parent/child relationships, as jump-to nodes (in which one node is able to jump to another node in the video tree without necessarily being a direct or indirect child), as parallel track nodes, as looping nodes, or other available node types. Element actions can be associated with the segment; for example, upon user interaction when viewing the segment during playback of the interactive video (and/or autonomously), the segment can allow the user to share the video with social networking connections, open a URL, control playback of the device, and so on. Other properties of a segment can be edited, such as the display name, display thumbnail, and associated notes, and other information about the segment.
In some implementations, by selecting a content segment shown on the timeline, an interactive and/or graphical content layer associated with the segment can be edited. Segments can include an interactive content layer which allows custom controls, text, graphics, timers, and/or other indicators or interactive elements to be associated with the audio/video content in the segment. The elements can be associated with individual segments, or, in some cases, across multiple segments. Elements present on the interactive content layer can be positioned, for example, on video content, a media player, or in other suitable locations. The interactive layer can be superimposed on the video such that the interactive elements are opaque or partially transparent, but the remainder of the layer is completely transparent, allowing the video to be viewed otherwise unobstructed. The interactive layer can be dimensioned equally to the video, or can occupy only a portion thereof. The interactive layer can appear immediately upon playback of the media content associated with a segment, and/or it can appear after a fixed, variable, or random delay.
In some implementations, the interactive layer includes button controls and/or a timer. It is to be appreciated that there are various graphical and textual forms that interactive controls, timers, and other elements can take, such as buttons, switches, dials, sliders, spinners, menus, progress bars, dialogs, popups, tabs, links, ribbons, graphical overlays, and the like. The elements on the interactive layer can be any size or color, and can be positioned anywhere on or around the video display. The elements can be icons, pictures, animations, and/or videos. Text entered by a viewer can appear on the interactive layer with various modifications and/or graphical effects. Elements can be rotoscoped onto the video, composited with the video using green screen or other techniques, superimposed, or otherwise overlaid on the video and can include visual effects such as shadowing, embossing, highlighting, distortion, and other desirable effects.
In some implementations, some elements on the interactive layer are hidden but active, such that a viewer cannot see the elements but can interact with them. In other implementations, some elements are passive, meaning that a viewer is unable to interact with the elements. Passive buttons can be displayed that allow a viewer to see what video path options are available and/or what path options are automatically selected for the viewer. Passive elements can be hidden or visible to the viewer.
Buttons (or other suitable controls) can be added to the interactive layer that allow a viewer to select an option during video playback that corresponds to a path to be followed. A timer can be added to the interactive layer to display the remaining amount of time that a viewer has to select a video path to follow. The timer can be represented as a clock, a bar, and/or any suitable textual and/or graphical representation of time. The timer can toggle between a visible and hidden display, which can be invoked automatically and/or by viewer interaction.
As described above with respect to
As the video is previewed, the associated dynamic timeline 200 can dynamically update in real-time to reflect the content path followed in the video. For example, on dynamic timeline 200, the current position indicator 220 is in the decision period of video segment 202b. Accordingly, the video in the video preview area 205 provides the user with two choice buttons 230a, 230b respectively associated with the two alternative nodes 102c, 104a in video tree 100 that branch from segment 202b (node 102b in video tree 100). If the user selects option 230b (“Sweetie pie”), the dynamic timeline 200 can be updated to replace video segments 202c, 202d, and 202e (corresponding to nodes 102c, 102d, and 102e in video tree 100, respectively) with the nodes corresponding to the new content path. Thus, as shown in
In some implementations, a dynamic timeline can behave similarly to a dynamic progress bar during editing and/or preview playback of an interactive video. For example, the timeline can take the form of a tree that is similar to or replicates all or a portion of the video tree structure that the interactive video is based on. The user can toggle the state of the dynamic timeline between a linear form and a tree form and can edit and manipulate the segments/nodes in either form using the techniques described herein. In one implementation, the dynamic timeline can take the form of a dynamic progress bar such as that described in U.S. patent application Ser. No. 13/622,795, filed on Sep. 19, 2012, and entitled, “Progress Bar for Branched Videos,” the entirety of which is incorporated by reference herein.
A user can reach a specific segment in the dynamic timeline, whether or not the segment is currently shown on the timeline, in various manners. For example, the user can select an option on the timeline that leads to the desired segment (e.g., select the desired segment from an alternative branch segment menu). The video can also be played until the segment is reached. In other instances, to reach a segment, the user can switch to a tree view of the timeline and select the specific segment and/or browse a list of segments that include all or a subset of the segments in the video tree. The segment can also be added to a list of “recently changed” or “important” segments, automatically and/or by the user.
The techniques described herein can be implemented in any appropriate hardware or software. If implemented as software, the processes can 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 can be implemented in software downloaded to or existing on a user's device. Some of the functionality can exist remotely; for example, video creation functions can be performed on one or more remote servers. In some implementations, the user'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 can be implemented on devices 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 can 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 can include a plurality of software processing modules stored in a memory and executed on a processor in the manner described herein. The program modules can be in the form of a suitable programming languages, which is converted to machine language or object code to allow the processor or processors to read the instructions. The software can 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 can 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 implementations, 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 implementation, 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 implementations, 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 can be implemented in various forms, for example, it can 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 can 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 can also be employed with the client software.
A communications network can connect the devices with one or more servers and/or with each other. The communication can 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 can 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 can be used.
It should also be noted that the present implementations can be provided as one or more computer-readable programs embodied on or in one or more articles of manufacture. The article of manufacture can 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 can be implemented in any programming language. The software programs can be further translated into machine language or virtual machine instructions and stored in a program file in that form. The program file can then be stored on or in one or more of the articles of manufacture.
Although the systems and methods 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 can be more than one audio, video, and/or other media content stream played in synchronization with other streams. Streaming media can include, for example, multimedia content that is continuously presented to a user 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 can be transcoded or converted into a format supporting streaming and/or seamless transitions.
While various implementations of the present invention have been described herein, it should be understood that they have been presented by example only. Where methods and steps described above indicate certain events occurring in certain order, those of ordinary skill in the art having the benefit of this disclosure would recognize that the ordering of certain steps can be modified and that such modifications are in accordance with the given variations. For example, although various implementations have been described as having particular features and/or combinations of components, other implementations are possible having any combination or sub-combination of any features and/or components from any of the implementations described herein.
Number | Name | Date | Kind |
---|---|---|---|
4569026 | Best | Feb 1986 | A |
5161034 | Klappert | Nov 1992 | A |
5568602 | Callahan et al. | Oct 1996 | A |
5607356 | Schwartz | Mar 1997 | A |
5636036 | Ashbey | Jun 1997 | A |
5676551 | Knight | Oct 1997 | A |
5734862 | Kulas | Mar 1998 | A |
5754770 | Shiels et al. | May 1998 | A |
5818435 | Kozuka et al. | Oct 1998 | A |
5848934 | Shiels et al. | Dec 1998 | A |
5887110 | Sakamoto et al. | Mar 1999 | A |
5894320 | Vancelette | Apr 1999 | A |
6067400 | Saeki et al. | May 2000 | 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 |
7231132 | Davenport | Jun 2007 | B1 |
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 |
7669128 | Bailey et al. | Feb 2010 | B2 |
7787973 | Lambert | Aug 2010 | B2 |
7917505 | van Gent et al. | Mar 2011 | B2 |
8024762 | Britt | Sep 2011 | B2 |
8065710 | Malik | Nov 2011 | B2 |
8151139 | Gordon | Apr 2012 | B1 |
8176425 | Wallace et al. | May 2012 | 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 |
8612517 | Yadid et al. | Dec 2013 | B1 |
8650489 | Baum et al. | Feb 2014 | B1 |
8826337 | Issa et al. | Sep 2014 | B2 |
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 |
9082092 | Henry | Jul 2015 | B1 |
9190110 | Bloch | Nov 2015 | B2 |
9257148 | Bloch | Feb 2016 | B2 |
9268774 | Kim et al. | Feb 2016 | B2 |
9271015 | Bloch et al. | Feb 2016 | B2 |
9390099 | Wang et al. | Jul 2016 | B1 |
9465435 | Zhang et al. | Oct 2016 | B1 |
9641898 | Bloch | May 2017 | B2 |
9672868 | Bloch et al. | Jun 2017 | B2 |
20020086724 | Miyaki et al. | Jul 2002 | A1 |
20020091455 | Williams | Jul 2002 | A1 |
20020105535 | Wallace | Aug 2002 | A1 |
20020106191 | Betz et al. | Aug 2002 | A1 |
20020120456 | Berg et al. | Aug 2002 | A1 |
20020129374 | Freeman et al. | Sep 2002 | A1 |
20020140719 | Amir et al. | Oct 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 |
20040091848 | Nemitz | May 2004 | A1 |
20040125124 | Kim et al. | Jul 2004 | A1 |
20040128317 | Sull et al. | Jul 2004 | 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 |
20050107159 | Sato | May 2005 | A1 |
20050210145 | Kim et al. | Sep 2005 | A1 |
20060024034 | Filo et al. | Feb 2006 | A1 |
20060028951 | Tozun et al. | Feb 2006 | A1 |
20060064733 | Norton | 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 |
20070003149 | Nagumo et al. | Jan 2007 | A1 |
20070024706 | Brannon et al. | Feb 2007 | A1 |
20070033633 | Andrews et al. | Feb 2007 | A1 |
20070099684 | Butterworth | May 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 |
20070253677 | Wang | Nov 2007 | A1 |
20070263722 | Fukuzawa | Nov 2007 | A1 |
20080019445 | Aono et al. | Jan 2008 | 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 |
20080170687 | Moors et al. | Jul 2008 | A1 |
20080178232 | Velusamy | Jul 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 |
20090191971 | Avent | Jul 2009 | A1 |
20090199697 | Lehtiniemi et al. | Aug 2009 | A1 |
20090228572 | Wall et al. | Sep 2009 | A1 |
20090258708 | Figueroa | Oct 2009 | A1 |
20090265746 | Halen et al. | Oct 2009 | A1 |
20090297118 | Fink et al. | Dec 2009 | A1 |
20090320075 | Marko | Dec 2009 | A1 |
20100017820 | Thevathasan et al. | Jan 2010 | A1 |
20100042496 | Wang | Feb 2010 | A1 |
20100077290 | Pueyo | Mar 2010 | A1 |
20100088726 | Curtis et al. | Apr 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 |
20100210351 | Berman | Aug 2010 | A1 |
20100262336 | Rivas et al. | Oct 2010 | A1 |
20100267450 | McMain | 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 |
20110033167 | Arling 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 |
20110163969 | Anzures et al. | Jul 2011 | A1 |
20110191684 | Greenberg | Aug 2011 | A1 |
20110197131 | Duffin | 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 | De Villiers | Oct 2011 | A1 |
20110307786 | Shuster | Dec 2011 | A1 |
20120004960 | Ma et al. | Jan 2012 | A1 |
20120005287 | Gadel et al. | Jan 2012 | A1 |
20120062576 | Rosenthal et al. | Mar 2012 | A1 |
20120081389 | Dilts | Apr 2012 | A1 |
20120089911 | Hosking et al. | Apr 2012 | A1 |
20120094768 | McCaddon et al. | Apr 2012 | A1 |
20120110620 | Kilar et al. | May 2012 | A1 |
20120134646 | Alexander | May 2012 | A1 |
20120147954 | Kasai et al. | Jun 2012 | A1 |
20120179970 | Hayes | Jul 2012 | A1 |
20120198412 | Creighton et al. | Aug 2012 | A1 |
20120308206 | Kulas | Dec 2012 | A1 |
20130028573 | Hoofien et al. | Jan 2013 | A1 |
20130039632 | Feinson | Feb 2013 | A1 |
20130046847 | Zavesky et al. | Feb 2013 | A1 |
20130054728 | Amir et al. | Feb 2013 | A1 |
20130055321 | Cline et al. | Feb 2013 | A1 |
20130061263 | Issa et al. | Mar 2013 | A1 |
20130097643 | Stone | Apr 2013 | A1 |
20130125181 | Montemayor et al. | May 2013 | A1 |
20130129308 | Karn et al. | May 2013 | A1 |
20130177294 | Kennberg | Jul 2013 | A1 |
20130188923 | Hartley et al. | Jul 2013 | A1 |
20130204710 | Boland et al. | Aug 2013 | A1 |
20130254292 | Bradley | Sep 2013 | A1 |
20130259442 | Bloch et al. | Oct 2013 | A1 |
20130282917 | Reznik et al. | Oct 2013 | A1 |
20130308926 | Jang et al. | Nov 2013 | A1 |
20140019865 | Shah | Jan 2014 | A1 |
20140025839 | Marko et al. | Jan 2014 | A1 |
20140040280 | Slaney et al. | Feb 2014 | A1 |
20140078397 | Bloch et al. | Mar 2014 | A1 |
20140082666 | Bloch | Mar 2014 | A1 |
20140094313 | Watson et al. | Apr 2014 | A1 |
20140101550 | Zises | Apr 2014 | A1 |
20140129618 | Panje et al. | May 2014 | A1 |
20140152564 | Gulezian et al. | Jun 2014 | A1 |
20140178051 | Bloch et al. | Jun 2014 | A1 |
20140186008 | Eyer | Jul 2014 | A1 |
20140194211 | Chimes et al. | Jul 2014 | A1 |
20140237520 | Rothschild et al. | Aug 2014 | A1 |
20140245152 | Carter et al. | Aug 2014 | A1 |
20140270680 | Bloch et al. | Sep 2014 | A1 |
20140282013 | Amijee | Sep 2014 | A1 |
20140380167 | Bloch | Dec 2014 | A1 |
20150046946 | Hassell et al. | Feb 2015 | A1 |
20150058342 | Kim et al. | Feb 2015 | A1 |
20150067723 | Bloch | Mar 2015 | A1 |
20150104155 | Bloch et al. | Apr 2015 | A1 |
20150179224 | Bloch et al. | Jun 2015 | A1 |
20150181301 | Bloch et al. | Jun 2015 | A1 |
20150185965 | Belliveau et al. | Jul 2015 | A1 |
20150195601 | Hahm | Jul 2015 | A1 |
20150199116 | Bloch | Jul 2015 | A1 |
20150201187 | Ryo | Jul 2015 | A1 |
20150258454 | King et al. | Sep 2015 | A1 |
20150293675 | Bloch et al. | Oct 2015 | A1 |
20150294685 | Bloch et al. | Oct 2015 | A1 |
20160062540 | Yang et al. | Mar 2016 | A1 |
20160104513 | Bloch | Apr 2016 | A1 |
20160105724 | Bloch | Apr 2016 | A1 |
20160132203 | Seto et al. | May 2016 | A1 |
20160170948 | Bloch | Jun 2016 | A1 |
20160173944 | Kilar et al. | Jun 2016 | A1 |
20160217829 | Bloch | Jul 2016 | A1 |
20160224573 | Shahraray et al. | Aug 2016 | A1 |
20160322054 | Bloch | Nov 2016 | A1 |
20160323608 | Bloch | Nov 2016 | A1 |
20170062012 | Bloch | Mar 2017 | A1 |
20170178409 | Bloch | Jun 2017 | A1 |
20170178601 | Bloch | Jun 2017 | A1 |
Number | Date | Country |
---|---|---|
2639491 | Mar 2010 | CA |
004038801 | Jun 1992 | DE |
10053720 | Apr 2002 | DE |
0965371 | Dec 1999 | EP |
1033157 | Sep 2000 | EP |
2104105 | Sep 2009 | EP |
2359916 | Sep 2001 | GB |
2428329 | Jan 2007 | GB |
2008005288 | Jan 2008 | JP |
20040005068 | Jan 2004 | KR |
20100037413 | Apr 2010 | KR |
WO-9613810 | May 1996 | WO |
WO-00059224 | Oct 2000 | WO |
WO-2007062223 | May 2007 | WO |
WO-2007138546 | Dec 2007 | WO |
WO-2008001350 | Jan 2008 | WO |
WO-2008052009 | May 2008 | WO |
WO-2008057444 | May 2008 | WO |
WO-2009137919 | Nov 2009 | WO |
Entry |
---|
An ffmpeg and SDL Tutorial, “Tutorial 05: Synching Video,” Retrieved from internet on Mar. 15, 2013: <http://dranger.com/ffmpeq/tutorial05.html>, 4 pages. |
Archos Gen 5 English User Manual Version 3.0, Jul. 26, 2007, pp. 1-81. |
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 for International Patent Application PCT/IL2010/000362 dated Aug. 25, 2010, 2 pages. |
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 and Writton Opinion for International Application PCT/IB2013/001000 dated Jul. 31, 2013, 12 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. |
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 EP10774637.2 (PCT/IL2010/000362) dated Jun. 20, 2012, 6 pages. |
Supplemental European Search Report for EP13184145 dated Jan. 30, 2014, 6 pages. |
Yang, H, et al., “Time Stamp Synchronization in Video Systems,” Teletronics Technology Corporation, <http://www.ttcdas.com/products/dausencoders/pdf/techpapers/tp2010timestampvideosystem.pdf>, Abstract, 8 pages. |
U.S. Appl. No. 15/356,913, Systems and Methods for Real-Time Pixel Switching, filed Nov. 21, 2016. |
U.S. Appl. No. 15/481,916, Systems and Methods for Creating Linear Video From Branched Video, filed Apr. 7, 2017. |
U.S. Appl. No. 15/085,209, Media Stream Rate Synchronization, filed Mar. 30, 2016. |
U.S. Appl. No. 15/165,373, Symbiotic Interactive Video, filed May 26, 2016. |
U.S. Appl. No. 15/189,931, Dynamic Summary Generation for Real-time Switchable Videos, filed Jun. 22, 2016. |
U.S. Appl. No. 15/395,477, Systems and Methods for Dynamic Weighting of Branched Video Paths, filed Dec. 30, 2016. |
Number | Date | Country | |
---|---|---|---|
20150293675 A1 | Oct 2015 | US |