Intel SVT-AV1

[hajj_3]

v1.6.0 - 2023-06-18

Encoder:

Improve the tradeoffs for the random access mode across presets M1-M13:
Speeding up the higher quality presets by 30-40%
Improving the BD-rate by 1-4% for the faster presets
Improve the tradeoffs for the low delay mode for both screen content and non-screen content encoding modes
Add a toggle to remove the legacy one-frame buffer at the input of the pipeline allowing the low delay mode to operate at sub-frame processing latencies
Add a new API allowing the user to specify quantization offsets for a region of interest per frame

Build, cleanup and bug fixes:

Various cleanups and functional bug fixes
Fix the startup minigop size BD-rate loss
Add ability to run the ci-testing offline

[ShortKatz]

Version 1.8.0

Encoder

Improve the tradeoffs for the random access mode across presets:
Speedup CRF presets M6 to M0 by 17-53% while maintaining similar quality levels
Re-adjust CRF presets M7 to M13 for better quality with BD-rate gains ranging from 1-4%
Improve the quality and speed of the 1-pass VBR mode
More details on the per preset improvements can be found in MR !2143
Add API allowing to update bitrate / CRF and Key_frame placement during the encoding session for CBR lowdelay mode and CRF Random Access mode
ARM Neon SIMD optimizations for most critical kernels allowing for a 4.5-8x fps speedup vs the c implementation
Cleanup and bug fixes and documentation

Various cleanups and functional bug fixes
Update the documentation for preset options and individual features

[Marsu42]

Version 1.8.0

Does anyone happen to have a Windows binary to share?

Strangely, except for being built into Handbrake (nightly) and ffmpeg I cannot finde recent "SvtAv1EncApp.exe" anywere for use with av1an or custom command lines.

And yes, I know about just-learn-to-compile-it-yourself so with me asking this isn't the answer. :thanks:

[Boulder]

There are some community builds available at the SVT-AV1 Discord channel.

[nakTT]

Version 1.8.0

Tested the ARM version of SVT-AV1 1.8.0 and it is as good as advertised. It is WAYYYY faster than the last one I tested (Version 1.4.1 released on 2022-12-12). HUGE progress made on the ARM front of the SVT-AV1 encoder within the space of just ONE year.
Many thanks to the AV1 development team.:thanks:

[Blue_MiSfit]

I highly recommend you get media-autobuild-suite up and running to cut binaries for you :)

[ShortKatz]

Does somebody know if there are plans to add support for YUV422 to SVT-AV1 ?
The only (outdated) information I found is this: https://www.phoronix.com/news/Intel-TODO-AV1-Decode-FFmpeg

[nakTT]

Version 2.0.0
Changelog

[2.0.0] - 2024-03-13

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


Cleanup and bug fixes and documentation

- Various cleanups and functional bug fixes
- Update the documentation to reflect the rate control changes

[ShortKatz]

Did someone experiment already with the new variance boost feature, especially with the values of variance-boost-strength and variance-octile?

[Boulder]

Did someone experiment already with the new variance boost feature, especially with the values of variance-boost-strength and variance-octile?

The default values are very good already and prevent boosting areas unnecessarily. For darker material, changing strength to 3 and/or octile to 4 can be useful.

[ShortKatz]

OK, thanks. I used the default values for some time and started with variance-boost-strength=3 today, so not much experience yet.

[benwaggoner]

The default values are very good already and prevent boosting areas unnecessarily. For darker material, changing strength to 3 and/or octile to 4 can be useful.
I imagine different parameters would be optimal for gamma versus PQ. Algorithms based on code values often fall apart when applied to PQ if they don't account for the big perceptual differences in PQ code values. For example, gamma needs lower QPs near black, but PQ does not. However PQ doesn't have a defined max brightness like gamma does, and can vary hugely between titles and shots.

[ShortKatz]

There is now a handy documentation for the new variance boost feature:
https://gitlab.com/AOMediaCodec/SVT-AV1/-/blob/master/Docs/Appendix-Variance-Boost.md

[benwaggoner]

There is now a handy documentation for the new variance boost feature:
https://gitlab.com/AOMediaCodec/SVT-AV1/-/blob/master/Docs/Appendix-Variance-Boost.md
Great link with some helpful illustrations.

[BlueSwordM]

