Technology

59322 readers

4428 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

185

YouTube moves to AV1 by default to the dismay of some Android users (www.androidpolice.com)

submitted 6 months ago by [email protected] to c/[email protected]

39 comments fedilink hide all child comments

Arif Dikici, who is a part of the Android Video and Image Codecs team at Google, recently announced on LinkedIn that Android will now use an AV1 decoder known as “libdav1d,” which was created by the team behind VLC.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 41 points 6 months ago* (last edited 6 months ago) (1 children)

This is not a very helpful article summary.

One of the key benefits of the codec is that it helps maintain video quality during compression and decoding, so many users are excited about the potential for higher quality AV1 video. However, not everyone is happy with the change — particularly those with older devices and midrange phones. It's mostly newer higher-end phones that have hardware decoding support for AV1, so those with midrange devices and older flagships may have to rely on software decoding now that YouTube has opted in to the libdav1d decoder. Many of these Android users have expressed concern over how the change will impact their battery life if it means a move away from hardware-accelerated decoding.

[–] [email protected] 28 points 6 months ago (3 children)

This is not a very helpful article summary.

Sorry it wasn't meant to be. I just thought it was funny that they're taking advantage of VideoLAN's library (which is presumably open source) rather than their own.

[–] [email protected] 13 points 6 months ago (1 children)

They are and it is. This was anounced two months ago, though i didnt find any articles about google paying for or directly contributing to videolan for the use of it.

https://www.androidauthority.com/android-update-av1-videos-3420418/

[–] [email protected] 13 points 6 months ago

Looks like it might be inferred by this:

https://www.videolan.org/projects/dav1d.html

About

dav1d is a new open-source AV1 decoder developed by the VideoLAN and FFmpeg communities and sponsored by the Alliance for Open Media.

https://aomedia.org/membership/members/

Founding Members:

Amazon
Apple
Cisco
Google
[etc]

It is good that Google is acknowledging that a decoder made by someone else is better than their own by switching to it though.

[–] [email protected] 6 points 6 months ago* (last edited 6 months ago)

AV1 is based on VP9. Google made VP9 and it's open source and royalty free.

Google just joined the Alliance for Open Media and gave their VP9 as a starter for AV1 instead of making some other successor called VP10 or something on their own.

During development of AV1 Google contributed a lot to libaom, the reference implementation in C++, but since this codebase grew together with the codec it is not the most clean design. Also the reference implementation benefits from being clear more than being fast.

Therefore, instead, these days the later projects rav1e (encoder in rust, started by Xiph Foundation) and dav1d (decoder in C, started by the VideoLAN non-profit) are the fastest, because they started from a green field approach when the wire-format for AV1 was mostly fixed and they focused on speed.

I think overall Google's stance on the Alliance for Open Media makes sense. As part of the new media streaming techno bubble they (as well as Amazon, Facebook, even Microsoft) have an interest in getting an interoperable royalty free codec into the market, and spread it as far as possible, to avoid the rent seeking behaviour of the old guard, Moving Picture Experts Group (MPEG) from Hollywood and similar groups. For every device that wants support for H265 the OEM has to pay a license of around 1 dollar currently.

[–] [email protected] 2 points 6 months ago

I would guess some Google devs have contributed to it.