• Kushan
    link
    fedilink
    English
    93
    edit-2
    1 month ago

    It’s incredibly difficult to read the captions on this meme, there’s not enough contrast with the white text on the light backgrounds.

  • @Petter1@lemm.ee
    link
    fedilink
    351 month ago

    Ahh, the time of streaming xvid codec and having divX video player everywhere 😂 good old times

  • @pHr34kY@lemmy.world
    link
    fedilink
    301 month ago

    Xiph have always produced the best stuff. Competition is great and all, but at the end of the day, Xiph’s codecs beat everyone at everything.

  • Delilah (She/Her)
    link
    fedilink
    English
    221 month ago

    libaom is a fucking joke. SVT might be a memory hog, but as the proud owner of a system with enough memory to run it, I can proudly say my 1 minute video rendered in less than ten minutes and somehow had worse compression than x264

    Wait, whot?

    • Constant Pain
      link
      fedilink
      321 month ago

      The image is implying it’s 95% written in Assembly and that’s why it finished so fast.

  • hitagi (ani.social)
    link
    fedilink
    151 month ago

    I really like SVT. AOM (or whatever the default was for ffmpeg) was terribly slow. Now I have to try out rav1e.

  • @jh29a@lemmy.blahaj.zone
    link
    fedilink
    7
    edit-2
    1 month ago

    I really want to know why they implemented a piece of software that’s this complicated in assembly. Is it just speed? Then I also want to know what all the great numbers of video codecs I have just uncovered after clicking on “the input format must be .y4m” in their Readme. Since OP seem to know about the 306 options of the official AOM encoder a little, and rav1e also sounds rather CLI-heavy, this also gets my uneducated head wondering where these products are used. Do other app developers drop it in like ffmpeg? Probably. It also sounds like Disney & Co. just have some servers that they have scripted to “encode the corporate fortune”. How true is this?