vt-enc calls FFmpeg which calls the VideoToolbox encoding framework. Without VT, ffmpeg commands will fail
Compressionist
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.
I’m pretty much all BTRFS at this point
Minecraft is arguably & measurably more performant on Linux, full stop. Anything using OpenGL performs better on Linux, check any Minecraft benchmark online.
Also, a lot of towns/cities remove those romantic locks regularly anyway.
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.
I have customized ZSH to be very similar to Fish
I’m partial to macOS and I agree, I think Windows font rendering looks like garbage. On GNOME, I’ve found things to be okay. Sucks that patents are involved in this mess
WebP images are not bad. Not great, but not bad. The lossless mode is quite good. It is on the software you use to support WebP.
I’m happy with Wayland
Chrome OS.
Huawei’s doing great. Plus, there’s a big push in China to consider RISC-V & Linux to reduce dependence on US-based tech like Windows, so seems like all good things
Go big or go home. No need to stick with anything from a large corporation if you’re already pulling away from M$
Aside from the backdoor (which is a moot point when talking about zstd anyway), there are a number of other very good reasons to use ZSTD.
Yes, it works on Wayland. I’d also give GNOME’s Console a shot.
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.