The Machinimatographer
2.1K views | +0 today
Follow
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!

10 Reliable HTML5 Video Players for Websites

10 Reliable HTML5 Video Players for Websites | The Machinimatographer | Scoop.it
Recently Flash players were extremely popular, but now they are going with the times. More often users choose HTML5 solutions. Choose your very best HTML5 video player!

Via Nicolas Weil
more...
Ludovic Bostral's comment, May 30, 2013 2:36 AM
video.js is very good, open source, it is our choice here
James Johnston's curator insight, May 30, 2013 8:06 AM

A cool list of HTML5 video players you can use on your sites.

James Johnston's comment, May 30, 2013 6:05 PM
I love open source, I always try and use open source when I can.
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!

Streaming Video to HTML5 with Media Source Extensions, DASH and DASH.js

my presentation from cf.objective 2013 on building a DASH-264 player in HTML/JavaScript

Via Nicolas Weil
Asil's insight:

For those looking to delve deep into the nerd-stream.

more...
Nicolas Weil's curator insight, May 16, 2013 6:34 PM

Excellent work shared by Jeff Tapper, as usual !

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.