SVT-AV1-PSY 2.0.0-A Release:
https://github.com/gianni-rosato/svt-av1-psy/releases/tag/v2.0.0-A

This time, we've decided to change the way we name these updates as they've been difficult to keep track of versioning against mainline SVT-AV1 and our own. We'll still follow the cadence of mainline SVT-AV1, but with letter releases added in between for additional clarity.

## 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 chroma qindex offset has been added to Tune 3 for more consistent quality across frames when encoding
- Minor speed bump to Preset 8
- Encoder innovation:
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](https://github.com/gianni-rosato/svt-av1-psy/blob/master/Docs/PSY-Development.md), 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


Yes, this is a near copy paste of what I've posted on other public forums :)

[ShortKatz]

Version 2.1 with variance boost has been released.

[2.1.0] - 2024-05-17
API updates

One config parameter added within the padding size. Config param structure size remains unchanged
Presets 6 and 12 are now pointing to presets 7 and 13 respectively due to the lack of spacing between the presets
Further preset shuffling is being discussed in #2152


Encoder

Added variance boost support to improve visual quality for the tune vq mode
Improve the tradeoffs for the random access mode across presets:
Speedup of 12-40% presets M0, M3, M5 and M6 while maintaining similar quality levels
Improved the compression efficiency of presets M11-M13 by 1-2% ( !2213)
Added ARM optimizations for functions with c_only equivalent

Cleanup, build, bug fixes and documentation

Use nasm as a default assembler and yasm as a fallback
Fix performance regression for systems with multiple processor groups
Enable building SvtAv1ApiTests and SvtAv1E2ETests for ARM
Added variance boost documentation
Added a mailmap file to map duplicate git generated emails to the appropriate author


https://gitlab.com/AOMediaCodec/SVT-AV1/-/releases

[BlueSwordM]

SVT-AV1-PSY 2.1.0-A release:
https://github.com/gianni-rosato/svt-av1-psy/releases/tag/v2.1.0-A

-> MAIN CHANGES:
- New parameter: `--max-32-tx-size`. This restricts block transform sizes to a maximum of 32x32 pixels. This can be useful in very specific scenarios for improving overall visual quality where the AV1 spec can allow for bad decisions decided by SAD/SSD/PSNR.

- New option: `--hdr10plus-json`. This parameter, added by quietvoid, allows for HDR10+ HDR support. In order to build a binary with support for HDR10+, see our PSY Development page

- New option: `--adaptive-film-grain`. This parameter 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.

-> TUNING:
- Disabled SSIM-cost transform decisions while keeping SSIM-cost mode decisions, generally improving Tune 3's efficiency & consistency. Future changes might contain additional tuning at this level.

-> PERFORMANCE:
- Additional NEON optimizations for ARM platforms, providing a speed increase

-> BUG FIXES:
- Temporarily disabled quantization matrices (--enable qm 0) for presets 5 and higher due to a visual consistency bug: https://github.com/gianni-rosato/svt-av1-psy/issues/56

[oibaf]

It looks like from 2.1.1 they removed the decoder:

[2.1.2] - 2024-06-27
Cleanup, bug fixes:

Fixed profile-guided-optimization build by removing the remaining decoder path


[2.1.1] - 2024-06-25
Cleanup, bug fixes, and documentation improvements:

Removed the SVT-AV1 Decoder portion of the project. The last version containing the decoder is SVT-AV1 v2.1.0.
Updated the folder structure and library build order to reflect the removal of the decoder.
Renamed all files (except for API files) to remove the "Eb" prefix and changed them to camel_case format.
Updated the gtest version to v1.12.1.
Added CI support for ARM-based macOS machines.
Improved documentation for accuracy and completeness.

[oibaf]

It looks like from 2.1.1 they removed the decoder:

Here is the rationale: https://gitlab.com/AOMediaCodec/SVT-AV1/-/issues/2182

[Spyros]

SVT-AV1 2.2.0 was released two days ago. (Release (https://gitlab.com/AOMediaCodec/SVT-AV1/-/releases/v2.2.0))

Encoder

Improve the tradeoffs for the random access mode across presets:
Speedup of ~15% across presets M0 - M8 while maintaining similar quality levels (!2253 (https://gitlab.com/AOMediaCodec/SVT-AV1/-/merge_requests/2253))
Improve the tradeoffs for the low-delay mode across presets (!2260 (https://gitlab.com/AOMediaCodec/SVT-AV1/-/merge_requests/2260))
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 4k10bit

Cleanup Build and bug fixes and documentation

Profile-guided-optimized helper build overhaul
Major cleanup and fixing of Neon unit test suite
Address stylecheck dependence on public repositories

[nakTT]

Version 2.2.1
Changelog

[2.2.1] - 2024-08-23

Cleanup and bug fixes and documentation

- Fixed debug arm macOS builds by removing invalid assert

[ShortKatz]

Version 2.3.0

Versionshinweise
[2.3.0] - 2024-10-28

API updates

Preset shift: M12/M13 mapped to M11, M7-M11 shifted one position down. API does not change, all presets from MR-M13 will still be accepted
svt_av1_enc_get_packet API is now a blocking call for low-delay enforcing a picture in, picture out model
--fast-decode range changed from 0-1 to 0-2 available on all presets
Introducing a new definition of --lp being levels of parallelism with a new field in the config structure level_of_parallelism
logical_processors will be deprecated in the 3.0 release
Encoder

NEW FAST DECODE MODE - (!2280)
New fast-decode (2) to allow for an average AV1 software cycle reduction of 25-50% vs fast-decode 0 with a 1-3% BD-Rate loss across the presets
Improved fast-decode (1) option to increase its AV1 software cycle reduction by ~10% while maintaining the same quality levels
Improved --lp settings for high resolutions, with CRF gaining a ~4% improvement in speed and VBR gaining ~15% (!2323)
Further Arm-based optimizations improving the efficiency of previously written Arm-neon implementations by an average of 30%. See below for more information on specific presets
Address speed regressions for high resolutions first pass encode by tuning the threading parameters, with 1080p showing the biggest gains
Enabled AVX512 by default in cmake allowing for ~2-4% speedup
Enabled LTO by default if using a new enough compiler (!2288, !2305)
If LTO is a problem or causes one, it can be disabled by adding -DSVT_AV1_LTO=OFF to cmake to force it off.
Please report any issues that occur when using it.
Cleanup Build and bug fixes and documentation

third_party: update safestringlib with applicable upstream changes
Improved the unit test coverage for Arm-neon code
Updated documentation
Arm Improvements

Speed comparison was done against v2.2 on AWS Graviton4 instances with Clang 19.1.1
--lp 1 was used for all tests


https://gitlab.com/AOMediaCodec/SVT-AV1/-/releases

[ShortKatz]

SVT-AV1 now has support for lossless encoding.

[ShortKatz]

This merge request has a comment about a AV1 spec bug.
https://gitlab.com/AOMediaCodec/SVT-AV1/-/merge_requests/2343/diffs#53baa26f2ca74120683504dad1c9740c6873cb8b_80_101

And a link to this bug https://aomedia.issues.chromium.org/issues/42302342

But I quite don't understand what this bug actually means for AV1 encoding. Will this interfere with encoding quality? Or performance?

[nevcairiel]

This merge request has a comment about a AV1 spec bug.
https://gitlab.com/AOMediaCodec/SVT-AV1/-/merge_requests/2343/diffs#53baa26f2ca74120683504dad1c9740c6873cb8b_80_101

And a link to this bug https://aomedia.issues.chromium.org/issues/42302342

But I quite don't understand what this bug actually means for AV1 encoding. Will this interfere with encoding quality? Or performance?

It doesnt cause anything, other then headaches for developers to obey the wrong-way-around values.

[oibaf]

This merge request has a comment about a AV1 spec bug.
https://gitlab.com/AOMediaCodec/SVT-AV1/-/merge_requests/2343/diffs#53baa26f2ca74120683504dad1c9740c6873cb8b_80_101

And a link to this bug https://aomedia.issues.chromium.org/issues/42302342


But I quite don't understand what this bug actually means for AV1 encoding. Will this interfere with encoding quality? Or performance?

According to the bug link it should impact BDRATE, so the quality, however "change is ~neutral overall":
* Change the encoder logic so that we never select a TRANSLATION
type global motion model. If the global motion search process
produces a TRANSLATION type model, we reset to an IDENTITY
type model.

The impact of this change is ~neutral overall, with no video
changing by more than +/- 0.2% BDRATE.

Overall impact on 150 frames, speed 1, const q mode:

lowres2: -0.002% BDRATE, -0.003% instr count
midres2: +0.005% BDRATE, +0.005% instr count
hdres2: -0.001% BDRATE, -0.035% instr count

[ShortKatz]

OK, thanks. :-)

[ShortKatz]

Interesting, it seems some SVT-AV1-PSY features are getting backported into SVT-AV1 mainline.

[oibaf]

Interesting, it seems some SVT-AV1-PSY features are getting backported into SVT-AV1 mainline.

Nice, here is the link to the MRs: https://gitlab.com/AOMediaCodec/SVT-AV1/-/merge_requests/?&search=SVT-AV1-PSY

[Z2697]

Interesting, it seems some SVT-AV1-PSY features are getting backported into SVT-AV1 mainline.

Now they shifted their focus to getting more -psy fork features merged into mainline.

[Kurt.noise]

Hi,

I'm experiencing an issue using svt-av1-psy with any different source files : on windows platform (windows 11 24H2), it seems encoding to 8 bits does not ending correctly within preset < 8 :

svt-av1-psy 2.3.0-A 8 bits :
E:\tools\svtav1psy>SvtAv1EncApp.exe -i "E:\Video\Raw.yuv" -w 1920 -h 1080 --input-depth 8 -n 1200 --fps-num 30000 --fps-denom 1001 --progress 3 --crf 30 --preset 4 -b "E:\Video\output.ivf"
Svt[info]: -------------------------------------------
Svt[info]: SVT [version]: SVT-AV1-PSY Encoder Lib v2.3.0-A-5-gf560b40
Svt[info]: SVT : Clang 18.1.8 64 bit
Svt[info]: LIB Build date: Dec 30 2024 07:49:20
Svt[info]: -------------------------------------------
Svt[info]: Level of Parallelism: 5
Svt[info]: Number of PPCS 140
Svt[info]: [asm level on system : up to avx2]
Svt[info]: [asm level selected : up to avx2]
Svt[info]: -------------------------------------------
Svt[info]: SVT [config]: main profile tier (auto) level (auto)
Svt[info]: SVT [config]: width / height / fps numerator / fps denominator : 1920 / 1080 / 30000 / 1001
Svt[info]: SVT [config]: bit-depth / color format : 8 / YUV420
Svt[info]: SVT [config]: preset / tune / pred struct : 4 / SSIM / random access
Svt[info]: SVT [config]: gop size / mini-gop size / key-frame type : 321 / 32 / key frame
Svt[info]: SVT [config]: BRC mode / rate factor : CRF / 30.00
Svt[info]: SVT [config]: AQ mode / variance boost strength / octile / curve : 2 / 2 / 6 / regular
Svt[info]: SVT [config]: Sharpness / QP scale compress strength / Frame low-luma bias : 1 / 1 / 0
Svt[info]: SVT [config]: Temporal Filtering Strength : 1
Svt[info]: SVT [config]: Keyframe TF Strength : 1
Svt[info]: -------------------------------------------
[B]Encoding: 1/1200 Frames @ 23.60 fpm | 380.05 kb/s | Time: 0:00:03 [-0:00:19] | Size: 0.22 MB [1.90 MB]


svt-av1-psy 2.3.0-A 10 bits:
E:\tools\svtav1psy>SvtAv1EncApp.exe -i "E:\Video\Raw.yuv" -w 1920 -h 1080 --input-depth 10 -n 1200 -
-fps-num 30000 --fps-denom 1001 --progress 3 --crf 30 --preset 4 -b "E:\Video\output.ivf"
Svt[info]: -------------------------------------------
Svt[info]: SVT [version]: SVT-AV1-PSY Encoder Lib v2.3.0-A-5-gf560b40
Svt[info]: SVT : Clang 18.1.8 64 bit
Svt[info]: LIB Build date: Dec 30 2024 07:49:20
Svt[info]: -------------------------------------------
Svt[info]: Level of Parallelism: 5
Svt[info]: Number of PPCS 140
Svt[info]: [asm level on system : up to avx2]
Svt[info]: [asm level selected : up to avx2]
Svt[info]: -------------------------------------------
Svt[info]: SVT [config]: main profile tier (auto) level (auto)
Svt[info]: SVT [config]: width / height / fps numerator / fps denominator : 1920 / 1080 / 30000 / 1001
Svt[info]: SVT [config]: bit-depth / color format : 10 / YUV420
Svt[info]: SVT [config]: preset / tune / pred struct : 4 / SSIM / random access
Svt[info]: SVT [config]: gop size / mini-gop size / key-frame type : 321 / 32 / key frame
Svt[info]: SVT [config]: BRC mode / rate factor : CRF / 30.00
Svt[info]: SVT [config]: AQ mode / variance boost strength / octile / curve : 2 / 2 / 6 / regular
Svt[info]: SVT [config]: Sharpness / QP scale compress strength / Frame low-luma bias : 1 / 1 / 0
Svt[info]: SVT [config]: Temporal Filtering Strength : 1
Svt[info]: SVT [config]: Keyframe TF Strength : 1
Svt[info]: -------------------------------------------
[B]Encoding: 1200/1200 Frames @ 2.48 fps | 51442.81 kb/s | Time: 0:08:04 [-0:00:00] | Size: 257.47 MB [257.47 MB]
SUMMARY --------------------------------- Channel 1 --------------------------------
Total Frames Frame Rate Byte Count Bitrate
1200 29.97 fps 257471283 51442.81 kbps


Channel 1
Average Speed: 2.478 fps
Total Encoding Time: 484198 ms
Total Execution Time: 484534 ms
Average Latency: 58361 ms
Max Latency: 96320 ms


For reference, testing also the current svt-av1 2.3.0 8 bits works fine :
E:\tools\svtav1psy>SvtAv1EncApp.exe -i "E:\Video\Raw.yuv" -w 1920 -h 1080 --input-depth 8 -n 1200 --fps-num 30000 --fps-denom 1001 --progress 3 --crf 30 --preset 4 -b "E:\Video\output.ivf"
Svt[info]: -------------------------------------------
Svt[info]: SVT [version]: SVT-AV1 Encoder Lib v2.3.0
Svt[info]: SVT : Visual Studio 2022 64 bit
Svt[info]: LIB Build date: Jan 5 2025 09:41:32
Svt[info]: -------------------------------------------
Svt[info]: Level of Parallelism: 5
Svt[info]: Number of PPCS 140
Svt[info]: [asm level on system : up to avx2]
Svt[info]: [asm level selected : up to avx2]
Svt[info]: -------------------------------------------
Svt[info]: SVT [config]: main profile tier (auto) level (auto)
Svt[info]: SVT [config]: width / height / fps numerator / fps denominator : 1920 / 1080 / 30000 / 1001
Svt[info]: SVT [config]: bit-depth / color format : 8 / YUV420
Svt[info]: SVT [config]: preset / tune / pred struct : 4 / PSNR / random access
Svt[info]: SVT [config]: gop size / mini-gop size / key-frame type : 161 / 32 / key frame
Svt[info]: SVT [config]: BRC mode / rate factor : CRF / 30
Svt[info]: SVT [config]: AQ mode / variance boost : 2 / 0
Svt[info]: -------------------------------------------
Encoding 1200
SUMMARY --------------------------------- Channel 1 --------------------------------
[B]Total Frames Frame Rate Byte Count Bitrate
1200 29.97 fps 11649088 2327.49 kbps


Channel 1
Average Speed: 20.573 fps
Total Encoding Time: 58328 ms
Total Execution Time: 58618 ms
Average Latency: 6539 ms
Max Latency: 8242 ms


Does anybody also experiment this ?

Same story using also this library through ffmpeg...

[GeoffreyA]

Yes, I had a similar problem with the latest version of SVT-AV1-PSY when using a lower preset. The encoding starts, then ends prematurely. Likely, something got broken recently.

[oibaf]

Check if your issue is already reported at https://github.com/psy-ex/svt-av1-psy/issues (maybe this: https://github.com/psy-ex/svt-av1-psy/issues/115), otherwise open a new issue so that they can fix it.

[Kurt.noise]

Thanks for confirmation. Yeah, it looks like issue #115, as already being reported.

And btw, debugging more deeper : issue occured between 2.3.0 & current releases.

[GeoffreyA]

Same for me. It was the recent A release. Before that, never once crashed.

[oibaf]

Please discuss it at: https://github.com/psy-ex/svt-av1-psy/issues/115 where their developers are working. Posting the details here won't help to fix it...

[GeoffreyA]

Sure.

[Kurt.noise]

A workaround has been found : https://github.com/psy-ex/svt-av1-psy/discussions/118

[MZ/X]

A new AV1 vfw encoder/decoder codec (xAV1vfw) is released on http://mpxplay.sourceforge.net with svt-av1 v2.3.0
(it can be used with VirtualDub2 for example)
You can follow the updates here too:
https://www.facebook.com/mpxplay

[BlueSwordM]

A workaround has been found : https://github.com/psy-ex/svt-av1-psy/discussions/118

It's been fully fixed now.

[Kurt.noise]

It's been fully fixed now.
yes, confirmed. Thank you.

[Kurt.noise]

Guys, could you benchmark 2.3.0-B windows x64 using different compilers please ?

https://www.mediafire.com/file/o7gmmb15mc8lx78/svtav1psy-2.3.0-B_x64__-_clang.7z/file
https://www.mediafire.com/file/almitji4ipgcat2/svtav1psy-2.3.0-B_x64_-_gcc.7z/file
https://www.mediafire.com/file/lzjwrvcqeos0nir/svtav1psy-2.3.0-B_x64_-_intel.7z/file

Seems intel one is sightly faster on my machine.

[oibaf]

Better late than never: SVT-AV1 v2.2.x Deep Dive (https://wiki.x266.mov/blog/svt-av1-third-deep-dive)

[oibaf]

The End of SVT-AV1-PSY (https://giannirosato.com/blog/post/end-of-psy/)

[BlueSwordM]

The End of SVT-AV1-PSY (https://giannirosato.com/blog/post/end-of-psy/)

Yeah, we decided on quite the title to get people to read it.

No need to worry though, as most of the team members are still there and somewhat working hard.

I'm working on a guide on how to best take advantage of svt-av1-psy and its new featureset to best effect, as while `--psy-rd` was modeled like what x264/x265 do it, it was extended further by making it touch many more things overall.

[oibaf]

Yeah, we decided on quite the title to get people to read it.

No need to worry though, as most of the team members are still there and somewhat working hard.

I'm working on a guide on how to best take advantage of svt-av1-psy and its new featureset to best effect, as while `--psy-rd` was modeled like what x264/x265 do it, it was extended further by making it touch many more things overall.

Thanks for the feedback and for all the effort on this!

Also very interesting that the patches are being submitted in SVT-AV1 (so that everyone can benefits)!
Actually, 8 patches out of 9 submitted are already merged:
https://gitlab.com/AOMediaCodec/SVT-AV1/-/merge_requests/?search=SVT-AV1-PSY
and will be included in SVT-AV1 version following latest 2.3.0.

[ShortKatz]

The End of SVT-AV1-PSY (https://giannirosato.com/blog/post/end-of-psy/)

Ah, this explains why they started porting features from SVT-AV1-PSY to SVT-AV1, I was already wondering.



Also very interesting that the patches are being submitted in SVT-AV1 (so that everyone can benefits)!
Actually, 8 patches out of 9 submitted are already merged:
https://gitlab.com/AOMediaCodec/SVT-AV1/-/merge_requests/?search=SVT-AV1-PSY
and will be included in SVT-AV1 version following latest 2.3.0.

The patch for noise-norm-strength was closed without merging. So it's 7 of 9. Only the sharpening PR is now missing. I am wondering if they are planning to port also other feature in the future.
Edit: Now sharpness is also merged. :-)

[oibaf]

Ah, this explains why they started porting features from SVT-AV1-PSY to SVT-AV1, I was already wondering.
I am wondering if they are planning to port also other feature in the future.

From the blog post:
We've authored over 20 highly effective features, aimed at improving perceptual quality and ease of use

20+ total.
8 merged (+1 discarded, + 1 compiler fix).

So, excluding the compiler fix, 20+ - (8 + 1), there are still 11+ specific features still in SVT-AV1-PSY only?

[Z2697]

What's spy-rd?

[Kurt.noise]

What's spy-rd?
it's a psychovisually-based metric focused on enhancing sharpness and detail retention, with a slight trade-off in blocking and banding artifacts, without deeply affecting RD/RDO decisions like psy-rd. The default is 0 (disabled).

It can be used independently or alongside psy-rd.