ffmpeg-build-script VS rav1e

Are there any plans to update agentdvr to support ffmpeg-shared builds v6? The ffmpeg build script for linux uses a modified version of this script https://github.com/markus-perl/ffmpeg-build-script Looks like he made a recent one with ffmpeg 6.0 support(v1.44)

It's straightforward to compile ffmpeg with libfdk_aac support to be sure quality remains high, especially e.g. build scripts.

After quite a bit of searching around I was unable to find a simple way of getting a build of FFMPEG with all the different AV1 encoders, and building manually would mean I'd have to go get all the libraries that are enabled by default in say, Ubuntu's FFMPEG repo. So I took it into my own hands and modified this build script and added rav1e to the build in my fork here.

install of ffmpeg. I've started using github.com/markus-perl/ffmpeg-build-script because, why re-invent the wheel

I'm currently using this build script so that I can use svt-av1, but I wan't to give rav1e a shot and it's not included. Does anyone know of somewhere I can get ffmpeg compiled with rav1e, or a relatively simple way to do it myself with all the other codecs that build script supports?

These days the situation is much better, but you really want FDK-AAC for best quality (it's proper Fraunhofer code released as Open Source for the Android project, and now widely compatible on all platforms). You can find a standalone front end in the repos, but I prefer to build ffmpeg with support for it for more flexibility. (The ffmpeg built in default aac encoder is still noticeably worse, despite it's improvement a few years ago.)

Sure. You'll see it very often in codec implementations. From rav1e, a fast AV1 encoder mostly written in Rust: https://github.com/xiph/rav1e/tree/master/src/x86

Large portions of the algorithm have been translated into assembly for ARM and x86. Shaving even a couple percent off something like motion compensation search will add up to meaningful gains.

Or the current reference implementation of JPEG: https://github.com/libjpeg-turbo/libjpeg-turbo/tree/main/sim...

Again, if anything AOM would be the one restricting licenses to AV1 (if they chose to) except AOM has stated and also published AV1 in a way to allow license free access to development (which allows people to make forks of the official build like it's open source) and usage. (1)(2) I don't see why they would suddenly change this.

You can speed up the sampling process with --vmaf n_subsample=5, which in my experience works more accurately than either 2 or 4, possibly due to this bug/feature present in multiple encoders. You might also need to manually set the number of threads used for VMAF calculation with --vmaf n_threads=16, but YMMV.

That remember me of https://github.com/xiph/rav1e which is an AV1 encoder

I put in the request for ffmpeg passthrough mastering-display data a few years ago and haven't heard of any support yet.

It's getting there.. Initial steps for FFmepg: https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=8444 rav1e: https://github.com/xiph/rav1e/pull/3000

It's entirely possible to re-use bits of other HW encoders for the first pass (motion estimation, etc).