By way of background, Android’s initial streaming strategy centered around the Flash player, which worked acceptably well until Adobe pulled the plug on updating the Flash player for Android and other platforms. This left Google in the lurch, which it tried to fill by adding support for HTTP Live Streaming (HLS), starting officially with Android 3.0+. This approach, implemented well, would be very attractive to producers who are already serving HLS streams to iOS devices, which support HLS natively.
For the 2012 Summer Games in London, the BBC demanded that its live streams be just as resilient as its broadcast channels. Learn how it delivered on that goal.
Live video streams were key to the ambitious online user proposition for the London 2012 Olympics, and that coverage had to mirror the very high traditional broadcast standards of resilience and quality. Hear the challenges the BBC faced when designing a resilient HTTP streaming infrastructure that was designed to cope with huge volumes. Learn about the solution the BBC used during the games and hear what changes to their methodology was required to build resilience into a cloud-based infrastructure.
In the tiny, cheap computing space, the Raspberry Pi is king thanks to the $25 and $35 price tags and marketable name. Once you get into the RasPi, though, you inevitably fall down a deep, dark rabbit hole of other tiny, cheap computers.
Android has limited support for HLS (Apple’s HTTP Live streaming protocol), and device support is not the same from one version or one device to the next. Android devices before 4.x (Gingerbread or Honeycomb), do not support HLS. Android tried to support HLS with Android 3.0, but excessive buffering often caused streams to crash. Devices running Android 4.x and above will support HLS, but there are still inconsistencies and problems.
Within days of each other, Microsoft and Amazon Web Services (AWS) released mobile-friendly notification services aimed at developers. Both services make it possible to quickly and cheaply broadcast millions of messages ...
This post is the result of a sort of challenge. The objective is to create an architecture to generate, manage and deliver HTTP streaming videos using free and/or open-source tools and/or applications. It need to answer to many questions : tools must be open source or free; reliability of the platform and the ability to scale up quickly. The architecture can be split in two parts : the content preparation and the delivery. I will expose an overview for each part of the architecture. Then I will list differents tools you can use. To finish, I will give you in details the architecture I will choose to deploy. But to realize this, few or some developments can be required, the language you will use, will be your choice. The operating system will be on Linux.