Announcement

Collapse
No announcement yet.

Google Chrome Adds VA-API Video Acceleration On Wayland

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

  • #51
    Originally posted by linux4kix View Post

    That patch and if you read the bug report, there were two other patches earlier in the discussion that had to be merged before that one landed. If you are using newer versions of chromium they may already be merged.
    Ok so I should be fine on version 122. Can you please check if you have VCN: Enabled while watching a video? VaapiVideoDecodeLinuxGL doesn't work for me.
    ## VGA ##
    AMD: X1950XTX, HD3870, HD5870
    Intel: GMA45, HD3000 (Core i5 2500K)

    Comment


    • #52
      Originally posted by darkbasic View Post

      Ok so I should be fine on version 122. Can you please check if you have VCN: Enabled while watching a video? VaapiVideoDecodeLinuxGL doesn't work for me.
      I don't have VCN. This is a polaris based card. VCN is only for newer integrated APUs and Navi and newer hardware.

      Comment


      • #53
        Originally posted by linux4kix View Post

        I don't have VCN. This is a polaris based card. VCN is only for newer integrated APUs and Navi and newer hardware.
        So maybe there is some difference in how vaapi is being implemented on different AMD architectures which explains why it doesn't work on mine with VaapiVideoDecodeLinuxGL while it works on your.
        ## VGA ##
        AMD: X1950XTX, HD3870, HD5870
        Intel: GMA45, HD3000 (Core i5 2500K)

        Comment


        • #54
          Originally posted by darkbasic View Post

          So maybe there is some difference in how vaapi is being implemented on different AMD architectures which explains why it doesn't work on mine with VaapiVideoDecodeLinuxGL while it works on your.
          Was curious about VaapiVideoDecodeLinuxGL. That patch was also recently merged (around December). I would think your 122 build should have it as my 120 stable does. https://chromium.googlesource.com/ch...d75357d79a32da

          Comment

          Working...
          X