SVT-AV1-PSY v2.2.1-A
GitHub: https://github.com/gianni-rosato/svt-av1-psy/releases/tag/v2.2.1-A
The fact that iPhones are getting this before Android phones without Google Play Services tells you all you need to know about the nature of RCS. Android has lost all of its intrigue and fun in favor of becoming GoogleOS
A Handbrake project to natively integrate svt-av1-psy in place of svt-av1, with Linux, Windows and macOS support!
Contribute to Nj0be/HandBrake-SVT-AV1-PSY development by creating an account on GitHub.
cross-posted from: https://lemmy.world/post/19262772 >Good morning my fellow video encoding afficionados. > > As usual, I was trying to find interesting stuff on the web, and I finally did! > > Someone in our wonderful AV1 enthusiast community has spent a lot of time working on natively adding svt-av1-psy to Handbrake; this is done through specific patches that add the additional functionality of svt-av1-psy in Handbrake. > > This allows for Windows, macOS, Linux (Flatpak) and native Linux builds of Handbrake to be built with nearly complete svt-av1-psy support. > > It's truly a great addition as it allows many more people to be at the leading edge of high fidelity AV1 encoding. > > Note that these are based on Nightly Handbrake, but this shouldn't pose a problem. > > Head over to the "Releases" page to find the full builds, CLI versions and even dynamic library replacement: > https://github.com/Nj0be/HandBrake-SVT-AV1-PSY/releases > > That'll be all from me. Thank you for your attention and have a great Saturday.
Let's Get SVT-AV1-PSY into Handbrake!
Description of the feature or enhancement you'd like to see in HandBrake I would like to request the integration of the SVT-AV1-PSY encoder into HandBrake. SVT-AV1-PSY is an enhanced version of the...
Give the issue & upvote and comment to show your support - every like helps!
Hey Blue - this isn't release 2.2.0-A. This is just plain PSY 2.2.0 - 2.2.0-A will come later ;)
SVT-AV1-PSY v2.2.0
Long time no see! We're back with another exciting release: SVT-AV1-PSY v2.2.0! 🎉 PSY Updates Features --tf-strength parameter for manually adjusting temporal filtering strength. By default, reduc...
SVT-AV1-PSY v2.2.0
Long time no see! We're back with another exciting release: SVT-AV1-PSY v2.2.0! 🎉
PSY Updates
Features
--tf-strength
parameter for manually adjusting temporal filtering strength. By default, reduces temporal filtering strength by 4x--chroma-qm-min
&--chroma-qm-max
parameters for adjusting quantization matrix flatness for chroma planes--tune 4
- A new Tune called Still Picture has been introduced for AVIF encoding, with promising gains observed over aomenc, aomenc 4:4:4, and mainline SVT-AV1
Quality & Performance
- Enable 10-bit subpixel motion estimation processing for 10-bit inputs on Preset 3 & below
- Enable SUPERRES_AUTO_ALL for Tune 3 when superres-mode=4
- Disables ALT-REF superres for speed and quality
- Add unipred bias for SSIM full mode decision cost when using Tune 3
- New perceptual QM curve when using Tune 3
- Better chroma QM adjustment & better high fidelity performance
- Vastly improved screen content detection when
--scm 2
is set. Currently only enabled in Tune 4
Documentation
--help
menu correctly prints maximum CRF value (70)- Default Tune 2 is better reflected across documentation
- Updated build documentation
- Additional featured projects
Bug Fixes
- Scoped down QM disablement to only affect NEON-enabled systems
- Scoped down global sharpness features to
--sharpness 1
, as was the original intention
Mainline Updates
API updates
- No API changes on this release
Encoder
- Improve the tradeoffs for the random access mode across presets:
- Speedup of ~15% across presets M0 - M8 while maintaining similar quality levels
- Improve the tradeoffs for the low-delay mode across presets
- Increased temporal resolution setting to 6L for 4k resolutions by default
- Added ARM optimizations for functions with
c_only
equivalent yielding an average speedup of ~13% for 4k 10-bit
Cleanup Build & bug fixes & documentation
- Profile-guided-optimized helper build overhaul
- Major cleanup and fixing of Neon unit test suite
- Address stylecheck dependence on public repositories
Support Us
As SVT-AV1-PSY's codebase has become more complex and the encoder's capabilities have increased dramatically, our efforts have scaled in kind. We have poured hours into coding, testing, distributing, and supporting this piece of open-source software entirely for free, and our work isn't stopping any time soon.
If you appreciate the work that we do and you'd like to support us, we are always excited to see code contributions from outside of the core development team. Otherwise, you can support us monetarily via the links below.
Gianni Rosato: Donate
Julio Barba: Donate Soon
BlueSwordM: Coming Soon
Clybius: Coming Soon
Any support you can offer goes a long way, and we sincerely appreciate it. ♥️
Thanks for using SVT-AV1-PSY! <3
Full Changelog: https://github.com/gianni-rosato/svt-av1-psy/commits/v2.2.0
You need VideoToolbox for this particular tool because it calls the VideoToolbox library from within FFmpeg in order to encode the video.
"Why do I need x264 to encode H.264 in FFmpeg?" is essentially what you're asking. FFmpeg needs VideoToolbox support to work with my tool.
If you're asking why I chose to use VideoToolbox in the first place, it was because I want this to be a macOS-specific tool with very fast encoding speeds at decent fidelity per bit. Hardware accelerated video encoding is one way to make this happen.
vt-enc calls FFmpeg which calls the VideoToolbox encoding framework. Without VT, ffmpeg commands will fail
VideoToolbox is the encoder that FFmpeg links to.
Filesystem compression is dope.
vt-enc: FFmpeg VideoToolbox frontend in Bash
FFmpeg VideoToolbox frontend in Bash. Contribute to gianni-rosato/vt-enc development by creating an account on GitHub.
cross-posted from: https://lemmy.ml/post/19003650 >> vt-enc is a bash script that simplifies the process of encoding videos with FFmpeg using Apple's VideoToolbox framework on macOS. It provides an easy-to-use command-line interface for encoding videos with various options, including codec selection, quality settings, and scaling.
vt-enc: FFmpeg VideoToolbox frontend in Bash
FFmpeg VideoToolbox frontend in Bash. Contribute to gianni-rosato/vt-enc development by creating an account on GitHub.
cross-posted from: https://lemmy.ml/post/19003650 >> vt-enc is a bash script that simplifies the process of encoding videos with FFmpeg using Apple's VideoToolbox framework on macOS. It provides an easy-to-use command-line interface for encoding videos with various options, including codec selection, quality settings, and scaling.
vt-enc: FFmpeg VideoToolbox frontend in Bash
FFmpeg VideoToolbox frontend in Bash. Contribute to gianni-rosato/vt-enc development by creating an account on GitHub.
> vt-enc is a bash script that simplifies the process of encoding videos with FFmpeg using Apple's VideoToolbox framework on macOS. It provides an easy-to-use command-line interface for encoding videos with various options, including codec selection, quality settings, and scaling.
Royalty-free blanket patent licensing is compatible with Free Software and should be considered the same as being unpatented. Even if it's conditioned on a grant of reciprocality. It's only when patent holders start demanding money (or worse, withholding licenses altogether) that it becomes a problem
I'm pretty much all BTRFS at this point
JPEG-XL is in no way patent encumbered. Neither is AVIF. I don't know what you're talking about
No, there aren't any licensing issues with JPEG-XL.
YouTube serves VP9 video (and more recently a lot of AV1) and I think the Pis only have hardware accelerated decoding of H.264/5 as it stands today
Minecraft is arguably & measurably more performant on Linux, full stop. Anything using OpenGL performs better on Linux, check any Minecraft benchmark online.
bdr-ssimu2 - Codec Comparison Script
Plot SSIMULACRA2 scores with FFmpeg via matplotlib - gianni-rosato/bdr-ssimu2
bdr-ssimu2
Encode, analyze, & plot SSIMULACRA2 scores using a source video file that is encoded with FFmpeg.
This Python script generates BD-Rate (Bjøntegaard-Delta Rate) graphs for comparing the performance of different encoding commands. It encodes a source video with various specified Constant Rate Factor (CRF) values, calculates SSIMULACRA2 scores, and plots the results via matplotlib
.
Features
- Encodes a source video using two user-configurable FFmpeg commands
- Calculates SSIMULACRA2 scores (and soon XPSNR scores as well)
- Generates BD-Rate curves comparing the two encoding commands
- Outputs both average and harmonic mean SSIMULACRA2 plots
- Allows for temporal metric analysis subsampling (sampling every nth frame)
Prerequisites
- Python 3.x
- FFmpeg
- VapourSynth with:
- VSZip Plugin
- FFMS2
- fmtconv
- Required Python packages:
vapoursynth
matplotlib
tqdm
See more in the linked Git repo's README!
Also, a lot of towns/cities remove those romantic locks regularly anyway.
We need more nuclear power ASAP
It is a modern successor to formats like WebP & JPEG. WebP was barely competitive with JPEG
As an Android user, I'm considering switching to iPhone due to how much worse the Android experience is becoming without Google Play Services. I'm using a custom ROM with microG, which potentially means no RCS since it is only available through Google Messages which doesn't work with microG.
As much as it would suck jumping ship, at the very least, Apple is still a consumer hardware company first & foremost while Google will always be an ads company. Android exists to that end & that end alone.
SVT-AV1-PSY v2.1.0-A
Hi there! We're back with our micro-release format to announce some exciting changes in SVT-AV1-PSY v2.1.0-A! 🎉 PSY Updates Features New parameter --max-32-tx-size, which restricts block transform...
Introducing SVT-AV1-PSY v2.1.0-A
Features
- New parameter
--max-32-tx-size
, which restricts block transform sizes to a maximum of 32x32 pixels. This can be useful in very specific scenarios for improving overall efficiency - Added support for HDR10+ JSON files via a new
--hdr10plus-json
parameter (thanks @quietvoid!). In order to build a binary with support for HDR10+, see our PSY Development page. - New parameter
--adaptive-film-grain
, which helps remedy perceptually harmful grain patterns caused by extracting grain from blocks that are too large for a given video resolution. This parameter is enabled by default
Quality & Performance
- Disabled SSIM-cost transform decisions while keeping SSIM-cost mode decisions, generally improving Tune 3's efficiency & consistency
- Additional NEON optimizations for ARM platforms, providing a speed increase
Documentation
- All of the features present in this release have been documented, so associated documentation has been updated accordingly
- Build documentation updated to reflect the HDR10+ build option
Bug Fixes
- Disabled quantization matrices for presets 5 and higher due to a visual consistency bug (#56)
Full Changelog: https://github.com/gianni-rosato/svt-av1-psy/commits/v2.1.0-A
Windows 10 is EOL in October 2025
cross-posted from: https://lemmy.ml/post/15988326 >> Windows 10 will reach end of support on October 14, 2025. The current version, 22H2, will be the final version of Windows 10, and all editions will remain in support with monthly security update releases through that date. Existing LTSC releases will continue to receive updates beyond that date based on their specific lifecycles. > > Source: https://learn.microsoft.com/en-us/lifecycle/products/windows-10-home-and-pro
SVT-AV1 2.1.0 just released, how does it compare to the previous version?
cross-posted from: https://lemmy.ml/post/15953505 >SVT-AV1 2.1.0 just released, how does it compare to SVT-AV1 2.0.0? Well-known encoder Trix attempts to answer this question with metrics, graphs, and detailed analysis.
SVT-AV1 2.1.0 just released, how does it compare to the previous version?
SVT-AV1 2.1.0 just released, how does it compare to SVT-AV1 2.0.0? Well-known encoder Trix attempts to answer this question with metrics, graphs, and detailed analysis.
SVT-AV1-PSY v2.0.0-A
Hi there! We're back with a new micro-release format to announce some exciting changes in SVT-AV1-PSY v2.0.0-A! 🎉 PSY Updates Features The CRF range, previously capped at 63, has been extended to ...
Hi there! We're back with a new micro-release format to announce some exciting changes in SVT-AV1-PSY v2.0.0-A! 🎉
PSY Updates
Features
- The CRF range, previously capped at 63, has been extended to a maximum value of 70. It can also be incremented in quarter increments of 0.25
- New option:
--enable-dlf 2
for a slower, more accurate deblocking loop filter - New option:
--qp-scale-compress-strength
(0 to 3) which sets a strength for the QP scale algorithm to compress values across all temporal layers. Higher values result in more consistent video quality - New option:
--frame-luma-bias
(0 to 100) enables experimental frame-level luma bias to improve quality in dark scenes by adjusting frame-level QP based on average luminance across each frame
Quality & Performance
- A temporal layer qindex offset has been added to Tune 3 for more consistent quality across frames when encoding
- Minor speed bump to Preset 8
- Dynamic delta_q_res switching implemented to help reduce signaling overhead, which should improve quality especially at CRF ≥40
- Other general improvements to Tune 3
Documentation
- PNG images have been replaced with smaller lossless WebP images, resulting in faster loading & repository cloning times.
- More consistent & thorough PSY Development page, including build instructions
Bug Fixes
- Help menu formatting adjusted for less frequent underlining
--progress 2
no longer reports the same information as--progress 3
Other
- Introducing PSY Micro-releases! Each micro-release will be marked with a letter, bringing a bundle of new features & improvements. The release letter will reset back to the initial
A
each time our mainline version is updated. More info can be found in this project's README & the PSY Development page
Thanks for using SVT-AV1-PSY! ♥️
Full Changelog: https://github.com/gianni-rosato/svt-av1-psy/commits/v2.0.0-A
SVT-AV1-PSY v2.0.0 Released in Tandem with Mainline
Hello, everyone! We've been hard at work improving SVT-AV1 with our additions to the encoder improving visual fidelity. Little by little, we are working on trying to bring many of them to mainline!...
From the GitHub releases:
> Hello, everyone! We've been hard at work enhancing SVT-AV1 with our additions to the encoder improving visual fidelity. Little by little, we are working on trying to bring many of them to mainline! For the time being, I want to note that major SVT-AV1-PSY releases & mainline releases are not the same, and the codebases differ due to our changes; the version numbers may be identical, but the versions themselves are not, which is disclosed within the encoder's version information. With that, we're excited to announce SVT-AV1-PSY v2.0.0! 🎉
PSY Updates
Variance boost
- Moved varboost delta-q adjusting code to happen before TPL, giving TPL the opportunity to work with more accurate superblock delta-q priors, and produce better final rdmult lambda values
- Fixed rare cases of pulsing at high CRFs (>=40) and strengths (3-4)
- 2% avg. bitrate reduction for comparable image quality
- Added an alternative boosting curve (
--enable-alt-curve
), with different variance/strength tradeoffs - Refactored boost code so it internally works with native q-step ratios
- Removed legacy variance boosting method based on 64x64 values
- Parameter
--new-variance-octile
->--variance-octile
- Parameter
Excitingly, a var-boost mainline merge has been marked with the highest priority issue label by the mainline development team, so we may see this in mainline SVT-AV1 soon! Congrats @juliobbv! 🎉
Other
- Presets got faster, so in addition to Preset -2, we have an even slower Preset -3
--sharpness
now accepts negative values- The SVT-AV1-PSY encoder now supports Dolby Vision encoding via Dolby Vision RPUs. To build with Dolby Vision support, install libdovi & pass
--enable-libdovi
to./build.sh
on macOS/Linux (orenable-libdovi
to./build.bat
on Windows).
Mainline Updates
Major API updates
- Changed the API signaling the End Of Stream (EOS) with the last frame vs with an empty frame
OPT_LD_LATENCY2
making the change above is kept in the code to help devs with integration- The support of this API change has been merged to ffmpeg with a 2.0 version check
- Removed the 3-pass VBR mode which changed the calling mechanism of multi-pass VBR
- Moved to a new versioning scheme where the project major version will be updated every time API/ABI is changed
Encoder
- Improve the tradeoffs for the random access mode across presets:
- Speedup presets MR by ~100% and improved quality along with tradeoff improvements across the higher quality presets (!2179,#2158)
- Improved the compression efficiency of presets M9-M13 by 1-4% (!2179)
- Simplified VBR multi-pass to use 2 passes to allow integration with ffmpeg
- Continued adding ARM optimizations for functions with
c_only
equivalent - Replaced the 3-pass VBR with a 2-pass VBR to ease the multi-pass integration with ffmpeg
- Memory savings of 20-35% for LP 8 mode in preset M6 and below and 1-5% in other modes / presets
- Film grain table support via
--fgs-table
(already in SVT-AV1-PSY) (link) - Disable film grain denoise by default (already in SVT-AV1-PSY) (link)
Cleanup, bug fixes & documentation
- Various cleanups and functional bug fixes
- Update the documentation to reflect the rate control
Thanks for using SVT-AV1-PSY! ♥️
Full Changelog: https://github.com/gianni-rosato/svt-av1-psy/commits/v2.0.0
An in-depth look at implementing a QOI encoder in the Zig programming language, exploring the QOI image format and Zig's features.
cross-posted from: https://lemmy.ml/post/13183095
An in-depth look at implementing a QOI encoder in the Zig programming language, exploring the QOI image format and Zig's features.
cross-posted from: https://lemmy.ml/post/13183095
An in-depth look at implementing a QOI encoder in the Zig programming language, exploring the QOI image format and Zig's features.
boycott Nintendo products
after what happened with yuzu emu, im done...
EDIT: This post is a joke! It was posted in /c/memes, of course it is going to be a meme! If you consider this news, please re-evaluate your choice of sources.
At the same time, I think it says something about Nintendo that some actually believed this...
Android currently ships with the libgav1 AV1 decoder, but a future update will switch that to libdav1d, which offers much better performance.
It's official that Android will be rolling out dav1d to replace libgav1 as a system wide codec on Android 14 devices, though there is potential for it to be supported as far back as Android 10. Finally, libgav1 is no more!
What are the craziest misconceptions you’ve heard about programming from people not familiar with it?
As someone who spends time programming, I of course find myself in conversations with people who aren't as familiar with it. It doesn't happen all the time, but these discussions can lead to people coming up with some pretty wild misconceptions about what programming is and what programmers do.
- I'm sure many of you have had similar experiences. So, I thought it would be interesting to ask.