Hardware acceleration for integrated Intel HD Graphics 515

I want to raise this issue in the topic "Features requests" but decided to ask first here. Maybe someone knows more about hw-acceleration on new Intel video cards?

The text of the appeal:

I'm on Intel® Core™ m5-6Y54(with integrated Intel® HD Graphics 515). I can't watch any 720p60 youtube clips on this hw(I can watch 1080p30 but it still software decoding).

Now on Windows hw-acceleration for this card support only Edge. On Linux - only Epiphany(through gstreamer-vaapi).

As I know, chromium use ffmpeg for playing multimedia content. On Linux we need to install vivaldi-ffmpeg-codecs for multimedia support. So ffmpeg have qsv plugin for hw-accel on newest cards(and enabled from FFMPEG 2.8).

Is it possible to use one of this solutions(ffmpeg-qsv or gstreamer) in next releases?

If you find it like Gwen-Dragon said, your Intel video accerleration should be OK.

Especially on Youtube, videos default are played with codec VP9. For VP9, accerleration works starting with Kaby-Lake (HD Graphics 610+). You can force playback in h264 with the extension h264ify - then accerleration on Youtube also works with your chip.

@gwen-dragon I'm already have installed and configured intel drivers and vaapi. And acceleration work in VLC, Epiphany(as I said before) and other multimedia players that support acceleration(based on mplayer, mpv or gstreamer).
I activate vivaldi://flags/#ignore-gpu-blacklist and on vivaldi://gpu it says that acceleration should work.
But on the practice browser render all videos through CPU(also you can read about this problem in this reddit thread). I can't see any 720p60fps youtube videos because of my CPU loading to 100% and start heating.
And this is not a Linux problem. On Windows I have exactly same experience. All browsers except Edge render video through CPU when m-players(VLC, mpc-hc) use hardware acceleration(DXVA on Windows).

@wernerfp h264ify already installed on the video and browser was restarted after it install.
UPD.: Stop, I'm test this video again - now its realy use h264 and ffmpegdecoder!
But CPU steel loaded over 50%. Similar load CPU have when I disable VAAPI in VLC(vlc also use ffmpeg):

VLC with VAAPI(vlc use 720p by default on youtube)

VLC without VAAPI:

How can I find out if vivaldi-ffmpeg-decoder realy use VAAPI? vivaldi-ffmpeg-codecs don't depend from system ffmpeg package, that has h264_vaapi:

I don't think so. I tested this video just now. I were download 1080p from youtube(muted) and test it in players.

VLC with VAAPI and mpv with --hwdec=vaapi loads CPU to 3-5% at all playing time.

mpv without --hwdec=vaapi and Vivaldi loads CPU to 13-16% first minute and at some clip point they both jump up to 100% and then go down to 60-70% of avg(from all 4 threads) CPU usage. At this moments video freezes.
I were use local 1080p copy of this video in all test.

Now I can definitely say that Vivaldi don't use VAAPI acceleration of my GPU. Yes, with h264ify I can see videos more smoothly but it still software rendering and still freezes exists.

Now I can definitely say that Vivaldi don't use VAAPI acceleration of my GPU.

Maybe so. I'm not sure that it is a Vivaldi problem. Firefox (in Arch) directly uses ffmpeg (about:config | layers.acceleration.force-enabled;true). CPU load by Vivaldi and Firefox in h264 is identical - at least on my systems.

If the problem can't be solved with your GPU, you may enjoy a workaround: I'm using a starter "MPV stream" which points to a bash script that fetches video urls from clipboard and starts them with mpv:

@hxss Strange, should work fine as hardware acceleration is active on your Vivaldi.
Please read first report the issue as a bug to Vivaldi.

How to do a bug report for Vivaldi

Report each bug separately at https://vivaldi.com/bugreport/
Describe the issue as precise as you can.
Add some information about extensions you use.
Add information about the operating system and version you use.
Add some information which security tools you use.
If you have problems with video or audio give us information about your installed codecs and graphics
card/GPU.
Add a exact link to the page where the issue comes up and can be tested.
After reporting the issue, you will receive a confirmation mail from the bugtracker.
In a reply to this mail you can add more information and files (like screenshots or testcases) as
attachments and it will be added automatically to bug report.

If you have questions about the bug please ask in forum first and do not forget to post the VB-XXXXX
bug number (you can find it in confirmation mail).