fhqwgads

From a technical level you should use something lossless in this situation, but it really quickly becomes impractical. Actually lossless 1080p60 is going to be something like 500mbps, so if you're playing for an hour I hope you have a spare 2tb drive laying around. The artifacts in really high bitrate compressed video are so minimal that they basically don't matter. Often codecs do noise removal first thing so whatever minor artifacts still exist will get smeared over by that anyway.

Also when you are testing make sure there's some movement in the video. AV1 especially has modes for presentations and things that basically make a PowerPoint, so sizes might be unrealistic if you're just recording your desktop. I don't think that gets enabled in handbrake but it's been a while since I looked.

If you're seeing any artifacts in the original video, you probably need to re-record in a higher bitrate. It needs to look identical to uncompressed. Your later encodes will be trying to encode all the artifacts in the original video, which could be why the file sizes keep getting bigger - you're giving it noisier video than the original.

50mbps for recording as an intermediate like that is well within the realm of normal. You can try having obs record in 264 with a quality setting instead of a bitrate setting, which can save space when things are more static - something like cq 6 or lower can do pretty well.

Unfortunately, yeah finding the sweet spot does take forever. One thing I would recommend is once you have an idea where you want to land, try a few much longer videos and see what the differences are. Slower paced sections might compress much better than the fast action stuff in one codec or another. Again it's all kind of a balancing act on where you want to be.

In the third screenshot, preset is on 7, change that to 4. That's the speed setting - 7 is trying to do it in close to real time, 4 will take much longer but be much more efficient.

Can you post a screenshot of your Handbrake settings? You should definitely be getting better efficiency than that.

Because it's just for personal archival, I would recommend recording in super high bitrate 264 or 265 depending on what your card can do in real time, then compressing that file later using either av1 or 265, depending on which works better for the content.

If you're playing in 1440p165, then you should record that to start although if it's an option I would play and record at 1080p120. 1440 is a bit of an odd duck resolution that some stuff doesn't really like, but it's getting better all the time so it's not a huge deal. More important is 120fps because if you decide to go down to 60 or even 30fps they split evenly, which is important since it means the extra frames just get thrown out. There's no 82.5 frame so it either has to blend two together or pick one that's at the wrong time, and neither looks good.

Record in OBS using like, 25-40mbps in whatever your graphics card can do realtime, with all the audio tracks in something lossless like FLAC. High enough it might as well be uncompressed.

Once you have your gameplay recording from OBS, use either Handbrake or FFMPEG to convert it to your long term storage format. Since this is such a big project I would make some samples using cheats to get an idea what the bullet-hell-iest parts will look like, then try a few different handbrake or ffmpeg settings, and see what gives you the tradeoff of file size and quality that you like. It'll also give you a ballpark idea about how much long term storage you'll need.

Non-realtime encoding like ffmpeg and Handbrake is much more efficient than realtime done by your graphics card, like on the order of like half the file size for the same quality - that's why you want the two step process. It also allows you to play in 120fps for that responsiveness, but watch at 60 or even 30fps to save some file size.

When you set up handbrake, you'll have a few settings to play with and make samples from - encoder, quality level, speed, fps, and rescaling.

Encoder is probably the most important. Use either x265 or SVT-AV1. In my experience, they're close in terms of efficiency, but AV1 pulls ahead in certain situations. AV1 is more efficient about large static sections and when it breaks up it just looks blurry. 265 is better at retaining texture, but when it fails its gross digital blocks. 265 is faster than AV1, but when you push AV1 and it takes 1000 years it does a better job. Basically, run a lot of tests and then decide.

Scaling is where you go from 1440 to 1080 and is probably the least important for file size. I honestly wouldn't bother with it, but you can try. Like I said, technically some TVs don't like 1440, and everything supports 1080, but I wouldn't worry about it too much.

FPS I have the least experience with. My guess is that going do something lower is going to save you some size, but its really going to depend on the codec and the content.

Quality level is the most important setting - just set it to what you think is watchable. It doesn't use a bitrate, it adjusts the bitrate to get a constant quality level, so it's much more efficient. It's important to note that they aren't exactly the same at every speed setting, so be careful.

