Qualcomm recently unveiled its shiny new Snapdragon 888 system-on-chip (SoC), which will appear in the next swathe of flagship Android handsets. However, there has been a significant omission, in the form of on-chip support for the AV1 codec.
Considering the hype for AV1, a product of Google and Netflix’s work in the Alliance for Open Media (AOMedia), it is a baffling misstep.
Speaking to CNET, Qualcomm VP of product management Judd Heape said that schedule and cost considerations meant AV1 couldn’t be implemented this time round. Heape said that upcoming designs would support it, but didn’t specify further.
This means that the leading developer of Android silicon has not implemented a codec that was finalized in 2018, either because the development process took too long or because it realized that the cost of including the extra silicon would make the Snapdragon 888 too expensive. Either way you slice it, that is not good news for AV1.
In terms of the codec choices, there are essentially two camps – the MPEG family and the rest. In the MPEG realm, we moved from H.264 (AVC, MPEG-4 Part 10, 2003) to H.265 (HEVC, MPEG-H Part 2, 2013), and have now just wrapped up H.266 (VVC, MPEG-I Part 3, 2020) as well as EVC (MPEG-5 Part 1, in theory 2020) and LCEVC (MPEG-5 Part 2, 2020).
Royalties appear to be the reason behind the fragmented approach, which has resulted in three releases in 2020. MPEG has always charged royalties, but this causes major headaches in the adoption of HEVC. So, this time, attempts have been made to create royalty free options. VVC (H.266) looks like a straightforward update to HEVC and retains the same traditional royalty approach.
EVC has a Baseline and a Main profile, where the former is royalty-free, while the latter performs better but does have royalties. LCEVC takes this a step further, by only having one profile but being “cheaper than royalty free”, according to V-Nova, back in August.
Of course, that has yet to be determined, and as we noted back in October, V-Nova is currently devising with customers and IP lawyers how to position its licensing strategy at an aggressively low price point, without appearing to devalue the reputations of partner companies involved in LCEVC.
Crucially, EVC and VVC increase the complexity of the encoding and decoding, meaning that you need to update the hardware to support this – that is, make the chips more powerful. However, LCEVC promises to only require software changes, and not hardware, which means that video services should be able to adopt it without having to wait for the device makers to implement it – getting by on established HEVC designs.
This brings us to the non-MPEG ecosystem, which is basically a party of one, at this stage. AOMedia’s AV1 is the replacement for the Google-backed VP9, which was the rival to HEVC. AV1 is now meant to be an alternative to the new generation of MPEG codecs, or perhaps rather, whichever of the three gains most traction.
Considering that one of the big selling points of AV1 has always been the lack of royalties (or claimed lack of royalties as some would testify), then it does seem like LCEVC is the most direct rival. So, returning to Qualcomm’s lack of AV1 support in the Snapdragon 888, can we draw any conclusions?
Well, as far as we can tell, the Samsung Galaxy S4 was the first mobile phone to support HEVC, and was launched in April 2013. It used the Snapdragon 800 SoC, as well as Samsung’s own Exynos 5 Octa 5410. Qualcomm had announced the Snapdragon 800 at CES 2013, meaning that it was in a flagship Android device within 3 months – technically in the same month that the HEVC standard received its first approved sign-off.
At MWC 2012, Qualcomm had a demonstration Android tablet, using a Snapdragon S4 SoC, which showed H.264 versus H.265 processing, and claiming a 50% bitrate reduction for HEVC. This means that we had a working demonstration some 14 months before the standard was finalized, and then an SoC in a flagship smartphone in the same month that the first proper version of the standard was completed.
Now, casting our eyes towards AV1 proper, we’re left scratching our heads – for Qualcomm at least. Back in April, Mediatek launched its Dimensity 1000 5G SoC supporting AV1, specifically for YouTube streams at 4K resolutions and 60 frames per second. That SoC had been announced in November 2019.
Rockchip had an SoC with AV1 support back in April 2019, the RK3588, although we haven’t found a smartphone that has adopted that chip yet. Rockchip was likely targeting Chromebooks with this SoC, as it has had little luck in penetrating the high end smartphone market. However, an AV1 first suggests that it at least has the technical chops to do so.
Looking away from smartphones, Xilinx FPGAs have supported AV1 since January 2019. Allegro announced its AL-E210 encoders in April 2019, which we understand to have been the first encoder to support AV1. Realtek unveiled an integrated circuit design in May 2019, then followed that up with an SoC for set tops in June 2019. Amlogic published a roadmap that showed three AV1 set top SoCs due by the close of the year.
In 2020, Intel, AMD, and Nvidia all announced support for AV1, across their desktop and server-oriented products, and both Samsung and LG used CES to announce support for AV1 in their flagship TV designs. Most recently, in terms of hardware, Roku added AV1 to its Roku Ultra designs.