• beerclue@lemmy.world
    link
    fedilink
    arrow-up
    158
    ·
    26 days ago

    I don’t understand what this is about, but I admire the commitment, the story, the CGI. 7/10.

  • Kushan@lemmy.world
    cake
    link
    fedilink
    English
    arrow-up
    93
    ·
    edit-2
    25 days 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
    arrow-up
    35
    ·
    26 days ago

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

  • pHr34kY@lemmy.world
    link
    fedilink
    arrow-up
    32
    ·
    26 days 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)@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    22
    ·
    25 days 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?

  • jh29a@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    25 days 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?