Probably the hottest thing the W3C is working on right now is their Encrypted Media Extension Working Draft. The EME draft is widely talked about as "the DRM standard for HTML5", but this is not truly what it's content covers. I'll look at what it is, why it's not a great idea, and some implications of its approval, were it to be approved.
It's possible to tell what's actually covered by the W3C's draft by carefully examining its title; the second word - "media" - is the key. Your average layman might assume that this refers to media in the general sense (and its oh-so-natural wont for encryption); whereas in fact, it refers very specifically to HTML5's media elements. You might know them as <audio> and <video>. The standard specifies some funky extensions to their DOM/Javascript API, based around cryptographic key management. There is almost nothing here about interesting DRM technology, but there are some warnings that it will introduce yet another way for advertisers to track you. Huzzah.
This year the EBU BroadThinking Conference was sounding like a holistic swirl, a milestone in the trend of technology to define sets that are greater than the sum of their parts, through creative evolution. « Where Broadcast Meets BroadBand », you get some interesting fusion effect occurring and diluting the traditional boundaries of the screens, with the handheld devices being part of the big screen experience or extending it rather than trying to scalp it, in an environment where all the devices converge towards a restricted set of standards rather than tracing their own line.
While we by default think that standardization kills creativity, events like BroadThinking show that it’s the opposite: if we gather energies to solve common problems together, we can both come up with a more evolved solution and concentrate on what’s important past the pixel grid: the user experience, so consistent across screens that you forget there’s more than one screen involved.
What the online video industry needs is simple standards for reaching all viewers. But when have standards ever simplified online video?
Proprietary technologies are inherently bad in the video space, except when they’re not. Standards inevitably simplify matters, except when they don’t. So it is with Flash, and its obvious successors, the Media Source Extensions (MSE), Encrypted Media Extensions (EME), and Dynamic Adaptive Streaming via HTTP (DASH).
MSE/EME/DASH are the standards that will enable web publishers to replace Flash in their playback architectures. MSE eliminates two of HTML5's most critical limitations by bringing standards-based adaptive streaming and live delivery to HTML5 browsers and devices. EME brings a single encryption API to HTML5 browsers, providing digital rights management (DRM), addressing another former deficit. DASH is the standards-based file format that will actually deliver the streams. The vision is one set of cache-friendly streams in DASH format that can play on any MSE/EME-compatible computer or device, which will replace the two streams most producers create today for Flash and HLS playback.
With most competing browsers and the content industry embracing the W3C EME specification, Mozilla has little choice but to implement EME as well so our users can continue to access all content they want to enjoy. Read on for some background on how we got here, and details of our implementation.
Usually when creating a video, all that is needed is to encode it using a codec (for example H.264 or HEVC). However, to transmit a video using MPEG-DASH, an extra segmentation step is required. Typical encoders do not provide this step and produce content which is not compatible with DASH.
Our dash.encrypt project provides a solution. It takes encoded video and audio from an array of different formats and repackages them as valid DASH streams. It also generates the required manifest which is the table of contents for the stream.
Hosted as a GitHub project, it is available as an open-source application written in Java. We provide everything you need to start creating DASH content and invite you to help refine the program.
The W3C HTML working group is developing media extension specifications for HTML5 to enable the delivery of commercial video to consumers over the Web. One of these is the Encrypted Media Extensions (EME) specification. The current specification describes an open interface which may be used to implement an EME-compliant Content Decryption Module (CDM) within a User-agent, providing access to a platform DRM component which supports the defined Content Decryption Module interface (CDMi).
Une présentation OVFSquad de Nicolas Weil le 17/10/13.
Les thèmes abordés : - panorama du support par l'industrie - facteurs d'adoption et freins - analyse du processus de standardisation - avancées en Common Encryption + Multi-DRM - point sur les players et HbbTV 1.5 - topo sur les prochains gros dossiers : HEVC, Multichannel audio et QoS - point sur les déploiements actuels et annoncés
Adobe also announced a new cloud DRM service that’s designed to simplify the deployment of content protected videos across devices. Adobe Primetime DRM, the company noted, already s being used by companies including AT&T, DirectTV, Fox, Scripps Networks, Turner Broadcasting System, Inc., Walt Disney Pictures, Hulu, HBO Go and Comcast.
The cloud-based version will help content owners and distributors bring more premium content to more devices efficiently. Available as a hosted web service in the cloud, the DRM manager handles compliance and robustness, management and scalability, and ensures that new features can be added easily without the need to update software on an on-premises server.
The demonstration featured simultaneous PlayReady encryption, powered by Inside Secure’s Downloadable DRM Agent for iOS, and Verimatrix encryption from the same MPEG-DASH url delivered to both Android and iOS players from Inside Secure and NXP Software.
The CENC scheme specifies standard encryption and key mapping methods that can be utilized by one or more digital rights management (DRM) and key management systems to enable decryption of the same file using different DRM systems. Such an approach supports a broader range of accessible clients from a single content stream.
Android has limited support for HLS (Apple’s HTTP Live streaming protocol), and device support is not the same from one version or one device to the next. Android devices before 4.x (Gingerbread or Honeycomb), do not support HLS. Android tried to support HLS with Android 3.0, but excessive buffering often caused streams to crash. Devices running Android 4.x and above will support HLS, but there are still inconsistencies and problems.
Intertrust Technologies has introduced an integrated content protection solution-as-a-service that it says is simple and cost-effective to implement by any service provider yet strong enough to protect high-value entertainment and media content including video, audio, ebooks and games.
Called ExpressPlay, it works with existing Marlin-enabled Smart TVs and set-top boxes and with iOS and Android apps. Intertrust also provides an embedded SDK for device manufacturers and a content packager for service providers to ingest content. ExpressPlay supports Marlin and media streaming standards such as DASH and HLS.
Nicolas Weil's insight:
One of the first standardized DRMs for DASH. Interesting announced upcoming support for SIlverlight & XBox...
Brightcove now supports transcoding video into the MPEG-DASH format. Support is also available for MPEG-DASH encrypted with Common Encryption, allowing multiple DRM systems to playback a single source asset. This topic provides an overview of the steps required to publish and play DASH content through Video Cloud.
Dynamic Adaptive Streaming over HTTP (DASH), also known as MPEG-DASH, is an adaptive bitrate streaming technique that enables high quality streaming of media content over the Internet delivered from conventional HTTP web servers. Similar to Apple's HTTP Live Streaming (HLS) solution, MPEG-DASH works by breaking the content into a sequence of small HTTP-based file segments, each segment containing a short interval of playback time of a content that is potentially many hours in duration, such as a movie or the live broadcast of a sports event. The content is made available at a variety of different bit rates and as the content is played back by an MPEG-DASH client, the client automatically selects from the alternatives the next segment to download and play back based on current network conditions.
Adobe Systems has made some upgrades to its Primetime Digital Rights Management platform that the software vendor said will bring its content protection service into the world of browser-based video.
Adobe announced Primetime DRM is now available on apps without a Flash Player plugin, as well as via HTML5 on major Web browsers. The changes are significant as they represent Adobe's shift away from its Flash-player approach in favor of using emerging HTML5 extensions that support video embedded directly into Web pages.
With the recent announcements from Apple/Netflix and Mozilla, all modern desktop browsers will soon support the proposed HTML Encrypted Media Extensions (EME) standard. EME provides a standardized approach for playing encrypted content in HTML5. One application of encrypted video is the enforcement of Digital Rights Management (DRM) on paid video content. Many content owners (film studios, sports leagues, etc.) mandate using DRM to distribute their content online.
What does all of this alphabet soup mean for users? In short, the EME standard enables publishers to deliver premium video to browsers without the need for plugins. To date, doing DRM in the browser requires the Adobe Flash, Microsoft Silverlight or Google Widevine plugins. These plugins use non-interoperable file formats, protocols and DRM key systems, creating fragmentation. EME solves (most of) these issues, enabling premium video in HTML5 using a single file format and streaming protocol.
Now Azure Media Services allow you to deliver Http-Live-Streaming (HLS) and Smooth Streams encrypted with Advanced Encryption Standard (AES) (using 128-bit encryption keys). Media Services also provides the key delivery service that delivers encryption keys to authorized users.
Azure Media Services also provides a Microsoft PlayReady license delivery service. PlayReady is a full-featured content access protection technology developed my Microsoft that uses Digital Rights Management (DRM). It protects a content media stream during playback by using a license server that provides the decryption key needed to decrypt the media stream.
Firstly, you need to pre-encrypt Smooth Streaming file with PlayReady License, by providing us License Acquisition URL, Key ID and Content Key. You could follow this MSDN article to use Azure Media Encryptor to encrypt the Smooth Streaming file. As a output, you could further package the encrypted Smooth Streaming into HLS and DASH (See how here). You could also define how the license could be authorized to your user. Similar to AES dynamic encryption, we enable Token/IP/Open authentication service.
Which platform/devices that PlayReady SDK covers?
Azure Media Services can be used to encode, download, or stream Smooth Streaming or MPEG DASH content encrypted with PlayReady. For consuming PlayReady encrypted content, client SDKsand the PlayReady Porting Kit are available under commercial licensing terms. (PlayReady clients for Windows 8.1 Store Apps can be built using the free SDK located HERE). These client-side SDKs are not part of this preview.
This solution demonstrates a DASH stream playing in Adobe Flash. The license key is exchanged between DRMtoday's cloud service and the Unified Streaming Platform. Live or on-demand content is encrypted on-the-fly and delivered for protected playback to any device supporting the Adobe Access DRM.
Advanced Digital Broadcast (ADB) today announced that it is first to market with a commercial MPEG-DASH (Dynamic Adaptive Streaming over HTTP) implementation, making standardised video delivery via the internet a reality for the first time. The MPEG-DASH implementation, along with a Common Encryption (CENC) scheme using Intertrust Technologies’ Marlin DRM, forms part of ADB’s new, ready-to-deploy OTT solution for video service providers looking for a high quality, standards-based OTT solution.
The first OTT service which uses tivùon! technology is Infinity, from Mediaset, which went live in Italy on December 11th. Customers with existing ADB-powered HD set-top boxes (i-CAN 1850S, 2850ST, 3820T) received an automatic over-the-air software update, adding support for MPEG-DASH and allowing them to enjoy the Infinity service from day one. All new Italian i-CAN HD set-top boxes will feature the new software.
J’ai assisté hier à plusieurs présentations au SATIS, dont la « Carte blanche OVFSquad – DRMs – quel prix pour la sécurité de l’OTT ? ».
La question est importante, car tous les distributeurs de contenus en OTT sont confrontés à l’implémentation des DRM imposées par les ayants droit (pour appuyer sur un fait exprimé par les intervenants, ce n’est pas de gaité de cœur que les sites de VOD mettent en place des DRM ; s’ils ne le font pas, ils n’ont pas les films, point !).
Quelques rappels tout d’abord :
- OTT (Over The Top) veut dire en pratique diffusion en dehors des plateformes IPTV des FAI, donc directement sur Internet; cela s’applique en particulier à la VOD (Vidéo à la Demande) sur PC, Mac, tablettes et TV connectées.
- DRM (Digital Rights Management ou gestion de droits numériques) correspond à la protection du contenu par un système de licence (qui limite l’utilisation du contenu à certaines plages de temps, certains pays, certains terminaux) et un système de chiffrement des contenus (qui évite une utilisation immodérée du contenu).
- ABR (Adaptive Bitrate) correspond à des technologies de streaming qui permettent d’adapter la qualité d’image d’un flux vidéo à la bande passante disponible. L’idée est de préférer une image de moins haute définition à une image qui bloque (freeze) de temps en temps.
Le problème est d’autant plus complexe le nombre de terminaux supportés est important. Supposons que vous développiez une plateforme VOD premium, qui commercialise des long-métrages pour lesquels l’implémentation d’un système de DRM est imposée, et qui désire mettre en place une diffusion ABR. Supporter PC et Mac est relativement facile, quoi que …
How dynamic is MPEG-DASH Ecosystem after IBC 2013 ? Here is an analysis of the latest trends and an extensive industry DASH-compliant solutions directory.
While most of IBC’s buzz was generated by the shiny HEVC + 4K couple, it was a good occasion to stand back from the hype and measure how one of the most important video standards (at least for the OTT world) had spread over the industry since last year. MPEG-DASH is not sexy (let’s remember that it’s basically a collection of XML schemes), it’s a bit boring (as it’s usually demonstrated with the Big Buck Bunny that you saw not less than 2.000 times) and it’s complex – but once you go past those defaults, you might find that its potential to simplify your workflows and boost the profitability of your video service is high…
And that’s precisely what the industry has finally understood: video distributors want to streamline their workflows and save their storage budgets by reducing the number of output formats, they search for ways to build long term strategies with evolutive solutions – and all of this implies rolling away from proprietary ABR solutions like Smooth Streaming, HLS, HDS and the now defunct Widevine WVM proprietary packaging format (rest in peace), DASH’s first victim.
We are on the verge of an important inflection point for the Web. In the next few years commercial web video delivery utilizing new, international standards (DASH Media Ecosystem) will become commonplace. These standards will enable cross-platform, interoperable media applications and will transform the media entertainment industry, delight consumers and expand the nature of the Web.
The new ExpressPlay content protection solution-as-a-service makes it dramatically easier to implement DRM for Connected TV and multiscreen services, Intertrust, the company behind the solution, claims. ExpressPlay is designed for use with Marlin DRM, the open-standard content protection system, and can be used with existing Marlin-enabled connected TVs and set-top boxes. The market for this service therefore includes HbbTV-based broadcast/broadband services as well as YouView in the UK. Intertrust says ITV and BT both use the ExpressPlay service for their DRM requirements on YouView. A good proportion of the transactions on the Tivù platform in Italy use the ExpressPlay hosted service. Eutelsat KabelKiosk is going to use this cloud-based content protection.
MPEG DASH is hot news. Widely anticipated to become the 'de facto' delivery standard, this session is part presentation -- to bring you up to speed on what MPEG DASH is -- and part opportunity to ask questions of one of the instigators of the standard.
Nicolas Weil's insight:
Interesting speach by Alex Zambelli on Microsoft DASH roadmap, from the 26th minute. Development track to confirm at IBC... 2013...
To get content containing either thought or leadership enter:
To get content containing both thought and leadership enter:
To get content containing the expression thought leadership enter:
You can enter several keywords and you can refine them whenever you want. Our suggestion engine uses more signals but entering a few keywords here will rapidly give you great content to curate.
Your new post is loading...
ajouter votre perspicacité ...