sysidentpy VS rav1e

Link para o site da documentação: SysIdentPy - SysIdentPy

I'm the only maintainer, but I keep including new features (some exclusives, like the algorithm I've developed in my thesis to create NARMAX models), improving the code and documentation, and fixing bugs.

benchmark codes: Welcome to SysIdentPy’s documentation! — NARMAX models

github: wilsonrljr/sysidentpy: A Python Package For System Identification Using NARMAX Models (github.com)

I built a package where you can build polynomial NARMAX models using the most used method for model selection of this class of models in the beckend. In addition, you can built NARX Neural Networks for forecasting problems (this is built on top of Pytorch) and you can use any model that have a fit/predict method (Catboost, any estimator from sklearn) in a NARX configuration to perform infinity-steps-ahead prediction. Maybe its worth a try. Here is the link of the package: GitHub - wilsonrljr/sysidentpy: A Python Package For System Identification Using NARMAX Models

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).