Page 28 of 29 FirstFirst ... 1826272829 LastLast
Results 271 to 280 of 283

Thread: AMD Releases Open-Source UVD Video Support

  1. #271
    Join Date
    Jan 2013
    Posts
    906

    Default

    Quote Originally Posted by Ibidem View Post
    Since when did the Intel troll get a say on what radeon should do? :P

    Bridgman has said that there's better power management in the works (currently in legal review), which will replace the current code. Anyone who wants better dynpm is free to fix it, or sponsor someone if that's not an option, but it works well enough for me for the present, and when something better is already on the way I'm fine with AMD working on other aspects of the driver.
    Also, alenbo is right: Off topic.
    Since I purchased two of their cards recently and actually stayed with radeon... My priorities are different than yours, its not something wrong..
    But I do think that amount of people with TVCards that have Radeon in the system is lower ,than amount of people with Radeon cards (with TVCard or not).
    And I don't like flicker...

  2. #272
    Join Date
    Dec 2007
    Posts
    2,273

    Default

    Quote Originally Posted by ptarcher View Post
    I have been trying out the new UVD support for my built in Radeon HD 4250 and it works great playing 1080p video's in mplayer.
    I am now trying to set it up in mythtv to be able to take advantage of the smooth playback provided by vdpau.
    rs780/880 chips like the 4250 do not yet have UVD support. You are most likely using the shader based vdpau implementation in mesa or software rendering.

  3. #273
    Join Date
    Apr 2013
    Posts
    6

    Default

    Quote Originally Posted by agd5f View Post
    rs780/880 chips like the 4250 do not yet have UVD support. You are most likely using the shader based vdpau implementation in mesa or software rendering.
    My vdpauinfo outputs the following

    Code:
    $ 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     8192  8192  NV12 YV12 
    422     8192  8192  NV12 YV12 UYVY YUYV 
    444     8192  8192  NV12 YV12 Y8U8V8A8 V8U8Y8A8 
    
    Decoder capabilities:
    
    name               level macbs width height
    -------------------------------------------
    MPEG1                16 262144  8192  8192
    MPEG2_SIMPLE         16 262144  8192  8192
    MPEG2_MAIN           16 262144  8192  8192
    
    Output surface:
    
    name              width height nat types
    ----------------------------------------------------
    B8G8R8A8          8192  8192    y  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 
    R8G8B8A8          8192  8192    y  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 
    R10G10B10A2       8192  8192    y  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 
    B10G10R10A2       8192  8192    y  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 
    
    Bitmap surface:
    
    name              width height
    ------------------------------
    B8G8R8A8          8192  8192
    R8G8B8A8          8192  8192
    R10G10B10A2       8192  8192
    B10G10R10A2       8192  8192
    A8                8192  8192
    
    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     8192
    VIDEO_SURFACE_HEIGHT             y        48     8192
    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
    And when playing with mplayer it only uses 30% CPU with perfectly smooth playback. I can actually play at least 2 HD video's at the same time with dynamic resize. Where should I be looking furthur to find if I am using shader based vdpau implementation in mesa or software rendering?

  4. #274
    Join Date
    Dec 2007
    Posts
    2,273

    Default

    It looks like you are using the shader-based implementation.

  5. #275
    Join Date
    Oct 2008
    Location
    Germany
    Posts
    65

    Default

    Quote Originally Posted by agd5f View Post
    It looks like you are using the shader-based implementation.
    Yep definitively shader based decoding.

    BTW: Does anybody volunteer to implement advanced deinterlacing? Or does anybody has a good & open source sample implementation?

    Christian.

  6. #276
    Join Date
    Feb 2011
    Posts
    124

    Default

    What about starting with a look at yadif: http://avisynth.org.ru/yadif/yadif.html?

  7. #277
    Join Date
    Jan 2011
    Location
    Toronto, Canada
    Posts
    4

    Default

    (I'm sorry for my slow response. I didn't get notification of your posting (surely my fault) and I almost never on this forum. This topic is particularly important to me.)

    Quote Originally Posted by bridgman View Post
    Hal2k1 was mentioning copyright. I included it in the larger list for completeness. Re: patents, the concern there is IP which is currently protected by trade secret but where we have patent applications in flight internally.
    OK. That explanation makes more sense.

    I don't see how it applies in all cases that we're talking about, but I guess that might be a consequence of it being a secret.


    Intel had been working on releasing materials to open source for years before we started. If you said "the sad thing is that in 10 years (or maybe 8, not sure) Intel has reached sufficient performance for video..." I would agree. I'm sure we will reach at least the same level in the same time.
    I guess that I wasn't clear. I was rooting for ATI/AMD. ATI/AMD had a significant (large) and consequential (qualitatively important to many Linux users) performance advantage over Intel video. For my purposes, Intel's HD 2000 and up performance is finally good enough: it can do the 3d acceleration (perhaps needlessly) required by modern Linux desktops, and it can reasonably do video decoding. A window has closed.

    It's amazing that nVidia, with its closed source drivers, has so much mindshare in the Linux world. It looks to me as if the reason is that they take great care of their Linux driver so that it is almost always up to date with the current production kernels, and it isn't too buggy. ATI/AMD's closed drivers haven't managed that.

    ATI/AMD could get a free-er ride with open source. But I admit that the vast majority of the work on the Intel open-source drivers is done by Intel staff.

    BTW, IMHO, Years ago, ATI should have harnessed Dave Arlie, not muzzled him.

  8. #278
    Join Date
    Oct 2009
    Posts
    1,987

    Default

    Quote Originally Posted by agd5f View Post
    It looks like you are using the shader-based implementation.
    Quote Originally Posted by Deathsimple View Post
    Yep definitively shader based decoding.
    I'm anxious on the RS780/880 support... any news?

  9. #279
    Join Date
    Oct 2009
    Posts
    1,987

    Default

    Quote Originally Posted by ptarcher View Post
    My vdpauinfo outputs the following

    Code:
    $ 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     8192  8192  NV12 YV12 
    422     8192  8192  NV12 YV12 UYVY YUYV 
    444     8192  8192  NV12 YV12 Y8U8V8A8 V8U8Y8A8 
    
    Decoder capabilities:
    
    name               level macbs width height
    -------------------------------------------
    MPEG1                16 262144  8192  8192
    MPEG2_SIMPLE         16 262144  8192  8192
    MPEG2_MAIN           16 262144  8192  8192
    
    Output surface:
    
    name              width height nat types
    ----------------------------------------------------
    B8G8R8A8          8192  8192    y  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 
    R8G8B8A8          8192  8192    y  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 
    R10G10B10A2       8192  8192    y  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 
    B10G10R10A2       8192  8192    y  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 
    
    Bitmap surface:
    
    name              width height
    ------------------------------
    B8G8R8A8          8192  8192
    R8G8B8A8          8192  8192
    R10G10B10A2       8192  8192
    B10G10R10A2       8192  8192
    A8                8192  8192
    
    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     8192
    VIDEO_SURFACE_HEIGHT             y        48     8192
    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
    And when playing with mplayer it only uses 30% CPU with perfectly smooth playback. I can actually play at least 2 HD video's at the same time with dynamic resize. Where should I be looking furthur to find if I am using shader based vdpau implementation in mesa or software rendering?
    ... what kind of file are you decoding? Is it mpeg1/2 or mpeg4/h263/h264? If any of the latter, you're definitely software decoding. Notice what it says under "decoder capabilities". Depending on your CPU, 30% may make perfect sense. A Sempron 140 can *almost* handle a 1080p h264 in software, so any middle-of-the-road quad-core would probably take about 30%-ish.

    Note that UVD should take about 0%.

  10. #280
    Join Date
    Oct 2008
    Posts
    2,905

    Default

    Quote Originally Posted by droidhacker View Post
    ... what kind of file are you decoding? Is it mpeg1/2 or mpeg4/h263/h264? If any of the latter, you're definitely software decoding. Notice what it says under "decoder capabilities". Depending on your CPU, 30% may make perfect sense. A Sempron 140 can *almost* handle a 1080p h264 in software, so any middle-of-the-road quad-core would probably take about 30%-ish.

    Note that UVD should take about 0%.
    He's probably running mpeg2. I think that
    Information string: G3DVL
    indicates the shader based decoder.

Posting Permissions

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