Video Breakthroughs
242.6K views | +0 today
Follow
Video Breakthroughs
Monitoring innovations in post-production, head-end, streaming, OTT, second-screen, UHDTV, multiscreen strategies & tools
Curated by Nicolas Weil
Your new post is loading...
Your new post is loading...
Scooped by Nicolas Weil
Scoop.it!

Hippo Media Server : NodeJS based HTTP server for MPEG DASH and Smooth Streaming media

Hippo Media Server : NodeJS based HTTP server for MPEG DASH and Smooth Streaming media | Video Breakthroughs | Scoop.it

The Hippo Media Server is a simple, standalone HTTP server designed to simplify the delivery of MPEG DASH and Smooth Streaming media. MPEG DASH and Smooth Streaming are both protocols for HTTP-based adaptive streaming. With adaptive Streaming, a media presentation is served to streaming clients as a sequence of small media segments (each segment containing typically 2 to 10 seconds of audio or video). Each segment is accessed over HTTP with an individual URL. In order to serve an adaptive streaming presentation with a regular HTTP server like Apache, Nginx or other populare HTTP servers, one needs to split the original media files into small individual files, one for each segment, so that they can be accessed through separate URLs. This can be very difficult to manage. The Hippo Media Server implements a simple URL virtualization scheme: instead of mapping each URL to a file in the server's filesystem, each URL consists of a pattern, which is parsed by the server when it handles a request, and from which it can locate the appropriate portion of a file in the filesystem. This way, a single media file containing the media data for the segments can be represented as discrete URLs.

No comment yet.
Scooped by Nicolas Weil
Scoop.it!

Realizing CRM in the broadcast industry — by using the second screen [EBU whitepaper, PDF]

Realizing CRM in the broadcast industry — by using the second screen [EBU whitepaper, PDF] | Video Breakthroughs | Scoop.it

Impressive whitepaper on using edge technologies to provide a quality feedback channel from TV second screen apps : audio watermarking, Node.js, Hadoop, Redis, Flume, Grails, Sqoop... all this in the Amazon EC2 cloud for scalability. Respect !

No comment yet.
Scooped by Nicolas Weil
Scoop.it!

HDS Bootstrap Data

HDS Bootstrap Data | Video Breakthroughs | Scoop.it

I’ve always been curious about what is contained in the bootstrap data for HDS content. Recently, I had the chance to find out and do some fun development with Node.js. We’ve been kicking around the idea of building a tool set for Adobe Media Server using Node.js and possibly socket.io. Last weekend we got some of the ideas going and one of those was parsing the hds bootstrap data created when content is packages for HDS delivery.

 

The bootstrap data can live in a couple of places:

In the <metadata> node of an F4M fileIn an external .bootstrap file

The .bootstap file contains binary data and the F4M file contains the same binary data that has been Base64 encoded. So, getting to the data is pretty trivial – either read in the .bootstrap file or un-encode the string in that is in the F4M. Getting to the data contained in the bootstrap binary data is the fun part.

No comment yet.