Behind the scenes
Users, platforms, and developers have have forced browsers to evolve. The browser is no longer just a window to view content. It is an environment that applications execute in. It used to be that you’d open a browser, search for something, or read something, then close it down and get to work. Now, what your work is in in the browser. Browsers are open all day.
Working with HDS Bootstrap Data I’ve always been curious about the bootstrap data for HDS content. Recently, I had the chance to find out more about it and get in 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. [...]
A great overview from Michael Labriola at Streaming Media West last year. It breaks down of MPEG-DASH, why MPEG-DASH, players, and how you’d build a DASH-264 player using OSMF.
Previously I showed you how to configure the Adobe Media Server to deliver Live HTTP Dynamic Streaming (HDS). Let’s add on a feature that will allow your users to pause and rewind the live video – DVR. DVR HTTP Live Streaming DVR can be (and actually already is) configured for both HTTP Dynamic Streaming (HDS) [...]
Here is a quickie on how to use Adobe’s F4M configurator tool to create set level manifest files. The configurator is installed with AMS 5.0 and can be found in the following directory: {AMS_INSTALL}/tools/f4mconfig/configurator/ Open the f4mconfig.html file in a browser. Enter the path to your server, application and event. For example for an event [...]
