• ludrol@programming.dev
    link
    fedilink
    arrow-up
    2
    ·
    42 minutes ago

    From Q&A in git repo:

    Is dav2d a recursive acronym?
    Yes, but it is less funny than dav1d :(, except in French (“deux-vid”)

  • PumaStoleMyBluff@lemmy.world
    link
    fedilink
    arrow-up
    6
    ·
    8 hours ago

    widely deployed AV1 format

    I’m glad they’re pressing forward but I feel like I still very rarely see AV1 in the wild. Hell, I still see h264 more often than h265.

    • yessikg@fedia.io
      link
      fedilink
      arrow-up
      1
      ·
      3 minutes ago

      AV1 is the preferred format for all streaming platforms now, and it’s very nice to use for personal use too. h265 is really expensive so people are dropping it left and right

    • kender242@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      8 hours ago

      “They also want to improve threading, accelerate dav2d for less common architectures, such as PPC, SSE2, RISC-V, or AVX-512, improve the C code base with various tweaks, use more GPU decoding when possible, provide a usable API for devs to integrate dav2d into their projects, and port dav2d to most platforms.”

      It’s in the plans (Step 15) but not forgotten.

      • brucethemoose@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        5 hours ago

        It’s the last step, though.

        I’m not making demands of free software; all of that development is appreciated.

        But it does seem to be CPU-first, like dav1d and previous efforts. And I know from previous projects, GPUs have many constraints that make offloading a CPU-centric project difficult, unless it’s the #1 priority from the start.

        I’m just saying it’d be interesting another AV2 project that shot for pure, or as-pure-as-possible, GPU shader decoding. It would make AV2 a whole lot more accessible than CPU-centric decoding.