Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
 Your new post is loading...
Your new post is loading...
Scoop.it!
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. 
No comment yet.
Sign up to comment
Scoop.it!
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.
Scoop.it!
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.
|
Scoop.it!
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.
Scoop.it!
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.
|
Read also : http://www.thekuroko.com/http-dynamic-streaming-download-and-playback/