The Machinimatogr...
Follow
Find tag "DRM"
1.9K views | +0 today
The Machinimatographer
Making machinima, mastering the virtual camera and posting what helps me grow.
Curated by Asil
Your new post is loading...
Your new post is loading...
Rescooped by Asil from Video Breakthroughs
Scoop.it!

Intertrust claims it is now easier to use Marlin than other DRMs

Intertrust claims it is now easier to use Marlin than other DRMs | The Machinimatographer | Scoop.it

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.


Via Nicolas Weil
Asil's insight:

Interesting read if you're planning to self-publish your work.

more...
No comment yet.
Rescooped by Asil from Video Breakthroughs
Scoop.it!

A Buyer's Guide to Multiformat Streaming Media Servers

A Buyer's Guide to Multiformat Streaming Media Servers | The Machinimatographer | Scoop.it

MPEG DASH is the biggest factor to consider -- or is it? Here are the key features to know about before making a decision.

 

2012 saw significant progress on several fronts for media servers. Some changes were small but important, such as naming conventions -- Adobe dropped Flash from its media server names, for instance -- while others were much more impactful for the industry going forward -- almost everyone agreeing that Dynamic Adaptive Streaming over HTTP, DASH for short, was worth supporting.

 

In this year's Buyer's Guide, we'll take a look at a few key features you'll need to know about to make an informed decision.


Via Nicolas Weil
Asil's insight:

Just in case you're streaming yer own content.

more...
No comment yet.
Rescooped by Asil from Video Breakthroughs
Scoop.it!

W3C proceeds with Web video encryption despite opposition

W3C proceeds with Web video encryption despite opposition | The Machinimatographer | Scoop.it

The Web standards group is going ahead with its Encrypted Media Extensions technology despite some opposition, arguing it's a step in the right direction.

 

The World Wide Web Consortium has decided to go ahead with a technology that will let companies like Netflix stream encrypted video using Web sites -- against the wishes of the Free Software Foundation, Electronic Frontier Foundation, and 25,600 petition signatories.

 

The Web standards group announced the move Thursday, to nobody's surprise. Entertainment-industry players had approached the group three years ago to discuss the technology, Microsoft has been helping develop it, and Google already has built the specification, called Encrypted Media Extensions (EME) into Chrome.

 

The standard doesn't actually handle encryption and digital rights management (DRM) to govern who gets to see or copy video. Instead, it provides a standard mechanism that lets a browser call upon a plug-in that handles the work. In other words, it enables encryption but doesn't do the encryption itself.

 


Via Nicolas Weil
more...
Nicolas Weil's curator insight, May 11, 2013 5:59 AM

Ars Technica's Opinion : "DRM in HTML5 is a victory for the open Web, not a defeat" http://goo.gl/BNHh1

Rescooped by Asil from Video Breakthroughs
Scoop.it!

HTML5 Encrypted Media Extensions W3C Working Draft

HTML5 Encrypted Media Extensions W3C Working Draft | The Machinimatographer | Scoop.it

This proposal extends HTMLMediaElement providing APIs to control playback of protected content.

 

The API supports use cases ranging from simple clear key decryption to high value video (given an appropriate user agent implementation). License/key exchange is controlled by the application, facilitating the development of robust playback applications supporting a range of content decryption and protection technologies.

 

This specification does not define a content protection or Digital Rights Management system. Rather, it defines a common API that may be used to discover, select and interact with such systems as well as with simpler content encryption systems. Implementation of Digital Rights Management is not required for compliance with this specification: only the simple clear key system is required to be implemented as a common baseline.

 

The common API supports a simple set of content encryption capabilities, leaving application functions such as authentication and authorization to page authors. This is achieved by requiring content protection system-specific messaging to be mediated by the page rather than assuming out-of-band communication between the encryption system and a license or other server.


Via Nicolas Weil
more...
No comment yet.