Page 3 of 3 FirstFirst 123
Results 21 to 30 of 30

Thread: Gallium3D VDPAU State Tracker Gets Ready For Action

  1. #21
    Join Date
    Oct 2011
    Location
    Italy
    Posts
    139

    Default

    This is the most interesting feature in linux, I have already bought the radeon hd 7750 for use with Gallium3D VDPAU. :-).
    I congratulate christian konig for his work.

  2. #22
    Join Date
    Feb 2009
    Posts
    370

    Default

    Quote Originally Posted by cl333r View Post
    Yes, but it's still not as good as flash, i.e. when in fullscreen and you press the sound up/down on the keyboard, the video leaves fullscreen, it's the same wrong behavior that adobe flash had a while ago (until it matured).

    Also, it's not only the youtube html5 support that improved, but also the firefox support for html5 video, like video/byte buffers or so that I read a while ago which allows for more flexible control of the stream.
    I don't know what's going on with your system, but mine does not do this. Volume control using the arrow keys works fine without exiting full screen. But you're right about the improvements being both in Firefox AND Youtube. I have to say that I'm completely satisfied with it now.

  3. #23
    Join Date
    Oct 2011
    Location
    Italy
    Posts
    139

    Default

    Hi, vdpauinfo with radeon 6450.


    vincenzo@PhenomII-550:~$ 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 NV12 YV12 UYVY YUYV
    444 16384 16384 NV12 YV12 Y8U8V8A8 V8U8Y8A8

    Decoder capabilities:

    name level macbs width height
    -------------------------------------------
    MPEG1 16 1048576 16384 16384
    MPEG2_SIMPLE 16 1048576 16384 16384
    MPEG2_MAIN 16 1048576 16384 16384

    Output surface:

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

    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 -
    DEINTERLACE_TEMPORAL_SPATIAL -
    INVERSE_TELECINE -
    NOISE_REDUCTION y
    SHARPNESS y
    LUMA_KEY -
    HIGH QUALITY SCALING - L1 -
    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 16384
    VIDEO_SURFACE_HEIGHT y 48 16384
    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


    qvdpautest 0.5.1
    AMD Athlon(tm) II X2 260 Processor
    Unknown GPU

    VDPAU API version : 1
    VDPAU implementation : G3DVL VDPAU Driver Shared Library version 1.0


    MPEG DECODING (1920x1080): 51 frames/s
    MPEG DECODING (1280x720): 100 frames/s

    MIXER WEAVE (1920x1080): 598 frames/s
    MIXER BOB (1920x1080): 596 fields/s
    MIXER TEMPORAL (1920x1080): 596 fields/s
    MIXER TEMPORAL + IVTC (1920x1080): 592 fields/s
    MIXER TEMPORAL + SKIP_CHROMA (1920x1080): 593 fields/s
    MIXER TEMPORAL_SPATIAL (1920x1080): 596 fields/s
    MIXER TEMPORAL_SPATIAL + IVTC (1920x1080): 596 fields/s
    MIXER TEMPORAL_SPATIAL + SKIP_CHROMA (1920x1080): 596 fields/s
    MIXER TEMPORAL_SPATIAL (720x576 video to 1920x1080 display): 598 fields/s

    MULTITHREADED MPEG DECODING (1920x1080): 30 frames/s
    MULTITHREADED MIXER TEMPORAL (1920x1080): 287 fields/s
    Last edited by Vincenzov; 03-19-2012 at 06:33 AM.

  4. #24
    Join Date
    Apr 2012
    Posts
    26

    Default

    Still missing some key features such as h.264, high quality scaling, etc.

    Looking forward to more of it so that I can get rid of the unstable hot GT520 from my machine (AMD).

  5. #25

    Default

    I'm very curious in following the development of these features. Obviously, Phoronix brings us the big updates, but is there a website that I can check in on to follow the progress of Gallium3d VDPAU development?

  6. #26
    Join Date
    Apr 2012
    Posts
    26

    Default

    You could possibly go to Mesa git log to see all latest mesa, gallium3d and pipevideo developments.

  7. #27
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,463

    Default

    Quote Originally Posted by mikejuni View Post
    You could possibly go to Mesa git log to see all latest mesa, gallium3d and pipevideo developments.
    lakerssuperman, the log mikejuni mentioned is here : http://cgit.freedesktop.org/mesa/mesa/log/

  8. #28

    Default

    Another question, given that this implementation will use shaders instead of the video decode block, do we have some idea about a baseline for required video hardware? How much horsepower will we need to decode full 1080p h264 video?

  9. #29
    Join Date
    Apr 2012
    Posts
    26

    Default

    I think it really have to be tested out. But so far there aren't much progress in this area I think. Only mpeg2 decoding, sharpness and noise cancellation function is available if you use vdpauinfo to check.

    But if you look at the overall API of vdpau I think it is quite robust. Maybe we all should start a petition to make it a standard so that everyone start to use it.

  10. #30

    Default

    Oh yes, I agree it's a ways off, but I was just curious if the developers had certain hardware in mind that they were targeting. I would love if this eventually came to fruition and VDPAU became the Linux equivalent of DXVA. It is already a default for XBMC and Flash targets VDPAU as it's acceleration method. As HTML5 video gains traction, it would be nice if the browser developers could count on VDPAU to be the acceleration method that would work on major hardware (AMD, NVIDIA). Also, it would be nice if the major media players could all target VDPAU.

    I think a consistent video acceleration API is something the major Linux distros need and even though the open source drivers don't have quite as much 3D power as the blobs, video acceleration would be a nice feather in their respective caps.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •