A friend and I were discussing recently the interesting phenomenon where despite us having highly unrelated jobs/passions with unrelated skillsets, we are both considered "software engineers" because we happen to write code. I believe this happens because when, say, family asks what we do, it usually feels like they're mainly interested in the day-to-day as opposed to the core purpose of the work. This makes perfect sense and is fine, but between two people who write code it is probably reductive communication.

This prompted us to strip back the code-writing part and come up with a new job title for each of our occupations; my actual job, and his primary interest. The new titles were far more descriptive of the core work we both do that is probably more salient on a fundamental level than the programming part.

Mine was "software engineer" -> "video compression researcher" His was "software engineer" -> "web platform designer/developer" (using developer in the name still feels like cheating, but we couldn't think of anything else)

SWEs (or CS students): Do this for yourselves. What does this look like for you?

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.

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

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 SVT-AV1 2.0.0? Well-known encoder Trix attempts to answer this question with metrics, graphs, and detailed analysis.

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

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

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 (or enable-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

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

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!

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.