After pushing AV1 codec, Google goes after Dolby with HDR and audio standards

Enlarge[1] / The Alliance for Open Media logo.Alliance for Open Media

Google can do basically whatever it wants regarding video and web standards. YouTube is the world's most popular video site. Chrome is the world's most popular browser.

Android is the world's most popular operating system. Anything Google wants to roll out can immediately have a sizable user base of clients, servers, and content. From there, it's just a matter of getting a few partners to tag along.

This is how Google's next-generation AV1 video codec[2] is being rolled out, and next, Google is setting its sights on HDR and 3D audio standards. Protocol's Janko Roettgers[3] has a report on "Project Caviar," Google's plan to take on Dolby and create royalty-free alternatives to its HDR standard (Dolby Vision) and its 3D audio standard (Dolby Atmos). Dolby's old-media business model relies on royalty fees from hardware manufacturers and support from content creators.

The company's technology is deeply embedded in movie theaters, Blu-rays, and more modern streaming companies like Apple are big backers[4] of Dolby technology. That all costs money, though, and Protocol's report says £50 streaming sticks end up having around £2 of that price tag go to Dolby. Surround sound has been a movie feature forever with various numbers of front, back, and side speakers, but Dolby Atmos adds height into the equation.

If you take a 5.1 or 7.1 speaker setup--that's three front speakers, two back, a subwoofer, and for 7.1, two side speakers--Dolby Atmos adds four overhead speakers into the mix, allowing sound to pan overhead of the viewer. Atmos is supported by Apple, Netflix[5], HBO Max, and Disney+. Google is tackling Dolby via the "Alliance for Open Media" standards group, which counts Amazon, Apple, Arm, Google, Intel, Meta, Microsoft, Mozilla, Netflix, Nvidia, and Samsung in its "founding members" group.

This is the same group behind the AV1 standard, which grew out of Google's purchase of On2[6] and the open sourcing of its video codec. Neither Dolby Vision nor Atmos competitors require new codec development. Google's strategy is mostly about standardizing a way to ship audio and video data that doesn't involve paying Dolby and branding it well enough to compete.

To start, the group already has specs for an "Immersive Audio Container[7]" published on the web, which describes itself as a "codec-agnostic audio bitstream format to deliver three dimensional sound fields that can be used for multichannel sound playback." For HDR, the group wants to adopt the HDR10+[8] standard, which was originally cooked up by Samsung but lacks content. It's not yet known what consumer-facing brand these standards will be for. That's a big deal, since the name "Dolby" still holds a lot of sway with home theater enthusiasts, and that means streaming apps can market the Dolby brand as a premium add-on, creating demand for the standards.

Few companies have enough sway over the media space to push a new standard, but Google is one of them.

As we've already seen with AV1, pushing support into YouTube, Android, Chrome, and any hardware manufacturers[9] looking to license access to YouTube is a powerful cudgel.

References

  1. ^ Enlarge (cdn.arstechnica.net)
  2. ^ AV1 video codec (arstechnica.com)
  3. ^ Protocol's Janko Roettgers (www.protocol.com)
  4. ^ big backers (www.apple.com)
  5. ^ Netflix (about.netflix.com)
  6. ^ purchase of On2 (arstechnica.com)
  7. ^ Immersive Audio Container (aomediacodec.github.io)
  8. ^ HDR10+ (arstechnica.com)
  9. ^ any hardware manufacturers (arstechnica.com)