• frazorth@feddit.uk
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    17 days ago

    If the driver is no longer using a dedicated piece of encoding hardware thats shit, but using the Vulkan logic then surely the quality would be essentially guaranteed by it being Vulkan conformant?

    The hardware wouldn’t support b-frames in this scenario, and wouldn’t matter because your just using the standard matrixes to encode the stream and if it didn’t work then surely games would also be broken.

    Or am I incorrect. Is this just standardising the API in Vulkan and it gets forwarded to the same video encoding driver? Could we not have Mesa doing a better job? 😒

    • Laser@feddit.org
      link
      fedilink
      arrow-up
      2
      ·
      17 days ago

      Or am I incorrect. Is this just standardising the API in Vulkan and it gets forwarded to the same video encoding driver? Could we not have Mesa doing a better job? 😒

      This is how I would read it. But if you have Mesa do it, it’s in software, and you might just be using a software coded directly then, it’s much easier.

      • frazorth@feddit.uk
        link
        fedilink
        arrow-up
        1
        ·
        17 days ago

        I wrote Mesa but meant ffmpeg. Wishful thinking that they are able to make a generic ffmpeg encoder in Vulkan to allow it to be accelerated in hardware but not relying on bad video driver codecs.

        Oh well, back to Intel.

    • heftig@beehaw.org
      link
      fedilink
      arrow-up
      2
      ·
      17 days ago

      It’s about adding API to Vulkan for access to the hardware encoding units that you’re complaining about.