Announcement

Collapse
No announcement yet.

NVIDIA 430.09 Linux Driver Brings GTX 1650 Support, Surprising VDPAU Improvements

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

  • enihcam
    replied
    Originally posted by phoronix View Post
    Phoronix: NVIDIA 430.09 Linux Driver Brings GTX 1650 Support, Surprising VDPAU Improvements

    With today's GeForce GTX 1650 launch, NVIDIA has posted the 430.09 Linux driver as their first in this new driver series...

    http://www.phoronix.com/scan.php?pag...Linux-Released
    Check this out, VDPAU is adding support of VP9:

    Leave a comment:


  • smitty3268
    replied
    Originally posted by Gusar View Post
    [USER="10517"]Edit: There's a possibility that the driver has the ability to decode 10bit video to 8bit surfaces, but that means you aren't getting the full 10 bits, but a scaled down result. And I'm not sure even that is supported by players. With VAAPI, you'll get the full 10 bits.
    I believe that's what happens. It decodes 10 bit video but with lower quality output.

    Leave a comment:


  • Gusar
    replied
    FireBurn Have you tried that in an actual player? Note how the patch you linked to only adds definitions to a header. Meaning it's possible for a driver to advertise support, but that's it. There is no way to actually use 10bit, unless you can point me to a commit that adds 10bit surface support to VDPAU.

    Edit: There's a possibility that the driver has the ability to decode 10bit video to 8bit surfaces, but that means you aren't getting the full 10 bits, but a scaled down result. And I'm not sure even that is supported by players. With VAAPI, you'll get the full 10 bits.
    Last edited by Gusar; 24 April 2019, 12:26 AM.

    Leave a comment:


  • FireBurn
    replied
    Originally posted by Gusar View Post
    Are you sure you're using VDPAU and not VAAPI? There is no 10bit surface support in VDPAU.
    Looks like 10bit & 12bit support were added 4 years ago for HEVC https://gitlab.freedesktop.org/vdpau...6327e85add7fa9

    Leave a comment:


  • FireBurn
    replied
    Originally posted by Gusar View Post
    Are you sure you're using VDPAU and not VAAPI? There is no 10bit surface support in VDPAU.
    vdpauinfo
    display: :0 screen: 0
    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

    Decoder capabilities:

    name level macbs width height
    ----------------------------------------------------
    MPEG1 --- not supported ---
    MPEG2_SIMPLE 3 65536 4096 4096
    MPEG2_MAIN 3 65536 4096 4096
    H264_BASELINE 52 65536 4096 4096
    H264_MAIN 52 65536 4096 4096
    H264_HIGH 52 65536 4096 4096
    VC1_SIMPLE 1 65536 4096 4096
    VC1_MAIN 2 65536 4096 4096
    VC1_ADVANCED 4 65536 4096 4096
    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 0 65536 4096 4096
    H264_EXTENDED --- not supported ---
    H264_PROGRESSIVE_HIGH --- not supported ---
    H264_CONSTRAINED_HIGH --- not supported ---
    H264_HIGH_444_PREDICTIVE --- not supported ---
    HEVC_MAIN 186 65536 4096 4096
    HEVC_MAIN_10 186 65536 4096 4096
    HEVC_MAIN_STILL --- not supported ---
    HEVC_MAIN_12 --- not supported ---
    HEVC_MAIN_444 --- not supported ---

    Output surface:

    name width height nat types
    ----------------------------------------------------
    B8G8R8A8 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 A8I8 I8A8
    R8G8B8A8 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 A8I8 I8A8
    R10G10B10A2 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 A8I8 I8A8
    B10G10R10A2 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 A8I8 I8A8

    Bitmap surface:

    name width height
    ------------------------------
    B8G8R8A8 16384 16384
    R8G8B8A8 16384 16384
    R10G10B10A2 16384 16384
    B10G10R10A2 16384 16384
    A8 16384 16384

    Video mixer:

    feature name sup
    ------------------------------------
    DEINTERLACE_TEMPORAL y
    DEINTERLACE_TEMPORAL_SPATIAL -
    INVERSE_TELECINE -
    NOISE_REDUCTION y
    SHARPNESS y
    LUMA_KEY y
    HIGH QUALITY SCALING - L1 y
    HIGH QUALITY SCALING - L2 -
    HIGH QUALITY SCALING - L3 -
    HIGH QUALITY SCALING - L4 -
    HIGH QUALITY SCALING - L5 -
    HIGH QUALITY SCALING - L6 -
    HIGH QUALITY SCALING - L7 -
    HIGH QUALITY SCALING - L8 -
    HIGH QUALITY SCALING - L9 -

    parameter name sup min max
    -----------------------------------------------------
    VIDEO_SURFACE_WIDTH y 48 4096
    VIDEO_SURFACE_HEIGHT y 48 4096
    CHROMA_TYPE y
    LAYERS y 0 4

    attribute name sup min max
    -----------------------------------------------------
    BACKGROUND_COLOR y
    CSC_MATRIX y
    NOISE_REDUCTION_LEVEL y 0.00 1.00
    SHARPNESS_LEVEL y -1.00 1.00
    LUMA_KEY_MIN_LUMA y
    LUMA_KEY_MAX_LUMA y

    Leave a comment:


  • tildearrow
    replied
    Originally posted by Gusar View Post
    no one in the end-user world deals with 4:4:4 video, it's only used in intermediate steps of video production.
    I primarily prefer 4:4:4 chroma subsampling for screen recordings.

    Leave a comment:


  • Gusar
    replied
    Originally posted by Hibbelharry View Post
    Since VDPAU is a X11 technology
    It's not actually. The windowing system support is a small part of the library and is well isolated. So it would not be that difficult to add support for a windowing system other than X. Nvidia would just need to care. Which they don't, since the creator of VDPAU left the company years ago. The things added in this driver release are very clearly something a specific workstation customer of Nvidia wanted, no one in the end-user world deals with 4:4:4 video, it's only used in intermediate steps of video production.

    Leave a comment:


  • Hibbelharry
    replied
    Since VDPAU is a X11 technology, it's also a dead end, it will never be decoupled from X11. The nvidia camp is rolling towards nvenc/nvdec(nvcuvid) and intel/amd are using va-api. VDPAU is mostly there for legacy environments.

    Leave a comment:


  • Gusar
    replied
    Originally posted by FireBurn View Post
    Seems to support 10bit here on AMD
    Are you sure you're using VDPAU and not VAAPI? There is no 10bit surface support in VDPAU.

    Leave a comment:


  • FireBurn
    replied
    Originally posted by Gusar View Post
    So Nvidia finally realized having a hardware decode interop that operates with fields instead of frames is braindead. Good. But VDPAU is still missing 10bit support, VP9 decoding and disentanglement from X.
    Seems to support 10bit here on AMD

    Leave a comment:

Working...
X