gianni

joined 2 years ago
MODERATOR OF
av1
[–] gianni@lemmy.ml 2 points 1 day ago (1 children)

I should have clarified that I was referring to “Restart” rather than “Shut Down” because I’m not aware of how frequently people actually “Shut Down” their devices. My intention was to ask: How often would you need to physically press the power button when the functionality of turning the device on and off is accessible through software?

On another note, I think the amount of attention posts like this get is a pretty clear indication of how deep Apple hate truly runs. I'm fine with Apple, more of a Linux person myself, but stuff like this makes me shrug my shoulders. Only Apple could garner this much attention for putting the power button in a weird spot on a tiny desktop that nobody complaining about it would buy even if it was on top of the device.

[–] gianni@lemmy.ml 5 points 5 days ago (12 children)

Unless your computer has issues, can’t you just power off from within macOS?

6
SVT-AV1-PSY v2.3.0 (svt-av1-psy.com)
3
SVT-AV1-PSY v2.2.1-B (svt-av1-psy.com)
[–] gianni@lemmy.ml 3 points 4 weeks ago

JPEG XL support in Waterfox is nice.

4
SVT-AV1-PSY v2.2.1-A (svt-av1-psy.com)
[–] gianni@lemmy.ml 14 points 1 month ago

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

 

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.

 

Give the issue & upvote and comment to show your support - every like helps!

[–] gianni@lemmy.ml 1 points 2 months ago

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, 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

[–] gianni@lemmy.ml 0 points 2 months ago

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.

[–] gianni@lemmy.ml 2 points 2 months ago (2 children)

vt-enc calls FFmpeg which calls the VideoToolbox encoding framework. Without VT, ffmpeg commands will fail

[–] gianni@lemmy.ml 1 points 2 months ago (4 children)

VideoToolbox is the encoder that FFmpeg links to.

[–] gianni@lemmy.ml 2 points 2 months ago

Filesystem compression is dope.

[–] gianni@lemmy.ml 2 points 2 months ago* (last edited 2 months ago) (1 children)

Thanks for the helpful advice! Shellcheck is the best :)

Edit: How do I get the ANSI escape colors to appear with the cat << EOF syntax?

 

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.

 

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 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.

 

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:
  • Required Python packages:
    • vapoursynth
    • matplotlib
    • tqdm

See more in the linked Git repo's README!

 

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

 

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

view more: next ›