The present invention relates generally to the field of media presentations and, in particular, to authoring, rendering, viewing, exporting, and sharing media presentations.
Current media presentation applications offer features for creating slides and manually customizing the ways in which a set of slides, i.e., a slideshow/media presentation, is played. Such applications also offer features for attaching themes to slideshows, where such themes may affect the appearance and general behavior of the slideshows when played. In addition, such applications further offer features such as customizing slide colors, customizing transition behavior, customizing transition delay, and manually adding clip art/image/audio/video files to one or more slides in a slideshow. These applications also permit basic sequential transition, forward or backward, and from one slide to another in a slideshow containing more than one slide. A user may customize the time that one slide should be viewed prior to the application invoking a transition to another slide, which may further have a custom viewing time associated with it as well. However, current media presentations applications do not provide a feature for authoring media presentations, comprising: defining a layer, wherein the layer comprises one or more effects; associating media content with the layer; aggregating the layer with one or more other layers; and assembling the aggregated layers. Moreover, current media presentation applications also do not provide a feature for dynamically profiling a slideshow soundtrack based on various criteria like beats per minute (BPM), rhythmic strength (RS), harmonic complexity (HC), and/or root mean square density (RMS or RMS strength). Such criteria, when profiled intelligently, may be further used to select appropriate effects and assemble such effects in useful ways applicable to a slideshow. Further, such effects could be customized according to durations, in/out points, and transitions in-sync with audio alone or the audio of a video. Finally, current media presentation applications do not provide features for automatic, as well as user-defined, authoring, rendering, exporting, and sharing media presentations/slideshows in an easily integrated modern platform.
Accordingly, the present invention is directed to a system and method for authoring, rendering, exporting, and sharing media presentations that substantially obviates one or more problems due to limitations and disadvantages of the related art.
An embodiment of the present invention provides a computer-implemented method for authoring media presentations, comprising: defining a layer, wherein the layer comprises one or more effects; associating media content with the layer; aggregating the layer with one or more other layers; and assembling the aggregated layers.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
To achieve these and other advantages and in accordance with the purpose of the present invention, as embodied and broadly described, a system comprises one or more processors; memory; one or more programs stored in memory, the one or more programs comprising instructions to: define a layer, wherein the layer comprises one or more effects; associate media content with the layer; aggregate the layer with one or more other layers; and assemble the aggregated layers.
In another aspect, a computer-readable storage medium stores one or more programs configured for execution by a computer, the one or more programs comprising instructions to: define a layer, wherein the layer comprises one or more effects; associate media content with the layer; aggregate the layer with one or more other layers; and assemble the aggregated layers.
In yet another aspect, a computer program product stores one or more instructions for execution by a computer, the one or more instructions comprising: creating a document; associating one or more layers to the document, wherein the layers are organized within the document; associating one or more effect containers with the layers, wherein the effect containers are linked and are organized within the layers; associating one or more effects with the effect containers; and assembling the effects, effect containers, and layers logically within the document.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide further explanation of the invention as claimed.
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of the specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention. In the drawings:
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous non-limiting specific details are set forth in order to assist in understanding the subject matter presented herein. It will be apparent, however, to one of ordinary skill in the art that various alternatives may be used without departing from the scope of the present invention and the subject matter may be practiced without these specific details. For example, it will be apparent to one of ordinary skill in the art that the subject matter presented herein can be implemented on any type of standalone system or client-server compatible system containing any type of client, network, server, and database elements.
In some embodiments, the exemplary embodiment of an application 1000, and its features/components, may be implemented by one or more modules/engines (
In some embodiments, the features/components of the application 1000 may be described as follows. The document 1001 (also,
In some embodiments, effect containers may be able to determine the order that images (or, alternatively, other media content) associated with a layer (e.g., steps 6002, 7002) are presented during a media presentation/slideshow. Such a determination may be based according to characteristics associated with the images (or, alternatively, other media content) (e.g., steps 6004, 7004). The characteristics may comprise a resolution, size, quality indicator, dots-per-inch, frames per second, window size, bit error rate (BER), compression type, or some other media content characteristic. The exemplary application 1000 may execute this process of assembling the layers (e.g., steps 6004, 7004) either manually or according to algorithms processing the characteristics and other layer-related data (described above). Further with respect to effect containers (e.g., a container or group of effects), multiple effects may be transitioned as one set into the next effect container. For example, effect containers are necessary in order for different text to be displayed on top of different effects. In some embodiments, from an implementation viewpoint, the effect containers permit the logical/physical grouping of different effects and link each of the effects to their respective different text, which is to be displayed on top of each respective effect. Each effect container may, for example, further contain a variable for storing a specific duration for determining how long each of the effects associated with an effect container (or, alternatively, “within” the effect container) are displayed/played.
In some embodiments, a keyframe 3015 (which may, for example, be one dimensional (1D) 3016, two dimensional (2D) 3017 or a vector (3018)), may be used by an animation path 3014 to guide or instruct the rate at which animation path 3014 should operate. Meaning, the higher the value of a keyframe 3015, the increased rate the animation path 3014 may operate (e.g., a faster pan-zoom effect or a faster layer rotation), and the lower the value of a keyframe 3015, the lower rate the animation path 3014 may operate at (e.g., a slower pan-zoom effect or a slower layer rotation). A 1D 3016 keyframe may be a keyframe that animates a property that has one value like, for example, a rotation angle. A 2D 3017 keyframe may be a keyframe that animates a property that has more than one value like, for example, a position (x-axis point, y-axis point) or a size (width/length, height). And, a vector 3018 keyframe may be a keyframe that animates a property that has more than two values like, for example, colors that manipulate the different values of their constituent color components (e.g., red, green, blue, alpha).
In some embodiments, filters 3019 operate as visual elements that are applied to a layer, effect container, effect, or slide. A filter 3019 may be, for example, a shadow, blurred image, or some other compatible visual element capable of being applied to a layer, effect container, effect, or slide (e.g., steps 6002, 7002).
In some embodiments, a playlist 3008 associated with a document 1001 may contain a list of songs (e.g., steps 6002, 7002). The playlist 3008 may organize songs such that they are played in a specific order, determined manually by a user of the exemplary application 1000, or automatically through the exemplary application 1000. An automatic playlist may be created according to song genre, file characteristics (e.g., type, size, date, etc.), or according to the feature for dynamically profiling a slideshow soundtrack based on various criteria like beats per minute (BPM), rhythmic strength (RS), harmonic complexity (HC), and/or root mean square density (RMS or RMS strength). The songs (e.g., a reference to a playlist) may be stored in digital format in local storage 4006 or on an auxiliary device/component 4005 that communicates with the system 4000 through a communications protocol or standard. The songs may be stored in a single file (or, other logical/physical data aggregator) or many files. In addition to songs, a playlist 3008 may contain other compatible media content like videos with audio content (which, for example, may be parsed from the video file into an individual song/audio file, or playlist). To associate a playlist, song/audio file, or any compatible media content with a document 1001, the user may select it/them from the select media content 1008 menu and drag the respective playlist, song/audio file, or other compatible media content, via the exemplary application 1000, into the effect containers region 1003 (see, for example, the reference to “Drag Audio Here” in the exemplary application 1000) (e.g., steps 6002, 7002). Songs may be played in the background while a document is being displayed/played, or they may, alternatively, be associated with foreground layers or effects that may be organized on top of another, thus, enabling the songs to be switched in coordination with the various switching (e.g., via gaps or transitions) from one layer or effect to another (e.g., steps 6004, 7004). Further, songs may, according to a default setting, start and stop playing based on the start and stop times that may be given from a media player or media management application. The user of the exemplary application 1000 may, however, define a custom start or stop time via a song (or, playlist) menu option of the application 1000.
In some embodiments, the core 3020 module may be considered the low-level data structure module and it may, for example, perform routines for representing how a slideshow/media presentation document is constructed, and contain the necessary information for accurately representing a slideshow/media presentation document according to features, many of which are described herein (e.g., steps 6001-6003, 7001-7003). Some of those features may include, for example, features related to timing (e.g., gaps 1013, transitions 1014), positioning (e.g., background layer 1004, foreground layer 1005, effects of effect containers 2004-2006, slides 2011, filters 3019, text 3010), sizing (e.g., keyframe 3015, animation path 3014, as well as their interaction), and files (e.g., songs 3008, playlists 3009).
In some embodiments, the producer 3021 may be considered the module for creating how a slideshow will look and feel (e.g., steps 6002-6003, 7002-7003), performing several analyses related to media content (e.g., images, audio, video of layers, effect containers, effects, and slides) (e.g., step 7016), and automatically assembling slideshows/media presentations according to data that may result from the analyses (e.g., steps 6004, 7004, 7011). The several analyses (e.g., step 7016) may include analysis of characteristics related to layers, effect containers, effects, and slides. Such characteristics may include, for example, layer type (e.g., background 1004, foreground 1005), layer number (e.g., position in relation to the background-most layer 1004), number of effect containers, length of gaps 1013 and transitions 1014, type of transitions 1014, type of effects, number of effects, number of slides, type of slides, document length 1004, user preferences (e.g., for ordering layers, effect containers, effects, slides), audio analyses, video analyses, or other similar characteristics. After performing the several analyses using, for example, the producer 3021, the resulting data from the several analyses may be processed by the producer 3021, the core 3020, the renderer 3022, the exporter 3023, or other module (e.g., step 7017). The producer 3021 may, for example, interface with and utilize the application programming interfaces (API) of frameworks like, for example, browsers or QuickTime® to gather such information as thumbnail data and resolutions for images, as well as audio or video durations or other characteristics. The gathered information may then be processed by the producer 3021 in accordance with one or more general/specific algorithms (or, other analytical methods) and then used by the producer 3021 (or, other module with which the producer 3021 may call), for example, to automatically assemble a slideshow or media presentation document (e.g., 7011). The producer 3021 may further, for example, assemble a document via core 3020 for play/display using the features of renderer 3022, by accessing photos and coupling such photos with a style (e.g., 1015). In addition, the producer 3021 may also, for example, perform audio analysis functions on songs 3009 or a set of songs (playlist 3008) using such analysis like, for example, beat detection/mapping. The producer 3021 may also keep track of available styles (e.g., 1015), effects 3004, transitions 3012, and frames 3006.
In some embodiments, the renderer 3022 may be considered the play/display module. The renderer 3022 may receive slideshow/media presentation data from, for example, the core 3020 and producer 3021 and may render such data such that it may be sent to a graphics card or other display device (or interface) (e.g., 4003). The renderer 3022 may interface with QuickTime® media player (e.g., the framework of QuickTime® media player) or another compatible application (or, framework) for audio/video decoding. In addition, the renderer 3022 may also interface with a composer-type application for actual rendering (e.g., of the slides), and the same or another similar application for applying filters 3006.
In some embodiments, the exporter 3023 may be considered the sharing module. The exporter 3023 may, for example, use renderer 3022 to export the slideshow/media presentation document to different formats (e.g., file formats) like those supported by QuickTime® or other similar applications. The exporter 3023 may, for example, obtain movie frame-type data from renderer 3022 and add it to a movie-type file. When the exporter 3023 is finished retrieving data for each movie, the slideshow/media presentation document would be available for access and sharing through the exemplary application 1000 or other applications that may access or handle the document in its final format.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.
This application claims the benefit and priority of the U.S. Provisional Patent Application No. 61/193,851 filed on Dec. 30, 2008, which is hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
5521841 | Arman et al. | May 1996 | A |
5752029 | Wissner | May 1998 | A |
5758093 | Boezeman et al. | May 1998 | A |
5760767 | Shore et al. | Jun 1998 | A |
5841438 | Cave | Nov 1998 | A |
5852435 | Vigneaux et al. | Dec 1998 | A |
6031529 | Migos et al. | Feb 2000 | A |
6067126 | Alexander | May 2000 | A |
6204840 | Petelycky et al. | Mar 2001 | B1 |
6320598 | Davis et al. | Nov 2001 | B2 |
6332147 | Moran et al. | Dec 2001 | B1 |
6369835 | Lin | Apr 2002 | B1 |
6463444 | Jain et al. | Oct 2002 | B1 |
6580438 | Ichimura et al. | Jun 2003 | B1 |
RE38401 | Goldberg et al. | Jan 2004 | E |
6744974 | Neuman | Jun 2004 | B2 |
RE38609 | Chen et al. | Oct 2004 | E |
6807361 | Girgensohn et al. | Oct 2004 | B1 |
6928613 | Ishii et al. | Aug 2005 | B1 |
7030872 | Tazaki | Apr 2006 | B2 |
7082572 | Pea et al. | Jul 2006 | B2 |
7085995 | Fukuda et al. | Aug 2006 | B2 |
7143362 | Dieberger et al. | Nov 2006 | B2 |
7149974 | Girgensohn et al. | Dec 2006 | B2 |
7213051 | Zhu et al. | May 2007 | B2 |
7352952 | Herberger et al. | Apr 2008 | B2 |
7469054 | Aratani et al. | Dec 2008 | B2 |
7512886 | Herberger et al. | Mar 2009 | B1 |
7528315 | Goodwin et al. | May 2009 | B2 |
7669132 | Widdowson | Feb 2010 | B2 |
7890867 | Margulis | Feb 2011 | B1 |
7979801 | Krishnaswamy et al. | Jul 2011 | B2 |
8621357 | Weber et al. | Dec 2013 | B2 |
8626322 | Weber et al. | Jan 2014 | B2 |
20020143961 | Siegel et al. | Oct 2002 | A1 |
20020154140 | Tazaki | Oct 2002 | A1 |
20020154158 | Fukuda et al. | Oct 2002 | A1 |
20030090506 | Moore et al. | May 2003 | A1 |
20030091204 | Gibson | May 2003 | A1 |
20030184598 | Graham | Oct 2003 | A1 |
20030189588 | Girgensohn et al. | Oct 2003 | A1 |
20040027369 | Kellock et al. | Feb 2004 | A1 |
20040255307 | Irudayaraj | Dec 2004 | A1 |
20050084232 | Herberger et al. | Apr 2005 | A1 |
20050275805 | Lin et al. | Dec 2005 | A1 |
20060075348 | Xu et al. | Apr 2006 | A1 |
20060152678 | Hung et al. | Jul 2006 | A1 |
20070006073 | Gerhard et al. | Jan 2007 | A1 |
20070146388 | Langmacher et al. | Jun 2007 | A1 |
20070163427 | Rigopulos et al. | Jul 2007 | A1 |
20070180979 | Rosenberg et al. | Aug 2007 | A1 |
20080077710 | Kouvelas et al. | Mar 2008 | A1 |
20080079690 | Foxenland et al. | Apr 2008 | A1 |
20080098032 | Wu et al. | Apr 2008 | A1 |
20080162228 | Mechbach et al. | Jul 2008 | A1 |
20080183751 | Cazier et al. | Jul 2008 | A1 |
20080215979 | Clifton et al. | Sep 2008 | A1 |
20090187826 | Heimbold et al. | Jul 2009 | A1 |
20100085379 | Hishikawa et al. | Apr 2010 | A1 |
20100168881 | Weber et al. | Jul 2010 | A1 |
20100169777 | Weber et al. | Jul 2010 | A1 |
20100169784 | Weber et al. | Jul 2010 | A1 |
Entry |
---|
“U.S. Appl. No. 12/497,462 , Response filed May 9, 2013 to Non Final Office Action mailed Feb. 15, 2013”, 11 pgs. |
“U.S. Appl. No. 12/497,462, Final Office Action mailed Jun. 12, 2012”, 10 pgs. |
“U.S. Appl. No. 12/497,462, Non Final Office Action mailed Feb. 15, 2013”, 10 pgs. |
“U.S. Appl. No. 12/497,462, Non Final Office Action mailed Dec. 28, 2011”, 10 pgs. |
“U.S. Appl. No. 12/497,462, Response filed Mar. 22, 2012 to Non Final Office Action mailed Dec. 28, 2011”, 11 pgs. |
“U.S. Appl. No. 12/497,462, Response filed Nov. 13, 2012 to Final Office Action mailed Jun. 12, 2012”, 8 pgs. |
“U.S. Appl. No. 12/497,534, Examiner Interview Summary mailed Apr. 23, 2013”, 3 pgs. |
“U.S. Appl. No. 12/497,534, Final Office Action mailed Feb. 5, 2013”, 17 pgs. |
“U.S. Appl. No. 12/497,534, Non Final Office Action mailed Jul. 20, 2012”, 12 pgs. |
“U.S. Appl. No. 12/497,534, Response filed May 3, 2013 to Final Office Action mailed Feb. 5, 2013”, 11 pgs. |
“U.S. Appl. No. 12/497,534, Response filed Nov. 20, 2012 to Non-Final Office Action mailed Jul. 20, 2012”, 11 pgs. |
“U.S. Appl. No. 12/499,794, Non Final Office Action mailed Oct. 25, 2012”, 12 pgs. |
“U.S. Appl. No. 12/499,794, Response filed Mar. 22, 2013”, 9 pgs. |
“U.S. Appl. No. 12/497,462, Notice of Allowance mailed Aug. 23, 2013”, 12 pgs. |
“U.S. Appl. No. 12/497,534, Corrected Notice of Allowability mailed Nov. 22, 2013”, 4 pgs. |
“U.S. Appl. No. 12/497,534, Corrected Notice of Allowance mailed Nov. 8, 2013”, 4 pgs. |
“U.S. Appl. No. 12/497,534, Notice of Allowance mailed Sep. 5, 2013”, 6 pgs. |
“U.S. Appl. No. 12/499,794, Examiner Interview Summary mailed Jan. 12, 2014”, 3 pgs. |
“U.S. Appl. No. 12/499,794, Final Office Action mailed Jul. 18, 2013”, 8 pgs. |
Number | Date | Country | |
---|---|---|---|
20100169783 A1 | Jul 2010 | US |
Number | Date | Country | |
---|---|---|---|
61193851 | Dec 2008 | US |