Author Archive: Jens Loeffler

Jens Loeffler

About Jens Loeffler

Jens Loeffler is a senior technical evangelist on Adobe's Media Solutions product management team focusing on online video and services. Equipped with a media computer science degree, Jens started his career in the agency world and has been living and breathing online video and mobile for the last decade. Currently Jens provides thought leadership as a public speaker and panelist at numerous industry events, and maintains a well-recognized blog covering industry trends. When he isn't working on secret projects at Adobe, Jens compensates with long runs, hikes and walks with his furry companion, and is an excellent guide to judge the authenticity of German cuisine in NYC.

Flash Media Server 4.5.2 Released with Robust HTTP Streaming Failover

Version 4.5.2 of Flash Media Server is now available. Besides numerous bug fixes, it includes a major improvement – robust HDS/HLS failover for origins.

packagecluster_wide31It’s not simply a “good-to-have”, but a “must-have” feature for reliable HTTP streaming deployments. The key issues it addresses are liveness and dropout situations.

Liveness is a server-side situation in which a packager advertises a stale bootstrap (that is, a stale view of a live stream).

Dropout is a server-side situation in which a packager has gaps in its bootstrap (that is, gaps in its fragment list).

Flash Media Server 4.5.2 introduces the following new features to address this:

FMS4.0-mnemonic1Best-effort fetch

Best-effort fetch enables the OSMF and iOS video players to continue playback as normally as possible in the presence of short-term liveness and dropout problems on the server-side.

The OSMF 2.0 player adds client-side robustness by supporting best-effort fetch. Specifically, when best-effort fetch is enabled on the server, OSMF 2.0 attempts fetches for fragments that have not been advertised in the bootstrap, but are expected to be present.

For iOS Video players, FMS 4.5.2 enables best-effort fetch for HLS as well.

Control plane application

To implement HTTP Streaming failover, it’s now possible to write a client application that manages the state of events and streams by using a set of REST-based control plane APIs. Control plane is a router term and in effect, that is what your client application does through these APIs.

You can find more detailed information in the FMS failover documentation.

HTTP failover is an absolutely critical improvement for more reliable workflows, therefore Flash Media Server 4.5.2 is an exciting new release for everyone with HTTP streaming deployments.

Download the Flash Media Server 4.5.2 upgrade.

Share

Adobe Video Solutions Team at NAB

The video solutions team is excited to be in Las Vegas for the NAB event from April 16th to the 19th.

We’ve made some significant efforts to reduce fragmentation and provide customers the best tools for publishing, protecting and monetizing online video to multi-screen devices. At this year’s NAB, we’ll be particularly emphasizing our recent Project Primetime announcement, which focuses on helping content creators get their premium video online, with seamless ad insertion and analytics.  Additionally we’ll be showing protected HLS and HDS HTTP streaming to the iPad and Galaxy Tab.

production

Come visit our booth to say hello, ask questions, and see our amazing streaming products and demos including speak peeks into our recent CS6 Production Premium announcement.

Share

Adobe Access – A Single DRM Workflow

We recently announced the upcoming availability of Adobe Access (formerly Flash Access) DRM protection for native iOS applications. So what does this mean for your workflow?

You can now finally reach a broad range of destination devices with a single, simple workflow, including Windows, OSX, iPad, iPhones, iPods, hundreds of Android smartphones and tablets (Android 2.2+), and televisions, including Samsung Smart TVs, TIVO and LG devices, and soon many more as part of project Primetime.

single_drm_workflow-1024x481

It not only saves you costs, but also provides a simple, robust DRM workflow, with a single content protection scheme.

Not convinced how this will work? Here are the steps.

1)   Real-Time packaging and protection of H.264 source files with Adobe Media Server

2)   HTTP delivery to target platforms (HLS to iOS, HDS to other devices)

3)   License acquisition from a single Adobe Access server, no matter what the playback platform is

As part of Project Primetime, Adobe is focused on solving the fragmentation challenges video distributors are confronted with in 2012. This is the first step to provide a secure end-to-end video delivery workflow

Share

Project Primetime to Enable a Single Video Publishing Workflow, Starting with Adobe Access for iOS and MPEG-Dash Support

As part of the quickly evolving device landscape, a unified video publishing workflow is more important than ever. Individual workflows for specific devices or platforms are not a long-term approach. It’s like having to build a different car, depending on the city you want to travel to. It’s expensive and distracts from the important part of your video application, the user experience.

As part of Project Primetime, we are continuing to invest in our own technology and industry standards that enable our video customers to have a single workflow that enables them to reach any web-enabled devices.

What does this mean for you? Instead of having to worry about using different content protection, video delivery or video publishing workflows, Project Primetime will provide a holistic solution, which will make your video strategy uniquely easy to deploy, protect and monetize.

We’re making two announcements today that will bring the industry towards a single video publishing workflow:

Adobe Access for native iOS applications

Adobe Access, our robust Digital Rights Management technology, will support native iOS applications.  With Adobe Access’ existing support for desktop (99% reach via Flash Player), Android (via AIR 3.0) and Smart TVs (via AIR for TV 2.5), video publishers can now reach a huge digital audience with a single content protection solution.

Here’s how it works: Adobe provides an Adobe Access DRM library that can be integrated into your native iOS application.  You build your experience using the Apple SDK, add the Adobe Access library as a component, and deliver through the Apple App Store. The Adobe Access DRM library provides all the necessary robustness. The video content is streamed using Apple’s HLS (HTTP Live Streaming) protocol, and Adobe Access provides the content protection required by studios.

MPEG-DASH support

We are announcing that our streaming technologies will support the emerging standard MPEG-DASH. It will provide the reach and flexibility required for a unified video workflow. It will not replace, but provide additional reach to existing Adobe streaming protocols. You can read more about our announcement here.

We are very excited about these announcements, which are first steps to provide a unified video publishing workflow that will offer the best reach, protection and monetization for video content.

Share