These are public posts tagged with #av1. You can interact with them if you have an account anywhere in the fediverse.
So I just ran some encoding tests for #AV1 with #Handbrake, just to see how adjusting some various settings affects the outcome. I've named the files according to the options I changed. The ones with "film grain" options had the following added to "Additional options".
film-grain-denoise=0:film-grain=FOO
This is a particularly difficult scene in Django Unchained that is prone to banding with AV1.
Source was an 8-bit 1080p Bluray.
Link: https://cloud.marcusandash.net/index.php/s/6CZ9kMnrX94LRyr
Nextcloud - A safe home for Adams family data
NextcloudGoing through some old videos and have decided to use #Handbrake to re-encode for space reduction. On this one video, I reduced it from 181.3 MiB to only 38.4 MiB, about a 79% file size reduction! Wow!
The original file was an MP4 encoded with H.264 and AAC. I re-encoded the file to #Matroska using the #AV1 and #Opus codecs. Everything was based on Handbrake's Fast 1080p30 preset.
(EDIT: To further add, the original audio was at ~256 Kbps encoded in AAC).
For AV1, the rate factor was set to 30, the frame rate Same as Source, and the rate factor 30. For Opus, I set the bitrate to 64 Kbps.
Improving AVIF in Open Source via the Halide blog
https://halide.cx/blog/improving-avif-in-open-source/index.html
I wanted to write this to explain some of what went into Tune 4/Tune IQ, & help outline some of my reasoning for starting Halide Compression in the first place. I hope you enjoy!
Introducing Iris-WebP, a better WebP encoder: https://halide.cx/iris/index.html
Iris offers up to >20% better compression than libwebp, and trades blows with libaom for AVIF.
My goal is to build an image-first encoder ecosystem for the modern Web, so that new web image codecs aren't generally superfluous.
After sorting out some subtitle issues with the next batch of encodes and a lot of prep work I've got the next set onto the servers. Encodes are looking great as they're coming in at around 1 hour and 15 minutes per episode. Sorted the subtitle issue by accident as I can point to multiple attachment directories in the `mkvmerge` module.
#Handbrake has been doing a pretty great job for me when encoding my Blurays to #AV1. I have noticed a few times though, especially in movies with lots of film grain in dark scenes, it can be pretty destructive on the grain in those dark scenes. I've discovered two changes to fix it.
1) Encode the movie to 10 bit color, even if the source file is 8 bit.
2) Add the following to "Additional Options" under the video tab of Handbrake.
film-grain-denoise=0:film-grain=20
讓 rav1d 視訊解碼器提速 1%
➤ 透過分析和優化,提升 AV1 解碼器的效率
✤ https://ohadravid.github.io/posts/2025-05-rav1d-faster/
這篇文章記錄了作者嘗試優化 Rust 版本的 AV1 視訊解碼器 rav1d 性能的過程。作者參與了 memorysafety.org 舉辦的性能提升競賽,透過分析 profiler 的資料,發現了兩個小的性能瓶頸,並針對其中一個瓶頸進行了優化,成功將解碼速度提升了略高於 1%,且未使用任何不安全的程式碼。優化重點集中在 cdef 濾鏡的實現上,發現 rav1d 使用了較大的暫存緩衝區來歸零,而 C 版本的 dav1d 則使用更精簡的方式。
+ 這篇文章很棒!詳細解釋瞭如何透過分析性能瓶頸,並針對性地進行優化,即使是很小的改進也能帶來實際的效能提升。
+ 令人印象深刻的是作者在未使用不安全程式碼的前提下完成了優化,這對於 Rust 語言來說尤其重要,也證明瞭 Rust 在性能上的潛力。
#視訊解碼 #性能優化 #Rust #AV1
*on macOS with an M3 chip *slightly more than 1%, on…
ohadravid.github.ioEnd-to-end, fully #opensource HDR10 pipeline. Hantro #AV1 10bit decoding accelerator, #Wayland color management protocol, #GStreamer video player. All running on the Radxa Rock5 RK3588. Drop by our table at Embedded Recipes to check it out! #Embedded #OpenSource
Boosteroid Ultra subscribers are getting a visual boost! They have begun rolling out support for the advanced AV1 codec, promising an even smoother, higher-fidelity cloud gaming experience.
#CloudGaming #Boosteroid #AV1
https://clouddosage.com/boosteroids-next-gen-cloud-gaming-with-av1-codec-support/
Discover how Boosteroid AV1 enhances cloud gaming with…
Cloud DosageI've been watching a couple of lectures on a phone during a train ride, and I feel like the following is my favorite minimum-bandwidth format: ~1MB/min - 480p 100kbit/s #AV1 video + 32kbit/s #Opus audio.
For non-action content (lectures, "talking-head" videos, ...) it's more than adequate for a phone screen over constantly-changing low-bandwidth connection. Text is nicely readable (over a couple of frames), especially if scene changes are far apart. And I'm more listening than watching anyway.
It's wild how effective hardware encoding is.
I needed to convert a 1080p 2 hour lecture down to a reasonable size (so that I can view it via slow mobile). I encoded it to #AV1 using VAAPI on my #Arc750. I'm getting 20x realtime encode speed
I'm happy to get 0.2x using software encoding with libsvtav1.
@ezra personally I think #Apple should be forced.to implement #AV1 & #WebM and that @EUCommission could mandate #OpenStandards.
As for quality, were it not for #patents and espechally #SoftwarePantents, we'd have way better #Codecs, but this way people engineering a #FLOSS #Codec are constantly required to specifically avoid infringement of Patents and other IP by not using anything remotely related to it...
Also if #H265 wasn't #patented and facing #PatentTrolls and #rentseekers we'd see way better quality there as well.
Cuz #CCSS & #FLOSS can't share code nor expertise at all.
And yes, Apple (#MPEGLA-Member) is at the root of the problem!
not that vp9 is bad quality, leagues better than h264,…
Wet-Dry WorldThat's why:
Duration: 00:00:10.23, start: 0.000000, bitrate: 30013 kb/s
...
Stream #0:1[0x2](eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 192 kb/s (default)
Stream #0:2[0x3](eng): Video: hevc (Main) (hvc1 / 0x31637668), yuvj420p(pc, bt709), 1920x1080, 29725 kb/s, SAR 1:1 DAR
Let's see how far I can compress it down with #av1 until "I see some pixels"
@atmuntenas El "problema" de #AV1 es que los dispositivos capaces de codificar y decodificar por hardware aún son limitados, así que aún le quedan algunos pocos años más hasta que se extienda (aunque la decodificación por CPU no consume tantos recursos). No obstante, muchos servicios ya priorizan AV1 si detectan que el hardware es compatible, como Netflix.
#Opus sí que está más extendido. Es el códec que usa Spotify, por ejemplo, y más servicios lo usan también porque casi todos los dispositivos actuales traen los códecs necesarios para ello de fábrica.
Estoy de acuerdo en que los formatos propietarios son cosa del pasado. Como mínimo, que sean la excepción y no la norma.
One observation with #AV1. Generally speaking I'm happier using it for my rips because it's completely open and royalty free, and I generally get comparable or better quality at smaller file size.
There is one area where it seems to struggle however; film grain. Sometimes it does just fine. Others however it almost seems to try to eliminate and smooth it, leaving you with some horrendous color banding in some scenes. I'm using RF 22, but have tried upping it to 18 with no improvement.
#ew25: End-to-end, fully #opensource HDR10 pipeline. Hantro #AV1 10bit decoding accelerator, #Wayland color management protocol, GStreamer video player. All running on the Radxa Rock5 RK3588. #embeddedworld #embedded
Re-ripping some of the shows and movies from my collection into #AV1 and I may have to start keeping the full ISO disc images of at least the things I'm particularly fond of. My DVD set of M*A*S*H is starting to delaminate and form bubbles around the center. Everything still reads OK, but it may not for much longer.