Created attachment 202282 [details]
Chromium 70+ and Firefox 65+ support AV1*. Let's follow in ffmpeg and vlc, so users can download and watch content locally. As decoding is more important maybe DAV1D at first then AOM at a later date e.g., after the next major/minor release.
A commit references this bug:
Date: Mon Mar 4 19:49:26 UTC 2019
New revision: 494638
multimedia/ffmpeg: enable DAV1D by default
Let package users watch AV1 content in standalone players.
Jan, since this has landed already, can we close it? Or is there anything left to do?
AV1 *en*coder is left. aom is the most complete and stable encoder compared to rav1e or SVT-AV1 but it only reached that point *after* 1.0.0. Enabling AOM option by default would imply frequent ffmpeg rebuilds due to aom updates. OTOH, ffmpeg had a lot of rebuilds recently due to ABI changes, so it may not be as bad as it seems. Going by libvpx history Google isn't particularly committed in maintaining standalone releases compared to whatever (snapshot) is bundled in Chromium (e.g., see mXY branches for Chromium XY milestones), so downstream sometimes have to patch vulnerabilities for months.
(In reply to Jan Beich from comment #3)
> ... frequent ffmpeg rebuilds due to aom updates.
This is how poudriere works around inconsistent PORTREVISION bumps. If the package version of a runtime dependency changed then all consumer packages are obsoleted in a chain reaction. I often abort build and force rebuild of direct consumers only to reduce the churn.