Managing Transition to HEVC/VP9/AV1 with Multi-Codec Streaming
•Download as PPTX, PDF•
2 likes•716 views
Video streaming is in transition towards the next generation of video codecs, offering to double the quality while lowering the required bandwidth. As the successor crown to the ubiquitous AVC/H.264 is still up for grabs, major content providers and device manufacturers are throwing their weights behind competing formats - HEVC/VP9/AV1 - leading to market fragmentation, specifically within web environments. To deal with this challenge, OTT services need to support multiple codecs in an efficient way. In this presentation, we will discuss how to evaluate the benefits and the tradeoffs of embracing these next generation compression technologies in your media workflow.
Recommended
Recommended
More Related Content
What's hot
What's hot (19)
Similar to Managing Transition to HEVC/VP9/AV1 with Multi-Codec Streaming
Similar to Managing Transition to HEVC/VP9/AV1 with Multi-Codec Streaming (20)
More from Bitmovin Inc
More from Bitmovin Inc (20)
Recently uploaded
Recently uploaded (20)
Managing Transition to HEVC/VP9/AV1 with Multi-Codec Streaming
- 1. Managing Transition to HEVC/VP9/AV1 with Multi- Codec Streaming
- 3. Codec landscape h.264/AVC h.265/HEVC VP9 AV1 Hardware support Yes Yes Yes In development Browser support Mobile platforms Coding Performance Good High High Very High Royalties Non-free Non-free unclear Free Free
- 4. Survey - Currently used video codecs
- 5. Survey - Planned to be used video codecs
- 6. New Codec Value ● Quality Improvements ● Bandwidth Savings ● Storage Savings Customers want: Better quality visuals (4K, HDR) Better quality when mobile Better streaming reliability Better bandwidth to homes, but increased usage Operators want to reduce transmission costs More video content available? Operators need to reduce costs on storage
- 8. Not all “next-gen” codecs supported on all devices and browsers!
- 9. Browsers Market Share & Codec Coverage
- 10. Encoding Challenges ● New and Next-Gen codecs are harder to encode ● Should you encode all your assets to all your codecs? ● What benefit will this have?
- 11. Encoding Decisioning ● Is an asset likely to cross a threshold that justifies an additional encode? ● Has an asset crossed a threshold of viewership that justifies an additional encode? ● Validate your real-world use: did customers watch the new codecs?
- 12. Analytics are Critical ● Understand your audience: what devices comprise your unique user base ● Understand your content: what assets will generate enough volume to benefit from additional codecs
- 13. Playback Challenges ● How to select the right asset for the environment? ● How do I configure the player?
- 14. Player Setup ● Give your player everything (all codecs you have made for the asset) ● Query browser capabilities, not browser versions
Editor's Notes
- History: 2003: AVC changed everything but royalty encumbered 2010: Google bought On2 and open-sourced their video codec as VP8 2013: HEVC version 1 finished + VP9 also frozen 2015: HEVC Advance (in addition to MPEG LA) 2015: AOM is formed to work on AV1
- Chrome 57% Safari 16% Firefox 7% Edge 2%
- Multi-codec: bandwidth/quality/storage: Quality: customers demand for better quality is increasing: Not just visual quality for home scenarios, with big TVs; better quality when on mobile on shiny new devices. Bandwidth: customers have more bandwidth available, but operator costs for streaming more HQ content is increasing Storage: content needs to be stored, in origins, CDNs, etc. New codecs help reduce storage costs, by reducing file-sizes. Reach? Not all end-points can do the new codecs yet.
- Mention Google using VP9 for YouTube (only 4K)
- Does an asset have velocity to go viral (certain volume of views in a time period, not necessarily crossed the practical threshold yet) Use analytics to make sure that your customers are seeing the new codecs
- Browser capabilities change faster than it makes sense to update your configuration Don’t depend on identifying the browser