US20100169753A1 - Media portability and compatibility for different destination platforms - Google Patents
Media portability and compatibility for different destination platforms Download PDFInfo
- Publication number
- US20100169753A1 US20100169753A1 US12/346,844 US34684408A US2010169753A1 US 20100169753 A1 US20100169753 A1 US 20100169753A1 US 34684408 A US34684408 A US 34684408A US 2010169753 A1 US2010169753 A1 US 2010169753A1
- Authority
- US
- United States
- Prior art keywords
- media
- source media
- instructions
- document
- portability
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B27/00—Editing; Indexing; Addressing; Timing or synchronising; Monitoring; Measuring tape travel
- G11B27/10—Indexing; Addressing; Timing or synchronising; Measuring tape travel
- G11B27/102—Programmed access in sequence to addressed parts of tracks of operating record carriers
- G11B27/105—Programmed access in sequence to addressed parts of tracks of operating record carriers of operating discs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
- G06F15/161—Computing infrastructure, e.g. computer clusters, blade chassis or hardware partitioning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/40—Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
- G06F16/44—Browsing; Visualisation therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/30—Arrangements for executing machine instructions, e.g. instruction decode
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B27/00—Editing; Indexing; Addressing; Timing or synchronising; Monitoring; Measuring tape travel
- G11B27/02—Editing, e.g. varying the order of information signals recorded on, or reproduced from, record carriers
- G11B27/031—Electronic editing of digitised analogue information signals, e.g. audio or video signals
- G11B27/034—Electronic editing of digitised analogue information signals, e.g. audio or video signals on discs
Definitions
- Playing a given media file on a computer system typically involves having appropriate technical infrastructure installed on that computer system.
- this technical infrastructure may include a codec to decode and render the file on that computer system.
- Managing this technical infrastructure can be difficult and unwieldy, particularly for technically unsophisticated users.
- particular codecs may be difficult to locate, install, and manage. Without the appropriate technical infrastructure, the media will not play on the given computer system.
- Another concern is that in corporate or enterprise environments, administrators may lock down individual computer systems, preventing users from loading additional technical infrastructure onto the systems. Therefore, these users may be unable to load the appropriate codec, even if they can locate it.
- Tools and techniques for media portability and compatibility for different destination platforms are provided. These tools may receive commands to launch a media portability capability, and may receive source media as input for transformation. These tools may also receive indications of profile settings for specifying how to transform the source media for enhanced portability on destination systems for playback. The source media may be transformed in response to the profile setting, with the transformed media inserted into a document. The tools may then distribute the document to the destination system for playback
- FIG. 1 is a combined block and flow diagram illustrating systems or operating environments suitable for implementing media portability and compatibility for different destination platforms.
- FIG. 2 is a combined block and flow diagram illustrating components and data flows provided by media portability tools.
- FIG. 3 is a diagram illustrating examples of different factors that may be considered when establishing profiles in connection with providing media portability and compatibility for different destination platforms.
- FIG. 4 is a flow diagram illustrating process flows related to media portability and compatibility for different destination platforms.
- program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
- program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
- program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
- subject matter described herein may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like.
- FIG. 1 illustrates systems or operating environments, denoted generally at 100 , suitable for implementing media portability and compatibility for different destination platforms.
- any number of users 102 may interact with corresponding user devices 104 , the user devices 104 , configured as described herein, may enable the users 102 to create or edit documents that contain multimedia for distribution to any number of different devices 106 a and 106 n (collectively, devices 106 ).
- this description may refer to the user devices 104 as originating devices or origin devices, and may refer to the devices 106 as destination devices or platforms.
- FIG. 1 denotes at 108 interactions between the users 102 and the originating devices 106 a and 106 n.
- these interactions 108 may represent commands issued by the users to the originating devices 104 , responses to these commands, and the like, in connection with providing media portability and compatibility for different destination platforms as described herein.
- these user devices 104 as shown in FIG. 1 may represent any number of such devices.
- the graphical representations of the user devices 104 as presented in FIG. 1 are chosen only for convenience of illustration, but not to limit possible implementations. More specifically, the user devices 104 may include, but are not limited to: relatively stationary desktop computing systems; laptop notebook, or other relatively mobile computing systems; wireless communications devices, such as cellular phones, smartphones, wireless-enabled personal digital assistants (PDAs), or other similar communications devices.
- PDAs personal digital assistants
- these devices may include one or more processors 110 , which may have a particular type or architecture, chosen as appropriate for particular implementations.
- the processor 110 may couple to one or more bus systems 112 , having type and/or architecture that is chosen for compatibility with the processor 110 .
- the user devices 104 may also include one or more instances of computer-readable storage medium or media 114 , which couple to the bus systems 112 .
- the bus systems 112 may enable the processors 110 to read code and/or data to/from the computer-readable storage media 114 .
- the media 114 may represent apparatus in the form of storage elements that are implemented using any suitable technology, including but not limited to semiconductors, magnetic materials, optics, or the like.
- the media 114 may include memory components, whether classified as RAM, ROM, flash, or other types, and may also represent hard disk drives.
- the storage media 114 may include one or more modules of instructions that, when loaded into the processor 110 and executed, cause the user devices 104 to perform various techniques related to media portability and compatibility for different destination platforms. As detailed throughout this description, these modules of instructions may also provide various tools or techniques by which the user devices 104 may provide for media portability and compatibility for different destination platforms, using the components, flows, and data structures discussed in more detail throughout this description.
- the storage media 114 may include one or more software modules that implement media portability tools 116 .
- the portability tools 116 may receive source media 118 as input.
- Examples of the source media 118 may include video, audio, or combinations of the foregoing, referred to collectively as multimedia.
- the originating devices 104 include any players or editors appropriate for displaying and/or editing the source media 118 .
- the originating devices 104 may include any specialized tools for rendering or manipulating the source media (e.g., media coder-decoder utilities or codecs, or the like).
- the destination devices 106 may or may not include the same media players or editors as does the originating device 104 .
- the destination devices 106 may or may not include the codecs appropriate for rendering the source media 118 . In cases where the source media is to be distributed to numerous different destination devices 106 , achieving media compatibility across all these destination devices 106 may be a challenge.
- the media portability tools 116 may transform or convert the source media 118 into instances of portable media more compatible with the destination devices 106 .
- FIG. 1 denotes examples of this portable media at 120 a and 120 n (collectively, portable media 120 ), as associated respectively with the destination devices 106 a and 106 n .
- the media portability tools 116 may transform the source media 118 into the portable media 120 a and 120 n , as appropriate to make the media more suitable for presentation on the destination devices 106 a and 106 n , taking into account the particular configurations of the particular destination devices 106 a and 106 n .
- the media portability tools 116 may operate based on expected configurations of the destination devices 106 . In other cases, the media portability tools 116 may have some degree of visibility into the actual configurations of the destination devices 106 .
- the originating devices 104 may communicate with the destination devices 106 over one or more intermediate communications networks 122 .
- these networks 122 may represent any number of communications networks.
- the networks 122 may represent local area networks (LANs), wide area networks (WANs), and/or personal area networks (e.g., Bluetooth-type networks), any of which may operate alone or in combination to facilitate operation of the tools and techniques provided in this description.
- the networks 122 as shown in FIG. 1 also represents any hardware (e.g., adapters, interfaces, cables, and the like), software, or firmware associated with implementing these networks, and may also represent any protocols by which these networks may operate.
- FIG. 2 illustrates components and data flows, denoted generally at 200 , provided by the media portability tools 116 shown in FIG. 1 .
- FIG. 2 carries forward example source media at 118 and carries forward example portable media at 120 , both of which were described above in FIG. 1 .
- the media portability tools 116 may include user control elements 202 .
- these user control elements unable the media portability tools 116 to gather or obtain any input parameters that control transformation of the source media 118 into portable media 120 .
- some implementations of the user control elements 202 may include an interactive user interface (UI), represented generally at 204 .
- UI interactive user interface
- the media portability tools 116 may obtain input from the user 102 regarding particular goals and/or objectives relevant to a particular transformation process.
- FIG. 2 denotes these goals/objectives at 206 .
- the user control elements 202 may include a programmatic object model, represented generally at 208 .
- the programmatic object model 208 may automatically or programmatically determine the goals/objectives 206 , based on data representing actual or expected configurations of the destination devices 106 .
- the media portability tools 116 may define a collection of transformation profiles, denoted generally at 210 . To elaborate further on the transformation profiles 210 , the discussion turns to FIG. 3 , before returning to complete the description of FIG. 2 .
- FIG. 3 illustrates examples of different factors, denoted generally at 300 , that may be considered when establishing transformation profiles 210 in connection with providing media portability and compatibility for different destination platforms.
- FIG. 3 carries forward from FIG. 2 examples of the goals/objectives 206 and the collection of profiles 210 .
- the collection of profiles 210 may include a plurality of different profile settings, with FIG. 3 illustrating two examples at 302 a and 302 m (collectively, profile settings 302 ). These profile settings 302 may represent trade-offs between any number of different factors of interest or priority in different particular transformations of the source media 118 .
- FIG. 3 provides examples in which different factors or criteria are presented along respective axes 304 , 306 , 308 , and 310 . This discussion provides these examples axes and related factors or criteria only to facilitate this discussion. However, implementations of this description may incorporate other factors or criteria without departing from the scope and spirit of this description.
- the axis 304 represents disk resources involved in storing a given instance of portable media 120 .
- the axis 304 may represent relatively large files containing the portable media 120
- the axis 304 may represent relatively small files. Points between these two extremes may represent files of any convenient intermediate sizes.
- the axis 306 represents different types of destination platforms for characterizing the destination devices 106 .
- some destination devices 106 may be PC-based computing platforms that run WINDOWS®-brand operating systems. Particular types of media players and/or codecs may be expected to provide better performance within such computing platforms.
- Other destination devices 106 may be APPLE®-based computing platforms that run different operating systems. Other types of media players and/or codecs may be expected to provide better performance within these latter computing platforms. Accordingly, any number of different computing platforms may be visualized along the axis 306 .
- the axis 308 represents a rendering quality desired when presenting the portable media 120 on the different destination devices 106 .
- some destination devices 106 may have physical or operational characteristics that support only a certain level of rendering quality. Accordingly, it may be possible to reduce the file size of the portable media 120 sent to such destination devices 106 .
- other destination devices 106 may be configured to benefit from “full-size” or “high quality” portable media 120 .
- any number of different degrees of rendering quality may be visualized along the axis 308 .
- the axis 310 represents time and/or computational complexity involved with decoding the portable media 120 on the various destination devices 106 .
- different codecs may involve different degrees of computational complexity while encoding and/or decoding media using those codecs.
- certain destination devices 106 may not possess sufficient computing capability to decode portable media 120 encoded with computationally-intensive codecs.
- the media portability tools 116 may choose particular codecs depending upon the computing power possessed by different destination devices 106 .
- the axis 310 any number of different codecs or other encoding schemes having different levels of complexity may be visualized along the axis 310 .
- the different factors or criteria shown along the axes 306 - 310 may be relatively independent from one another in some cases. In other cases, however, different factors may be balanced or traded off against one another.
- one criteria of interest in performing some transformations is the file size of the portable media 120 after the transformation is complete.
- Certain types of media e.g., video
- transmitting large video files may consume significant amounts of network bandwidth.
- particular destination devices 106 may provide a reasonable video playback experience, even if the file size of the source media 118 is reduced to some degree in producing the portable media 120 .
- This reduced file size may provide additional benefits, in that the portable media may consume less storage when loaded into the destination devices 106 , as well as consuming less bandwidth when transmitted over the networks 122 .
- smaller file sizes may be traded off against reduced rendering quality however, implementations of this description may address any number of different scenarios in which certain factors are traded off against other factors.
- FIG. 3 illustrates two profile settings 302 a and 302 m only for convenience of illustration and description. However, any number of profile settings 302 are possible in different implementations. In general, the profile settings 302 represent technical settings that realize the goals or objectives 206 specified for a particular media transformation, considering the various illustrative factors shown in FIG. 3 .
- the media portability tools 116 may include a portability engine 212 , which receives the input source media 118 , and transforms the source media 118 according to the profile settings 302 .
- the portability engine 212 may receive an indication, denoted generally at 214 , of a particular target platform for which the source media 118 is being transformed.
- This indication of target platform 214 may represent any of the destination devices 106 , at any level of appropriate detail.
- the target platform 214 may represent the destination devices 106 relatively generically (e.g., a WINDOWS® system or a Mac® system), or may represent the destination devices 106 more specifically.
- the destination device 106 a may be represented as a system having a relatively powerful processor, video card, memory, or other configuration elements, while the destination device 106 n may be represented as a system having a more moderately powered processor, video card, etc.
- the indication of target platform 214 may represent expected or actual configurations for the destination devices 106 .
- the portability engine 212 may be a stand-alone component. However, in other scenarios, such as those shown in FIG. 2 , the portability engine 212 may be integrated into another application, represented generally at 216 .
- This application 216 may be configured to allow users 102 to invoke the capability provided by the portability engine 212 from within the application 216 . Examples of the application 216 may include, but are not limited to, presentation software, word processing software, database or spreadsheet software, and the like. In general, the application 216 may represent any application software into which media may be included or embedded.
- the portability engine 212 may produce different outputs in different implementation scenarios. For example, FIG. 2 carries forward the portable media 120 as an illustrative output of the portability engine 212 . In addition, however, the portability engine 212 may generate and output an alpha mask, denoted generally at 218 .
- the alpha mask 218 may enable application of several types of post-transformation effects, without re-computing the transformation of the source media 118 to the portable media 120 . Illustrative but non-limiting examples of these effects may include providing three-dimensional ( 3 -D) visual effects, introducing glow or highlight, changing colors, adjusting transparency, and the like.
- the application 216 may generate an output document 220 .
- This output document 220 may include one or more instances of embedded portable media, as represented at 222 .
- the output document 220 may also include one or more instances of alpha masks 224 , which may be associated with corresponding embedded portable media 222 .
- the portable media 120 may be an intermediate result that may or may not be the final viewable result that is presented on the destination devices 106 .
- the destination devices 106 may apply the alpha mask to the intermediate result to generate the final result.
- the alpha masks 218 may provide greater flexibility on the destination machine, by providing for a variety of different visual effects starting from the same media transformation.
- the portability engine 212 may transform the source media 118 into portable media 120 that has a certain transparency level.
- the portability engine may define a related alpha mask 218 that has another transparency level.
- the portability engine 212 may embed both the portable media 222 and the alpha mask 224 into an output document 220 , which is then sent to any number of destination devices 106 .
- the destination device 106 may combine the embedded portable media 222 with the embedded alpha mask 224 , to achieve yet another transparency level resulting from this combination.
- different alpha masks 224 have a different transparencies may provide for different combined transparencies. This example illustrates one scenario out of many facilitated by alpha mask 218 .
- FIG. 4 illustrates process flows, denoted generally at 400 , related to media portability and compatibility for different destination platforms.
- the process flows 400 are described in connection with the portability engine 212 described above in FIG. 2 .
- implementations of this description may perform at least portions of the process flows 400 with other components, without departing from the scope and spirit of this description.
- block 402 represents receiving a command to launch an application (e.g., 216 in FIG. 2 ) that integrates the capabilities provided by the media portability tools 116 .
- the portability engine 212 may be a stand-alone component, or may also be integrated into an application. Stand-alone implementations of the portability engine 212 may omit block 402 .
- Block 404 represents receiving a command to launch the portability features as provided in this description.
- block 404 may include receiving a command issued within that application to launch the portability features.
- block 404 may include receiving a command issued directly to that stand-alone component.
- Block 406 represents receiving one or more instances of source media for transformation.
- FIG. 1 provides examples of source media at 118 .
- the source media 118 is typically compatible with the originating device 104 , but may or may not have optimum compatibility with the destination devices 106 .
- Block 408 represents receiving an indication of a suitable profile for transforming the source media received in block 406 .
- FIG. 3 described above provides various examples of profile settings 302 that implement the goals or objectives 206 relevant to transforming a given instance of source media. Accordingly, block 408 may include any number of different factors or criteria relevant to such a transformation, including but not limited to any of the factors represented on the axes 304 - 310 shown in FIG. 3 .
- Block 410 represents transforming the source media into portable media per the profile setting established in block 408 .
- Block 410 may generate as output the portable media 120 as shown in FIG. 1 .
- block 412 represents inserting or embedding the transformed media into an output file or document.
- FIG. 2 illustrates an example output document at 220 , which contains the embedded portable media 222 .
- block 412 may include embedding the transformed media into an output document as generated by that application 216 .
- block 412 may include generating an output file that includes only the transformed media.
- Block 414 represents defining an alpha mask associated with the transformed source media.
- FIG. 2 provides examples of alpha mask at 218 , as output from the portability engine 212 .
- Block 416 represents inserting or embedding the alpha mask into output file.
- FIG. 2 also provides examples of an alpha mask 224 , as embedded into an output document 220 .
- Block 418 represents distributing the output file as generated by block 412 and/or 416 .
- alpha masks 218 may or may not be associated with every instance of portable media 120 .
- block 418 may include distributing instances of portable media 120 to any number of destination devices 106 .
Abstract
Description
- Playing a given media file on a computer system typically involves having appropriate technical infrastructure installed on that computer system. For example, this technical infrastructure may include a codec to decode and render the file on that computer system. Managing this technical infrastructure can be difficult and unwieldy, particularly for technically unsophisticated users. Sometimes, particular codecs may be difficult to locate, install, and manage. Without the appropriate technical infrastructure, the media will not play on the given computer system. Another concern is that in corporate or enterprise environments, administrators may lock down individual computer systems, preventing users from loading additional technical infrastructure onto the systems. Therefore, these users may be unable to load the appropriate codec, even if they can locate it.
- Tools and techniques for media portability and compatibility for different destination platforms are provided. These tools may receive commands to launch a media portability capability, and may receive source media as input for transformation. These tools may also receive indications of profile settings for specifying how to transform the source media for enhanced portability on destination systems for playback. The source media may be transformed in response to the profile setting, with the transformed media inserted into a document. The tools may then distribute the document to the destination system for playback
- It should be appreciated that the above-described subject matter may be implemented as a computer-controlled apparatus, a computer process, a computing system, or as an article of manufacture such as a computer-readable medium. These and various other features will be apparent from a reading of the following Detailed Description and a review of the associated drawings.
- This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended that this Summary be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to implementations that solve any or all disadvantages noted in any part of this disclosure.
-
FIG. 1 is a combined block and flow diagram illustrating systems or operating environments suitable for implementing media portability and compatibility for different destination platforms. -
FIG. 2 is a combined block and flow diagram illustrating components and data flows provided by media portability tools. -
FIG. 3 is a diagram illustrating examples of different factors that may be considered when establishing profiles in connection with providing media portability and compatibility for different destination platforms. -
FIG. 4 is a flow diagram illustrating process flows related to media portability and compatibility for different destination platforms. - The following detailed description provides tools and techniques for media portability and compatibility for different destination platforms. While the subject matter described herein presents a general context of program modules that execute in conjunction with the execution of an operating system and application programs on a computer system, those skilled in the art will recognize that other implementations may be performed in combination with other types of program modules. Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the subject matter described herein may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like.
- The following detailed description refers to the accompanying drawings that form a part hereof, and that show, by way of illustration, specific example implementations. Referring now to the drawings, in which like numerals represent like elements through the several figures, this description provides various tools and techniques for asynchronous database updates between collaborative applications and search utilities.
-
FIG. 1 illustrates systems or operating environments, denoted generally at 100, suitable for implementing media portability and compatibility for different destination platforms. Turning toFIG. 1 in more detail, any number of users 102 may interact withcorresponding user devices 104, theuser devices 104, configured as described herein, may enable the users 102 to create or edit documents that contain multimedia for distribution to any number of different devices 106a and 106n (collectively, devices 106). Accordingly, without limiting possible implementations, this description may refer to theuser devices 104 as originating devices or origin devices, and may refer to thedevices 106 as destination devices or platforms. -
FIG. 1 denotes at 108 interactions between the users 102 and the originating devices 106a and 106n. In general, these interactions 108 may represent commands issued by the users to the originatingdevices 104, responses to these commands, and the like, in connection with providing media portability and compatibility for different destination platforms as described herein. - Turning to the
user devices 104 in more detail, theseuser devices 104 as shown inFIG. 1 may represent any number of such devices. In addition, the graphical representations of theuser devices 104 as presented inFIG. 1 are chosen only for convenience of illustration, but not to limit possible implementations. More specifically, theuser devices 104 may include, but are not limited to: relatively stationary desktop computing systems; laptop notebook, or other relatively mobile computing systems; wireless communications devices, such as cellular phones, smartphones, wireless-enabled personal digital assistants (PDAs), or other similar communications devices. - Turning to the
user devices 104 in more detail, these devices may include one ormore processors 110, which may have a particular type or architecture, chosen as appropriate for particular implementations. Theprocessor 110 may couple to one ormore bus systems 112, having type and/or architecture that is chosen for compatibility with theprocessor 110. - The
user devices 104 may also include one or more instances of computer-readable storage medium ormedia 114, which couple to thebus systems 112. Thebus systems 112 may enable theprocessors 110 to read code and/or data to/from the computer-readable storage media 114. Themedia 114 may represent apparatus in the form of storage elements that are implemented using any suitable technology, including but not limited to semiconductors, magnetic materials, optics, or the like. Themedia 114 may include memory components, whether classified as RAM, ROM, flash, or other types, and may also represent hard disk drives. - The
storage media 114 may include one or more modules of instructions that, when loaded into theprocessor 110 and executed, cause theuser devices 104 to perform various techniques related to media portability and compatibility for different destination platforms. As detailed throughout this description, these modules of instructions may also provide various tools or techniques by which theuser devices 104 may provide for media portability and compatibility for different destination platforms, using the components, flows, and data structures discussed in more detail throughout this description. For example, thestorage media 114 may include one or more software modules that implementmedia portability tools 116. - Turning to the
media portability tools 116 in more detail, in overview, theportability tools 116 may receivesource media 118 as input. Examples of thesource media 118 may include video, audio, or combinations of the foregoing, referred to collectively as multimedia. Typically, the originatingdevices 104 include any players or editors appropriate for displaying and/or editing thesource media 118. In addition, theoriginating devices 104 may include any specialized tools for rendering or manipulating the source media (e.g., media coder-decoder utilities or codecs, or the like). However, thedestination devices 106 may or may not include the same media players or editors as does theoriginating device 104. In addition, thedestination devices 106 may or may not include the codecs appropriate for rendering thesource media 118. In cases where the source media is to be distributed to numerousdifferent destination devices 106, achieving media compatibility across all thesedestination devices 106 may be a challenge. - To address these compatibility issues, the
media portability tools 116 may transform or convert thesource media 118 into instances of portable media more compatible with thedestination devices 106.FIG. 1 denotes examples of this portable media at 120 a and 120 n (collectively, portable media 120), as associated respectively with the destination devices 106 a and 106 n. More specifically, themedia portability tools 116 may transform thesource media 118 into the portable media 120 a and 120 n, as appropriate to make the media more suitable for presentation on the destination devices 106 a and 106 n, taking into account the particular configurations of the particular destination devices 106 a and 106 n. In some cases, themedia portability tools 116 may operate based on expected configurations of thedestination devices 106. In other cases, themedia portability tools 116 may have some degree of visibility into the actual configurations of thedestination devices 106. - In some implementations, but not necessarily all, the
originating devices 104 may communicate with thedestination devices 106 over one or moreintermediate communications networks 122. Turning to thenetworks 122 in more detail, thesenetworks 122 may represent any number of communications networks. For example, thenetworks 122 may represent local area networks (LANs), wide area networks (WANs), and/or personal area networks (e.g., Bluetooth-type networks), any of which may operate alone or in combination to facilitate operation of the tools and techniques provided in this description. Thenetworks 122 as shown inFIG. 1 also represents any hardware (e.g., adapters, interfaces, cables, and the like), software, or firmware associated with implementing these networks, and may also represent any protocols by which these networks may operate. -
FIG. 2 illustrates components and data flows, denoted generally at 200, provided by themedia portability tools 116 shown inFIG. 1 . For ease of reference, but not to limit possible implementations,FIG. 2 carries forward example source media at 118 and carries forward example portable media at 120, both of which were described above inFIG. 1 . - Turning to
FIG. 2 in more detail, themedia portability tools 116 may includeuser control elements 202. In general, these user control elements unable themedia portability tools 116 to gather or obtain any input parameters that control transformation of thesource media 118 intoportable media 120. As shown inFIG. 2 , some implementations of theuser control elements 202 may include an interactive user interface (UI), represented generally at 204. Through thisuser interface 204, themedia portability tools 116 may obtain input from the user 102 regarding particular goals and/or objectives relevant to a particular transformation process.FIG. 2 denotes these goals/objectives at 206. - In other implementations, the
user control elements 202 may include a programmatic object model, represented generally at 208. Theprogrammatic object model 208 may automatically or programmatically determine the goals/objectives 206, based on data representing actual or expected configurations of thedestination devices 106. - The
media portability tools 116 may define a collection of transformation profiles, denoted generally at 210. To elaborate further on the transformation profiles 210, the discussion turns toFIG. 3 , before returning to complete the description ofFIG. 2 . -
FIG. 3 illustrates examples of different factors, denoted generally at 300, that may be considered when establishingtransformation profiles 210 in connection with providing media portability and compatibility for different destination platforms. For ease of reference, but not to limit possible implementations,FIG. 3 carries forward fromFIG. 2 examples of the goals/objectives 206 and the collection ofprofiles 210. - Turning to
FIG. 3 in more detail, the collection ofprofiles 210 may include a plurality of different profile settings, withFIG. 3 illustrating two examples at 302a and 302m (collectively, profile settings 302). Theseprofile settings 302 may represent trade-offs between any number of different factors of interest or priority in different particular transformations of thesource media 118. -
FIG. 3 provides examples in which different factors or criteria are presented alongrespective axes - In the visual representation of these axes as shown in
FIG. 3 , theaxis 304 represents disk resources involved in storing a given instance ofportable media 120. For example, at one extreme, theaxis 304 may represent relatively large files containing theportable media 120, and at another extreme, theaxis 304 may represent relatively small files. Points between these two extremes may represent files of any convenient intermediate sizes. - The
axis 306 represents different types of destination platforms for characterizing thedestination devices 106. For example, somedestination devices 106 may be PC-based computing platforms that run WINDOWS®-brand operating systems. Particular types of media players and/or codecs may be expected to provide better performance within such computing platforms.Other destination devices 106 may be APPLE®-based computing platforms that run different operating systems. Other types of media players and/or codecs may be expected to provide better performance within these latter computing platforms. Accordingly, any number of different computing platforms may be visualized along theaxis 306. - The
axis 308 represents a rendering quality desired when presenting theportable media 120 on thedifferent destination devices 106. For example, somedestination devices 106 may have physical or operational characteristics that support only a certain level of rendering quality. Accordingly, it may be possible to reduce the file size of theportable media 120 sent tosuch destination devices 106. On the other hand,other destination devices 106 may be configured to benefit from “full-size” or “high quality”portable media 120. In general, any number of different degrees of rendering quality may be visualized along theaxis 308. - The axis 310 represents time and/or computational complexity involved with decoding the
portable media 120 on thevarious destination devices 106. For example, different codecs may involve different degrees of computational complexity while encoding and/or decoding media using those codecs. In some cases,certain destination devices 106 may not possess sufficient computing capability to decodeportable media 120 encoded with computationally-intensive codecs. Accordingly, themedia portability tools 116 may choose particular codecs depending upon the computing power possessed bydifferent destination devices 106. Accordingly, the axis 310 any number of different codecs or other encoding schemes having different levels of complexity may be visualized along the axis 310. - The different factors or criteria shown along the axes 306-310 may be relatively independent from one another in some cases. In other cases, however, different factors may be balanced or traded off against one another. For example, one criteria of interest in performing some transformations is the file size of the
portable media 120 after the transformation is complete. Certain types of media (e.g., video) consume relatively large amounts of storage. In cases where the originatingdevices 104 communicate withdestination devices 106 over anetwork 122, as shown inFIG. 1 , transmitting large video files may consume significant amounts of network bandwidth. Furthermore, in some cases,particular destination devices 106 may provide a reasonable video playback experience, even if the file size of thesource media 118 is reduced to some degree in producing theportable media 120. This reduced file size may provide additional benefits, in that the portable media may consume less storage when loaded into thedestination devices 106, as well as consuming less bandwidth when transmitted over thenetworks 122. Thus, in some cases, smaller file sizes may be traded off against reduced rendering quality however, implementations of this description may address any number of different scenarios in which certain factors are traded off against other factors. -
FIG. 3 illustrates two profile settings 302 a and 302 m only for convenience of illustration and description. However, any number ofprofile settings 302 are possible in different implementations. In general, theprofile settings 302 represent technical settings that realize the goals orobjectives 206 specified for a particular media transformation, considering the various illustrative factors shown inFIG. 3 . - Returning to
FIG. 2 , representative profile settings are carried forward at 302. Themedia portability tools 116 may include aportability engine 212, which receives theinput source media 118, and transforms thesource media 118 according to theprofile settings 302. In addition, theportability engine 212 may receive an indication, denoted generally at 214, of a particular target platform for which thesource media 118 is being transformed. This indication oftarget platform 214 may represent any of thedestination devices 106, at any level of appropriate detail. For example, thetarget platform 214 may represent thedestination devices 106 relatively generically (e.g., a WINDOWS® system or a Mac® system), or may represent thedestination devices 106 more specifically. In example scenarios, the destination device 106 a may be represented as a system having a relatively powerful processor, video card, memory, or other configuration elements, while the destination device 106 n may be represented as a system having a more moderately powered processor, video card, etc. In addition, the indication oftarget platform 214 may represent expected or actual configurations for thedestination devices 106. - In some cases, the
portability engine 212 may be a stand-alone component. However, in other scenarios, such as those shown inFIG. 2 , theportability engine 212 may be integrated into another application, represented generally at 216. Thisapplication 216 may be configured to allow users 102 to invoke the capability provided by theportability engine 212 from within theapplication 216. Examples of theapplication 216 may include, but are not limited to, presentation software, word processing software, database or spreadsheet software, and the like. In general, theapplication 216 may represent any application software into which media may be included or embedded. - The
portability engine 212 may produce different outputs in different implementation scenarios. For example,FIG. 2 carries forward theportable media 120 as an illustrative output of theportability engine 212. In addition, however, theportability engine 212 may generate and output an alpha mask, denoted generally at 218. Thealpha mask 218 may enable application of several types of post-transformation effects, without re-computing the transformation of thesource media 118 to theportable media 120. Illustrative but non-limiting examples of these effects may include providing three-dimensional (3-D) visual effects, introducing glow or highlight, changing colors, adjusting transparency, and the like. - In scenarios in which the
portability engine 212 is integrated with theapplication 216, theapplication 216 may generate anoutput document 220. Thisoutput document 220 may include one or more instances of embedded portable media, as represented at 222. In some implementations, theoutput document 220 may also include one or more instances ofalpha masks 224, which may be associated with corresponding embeddedportable media 222. - In those implementations that incorporate the
alpha mask 218, theportable media 120 may be an intermediate result that may or may not be the final viewable result that is presented on thedestination devices 106. In some cases, thedestination devices 106 may apply the alpha mask to the intermediate result to generate the final result. In this manner, the alpha masks 218 may provide greater flexibility on the destination machine, by providing for a variety of different visual effects starting from the same media transformation. For example, theportability engine 212 may transform thesource media 118 intoportable media 120 that has a certain transparency level. In addition, the portability engine may define arelated alpha mask 218 that has another transparency level. Theportability engine 212 may embed both theportable media 222 and thealpha mask 224 into anoutput document 220, which is then sent to any number ofdestination devices 106. - Having received the
output document 220, thedestination device 106 may combine the embeddedportable media 222 with the embeddedalpha mask 224, to achieve yet another transparency level resulting from this combination. In addition,different alpha masks 224 have a different transparencies may provide for different combined transparencies. This example illustrates one scenario out of many facilitated byalpha mask 218. -
FIG. 4 illustrates process flows, denoted generally at 400, related to media portability and compatibility for different destination platforms. To facilitate this description, but not to limit possible implementations, the process flows 400 are described in connection with theportability engine 212 described above inFIG. 2 . However, implementations of this description may perform at least portions of the process flows 400 with other components, without departing from the scope and spirit of this description. - Turning to the process flows 400 in more detail, block 402 represents receiving a command to launch an application (e.g., 216 in
FIG. 2 ) that integrates the capabilities provided by themedia portability tools 116. As described above, theportability engine 212 may be a stand-alone component, or may also be integrated into an application. Stand-alone implementations of theportability engine 212 may omit block 402. -
Block 404 represents receiving a command to launch the portability features as provided in this description. In scenarios in which theportability engine 212 is integrated into another application, block 404 may include receiving a command issued within that application to launch the portability features. In scenarios in which theportability engine 212 is a stand-alone component, block 404 may include receiving a command issued directly to that stand-alone component. -
Block 406 represents receiving one or more instances of source media for transformation.FIG. 1 provides examples of source media at 118. As noted above, thesource media 118 is typically compatible with the originatingdevice 104, but may or may not have optimum compatibility with thedestination devices 106. -
Block 408 represents receiving an indication of a suitable profile for transforming the source media received inblock 406.FIG. 3 described above provides various examples ofprofile settings 302 that implement the goals orobjectives 206 relevant to transforming a given instance of source media. Accordingly, block 408 may include any number of different factors or criteria relevant to such a transformation, including but not limited to any of the factors represented on the axes 304-310 shown inFIG. 3 . -
Block 410 represents transforming the source media into portable media per the profile setting established inblock 408.Block 410 may generate as output theportable media 120 as shown inFIG. 1 . - In turn, block 412 represents inserting or embedding the transformed media into an output file or document. For example,
FIG. 2 illustrates an example output document at 220, which contains the embeddedportable media 222. In scenarios in which theportability engine 212 is integrated into anapplication 216, block 412 may include embedding the transformed media into an output document as generated by thatapplication 216. In scenarios in which theportability engine 212 is a stand-alone component, block 412 may include generating an output file that includes only the transformed media. -
Block 414 represents defining an alpha mask associated with the transformed source media.FIG. 2 provides examples of alpha mask at 218, as output from theportability engine 212. -
Block 416 represents inserting or embedding the alpha mask into output file.FIG. 2 also provides examples of analpha mask 224, as embedded into anoutput document 220. -
Block 418 represents distributing the output file as generated byblock 412 and/or 416. As noted above withFIG. 2 , alpha masks 218 may or may not be associated with every instance ofportable media 120. As described previously withFIG. 1 , block 418 may include distributing instances ofportable media 120 to any number ofdestination devices 106. - The foregoing description provides technologies for media portability and compatibility for different destination platforms. Although the this description incorporates language specific to computer structural features, methodological acts, and computer readable media, the scope of the appended claims is not necessarily limited to the specific features, acts, or media described herein. Rather, this description provides illustrative, rather than limiting, implementations. Moreover, these implementations may modify and change various aspects of this description without departing from the true spirit and scope of this description, which is set forth in the following claims.
Claims (20)
Priority Applications (9)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/346,844 US8578259B2 (en) | 2008-12-31 | 2008-12-31 | Media portability and compatibility for different destination platforms |
PCT/US2009/064589 WO2010077452A1 (en) | 2008-12-31 | 2009-11-16 | Media portability and compatibility for different destination platforms |
CN2009801537548A CN102272750A (en) | 2008-12-31 | 2009-11-16 | media portability and compatibility for different destination platforms |
EP09836595.0A EP2370905B1 (en) | 2008-12-31 | 2009-11-16 | Media portability and compatibility for different destination platforms |
RU2011126674/08A RU2523123C2 (en) | 2008-12-31 | 2009-11-16 | Media portability and compatibility for different destination platforms |
BRPI0922103-4A BRPI0922103A2 (en) | 2008-12-31 | 2009-11-16 | media compatibility and portability for different target platforms |
KR1020117014910A KR101702675B1 (en) | 2008-12-31 | 2009-11-16 | Media portability and compatibility for different destination platforms |
JP2011543522A JP5400170B2 (en) | 2008-12-31 | 2009-11-16 | Media portability and compatibility for different destination platforms |
TW98141240A TWI473017B (en) | 2008-12-31 | 2009-12-02 | Apparatus and computer-implemented process for media portability and compatibility for different destination platforms |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/346,844 US8578259B2 (en) | 2008-12-31 | 2008-12-31 | Media portability and compatibility for different destination platforms |
Publications (2)
Publication Number | Publication Date |
---|---|
US20100169753A1 true US20100169753A1 (en) | 2010-07-01 |
US8578259B2 US8578259B2 (en) | 2013-11-05 |
Family
ID=42286411
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/346,844 Expired - Fee Related US8578259B2 (en) | 2008-12-31 | 2008-12-31 | Media portability and compatibility for different destination platforms |
Country Status (9)
Country | Link |
---|---|
US (1) | US8578259B2 (en) |
EP (1) | EP2370905B1 (en) |
JP (1) | JP5400170B2 (en) |
KR (1) | KR101702675B1 (en) |
CN (1) | CN102272750A (en) |
BR (1) | BRPI0922103A2 (en) |
RU (1) | RU2523123C2 (en) |
TW (1) | TWI473017B (en) |
WO (1) | WO2010077452A1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9807459B2 (en) | 2015-05-14 | 2017-10-31 | At&T Intellectual Property I, L.P. | Media interface device |
WO2019098486A1 (en) * | 2017-11-20 | 2019-05-23 | Hp Printing Korea Co., Ltd. | Data backup using cloud |
US10904706B2 (en) | 2019-04-10 | 2021-01-26 | Here Global B.V. | Method and apparatus for providing contextual content for an end-to-end seamless experience during an autonomous vehicle trip |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CA2767368C (en) | 2009-08-14 | 2013-10-08 | Azuki Systems, Inc. | Method and system for unified mobile content protection |
Citations (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5911776A (en) * | 1996-12-18 | 1999-06-15 | Unisys Corporation | Automatic format conversion system and publishing methodology for multi-user network |
US5928330A (en) * | 1996-09-06 | 1999-07-27 | Motorola, Inc. | System, device, and method for streaming a multimedia file |
US6177946B1 (en) * | 1997-11-14 | 2001-01-23 | Ati Technologies, Inc. | Method and apparatus for processing video data and graphics data by a graphic controller |
US20020097433A1 (en) * | 2001-01-19 | 2002-07-25 | Chang William Ho | Method of operating an information apparatus and software for carrying out the method |
US6498865B1 (en) * | 1999-02-11 | 2002-12-24 | Packetvideo Corp,. | Method and device for control and compatible delivery of digitally compressed visual data in a heterogeneous communication network |
US20030050062A1 (en) * | 2001-09-07 | 2003-03-13 | Chen Yih-Farn Robin | Personalized multimedia services using a mobile service platform |
US20030110234A1 (en) * | 2001-11-08 | 2003-06-12 | Lightsurf Technologies, Inc. | System and methodology for delivering media to multiple disparate client devices based on their capabilities |
US20030158913A1 (en) * | 2002-02-15 | 2003-08-21 | Agnoli Giovanni M. | System, method, and computer program product for media publishing request processing |
US20030225723A1 (en) * | 2002-05-29 | 2003-12-04 | International Business Machines Corporation | Content transcoding in a content distribution network |
US20040162818A1 (en) * | 2003-02-10 | 2004-08-19 | Shaw Venson M. | Distributed profile storage and management in a telecommunication network |
US20040215757A1 (en) * | 2003-04-11 | 2004-10-28 | Hewlett-Packard Development Company, L.P. | Delivery context aware activity on networks: devices, software, and methods |
US20050125734A1 (en) * | 2003-12-08 | 2005-06-09 | Microsoft Corporation | Media processing methods, systems and application program interfaces |
US20050182855A1 (en) * | 2004-02-13 | 2005-08-18 | Apostolopoulos John G. | Media data transcoding devices |
US20050226324A1 (en) * | 2001-07-31 | 2005-10-13 | He Ouyang | Multiple format video compression |
US20060265476A1 (en) * | 1999-10-21 | 2006-11-23 | Sean Barger | Automated media delivery system |
US20070226365A1 (en) * | 2004-05-03 | 2007-09-27 | Microsoft Corporation | Aspects of digital media content distribution |
US7296295B2 (en) * | 2002-12-11 | 2007-11-13 | Broadcom Corporation | Media processing system supporting different media formats via server-based transcoding |
US20080007751A1 (en) * | 2006-07-06 | 2008-01-10 | Seiko Epson Corporation | Image display system |
US20080107170A1 (en) * | 2006-11-06 | 2008-05-08 | Creative Technology Ltd | Method and system for media file conversion |
US7383502B2 (en) * | 2004-04-30 | 2008-06-03 | Microsoft Corporation | Packages that contain pre-paginated documents |
US20080134012A1 (en) * | 2006-11-30 | 2008-06-05 | Sony Ericsson Mobile Communications Ab | Bundling of multimedia content and decoding means |
US20090028428A1 (en) * | 2005-09-28 | 2009-01-29 | Kristofer Dovstam | Media Content Management |
US20090080870A1 (en) * | 2005-05-02 | 2009-03-26 | Mudie George S | Media Transcoding Device and Method |
US20100162117A1 (en) * | 2008-12-23 | 2010-06-24 | At&T Intellectual Property I, L.P. | System and method for playing media |
US20100223354A1 (en) * | 2006-12-19 | 2010-09-02 | AT&T Intellectual Property II, LP via transfer from AT&T Corp. | Method for Creating and Providing Layered Syndicated Data for Multimedia Content to Users |
US8028093B2 (en) * | 2002-12-11 | 2011-09-27 | Broadcom Corporation | Media processing system supporting adaptive digital media parameters based on end-user viewing capabilities |
US8086445B2 (en) * | 2000-11-03 | 2011-12-27 | Audible Magic Corporation | Method and apparatus for creating a unique audio signature |
US8145722B2 (en) * | 2008-08-28 | 2012-03-27 | Nathan Douglas Koons | Media transfer system and associated methods |
US20120117274A1 (en) * | 2006-05-22 | 2012-05-10 | Apple Inc. | Communication Protocol For Use With Portable Electronic Devices |
US8321905B1 (en) * | 2009-10-02 | 2012-11-27 | Adobe Systems Incorporated | Fast switching of media streams |
US8381110B2 (en) * | 1999-10-21 | 2013-02-19 | Equilibrium | Automated media delivery system |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1245005C (en) | 2000-11-29 | 2006-03-08 | 罗技欧洲公司 | System and method for inserting and integrating streaming video content intoadigital medium |
US6407680B1 (en) | 2000-12-22 | 2002-06-18 | Generic Media, Inc. | Distributed on-demand media transcoding system and method |
JP2002342218A (en) | 2001-05-16 | 2002-11-29 | Nippon Telegr & Teleph Corp <Ntt> | Method and system for providing contents |
JP4664527B2 (en) | 2001-05-24 | 2011-04-06 | 株式会社日立国際電気 | Video distribution system and video distribution method |
JP2005522957A (en) | 2002-04-12 | 2005-07-28 | コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィ | Coding / decoding method and coding / decoding apparatus |
KR20050034811A (en) | 2003-10-10 | 2005-04-15 | 한국전자통신연구원 | Systematic modality conversion methodology for supporting qos in multimedia services over heterogeneous environment, and system thereof |
JP4203812B2 (en) | 2003-12-29 | 2009-01-07 | ソニー株式会社 | FILE RECORDING DEVICE, FILE RECORDING METHOD, FILE RECORDING METHOD PROGRAM, RECORDING MEDIUM CONTAINING FILE RECORDING METHOD PROGRAM, FILE REPRODUCTION DEVICE, FILE REPRODUCTION METHOD, FILE REPRODUCTION METHOD PROGRAM, AND RECORDING MEDIUM RECORDING PROGRAM |
TW200718134A (en) | 2005-06-23 | 2007-05-01 | Lalit Sarna | Apparatus, system, method, and article of manufacture for automatic context-based media transformation and generation |
US7555715B2 (en) | 2005-10-25 | 2009-06-30 | Sonic Solutions | Methods and systems for use in maintaining media data quality upon conversion to a different data format |
KR20080011986A (en) | 2006-08-02 | 2008-02-11 | 경북대학교 산학협력단 | Multimedia contents service system and method |
WO2008030302A1 (en) | 2006-09-01 | 2008-03-13 | Sandisk Corporation | Video content recording apparatus with syntax for video content recording parameters and method for use therewith |
US20080205389A1 (en) | 2007-02-26 | 2008-08-28 | Microsoft Corporation | Selection of transrate and transcode processes by host computer |
-
2008
- 2008-12-31 US US12/346,844 patent/US8578259B2/en not_active Expired - Fee Related
-
2009
- 2009-11-16 BR BRPI0922103-4A patent/BRPI0922103A2/en not_active Application Discontinuation
- 2009-11-16 WO PCT/US2009/064589 patent/WO2010077452A1/en active Application Filing
- 2009-11-16 RU RU2011126674/08A patent/RU2523123C2/en not_active IP Right Cessation
- 2009-11-16 KR KR1020117014910A patent/KR101702675B1/en active IP Right Grant
- 2009-11-16 JP JP2011543522A patent/JP5400170B2/en not_active Expired - Fee Related
- 2009-11-16 EP EP09836595.0A patent/EP2370905B1/en not_active Not-in-force
- 2009-11-16 CN CN2009801537548A patent/CN102272750A/en active Pending
- 2009-12-02 TW TW98141240A patent/TWI473017B/en not_active IP Right Cessation
Patent Citations (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5928330A (en) * | 1996-09-06 | 1999-07-27 | Motorola, Inc. | System, device, and method for streaming a multimedia file |
US5911776A (en) * | 1996-12-18 | 1999-06-15 | Unisys Corporation | Automatic format conversion system and publishing methodology for multi-user network |
US6177946B1 (en) * | 1997-11-14 | 2001-01-23 | Ati Technologies, Inc. | Method and apparatus for processing video data and graphics data by a graphic controller |
US6498865B1 (en) * | 1999-02-11 | 2002-12-24 | Packetvideo Corp,. | Method and device for control and compatible delivery of digitally compressed visual data in a heterogeneous communication network |
US8381110B2 (en) * | 1999-10-21 | 2013-02-19 | Equilibrium | Automated media delivery system |
US20060265476A1 (en) * | 1999-10-21 | 2006-11-23 | Sean Barger | Automated media delivery system |
US8086445B2 (en) * | 2000-11-03 | 2011-12-27 | Audible Magic Corporation | Method and apparatus for creating a unique audio signature |
US20020097433A1 (en) * | 2001-01-19 | 2002-07-25 | Chang William Ho | Method of operating an information apparatus and software for carrying out the method |
US20100227550A1 (en) * | 2001-01-19 | 2010-09-09 | Flexiworld Technologies, Inc. | Method and apparatus for wireless output of digital content |
US20050226324A1 (en) * | 2001-07-31 | 2005-10-13 | He Ouyang | Multiple format video compression |
US20030050062A1 (en) * | 2001-09-07 | 2003-03-13 | Chen Yih-Farn Robin | Personalized multimedia services using a mobile service platform |
US20030110234A1 (en) * | 2001-11-08 | 2003-06-12 | Lightsurf Technologies, Inc. | System and methodology for delivering media to multiple disparate client devices based on their capabilities |
US20030158913A1 (en) * | 2002-02-15 | 2003-08-21 | Agnoli Giovanni M. | System, method, and computer program product for media publishing request processing |
US20030225723A1 (en) * | 2002-05-29 | 2003-12-04 | International Business Machines Corporation | Content transcoding in a content distribution network |
US7296295B2 (en) * | 2002-12-11 | 2007-11-13 | Broadcom Corporation | Media processing system supporting different media formats via server-based transcoding |
US8028093B2 (en) * | 2002-12-11 | 2011-09-27 | Broadcom Corporation | Media processing system supporting adaptive digital media parameters based on end-user viewing capabilities |
US20040162818A1 (en) * | 2003-02-10 | 2004-08-19 | Shaw Venson M. | Distributed profile storage and management in a telecommunication network |
US20040215757A1 (en) * | 2003-04-11 | 2004-10-28 | Hewlett-Packard Development Company, L.P. | Delivery context aware activity on networks: devices, software, and methods |
US20050125734A1 (en) * | 2003-12-08 | 2005-06-09 | Microsoft Corporation | Media processing methods, systems and application program interfaces |
US20050182855A1 (en) * | 2004-02-13 | 2005-08-18 | Apostolopoulos John G. | Media data transcoding devices |
US7383502B2 (en) * | 2004-04-30 | 2008-06-03 | Microsoft Corporation | Packages that contain pre-paginated documents |
US20070226365A1 (en) * | 2004-05-03 | 2007-09-27 | Microsoft Corporation | Aspects of digital media content distribution |
US20090080870A1 (en) * | 2005-05-02 | 2009-03-26 | Mudie George S | Media Transcoding Device and Method |
US20090028428A1 (en) * | 2005-09-28 | 2009-01-29 | Kristofer Dovstam | Media Content Management |
US20120117274A1 (en) * | 2006-05-22 | 2012-05-10 | Apple Inc. | Communication Protocol For Use With Portable Electronic Devices |
US20080007751A1 (en) * | 2006-07-06 | 2008-01-10 | Seiko Epson Corporation | Image display system |
US20080107170A1 (en) * | 2006-11-06 | 2008-05-08 | Creative Technology Ltd | Method and system for media file conversion |
US20080134012A1 (en) * | 2006-11-30 | 2008-06-05 | Sony Ericsson Mobile Communications Ab | Bundling of multimedia content and decoding means |
US20100223354A1 (en) * | 2006-12-19 | 2010-09-02 | AT&T Intellectual Property II, LP via transfer from AT&T Corp. | Method for Creating and Providing Layered Syndicated Data for Multimedia Content to Users |
US8145722B2 (en) * | 2008-08-28 | 2012-03-27 | Nathan Douglas Koons | Media transfer system and associated methods |
US20100162117A1 (en) * | 2008-12-23 | 2010-06-24 | At&T Intellectual Property I, L.P. | System and method for playing media |
US8321905B1 (en) * | 2009-10-02 | 2012-11-27 | Adobe Systems Incorporated | Fast switching of media streams |
Non-Patent Citations (5)
Title |
---|
"Mp4cam2avi" http://mp4cam2avi.sourceforge.net/interface.htm, Jul 4, 2008 pp 1-7 * |
"Video Converter", http://forums.afterdawn.com/thread_view.cfm/268285, Dec 30, 2006, pp 1-6 * |
"Xilisoft FAQ", http://www.xilisoft.com/video-converter/faq.html Oct 30, 2007, pp 1-6 * |
Apple Computers Inc. , Keynote 2 User's Guide, 2005, Apple, pp 7,10,50-52 * |
Macworld http://www.macworld.com/article/1047473/ipodpsp.html Oct 14, 2005, pp1-5 * |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9807459B2 (en) | 2015-05-14 | 2017-10-31 | At&T Intellectual Property I, L.P. | Media interface device |
US10757479B2 (en) | 2015-05-14 | 2020-08-25 | At&T Intellectual Property I, L.P. | Media interface device |
WO2019098486A1 (en) * | 2017-11-20 | 2019-05-23 | Hp Printing Korea Co., Ltd. | Data backup using cloud |
US11188662B2 (en) * | 2017-11-20 | 2021-11-30 | Hewlett-Packard Development Company, L.P. | Encrypted data backup and restoration for image forming apparatuses using cloud |
US10904706B2 (en) | 2019-04-10 | 2021-01-26 | Here Global B.V. | Method and apparatus for providing contextual content for an end-to-end seamless experience during an autonomous vehicle trip |
Also Published As
Publication number | Publication date |
---|---|
CN102272750A (en) | 2011-12-07 |
RU2011126674A (en) | 2013-01-20 |
BRPI0922103A2 (en) | 2020-08-11 |
US8578259B2 (en) | 2013-11-05 |
KR20110107802A (en) | 2011-10-04 |
WO2010077452A1 (en) | 2010-07-08 |
EP2370905B1 (en) | 2018-12-26 |
RU2523123C2 (en) | 2014-07-20 |
EP2370905A4 (en) | 2012-12-26 |
JP5400170B2 (en) | 2014-01-29 |
TW201025130A (en) | 2010-07-01 |
EP2370905A1 (en) | 2011-10-05 |
KR101702675B1 (en) | 2017-02-03 |
JP2012514383A (en) | 2012-06-21 |
TWI473017B (en) | 2015-02-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8577204B2 (en) | System and methods for remote manipulation of video over a network | |
US8265457B2 (en) | Proxy editing and rendering for various delivery outlets | |
US20100036936A1 (en) | Modification of social networks via design codes | |
US20200143839A1 (en) | Automatic video editing using beat matching detection | |
US8610713B1 (en) | Reconstituting 3D scenes for retakes | |
US8522201B2 (en) | Methods and apparatus for sub-asset modification | |
US8578259B2 (en) | Media portability and compatibility for different destination platforms | |
US9674540B2 (en) | Processing parameters for operations on blocks while decoding images | |
US20140115056A1 (en) | Book thinning | |
US20110018889A1 (en) | Media processing comparison system and techniques | |
CN111385599A (en) | Video processing method and device | |
US8014883B2 (en) | Templates and style sheets for audio broadcasts | |
US9761030B2 (en) | Scene image generator | |
CN113082720A (en) | Prompt message determination method and device and electronic equipment | |
CN112565268B (en) | Transmission control method, device and equipment of multimedia information and computer storage medium | |
KR20120117312A (en) | Communication terminal apparatus, apparatus and method for providing contents, system and method for authoring e-book | |
US20130232398A1 (en) | Asset management during production of media | |
CN116980705A (en) | Method, device, equipment and storage medium for special effect production | |
CN114880499A (en) | Three-dimensional slide playing and generating method, device and equipment | |
CN113992866A (en) | Video production method and device | |
CN113299320A (en) | Holographic recording method and system based on virtual reality | |
CN115065866A (en) | Video generation method, device, equipment and storage medium | |
iPod et al. | Farshad Fotouhi Wayne State University | |
US20110064389A1 (en) | Apparatus and method for generating moving image & apparatus and method for reproducing moving image |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MICROSOFT CORPORATION,WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CHEN, JEFFREY CHAO-NAN;LI, BARN WAN;LUI, KAI CHUNG;SIGNING DATES FROM 20081219 TO 20081229;REEL/FRAME:023192/0971 Owner name: MICROSOFT CORPORATION, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CHEN, JEFFREY CHAO-NAN;LI, BARN WAN;LUI, KAI CHUNG;SIGNING DATES FROM 20081219 TO 20081229;REEL/FRAME:023192/0971 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034564/0001 Effective date: 20141014 |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20211105 |