• 0 Posts
  • 45 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle

  • Normally I would recommend a 50 or a little higher for portraits but if it’s going to be your only lens 35 isn’t a bad choice (on aps-c).

    The 85 or 100 might be nicer to use for macro not because of the 1:1 but because of the farther working distance. But they are going to be borderline useless for day to day portraits. For studio portraits maybe it would work but I definitely wouldn’t want it as my only lens.

    If you’re specifically worried about magnification on the 35, consider grabbing some extension tubes. They’re really cheap, and you don’t need an enormous set if you’re starting at 1:2.

    Part of me wants to say get the 24 macro and the 50 1.8 which is like the cheapest lens they make and would be a pretty good portrait lens, but wide macros are weird, and 35 is such a do everything length it’s hard to go wrong with it.



  • On the other side of the coin, large electric pressure cookers get kind of enormous. If you use your immersion circulator to do large batches, like 30 individual cheesecakes for a party or large cuts of meat, you’ll run out of room very quickly, which means batches which would take forever. Whereas an immersion circulator can be stuck in a cooler or even the bathtub and cook a lot of food at once. A small pressure cooker and an immersion circulator is a lot less space than a large pressure cooker. If you only ever cook for a few people a combo unit would be fine, but I find myself pulling out the immersion circulator much more often for events.

    I say this as someone who bought a large pressure cooker because it was a really good deal and now struggles to store it, lol.




  • fhqwgads@possumpat.iotoScience Memes@mander.xyzScIence
    link
    fedilink
    English
    arrow-up
    87
    ·
    edit-2
    6 months ago

    https://en.m.wikipedia.org/wiki/Metric_prefix

    In case you wondered where they came in the list like I immediately did:

    • quetta Q 10^30
    • ronna R 10^27
    • yotta Y 10^24
    • zetta Z 10^21
    • exa E 10^18
    • peta P 10^15
    • tera T 10^12
    • giga G 10^9
    • mega M 10^6
    • kilo k 10^3
    • hecto h 10^2
    • deca da 10^1
    • ——
    • deci d 10^−1
    • centi c 10^−2
    • milli m 10^−3
    • micro μ 10^−6
    • nano n 10^−9
    • pico p 10^−12
    • femto f 10^p−15
    • atto a 10^−18
    • zepto z 10^−21
    • yocto y 10^−24
    • ronto r 10^−27
    • quecto q 10^−30

  • To be fair, if Lemmy’s discoverability wasn’t trash you could probably have both. I would love to have a bunch of small instances that were focused on individual topics, like Star Trek or anime or knitting or gardening or whatever and just jump between them. It feels like that’s what federation was built for.

    But because Lemmy is so small right now and discoverability is so bad it seems like almost every instance is either intentionally a tech / general purpose one or so adjacent it might as well be. As long as there’s just one community for that thing that people can find that would be great, but instead there are like 10 spread around 3 different instances and 8 of them are dead and 1 just bot reposts the subreddit - and it’s really hard to tell which is which. Like, if everything was actually on one instance at least you could just list everything.








  • To be fair, people are generally coming around to it and it’s kind of on it’s way to being a cult classic now. People say this about everything but it was actually ahead of its time in terms of its visual style and the way it deals with the serious elements within the wild cartoon visuals.

    Weirdly, I kind of think Marvel movies like Guardians might have been the thing that tipped the scales. The breakneck editing is still way ahead of anything I’ve seen since though.


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




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