Per-Title Encoding 2022

My article, Buyers’ Guide to Per-Title Encoding is up on Streaming Media.

Per-title encoding is one of the simplest and least expensive ways to reduce streaming bandwidth, increase viewer QoE, or accomplish both. It’s becoming a standard feature in cloud-encoding services.

The article begins with an overview of what per-title encoding is and why it’s important. Then it compares per-title encoding controls, and comparable configuration options, and ends with a section on how to compare per-title services.

It’s a great way to learn why you should care about per-title encoding and how to compare the various services.

About Jan Ozer

Avatar photo
I help streaming and video technology companies solve complex technical and market-facing problems in practical business terms. Engagements range from fixed-scope audits and codec strategy reviews to product testing and technical content that helps customers, prospects, and internal teams connect technical performance to business outcomes. I am a contributing editor to Streaming Media Magazine, writing about codecs and encoding tools. I have written multiple authoritative books on video encoding, including Video Encoding by the Numbers: Eliminate the Guesswork from your Streaming Video (https://amzn.to/3kV6R1j) and Learn to Produce Video with FFmpeg: In Thirty Minutes or Less (https://amzn.to/3ZJih7e). I have multiple courses relating to streaming media production, all available at https://bit.ly/slc_courses.

Check Also

Netflix’s Masterclass: Engineering Live Streaming at Scale

As a technologist and part-time couch potato, I appreciate Netflix on many levels. During the …

Inside AV2: Architecture, Performance, and Adoption Outlook

Three recent Alliance for Open Media presentations on YouTube shed new light on AV2’s performance …

The Future of Multiview: Client, Server, and Build Your Own (BYOMV)

Multiview, or the ability to view multiple live feeds simultaneously, is quickly becoming a must-have …

Leave a Reply

Your email address will not be published. Required fields are marked *