• 1 Post
  • 56 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle
  • 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.





  • It entirely depends on how much and what you’ll use them for. They’re going to be around $200 USD all in, so if they’re for occasional use probably not. If you’re going to use them a lot like for work or a regular hobby then it’s not a crazy amount to spend. They tend to be more comfortable than flange earplugs, and a little better than foamies, but for me at least I don’t want them in for more than 3 hours.

    Etymotic makes a few different ones for general noise, sleeping, music, and they also do ones for their earphones.


  • Look for a local print or embroidery shop that you can get like work shirts and business cards and whatnot made. Unless you’re really in the middle of nowhere, there’s probably a local print shop that will at least be able to point you in the right direction. If you want a one off instead of a small batch look for a place that offers embroidery - it sounds more expensive but because they can just throw whatever on the machine and do a one off, it’s usually actually less expensive than traditional screen printing. Specifically for hats in not sure if you can get them digitally printed in most smaller local shops.


  • If you are working with a specific company to produce a personalized / custom product, they will generally have at least one person on staff that can do design, or at least deal with any file conversion and technical stuff like that. They should be able to quote you a price.

    If you are working with an artist first, they may have a company they’re familiar with to have the item produced, and if they do, should be able to handle most of it themselves. If they don’t, or you would like it produced somewhere specific, just let the artist know - most places will have all the information the artist will need on their website, or the artist can just get in touch with them directly.

    In general, if you’re going to an artist or design shop they should be able to give you some kind of quote with a very rough idea of what you want - especially if they do this professionally, talking to people who don’t have an art background is basically half their job. If you want to be specific it’s much more useful to send something like a mood board or a collage of similar things than a bunch of text. It’s also generally a good idea to be open to their ideas, as they often have experience that may be helpful and will see some problems much quicker than you might.









  • To be fair I’d call it a wash. Bedrock fixes a lot of weird stuff like quasi connectivity and being able to push things like chests with pistons but also introduces it’s own bugs like weird timing things and randomly taking fall damage. There’s also weird differences like being able to do things with cauldrons or just like minor texture differences that they are slowly bringing into sync.


  • Because Bedrock runs on phones, tablets, consoles, and a host of other random crap, and does so relatively well. Because of that the install base and playtime especially among younger players is actually massively skewed toward Bedrock being the more used. Add to that rumors that the Java codebase at least was a terrible mess, and the performance issues Java edition still has to this day and it’s no wonder they wanted to do a full rewrite, especially after having to make things like the console editions and even one for the 3DS.

    The windows launcher is annoying though.


  • If I remember correctly, it’s not the freezing point. Fahrenheit used a brine that included ammonium chloride to set 0 on his scale since it was the closest thing he could make in his lab that was a consistent temperature. The other end was body temperature, which he set at 96 if I’m remembering right since it’s more easily divisible than 100. He was a little off on his body temperature measurements so it’s considered a little higher than that now.



  • It is and it isn’t, those are pretty standard fixed wireless rates. It’s largely used in pretty rural areas where you wouldn’t be able to get fiber or cable or often even DSL. They compete against things like hughesnet that’s more expensive and has something like a 15gb data cap. Or starlink for $150 a month and $500 of equipment and the weight on your soul of giving Elon money.

    They often run wireless backhauls for tens of miles across multiple towers so bandwidth is pretty limited and setup and maintenance is somewhat specialized. Like yeah if you can get cable or fiber do that it’s way better. But when there’s no other option is not that bad all things considered.