Executive Summary: Now might be the time to consider phasing out the lowest quality streams in your encoding ladder to reduce encoding and storage costs. Check your server logs to determine consumption of these streams before doing so.
Overview and Discussion: All streams in your adaptive group cost money to encode, store, and administrate, even low-quality streams. A recent discussion with an encoding professional at online video platform (OVP) Kaltura indicated that the company’s default lowest quality stream for their clients is 640×360@400 kbps (video only). Though clients can request a lower quality streams, like those recommended in TN2224 (below), Kaltura doesn’t recommend them out of hand.
Interestingly, the discussion started after the Kaltura executive, who attended the Streaming Learning Center webinar on Content Aware Encoding, asked webinar host Jan Ozer why he still recommended a 640×360 stream. The executive stated:
Concerning 360p – yep, you are right, it’s time to question whether it is relevant. The fact that ladders still have frame sizes lower than 360p, does not really mean that it is actually used in many cases. From my experience there is almost no use for frame sizes lower than 360p. Therefore it is a time to question 360p too.
The Kaltura exec then shared. “Our default encoding set is:
There are no renditions (‘flavors’ in Kaltura terminology) smaller than 360p in the default flavor set, and there are very few customers that ask for smaller flavors. Therefore I know for sure that Kaltura serves very few renditions that are smaller than 360p.”
There are many reasons why streams smaller than 360p are not being consumed. Mobile bandwidths have increased to the point where 400 kbps over 3G or 4G is almost assured, and even the smallest mobile device has a screen that’s larger than 640×360. For example, the iPhone 4 has a 960×640 resolution screen. Not all videos are useful at very small resolutions with reduced frame rates, so few viewers may decide to access them for playback under these conditions.
As a counterpoint, however, Netflix recently shared a custom encoding ladder that included a 320×240 stream at 150 kbps. This is the stream on the right in the table below; the stream on the left was from the standard encoding ladder Netflix deployed before instituting per-title encoding parameters.
The bottom line is that you may be able to reduce encoding and storage costs without stranding any potential viewers. The obvious first step is to check your own server logs to check how many streams in lower than 360p configurations are being consumed.
1. Identify the streams in your encoding ladder.
2. Check your server logs to identify streams with very low consumption rates.
3. Consider how many potential viewers eliminating these streams would strand without an alternative, and the potential value of those viewers.
4. If the numbers are low for any streams, particularly at the low end, consider eliminating them from your encoding ladder.
How Netflix Pioneered Per-Title Video Encoding Optimization, Streaming Media Magazine, January 14, 2016
Udemy Course: Encoding for Multiple Screen Delivery, www.udemy.com, 18 lessons, 2.5 hours of instruction
Apple Changes Encoding Recommendations for HLS, Streaming Media Magazine, April 5, 2014
About the Streaming Learning Center: The Streaming Learning Center is a premiere resource for companies seeking advice or training on cloud or on-premise encoder selection, preset creation, video quality optimization, adaptive bitrate distribution, and associated topics. Please contact Jan Ozer at firstname.lastname@example.org for more information about these services.