Add support for AV1 itags.

[FireMasterK]

• [x] I carefully read the contribution guidelines and agree to them.
• [ ] I have tested the API against NewPipe.
• [ ] I agree to create a pull request for NewPipe as soon as possible to make it compatible with the changed API.

I don't really like this approach, since this can include 60 fps streams as well as HDR streams... #488 is the ideal solution, but there's a lot of work to be done on the NewPipe app side which I know nothing about

Closes #672

[litetex]

Tested this on a experimental branch with #488 in the NewPipe app. https://www.youtube.com/watch?v=kJQP7kiw5Fk worked fine (maybe a non AV1-codec was used - idk). However videos like https://www.youtube.com/watch?v=aqz-KE-bpKQ failed on higher resolutions (>1080p):

See also https://github.com/TeamNewPipe/NewPipeExtractor/pull/488#issuecomment-904741877

TL;DR Would not recommend merging currently

[FireMasterK]

Discussion continued on https://github.com/TeamNewPipe/NewPipeExtractor/pull/488#issuecomment-904766848, this behavior happens on high-resolution WEBM and AV1 streams, and even HDR streams and is to be fixed on the App side, and not the extractor.

[ghost]

Unfortunately that means until #488 is merged this won't be merged?

[FireMasterK]

Neither of these PRs can be merged currently as there is work to be done in the app to adapt for these changes.

[ehyoitsdavid]

Android 14 will force the support of software AV1 decoding, even if the hardware does not support. Will you consider supporting it in NewPipe (hopefully) by the time Android 14 is released to general public?

[ag2s20150909]

https://corp.mediatek.com/news-events/press-releases/mediatek-to-enable-cutting-edge-av1-video-codec-technology-on-android-smartphones