ab-av1 VS redb

Calculate vmaf before you encode the whole file. -> https://github.com/alexheretic/ab-av1 has a search mode with samples, the estimation of time and filesize is very good and does everything in one step

ab-av1 auto-encode with a VMAF quality target of 97-98 + a script for the deletion of files sounds like what you need.

ab-av1

My case is ab-av1, a cli for encoding videos. The local db stores cached vmaf analysis.

If the goal is space saving and a consistent visual quality rather than just having a library as AV1 for its own sake, I'd use ab-av1. Not sure how (or if) it'll handle the Opus audio channels cases, but bugs can be filed.

Try this https://github.com/alexheretic/ab-av1

Use this tool and you will get excellent results https://github.com/alexheretic/ab-av1 calculates and converts automatically calculates the vmaf and crf properly

Check this, might help you optimize the process.

I wrote redb (https://github.com/cberner/redb) using mmap, initially. However, I later removed it and switched to read()/write() with my own user space cache. I'm sure it's not as good as the OS page cache, but the difference was only 1.2-1.5x performance on the benchmarks I cared about, and the cache is less than 500 lines of code.

exposure of the redb builder functionalities.

redb has reached its 1.0 release. The file format is now gauranteed to be backward compatible, and the API is stable. I've run pretty extensive fuzz testing, but please report any bugs you encounter.

I'm just now updating the benchmarks in the readme with multi-threaded workloads :) https://github.com/cberner/redb/pull/576

redb, but that doesn't have a stable file format yet,

I also have to support web, so I'm considering a hybrid approach with a direct IndexedDB API there and something like sqlite, percy, sanakirja, or redb on native.

Nice list, but don’t forget persy, redb and sanakirja too!

check out https://github.com/cberner/redb! it is inspired by LMDB and has comparable performance, but is entirely built in rust!

Yup, the language is immature in some domains like data replication, compilation time, lifetime expressivity, not having a default async runtime and the incompatibility of all of them. But many of these domains are worked on and improved every day this is why I love this language so much. This is because there is space for improvement. I also hope that one day we will have a pure-Rust LMDB alternative that I can contribute to without fear of C.

they are, ya! I'm quite excited about that, and already have a PR open to use GATs. It's not enough to fix this issue though, because std needs to add support for LendingIterator too