I believe h.265 has particular handling for "film grain". And it has hardware decoding on just about every chip out there. And you probably already have a hardware encoder, so you can do something like QSV in a reasonable time frame.
300MB for a half-hour is a pretty reasonable bitrate, for one and a half hours it is quite dire.
sl is the single best utility, hands down
The fix is to make it a Ctrl key.
Kinda wish that Valve would just make hall-effect the stock part. My left stick only lasted about a year, while the Gulikit shows no signs of stopping.
First, it never hurts to reboot. There could be some dumb state going on in your display server. Or kernel DRM. Or in some little bs microcontroller in the video card.
Next, read the arch wiki on hardware video acceleration. Contemplate the note(2) at the very bottom of the page and boggle at all the PPANAPAPPI acronyms bouncing around in there.
VLC has two major sides to its video settings, the (Video)output method and the (Input/Codecs)hardware-acceleration. You are on the VDPAU acceleration API, so give VAAPI a try for a bit. Remember you have to restart VLC before any change takes. VLC should be smart about choosing a good Automatic option, but it can't do much about "looks like an API's there, but it's broke".
Try mpv. Try VLC, but from Flatpak (which brings its own version of a lot of the acceleration libraries).
Btrfs. Just format as one big partition (besides that little EFI partition of course) and don't worry about splitting up your disk into root and home. Put home on its own subvolume so that root can be rolled back separately from it. You can have automatic snapshots, low-overhead compression, deduplication, incremental backups. Any filesystem can fsck its own metadata, but btrfs is one of the few that also cares if your data is also intact.
There should be exactly one game allowed to keep its "fuck your accessibility, git gud nüb" difficulty, and its name is Zadette.
The reason you can't is "because Intel deliberately designed it that way". Back when USB was just a notion, PDAs were a really cool thing. There was apparently concern at Intel that someday these little things might be all that someone might own. You might connect your PDA directly to the printer, rather than syncing it to your Intel Desktop and printing from there. You might connect your PDA to the modem and collect electronic mailographs directly, instead of syncing with a PC. If you could do enough without the PC middleman, you might even skip on buying an Intel computer altogether.
So, Intel baked into the protocol anything they could think of to make peer-to-peer communications impossible in USB, make life easy for the singular PC communications master, and put a timing onus on devices that forced them to be dumbed-down state machines instead of computers in their own right.
Professional accreditation is such a racket lol. I've seen plenty of tax courses with "the last tax year that so-and-so was relevant was 1988, NEVERTHELESS this will be on the test." Zero effort goes into updating the material, just keep on reselling the same crap to a captive audience forever.
And if you want to get really funky, Intel also does their JTAG over USB. They are quite secretive about it, your bios should have turned it off, but it is there.
pv. It's just cat, with a progress meter.