SVT-AV1
SVT-AV1 | distributed-transcode | |
---|---|---|
176 | 2 | |
- | - | |
- | - | |
- | - | |
- | - | |
- | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
SVT-AV1
-
Any recent comparison between the encoders, specially rav1e and SVT-AV1?
The docs mention that the unit for this option is in "frames" (not "seconds").
-
SVT-AV1 git: Neon optimizations across all processes - part2
From the pull request:
- SVT-AV1 git: Updating encoding parameters during the encoding session (RTC only)
-
Guide to Adopting AV1 Encoding
In these tests SVT-AV1 beats x265 on quality:
- FullHD: http://compression.ru/video/codec_comparison/2022/main_repor...
- FullHD 10-bit: http://compression.ru/video/codec_comparison/2022/10_bit_rep...
- 4K: http://compression.ru/video/codec_comparison/2022/4k_report....
SVT-AV1 has seen a number of speed ups in recent releases:
https://gitlab.com/AOMediaCodec/SVT-AV1/-/releases
-
10-bit and 4:2:2 Chroma Subsampling support for AV1?
I don't see this options under the "Advanced features" like for H.265/HEVC (for example). Also, adding "-input-depth 10" manually to the command line doesn't work (it doesn't recognize the parameter, despite it clearly being written here as one of them).
-
Does Handbrake publish AV1 documents?
Docs for SVT-AV1 at https://gitlab.com/AOMediaCodec/SVT-AV1/-/tree/master/Docs
-
[SVT-AV1 Git] The experimental SSIM RD tune in SVT-AV1 has been added to mainline
I find it interesting that you know the project well enough to get to the pre-compiled binaries page, yet somehow missed that the merge request explictly calls out a VMAF LOSS for the SSIM tune by several percentage points.
-
What's the status of AV1 encoding on ARM?
SVT-AV1 has no NEON.
-
My AV1 testing (Part 3)
I used the precompiled FFmpeg from SVT-AV1's git: https://gitlab.com/AOMediaCodec/SVT-AV1/-/jobs/4540276837
- SVT-AV1 1.6.0 windows x64 binaries ?
distributed-transcode
-
Guide to Adopting AV1 Encoding
Back when I still cared about saving disk space, I made a cluster of NVidia Jetson Nanos running in a docker swarm configuration [1], but honestly even when you have six computers working at once, H264 on a single computer is still often faster.
On the Jetson Nanos I was lucky to get maybe 1fps in ffmpeg using VP9. Multiply that by six boards and that's about 6fps in total; ffmpeg running x264 in software mode was getting around 11fps on a single board, not even counting using the onboard encoder chip, meaning that I was getting better performance from one board using x264 than all six using VP9.
Now obviously this is a single anecdote on specific hardware, so I'm not saying that this applies to every single case, but it's a big reason why I personally have not used VP9 for anything substantial yet.
[1] https://gitlab.com/tombert/distributed-transcode
-
Ask HN: Have you created programs for only your personal use?
I have a fairly large blu-ray collection (~300 movies, ~15 complete TV series). I rip them and serve them with Jellyfin, which works, but due to codec annoyances, I need to transcode them to run on web browsers, and the SBC I'm running Jellyfin + ZFS on is not really fast enough to transcode in real time.
Since I have a ton of little SBCs sitting around my house, I decided to write a clojure app the queues up and transcodes my movies to H264. It uses Docker Swarm to handle distribution of nodes, RabbitMQ to queue up the movies, and core.async to handle local queuing within the application, and uses the Java NIO filesystem stuff to handle any kind of atomicity.
It's hardly the "first" or the "best" at what it does, but the advantage of writing your own is of course that you can tailor it exactly to your setup, and of course it was fun to write.
https://gitlab.com/tombert/distributed-transcode
What are some alternatives?
Av1an - Cross-platform command-line AV1 / VP9 / HEVC / H264 encoding framework with per scene quality encoding
m4b-tool - m4b-tool is a command line utility to merge, split and chapterize audiobook files such as mp3, ogg, flac, m4a or m4b
rav1e - The fastest and safest AV1 encoder.
nitter - Alternative Twitter front-end
FFmpeg-Builds
polybar-clockify - Control Clockify through Polybar
aom-av1-lavish - A fork of aom-av1-psy, which is a fork of aomenc. Designed to open up the encoder for hyper-tuning and fidelity.
ppp_thing - A poorly written, minimum viable PPPoE client with session handoff between redundant FreeBSD routers
media-autobuild_suite - This Windows Batchscript helps setup a Mingw-w64 compiler environment for building ffmpeg and other media tools under Windows.
fastmod - A fast partial replacement for the codemod tool
ab-av1 - AV1 re-encoding using ffmpeg, svt-av1 & vmaf.
cmdg - Command line Gmail client