This would do decoding only ; not rendering (yet)
Hardware decoding on Intel Ironlake should be used only for 720p and lower. Hardware 1080p decoding on Intel Ironlake is slower than software decoding on CPU: https://bugs.freedesktop.org/show_bug.cgi?id=47858 GPU model from about:support Intel Open Source Technology Center -- Mesa DRI Intel(R) Ironlake Mobile I need to fill separate issue about VA-API on Ironlake or drop this info here is fine?
(In reply to russianneuromancer from comment #1) > Hardware decoding on Intel Ironlake should be used only for 720p and lower. > Hardware 1080p decoding on Intel Ironlake is slower than software decoding > on CPU: https://bugs.freedesktop.org/show_bug.cgi?id=47858 > > GPU model from about:support > Intel Open Source Technology Center -- Mesa DRI Intel(R) Ironlake Mobile > > I need to fill separate issue about VA-API on Ironlake or drop this info > here is fine? We have a generic preference to disable hardware acceleration, I'll hook it up to vaapi, but I have no intention at this stage to make specific cases for particular chipset. Would have to be in a separate bug.
4 years ago
Priority: -- → P2
See bug 1210726.
Gentle reminder: * Our guidelines ask you don't argue about priority setting on bugs. Triage leads and Mozillians working on the bug set the priority. See: https://bugzilla.mozilla.org/page.cgi?id=etiquette.html * "Me too" or "Fix this or I'm moving to Chrome/Lynx/Gopher/Edge/Webkit" comments are off topic and just add noise.
(In reply to Paul Menzel from comment #11) > Laurent, if this is still reproducible – I only have 45.9.0 here –, could > you please create a separate report for this issue? That’d be great. Is there already a separate report for this issue? There are also some other useful informations gone (i can't remember exactly, but e.g. regarding OpenGL acceleration).
Yes, we also need accelerated layers to be able to render the frames. And right now, this has taken a set back and the feature has been disabled for now.
Just FYI: https://chromium-review.googlesource.com/c/532294 this will be [chrome-parity] soon
Whiteboard: [parity-chrome][qf] → [parity-chrome]
There is a bounty for this issue at https://www.bountysource.com/issues/55506502-add-va-api-hardware-decoding-support-on-linux
You need to log in before you can comment on or make changes to this bug.