Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)RX
Posts
42
Comments
838
Joined
2 yr. ago

  • I meant visually web vs disc. To me, a 4k 15 Mbps web-DL is visually 99% as good as a 60+Mbps UHD BR remux.

    Web-DL may not be how I want to watch something like Interstellar (shot on 70mm film) but is probably fine for something like 7 Fast 9 Furious Tokyo Zoom Zoom (shot on Vin Diesel's iPhone, probably)

  • Is the h264 or x264 part of the name the bitrate?

    No, that's the encoding algorithm, aka codec. As another person pointed out, AVC/h264/x264 (all different names for what is effectively the same thing) is a lot easier to process than HEVC/h265/x265 (again, different names, same end result).

    Bitrate is just the overall file size divided by the movie duration, basically indicating how compressed the movie is, with compression coming at the loss of finer details. You can generally gauge bitrate based on file size. A 5000 Mb file that is 1000 s long is, on average, 5000/1000=5 Mbps.

    Since you're very clearly not picky, you're probably best off going for 720p or 1080p content with small file sizes (1-5 GB / movie). Feel free to download smaller though, if it doesn't impact your experience, just make a mental note if you ever find anything that is too small for you to tolerate, and set your minimum file size somewhere above that.

    Based on your criteria, you probably want to steer clear of terms like Atmos, TrueHD, DTS-MA, and DTS-X. These are all terms for different flavors of totally uncompressed audio, which alone can be up to 5GB of unnecessary (for you) added disc space for a given movie. Instead you want compressed audio like DDP, AAC, or AC3

    DivX/XVID are really old video codecs, kinda like x264. I wouldn't fuck with them even with your preferences unless you have no other choice, given your average potato nowadays can handle x264.

    TL;DR, based on your preferences, look for / avoid these terms, but know not all files have all of the same fields identified:

    GOOD

    Video

    AVC/h264/x264

    720p or 1080p

    8-bit (you'll want this over 10-bit, if specified)

    Audio

    DDP, AAC, or AC3

    Overall

    1-5 GB file size / movie

    MEH

    Video

    DivX/XVID

    Overall

    Be mindful of files smaller than 1 GB / movie, they may be fine for you but this is where you can really start to see some gnarly banding

    AVOID

    Video

    HEVC/h265/x265 or VC1

    2160p

    HDR, HDR10, HDR10+, DoVi, or DV (not mentioned earlier but these need special, more modern, displays)

    Audio

    Atmos, TrueHD, DTS-MA, and DTS-X

    Overall

    Really large or comically small files.

  • Unfortunately quality is entirely subjective. What you may think is fine, I may hate, and vice versa.

    Generally speaking, for a given movie, quality and bitrate are linked, but two movies with the same bitrate likely don't have the same quality because of a myriad of factors.

    For me, with a few limited exceptions of movies I know like the back of my hand, I have a really hard time distinguishing between a good 4K webrip (15-20 Mbps) and remux (40-80 Mbps), so I have no issue keeping the majority of my library encoded at ~18Mbps

    Unfortunately there's no quality magic wand, but if you find a release group that does encodes you like, try to get to their home tracker and just let them handle it.

    If you're good with 1080p non-HDR content, for your use case you probably want to focus on "AVC" aka "H.264" or "x264" encodes of decent bitrate. HEVC yields better quality than AVC for a given bitrate, but comes at the cost of being much more intensive to encode and decode, which may be a source of problems for your 10 y.o. box. If your bar is "tell what's happening", you can go to pretty low bitrates.

    Handbrake is a robust piece of software, but it's really not beginner friendly because the automatic encoder settings will just absolutely ruin whatever you feed it.

    If you're on windows, check out StaxRip for encoding

  • The folks over at XDA have rooted the original Hibreak and are actively working on trying to reverse engineer the display drivers so they can install LineageOS. The person working on it right now has a good track record with other e-ink phones.

    I wouldn't pull any triggers until it's released, but worth watching that activity.

    ETA: https://xdaforums.com/t/bigme-hibreak-root-mediatek-6765.4697830/page-7

  • Not sure I understand the boycott but still watch crowd. Sure, not watching makes viewership go down a tick, but the Superbowl is so cultural, every hallway "did you see the game" helps push those viewership numbers right back up

  • Speak with your money.

    This is tough to do when there's often not a functional alternative. Buying old motherboard stock and a non-HDR monitor isn't going to teach manufactures people want Linux support, they'll just think you are saving money / don't care about new features.

    Without some sort of clear 'Linux Certified' system they can compare sales against, no hardware manufacturer is going to be able to recognize the 0.1% sales increase stemming from the time random internet volunteers fixed the open source implementation of their display drivers.

  • Dear lord I can't believe this is only now becoming a feature - those redirect spammers are the worst! What do you gain from making my life more difficult? I just close the tab and search again, this time with your website blacklisted.

  • Cool story bro. There was (and likely still is, because you clearly haven't found it) a keylogger on your system when you logged into Steam at some point.

    You can continue in denial if you want, it literally makes no difference to me - I'm not the one getting HIBP Stealer Log emails. Just trying to warn you, I wouldn't log into anything you care about getting hacked until you find out what caused the breach.

  • Man, the denial runs deep.

    HIBP works by finding big databases of stolen information on the dark web. Usually these databases are attributed to websites that have been breached.

    In the case of "stealer logs" though, the databases are full of logins to a bunch of different websites, instead indicating it comes from hacked computers.

    They, and I, can't truly say for certain that your computer was hacked, so instead they have to make vague statements like "someone attempted to log into your account on a compromised computer". That information went to the hackers who developed the virus, and they posted it online. They don't know your computer is infected, just that your information ended up in a pile with a bunch of other people's whose computers were infected.

    The person logging in could be you, could be anyone, they may not have even gotten in, but the #1 most likely scenario is you logged into your account on your computer while a virus was running in the background capturing information.

    Your computer being the one with the virus is made 1000x more likely because you mention in previous posts that you use pirated software.

    If you pirate software, and you get a HIBP stealer log notice, I'd wager there's a 99.7% chance someone snuck a keylogger into one of the programs you downloaded.