Content Preparation for Adaptive Bitrate Video

Share on Facebook0Tweet about this on TwitterShare on LinkedIn17Email this to someone

By Piotr Kreglicki

Preparing ABR content takes several steps. First, the desired packaging and layer structures need to be identified. Next, content must be encoded, checked for quality, packaged, encrypted and delivered.

Choosing packaging and profiles

Packaging choice is generally driven by what devices must be supported. Not every device supports players for every type of ABR streaming technology. As a result, one should catalogue both the devices and the players that will be supported. The necessary packaging will naturally become apparent as a result.

The selection of optimal bit rates, frame sizes and frame resolutions will vary depending upon device types, connection types and encoding technology. Apple and Adobe provide excellent starting points with suggested profiles suitable for their ecosystems. However, the entire catalogue of devices, expected network connections and network costs must be considered when designing layers.

With these considerations, layer design is a balancing act between frame size, bit rate and quality. The actual encoding technology used may have the biggest effect upon quality. For example, one study performed by the MSU Graphics & Media Lab, showed that the use of x264 encoding technology saved necessary bit rates by as much as 50 percent compared to other H.264 encoding technologies at the same quality level. As a result, it is recommended that layers be designed while performing actual encoding tests with the final encoding technology.

Most packages generally contain between 16 and 24 layers. Part of layer design will require a reduction in the number of layers. It is best to select a few common native display frame sizes (such as 1080p) and then encode multiple bit rates to those frame sizes. Doing so will avoid unnecessary performance degradation on players that use software scaling.

Encoding, packaging, delivery and DRM

Each layer will require that a complete H.264 stream be encoded. With 16 to 24 layers, encoding an ABR package can easily require 20 times the processing power needed for a single H.264 stream. Fortunately, highly parallelized multirate H.264 encoding technology exists, that re-uses information across the different streams. When combined with GPU acceleration, today’s encoding systems can offer 10 or 20 times the speed of CPU-based systems.

When preparing for multiple devices, an important aspect of encoding is transmuxing, the ability to re-use encoded H.264 streams across multiple package types. This prevents having to re-encode the same bit rates simply to package the video differently. Transmuxing results in increased productivity and reduced costs.

With on-demand content, it is important to perform QC checks on the different video streams. QC may be performed visually or by using automated tools that measure quality across all of the streams.  (Note: Telestream’s Vidcheck product can be used for QC in the cloud or on premises). QC can be built into any media processing flow and can be automated.

On-demand content often requires user authentication and protection prior to playback, which requires digital rights management (DRM). When using DRM, the video must be encrypted during packaging.  The industry standard today is based on AES 128-bit encryption. DRM systems typically have subtle requirements that impacts the encoder or packager.  It is important to make sure that the selected DRM technology can indeed work with the encoder system being used.

Finally, content delivery will be performed, either as a compressed TAR file or in the native package form. Where possible, it is recommended that the entire production process (ingest, encoding, transmuxing, packaging, quality control, encryption and delivery) be combined into a single automated workflow or process flow. Manual steps will significantly slow production time and may result in errors.

Telestream’s products can automate the entire process.  This automated process can be deployed using on premises Hardware/Software solutions or can be deployed in the Telestream Cloud.

For more information go to https://cloud.telestream.net.

Share on Facebook0Tweet about this on TwitterShare on LinkedIn17Email this to someone

Be the first to comment

Leave a Reply

Your email address will not be published.


*