DaGeek247 of https://dageek247.com

  • 3 Posts
  • 54 Comments
Joined 5 months ago
cake
Cake day: February 16th, 2024

help-circle




  • When you think about it, Calvin & Hobbs is really the story of a lonely boy seeping deeper and deeper into mental illness, while he struggles with low self esteme

    What? No, not even. First of all, Calvin and Hobbes is written specifically to allow for a Toy Story situation; they’re only pretending to be not alive when adults are watching.

    Second of all, Calvin never had any major mental illnesses (except maybe undiagnosed ADHD), much less “seeping deeper and deeper” into it. The author never intended that, and I damn sure never got that from any of my re-reads either.

    Meanwhile his parents mostly ignore him. Only being used in panels where Calvin needs discipline.

    Again, not even close. It wasn’t even hard to find counter-evidence for this.

    the most famous image of Calvin is him peeing

    Only in the same way that Shirley Temple is most famous for her childhood acting, despite being a US diplomat later in life. What Calvin and Hobbes is most widely recognizable as has no bearing on what the majority of the comic was about.











  • Both. How quickly a server can send a webpage with images (even if they’re small) is directly proportional to the storage mediums seeks times. The worse the seek times, the less ‘responsive’ a website feels. Hard drives are a terrible location to keep your metadata.

    The server scan will search for the files, look them up and grab metadata, and then store that metadata in the metadata location. If your metadata location is the same spot as your movie, it will cause some major thrashing, and will significantly increase the scan time for jellyfin. Essentially, it gets bogged down trying to read and write lots of tiny files on the same drive, the absolute worst case scenario for a hard drive to have.

    If the movies are on a hard drive, and the metadata on an ssd (or even just a different hard drive) the pipeline will be a lot less problematic.



  • Skipping the audio encode from a blu-ray will lose op out on a surprisingly large amount of space, especially with 110 source disks. I checked one of my two hour blu-ray backups. Audio will net you about nine audio tracks (english, french, etc). A single 5.1 448kbs audio track will take about 380MB of space per movie. Multiply that by nine (the number of different tracks in my sample choice) and you’ll get 3420MB per disk. That means about 376GB of space is used on audio alone for ops collection. A third of a terabyte. You can save a lot of space by cutting out the languages you don’t need, and also by compressing that source audio to ogg or similar.

    By running the following ffmpeg command; ffmpeg -i out-audio.ac3 -codec:a libvorbis -qscale:a 3 small-audio.ogv I got my 382MB source audio track down to 200MB. Combine that with only keeping the language you need, and you end up dropping from 376GB down to 22GB total.

    You can likely save even more space by skimping on subtitles. They’re stored as images, so they take up a chunk of space too.