Your new post is loading...
Your new post is loading...
Dash.as runs MPEG-DASH video on any device supporting Adobe Flash. It was designed from the ground-up to be lightweight with performance in mind. Hosted as a GitHub project, it is available as an open-source video player written in Adobe ActionScript. We provide everything you need to get started and invite you to help refine the application.
Having been involved in the Together project, I was assigned a task to enable Apple HLS video playback on the Flash platform. Video content delivery in a single format (HLS in this case) is usually very easy and offers many benefits. To process video, Flash has an open source OSMF framework that can be easily enhanced with various plugins. But there is one problem: the framework is absolutely HLS-agnostic. Adobe promoted RTMP first, and only then offered HTTP Dynamic Streaming (HDS) as an alternative to Apple HLS. In this post, we’ll cover a free HLS plugin that we have developed to run HLS in OSMF-enabled video players. Github page : https://github.com/denivip/osmf-hls-plugin
Slides from Streaming Media West Presentation, "How to Create A DASH-264 player for Adobe Flash" by Jeff Tapper and Michael Labriola of Digital Primates.
Adobe has announced the launch of version 2.0 of its Open Source Media Framework(OSMF), an open software framework for building media players and applications, based on the company's closed source Flash platform. Kelash Kumar, Adobe Video Solutions Group Product Manager, says that the new version of OSMF includes a number of improvements aimed at helping developers "create even more engaging experiences" and notes that the developers have "reworked the inner workings of OSMF". OSMF 2.0 includes changes to the Adaptive Bit Rate (ABR) algorithm and APIs that improve overall performance, and updates the default Switch Manager, which determines when a bit rate change should be made and to what quality. Doneness support in version 2.0 means that the framework can now distinguish between HTTP Dynamic Streaming (HDS) content streams shutting down due to server-side problems and shutting down because an event stream has completed.
Vous allez me dire, mais qu’est ce que ce titre signifie en réalité ? C’est assez simple, je vais décomposer : - HDS pour HTTP Dynamic Streaming est un protocole de diffusion des vidéos (créé par Adobe). Le principe est similaire au HTTP Live Streaming utilisé sur les iPhone et iPad (j’avais présenté ce protocole). - Late Binding Audio : comprenez par là la possibilité d’avoir plusieurs pistes audios associé à un flux vidéo - OSMF pour Open Source Media Framework, un framework Flex utilisé pour la gestion des vidéos.
When you are using F4M’s with OSMF you are essentially giving the framework a XML manifest file which in its contents tell it what to create an actual MediaElement for. However it has to take a few steps to get there.
Part 1 of this series discussed HTTP Dynamic Streaming (HDS) at a fairly high level. The next few editions in the series will explore some of the more powerful features that make using this protocol advantageous. Multi-bitrate stream switching and file encryption are two important features that we’ll cover in the very near future, as they’re very big reasons to stream over any protocol. However, in this article I’d like to discuss a brand new feature of the Open Source Media Framework (OSMF) known as “late-binding audio”. Late-binding audio refers to the ability to stream videos with multiple associated audio tracks. This makes it possible to play an alternative audio track on the client-side using the same video file. There’s no need to encode, store, and deliver separate video + audio assets for each version you would like to provide. Say for example that you would like to provide video content with audio translated into multiple languages. Instead of creating separate video + audio files for each language, you instead encode the video only once, and include the alternate audio-only tracks along with the it. This represents a huge savings in time, storage, and bandwith that anyone making the switch to HTTP Dynamic Streaming can take advantage of.
The OSMF team has just released the latest sprint drop for OSMF 1.6, Sprint 5, and the key new feature is support for multiple audio tracks for HTTP Dynamic Streaming, often referred to as “late-binding audio.” This feature allows publishers to associate multiple audio-only streams with a particular video and present these as alternate audio tracks to the consumer.
|
This blog gives an overview of what kind of client support Microsoft offers as part of Windows Azure media Services. On one side, you could create, manage, package and deliver media asset through Windows Azure media services. Many popular streaming formats are supported, such as Smooth Streaming, Http Llive Streaming and MPEG-dash. On the other hand, we provide various SDKs and frameworks for you to consume media asset by building rich media applications rapidly on many platforms, such as PC, XBox, mobile and etc.
The Open Source Media Framework (OSMF) doesn’t respond well when you pass it a local F4M file path for playback. Playing back local HDS fragments is an edge case, but enough people have encountered this problem that I think it deserves a little attention.
The Open Source Media Framework (OSMF) is an Adobe-led, open-source ActionScript 3 coding framework for loading, playing and displaying media. Just as Adobe created the Flex Framework to standardize and expedite the creation of applications on the Flash Platform, OSMF is a means to standardize media handling in your Flash Platform experiences. With video, audio, and image playback handled so differently in AS3, OSMF succeeds at creating a simplified, standard way to work with all media inside Flash. In this DZone Refcard you will learn about Strobe Media Playback, Flash Media, key events, streaming, composite elements, and more.
One thing kept bugging us though; now that there’s all this great support in Flash for HTTP protocols, might it be possible to actually deliver Apple’s HTTP Live Streaming (HLS) protocol to Flash as well? This would, of course, have great benefits for our customers already using Unicorn Once for delivery to the myriad of devices (iPhone, iPad, Roku, Samsung, LG, etc) that already support HLS, since those HLS fragments would potentially have higher cache-ability in the CDN, and thus better performance. Well, it turns out it was indeed possible to deliver HLS to Flash, just as we had thought. We found a great project that had already been started, but apparently abandoned before more advanced features like dynamic stream switching had been added. We announced today that we have extended that project and will soon be releasing the updated version to the world as an open-source library called the Once More Project. The decision to entirely open source this software (our first contribution to the open source community) was made primarily because we think this kind of technology needs to proliferate throughout the entire industry. In keeping with the overall vision for Unicorn Once, we wanted to ensure that our clients have their choice about how they want to deliver their content on every device- and because we believe in open standards like HLS. SEE apple-http-osmf project : http://code.google.com/p/apple-http-osmf
For most players, simply enabling OSMF's default Dynamic Streaming is sufficient. For some players, customizing the HTTP Dynamic Streaming (HDS) adaptive bitrate algorithm may be desired, but note that this is an advanced task. Below is a representation of the customizable areas of the adaptive bitrate algorithm. The rest of this article describes the various levels of customization, in order of complexity, starting with simple parameter customization and ending with the complete replacement of the adaptive bitrate algorithm.
In this article, you'll learn how to create a simple video player that streams Adobe HTTP Dynamic Streaming (HDS) video to Internet-connected televisions, set top boxes, and other devices. Playing video content on Internet-connected devices requires the AIR for TV (A4TV) 2.5.1 or higher runtime. This article describes how to configure Flash Builder to develop and compile a simple player for A4TV using the Open Source Media Framework (OSMF). The A4TV runtime requires developers use the proper AIR namespace in their application descriptor file. OSMF facilitates player development for consuming HDS content that cannot be consumed by the popular FLVPlayback or VideoDisplay components. The sample project described in this article uses: - AIR 2.5 SDK - Flex 3.6 SDK - OSMF MediaPlayerSprite class
EQUIVALENT TUTORIAL WITH FLASH PRO : http://www.adobe.com/devnet/flashmediaserver/articles/osmf-air-tv-flash-pro.html
Back in early June, we reported on the pre-release of Adobe’s OSMF 1.6, and its support for late-binding audio. Adobe has been working hard to improve upon the upgrades they gave us with the OSMF 1.6, Sprint 5 release, and to add even more new features for mobile as well. Today Realeyes Media is pleased to announce that OSMF 1.6, and Strobe Media Playback 1.6 have been granted their final release status. OSMF 1.6 - In regards to late-binding audio, as promised, today’s release supports live playback as well as video on demand (VOD). - For mobile – offers Stage Video support for hardware-accelerated video presentation(requires Flash Player 10.2+). - DVR rolling window support, which allows you specify how far back from the live point viewers can rewind (requires the newly released FMS 4.5). Core Framework - Improvements to HTTP Dynamic Streaming as well as the ability to better manage bitrate profiles with multi-level manifests.
New version of Flash Media Server offers expanded, dynamic protocol support, including HTTP Live Streaming to iDevices, as well as DRM enhancements. FMS 4.5's primary intent is to leave the heavy lifting of choosing which protocol to deliver in (RTMP, HTTP Dynamic Streaming, HLS, etc) to the server. FMS 4.5 can generate real-time repackaging of an mp4 file for both HTTP Dynamic Streaming and HLS, including automated segmentation of mp4 files into the specific fragmented mp4 (fMP4) segmentation required by various Android, iOS and other mobile devices. In addition to single stream repackaging, FMS 4.5 will also automatically create multiple bitrate segmentations, for adaptive streaming, as well as manifest files in Apple's m3u8 format. Instead of the previous manual process of rewrapping, segmentation creation, and manifest files, FMS 4.5 promises the ability to automate these basic processes. With a nod to digital rights management, FMS 4.5 will also include DRM based on the Flash Access DRM scheme. Rather than requiring a broadcaster to buy a full-blown Flash Access 3.0 server, however, there will be a limited version of Flash Access baked into FMS 4.5 to cover RMTPe (encrypted) and segment-level DRM (a key feature of fMP4, which separates the header information from each fragment). Adobe claims it is also enhancing DRM to cover iOS devices to a limited degree--a claim we'll explore when we get a chance to review Flash Access 3.0 and FMS 4.5 , as HLS is based on MPEG-2 Transport Stream, which has no inherent capacity for DRM within each packet. RTMFP will be available on the FMIS, a change from Adobe's previous scenario of only allowing RTMFP on the Enterprise Server version.
AS3 libs for HLS streaming in Flash by Matthew Kaufman - a way of building a decent video player on iOS or the final end of RTMP streaming ?
|