New Flash DRM Comes With Output Control

drm-thumbnail

Adobe has introduced a new version of its Digital Rights Management (DRM) solution, dubbed Flash Access 2.0, that aims to help content providers to monetize premium video through advertising, rental and subscription models. Flash Access 2.0 makes it possible to define a number of different usage rules for a single piece of content, so that vendors can combine a number of these models without having to build out separate video offerings.

The latest version of Adobe’s DRM contains a number of security features that are meant to provide confidence to Hollywood studios and other content providers, including the ability to detect rogue clients that could be used to copy content. The system will also monitor if users change the date and time settings on their machines to extend the typical 24 to 48 hour viewing periods for rented content, and allows anonymous access to content through authentication codes to offer owners of Blu-ray discs access to additional online clips.

One feature that will likely be controversial is Flash Access 2.0’s capability to utilize output controls on Windows systems. Content owners can use this feature to check whether a user has a display that adheres to a copy protection standard called High-bandwidth Digital Content Protection (HDCP). HDCP was developed by Intel and is meant to prevent users from capturing HD signals through unauthorized devices. The result of this being implemented in Flash mean that only users with new, compliant monitors get to see the full HD version of a Flash stream or download, while others have to make do with a lower-quality version.

Adobe is also going to showcase HTTP streaming and its Open Source Media Framework at Streaming Media East. One of the new ways companies can utilize the Open Source Media Framework is the OSMF App Studio, a drag-and-drop media player solution that will be launched by Kickapps tomorrow.

Picture courtesy of Flickr user rebopper.

Related content on GigaOm Pro: Making Movies Mobile (subscription required)

loading

Comments have been disabled for this post