Open Source Media Framework Develop and share open standards.
Download

Open Source Media Framework Ranking & Summary

Open Source Media Framework Tags

develop component assemble assemble component develop stantard develop framework

Open Source Media Framework Description

Develop and share open standards. Open Source Media Framework (OSMF), currently in public prerelease, enables developers to easily assemble pluggable components to create high-quality, full-featured playback experiences. The open aspect of the framework encourages collaborative development that can be focused on web video monetization, with faster turnaround and lower costs.This project is intended to facilitate the development and sharing of open standards and best practices for video player applications built on the Adobe Flash Platform. Media players today are a nexus of complexity for so many technologies, services, and providers that the project can best tackle these integration challenges through an open source approach. Open Source Media Framework serves as a resource for the industry, encouraging the use of standards and best practices and offering the open source library.Open Source Media Framework can be leveraged in ActionScript 3 or MXML. For more information about building video applications in Adobe Flash CS4 Professional or Adobe Flash Builder, you may wish to visit the Video Technology Center on the Adobe Developer Connection. What's New in This Release: · Live stream support - Live streaming is now supported using OSMF and a standard FMS 3.5 installation. This feature provides the means for player and plug‐in developers to specify the stream type so the underlying framework can make the correct NetStream.play() method call. · CompositeElement support for bytesLoaded and bytesTotal - This feature introduces support for querying the number of bytes loaded (and total number of bytes) on · SerialElement and ParallelElement, as well as directly from the MediaPlayer. · Subclip support - This feature allows for playback of subclips, or contiguous sub‐sections, of a streamed video. A use case for this feature is playback of a single video interspersed by mid‐roll ads. · Metadata Merge refactoring - Serial and ParallelElements now reflect the metadata of their children. With the introduction of facet synthesizers, there is now more fine‐grained control over how a child’s metadata will surface on its parent. · Preassigned durations - VideoElement and AudioElement were extended with a defaultDuration property. The addition of the defaultDuration property allows for the elements to reflect a duration before being loaded. This enables a SerialElement that consists of two or more such elements to know its total duration before the second · element has been loaded. As a result, a scrub bar can now reflect the total duration of a serial composition. · Manifest Loader - The Manifest Loader loads a Flash Media Manifest file, parses it, and creates the proper resource for the media element. Manifest files allow MBR and other content metadata to be specified in a single file. · Note: The spec for the Flash Media Manifest file format is not yet available, but we expect to be able post it soon. · This feature introduces the LoadableProxyElement class. The LoadableProxyElement class is useful when the type of MediaElement to be created is unknown. For example when loading of an external manifest file is not complete. · Captioning plug-in - The Captioning Plug‐in allows an external captioning document to be associated with a media element via resource metadata and dispatches events of type TemporalFacetEvent at the correct time, as the media plays. This effort leverages the TemporalFacet work from Sprint 7. · API refactoring changes from Sprint 7 to Sprint 8 - The primary change is that traits are now classes instead of interfaces. Furthermore, event classes were merged so that there’s one event class per trait class (with potentially multiple event constants per event class). The main motivation for this change was ease of maintaining backwards compatibility and consistency with the rest of the Flash Platform. · If you are already familiar with the framework, it will help if you browse through some of the code in Sprint 8, in order to get familiar with the new structures and naming patterns. · When first working with the refactored APIs, a significant shift in thinking is required. The main idea that needs to change is in thinking of traits as nouns rather than adjectives. For example we now use LoadTrait, a thing, rather than ILoadable, a description. After a little time to transition and digest the new grammar it should make sense and be fairly intuitive.

Open Source Media Framework Related Software