Announcement

Collapse
No announcement yet.

Mesa 22.2 Released With AMD RDNA3 Prep, Intel Arc Graphics, Many Vulkan Improvements

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Quackdoc
    replied
    Originally posted by marlock View Post
    Oh, I see! Thanks for clearing it up! That's much nicer than the parallel reality I was briefly living in
    I wouldn't even be all that upset myself, since it would help push av1 and vp9 even more

    Leave a comment:


  • marlock
    replied
    Oh, I see! Thanks for clearing it up! That's much nicer than the parallel reality I was briefly living in

    Leave a comment:


  • Quackdoc
    replied
    Originally posted by marlock View Post

    Isn't that what this means?

    Sure enough you can use an old version of mesa, or patch the new code, but that's very different from flipping a flag when compiling the new code.
    ah I see, no you got it backwards, it means that mesa introduced the capability to build mesa without needing to enable those codecs, before if you enabled vaapi you had to enable all codecs such as avc and hevc, so what is being said here is that you now have the ability to build mesa with vaapi without needing said codecs.

    now you specify something like -Dvideo-codecs h264enc h265dec etc.

    Leave a comment:


  • marlock
    replied
    Originally posted by Quackdoc View Post

    what are you talking about here? you can still enable the codecs in git...
    Isn't that what this means?
    Support for building Mesa with select video codecs disabled out of software patent concerns.
    Sure enough you can use an old version of mesa, or patch the new code, but that's very different from flipping a flag when compiling the current version of the code. And the way this is written isn't pointing towards just a new compile flag with default state off.
    Last edited by marlock; 18 October 2022, 05:33 AM.

    Leave a comment:


  • Quackdoc
    replied
    Originally posted by marlock View Post
    wow, i knew it was sensible of RedHat to pull out those codecs from a finished distro release, but to see mesa devs deem it legally too risky to even let the option available for others to compile mesa with those codecs?!

    it's horrible to see how patent law can be so pernicious and antagonic to technological advancement and adoption, and it's also a bit scary that this has been in there until now and only now did they wake up to such a big risk being taken...
    what are you talking about here? you can still enable the codecs in git...

    Leave a comment:


  • marlock
    replied
    also it's a bit ironic that Nvidia now has a VA-API over NVENC compatibility layer at the same time that so many patent-encumbered codecs are ripped off of opensource drivers...

    Leave a comment:


  • marlock
    replied
    wow, i knew it was sensible of RedHat to pull out those codecs from a finished distro release, but to see mesa devs deem it legally too risky to even let the option available for others to compile mesa with those codecs?!

    it's horrible to see how patent law can be so pernicious and antagonic to technological advancement and adoption, and it's also a bit scary that this has been in there until now and only now did they wake up to such a big risk being taken...

    Leave a comment:


  • nuetzel
    replied
    Yes, thanks (I konw ;-) )
    All fine for some days.
    But I haven't had time for earlier posting.
    More to come.

    See here, too:
    Fedora Linux Disabling Mesa's H.264 / H.265 / VC1 VA-API Support Over Legal Concerns
    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

    Leave a comment:


  • LoneVVolf
    replied
    Check if the mesa build you use adds
    Code:
    -D video-codecs=vc1dec,h264dec,h264enc,h265dec,h265enc
    to its meson command.

    See https://gitlab.freedesktop.org/mesa/...29c163e42c3600 and https://bugs.archlinux.org/task/74615 for more info.

    Leave a comment:


  • nuetzel
    replied
    Radeon(SI)
    Can anyone please verify if most VA and VDPAU hardware accelerated modes didn't work for you any longer, too?

    Polaris 20, here.
    See it for several months.
    Due to LLVM 14/15 (git) and other toolchain things I haven't bisected it, yet.
    I've currently no idea which commit could be the culprit.

    vainfo
    libva info: VA-API version 1.15.0
    libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
    libva info: Found init function __vaDriverInit_1_15
    ATTENTION: default value of option mesa_glthread overridden by environment.
    ATTENTION: default value of option allow_draw_out_of_order overridden by environment.
    libva info: va_openDriver() returns 0
    vainfo: VA-API version: 1.15 (libva 2.15.0)
    vainfo: Driver version: Mesa Gallium driver 22.3.0-devel for AMD Radeon RX 580 Series (polaris10, L
    LVM 15.0.0, DRM 3.47, 5.19.10-3.g415f514-default)
    vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple : VAEntrypointVLD
    VAProfileMPEG2Main : VAEntrypointVLD
    VAProfileJPEGBaseline : VAEntrypointVLD
    VAProfileNone : VAEntrypointVideoProc

    vdpauinfo
    display: :0 screen: 0
    ATTENTION: default value of option mesa_glthread overridden by environment.
    ATTENTION: default value of option allow_draw_out_of_order overridden by environment.
    API version: 1
    Information string: G3DVL VDPAU Driver Shared Library version 1.0

    Video surface:

    name width height types
    -------------------------------------------
    420 16384 16384 NV12 YV12
    422 16384 16384 UYVY YUYV
    444 16384 16384 Y8U8V8A8 V8U8Y8A8
    420_16 16384 16384
    422_16 16384 16384
    444_16 16384 16384

    Decoder capabilities:

    name level macbs width height
    ----------------------------------------------------
    MPEG1 --- not supported ---
    MPEG2_SIMPLE 3 65536 4096 4096
    MPEG2_MAIN 3 65536 4096 4096
    H264_BASELINE --- not supported ---
    H264_MAIN --- not supported ---
    H264_HIGH --- not supported ---
    VC1_SIMPLE --- not supported ---
    VC1_MAIN --- not supported ---
    VC1_ADVANCED --- not supported ---
    MPEG4_PART2_SP 3 65536 4096 4096
    MPEG4_PART2_ASP 5 65536 4096 4096
    DIVX4_QMOBILE --- not supported ---
    DIVX4_MOBILE --- not supported ---
    DIVX4_HOME_THEATER --- not supported ---
    DIVX4_HD_1080P --- not supported ---
    DIVX5_QMOBILE --- not supported ---
    DIVX5_MOBILE --- not supported ---
    DIVX5_HOME_THEATER --- not supported ---
    DIVX5_HD_1080P --- not supported ---
    H264_CONSTRAINED_BASELINE --- not supported ---
    H264_EXTENDED --- not supported ---
    H264_PROGRESSIVE_HIGH --- not supported ---
    H264_CONSTRAINED_HIGH --- not supported ---
    H264_HIGH_444_PREDICTIVE --- not supported ---
    VP9_PROFILE_0 --- not supported ---
    VP9_PROFILE_1 --- not supported ---
    VP9_PROFILE_2 --- not supported ---
    VP9_PROFILE_3 --- not supported ---
    HEVC_MAIN --- not supported ---
    HEVC_MAIN_10 --- not supported ---
    HEVC_MAIN_STILL --- not supported ---
    HEVC_MAIN_12 --- not supported ---
    HEVC_MAIN_444 --- not supported ---
    HEVC_MAIN_444_10 --- not supported ---
    HEVC_MAIN_444_12 --- not supported ---
    AV1_MAIN --- not supported ---
    AV1_HIGH --- not supported ---
    AV1_PROFESSIONAL --- not supported ---

    Leave a comment:

Working...
X