It is possible to overstate the complexity of multi-screen video, but the absolute number and types of display devices are indeed increasing, which means that efforts to promote standards and greater simplicity address a live concern. A current initiative, playing out within the MPEG-DASH Industry Forum, among other places, to enable digital rights management (DRM) interoperability is a case in point.
Building his case for a common downloadable DRM framework that is independent of but compatible with CE devices of all shapes and sizes, Tranter (VP at NDS, now part of Cisco) names three standards that could play a foundational role, namely:
* Simulcrypt—the long-standing DVB protocol published by ETSI used to enable multiple key management systems; * MPEG-DASH—Dynamic Adaptive Streaming over HTTP (DASH), which became an ISO standard in late 2011; and * UltraViolet—an authentication and cloud-based rights system deployed over the past few years by a consortium of studios, manufacturers and service providers.
Creating technically seamless applications has always been a pretty tough task in terms of time and complexity. Moreover, helpful data is scattered across multiple sources. This also applies to iOS video applications development. In this post, we have aggregated the most vital and helpful information on efficient use of all the features of HTTP Live Streaming, with detailed data source list. These materials are prerequisite to anyone who intends to ensure high quality of viewing experience.
This proposal extends HTMLMediaElement to enable playback of protected content. The proposed 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. No "DRM" is added to the HTML5 specification, and only simple clear key decryption is required as a common baseline.
After the first post which give an overview and explain how set-up a WAMS environment, I continue the discovery of WAMS World (sorry for the pun ). In this post, we will see how we can transform a video from a input format to another format. It’s possible to generate multiple output format or to encrypt the video. But we will see it in a next posts.
First of all, we need to understand the different terms we will use in WAMS. In my example, I want to obtain this workflow : 1. create an asset : an asset is an entity which contains all informations on the video (metadata, …) 2. upload a file in blob storage and associate to the asset 3. apply a job on the asset. A job is composed by one or more tasks. A task is an action : eg: encoding with protection. To run the task, we use a MediaProcessor. 4. after the job completed, deliver the video via the Azure CDN.
First things first – What is a Mezzanine format? A mezzanine format is a mid-rez working copy of your video asset which is of sufficient quality to generate your highest output, but small enough to move around, archive, and work with. The goal is to free up resources once all major edits and processing are completed. The source of your mezzanine format can come from many places. When encoding from a tape with a fully completed asset, the encode can be the mezzanine file. When exporting from a non-linear editor such as Final Cut or Avid, the format chosen as the output can be a mezzanine. The point is, all major editing and processing is completed in the highest format available and this smaller asset can take it from here.
Robin Good: Pivotshare is a web platform which allows you to create a branded web site where you can curate, promote and sell your best digital media video and audio files.
The service accepts .mp4, .mov, .avi and .mp3 files for upload and it lets you set the price and the business model (subscription or pay-per-view or a combination of both) that you want to use.
On Pivotshare you can brand your channel with your logo and customize its look and feel, and you can also "bookmark" specific "spots" inside your audio and video content.
Content on PIvotshare is accessible by both desktop computers as well by smartphone and tablet devices and it has the ability to memorize, for the user, where a sesson is left, so that it can be picked up next time he logs in.
You can set up some of your content to be free and some of it to be accessible only by paying for it. Each channel can be fueled by more than a contributor and you are free to decide who will team up with you.
There are two delivery formats available to curate and organize your key assets: a) the Showcase (ideal for ten items or less) and b) the Library (for collections of 50 or more items).
Revenue-wise Pivotshare takes 30% from a Channel’s revenue, and passes the rest to the Editor and Contributors of that Channel.
For most players, simply enabling OSMF's default Dynamic Streaming is sufficient. For some players, customizing the HTTP Dynamic Streaming (HDS) adaptive bitrate algorithm may be desired, but note that this is an advanced task.
Below is a representation of the customizable areas of the adaptive bitrate algorithm. The rest of this article describes the various levels of customization, in order of complexity, starting with simple parameter customization and ending with the complete replacement of the adaptive bitrate algorithm.