Lastly is the speed. 265 goes from very fast to very slow, and AV1 goes from 9 (fast) to 0 (stupid slow). Personally I use slow or very slow for 265 and about 4 for AV1, but if you have a lot of video to crunch through you might want to crank that up a bit.

For audio use OPUS. 96 is the default "bitrate" and I find it to be enough. Some players don't like it but if you're thinking about using AV1, anything that would support AV1 supports opus.

The main thing will just be doing a bunch of video encode samples and finding the settings and workflow that's right for you.

Mot and Monstrum? Why target me so precisely?

https://www.pbs.org/video/mothman-americas-notorious-winged-monster-ivhuou/

The way I've been thinking about would be to have the "meta community" be a separate thing from each individual community. Each individual community would opt in to joining, and would retain their own moderation and users, but the posts would be sort of cross posted to the meta community. The meta community mods largely just deal with removing posts that don't fit. All the comments go on the original instance of the post and are moderated there, so the meta community mods might be allowed to moderate those comments on an opt in basis.

The idea is that it's for very similar communities across different instances, but because it's opt in there are probably other uses. The hope would be that each individual community could retain their vibe, while the meta community would have more of a firehose of content, and possibly filter some of those topics back down for more in depth discussion.

I'd also love for individual users to be able to group communities for themselves, and for those to be shareable, which seems much quicker to implement.

Do you mean specifically webcam drivers? Because Magic Lantern still works as far as I know?

https://www.magiclantern.fm/

Oh no not this again. These articles pop up all the time and they're kind of awful when put in context - like yeah solar panels aren't perfect, but they're pretty dang close honestly. It's great that they mention the stuff at the end about laser welding, but the rest of the article is kind of just fear mongering.

Firstly, panels don't really go bad - the article mentions this. But that doesn't mean they have to be thrown away. Yeah, it makes sense to put 300w/m² panels on your solar farm and replace your old 200w/m² panels. But those old panels are generally still producing power, and can be sold as used for projects less focused on absolute peak efficiency. The old three Rs tell us, Reuse is generally better than Recycle.

Secondly, panels don't randomly leech heavy metals. They sometimes have lead based solder, and contain small amounts of cadmium. If the panel is in tact in a pile or deployed it's all locked up within the panel and doesn't just jump out. It can leech out if you put ground up panels in an acidic landfill that leeches into the ground water - that's bad so we shouldn't do that, but we already don't and have even more regulation coming.

Panels are mostly glass and aluminum by weight, they're not like 20% lead or anything crazy. Recycling them safely is not some kind of crazy future tech, just a matter of regulation and economics.

Moreover, the amounts they contain are miniscule compared to what fossil fuels produce. As Nickelback says, look at this graph:

from here

Or this North Carolina paper:

Every GWh of electricity generated by burning coal produces about 4 grams ofcadmium air emissions.21 Even though North Carolina produces a significant fraction of our electricity from coal, electricity from solar offsets much more natural gas than coal due to natural gas plants being able to adjust their rate of production more easily and quickly. If solar electricity offsets 90% natural gas and 10% coal, each 5-megawatt (5 MWAC, which is generally 7 MWDC) CdTe solar facility in North Carolina keeps about 157 grams, or about a third of a pound, of cadmium out of ourenvironment.

from here

And as far as total landfill waste its dwarfed by what fossil fuels produce, even just general consumer trash:

from this paper via this blog

For most panels it seems like the most polluting thing about them is that they are produced using our current grid and not other solar panels.

the not removable Google search on the home screen and non removable date on the home screen means that I will never buy another Google phone.

I'm fairly sure that's just a launcher limitation, you can swap out the entire launcher to whatever you want. If you don't want something radically different I think lawnchair is still around.

https://lawnchair.app/

5 KILOwatt hours is a typical laptop battery? Aren't they more like 50-100wh?

Love the idea and article, but...

just 800 watts, enough to power a small fridge or charge a laptop,

I want to see a laptop with an 800w charger.