FreezyLemon

If the information in that ffmpeg issue is to be believed: > After discussion with Apple this is due to the fact that they require VP9 alt-ref frames to be...

> cc @FreezyLemon , not sure if you're also looking to bring the libraries up to date as part of #5974. I'd like to, but the VP9 decoding bug is...

Is this still needed? I could take a look at this, but it looks like version updates of native libraries are done manually at the moment.

From a translator's perspective, applying the existing *custom* identifier from an English section heading seems perfectly reasonable. Basically: Just copy the ID thing when translating. Adding custom identifiers to section...

It looks like `BufRead::fill_buf` is pretty much a `peek` [equivalent](https://doc.rust-lang.org/std/io/trait.BufRead.html#tymethod.fill_buf): > When calling this method, none of the contents will be “read” in the sense that later calling read may...

I hit this too. The relevant error seems to be: `AttributeError: 'PathDistribution' object has no attribute 'name'` Which seems to be a problem with python 3.11 and the [importlib_metadata package](https://github.com/python/importlib_metadata/issues/396).

The following is a workaround that worked for me: 1. Install Python 3.9 2. Symlink `python3` to be Python 3.9 3. Rerun the bazel command

This is surprising behaviour, and I did not know it worked like that. It might be even better to max it out at 4 and give a runtime warning..

It is possible to build av1an targeting ffmpeg 6.0. It is not well documented, but you might want to set the environment variable `FFMPEG_DIR` to the directory where you have...

Can someone confirm whether compiling against R63 fixes this? The mentioned issue in the VS repo seems to have been fixed.