Add VA-API hardware decoding support on Linux

NEW
Unassigned

Status

()

enhancement
P3
normal
4 years ago
8 days ago

People

(Reporter: jya, Unassigned)

Tracking

(Blocks 1 bug, {parity-chrome})

Trunk
Desktop
Linux
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

()

Reporter

Description

4 years ago
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?
Reporter

Comment 2

4 years ago
(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.
Comment hidden (offtopic)
Comment hidden (offtopic)
Comment hidden (offtopic)
Comment hidden (offtopic)
Comment hidden (offtopic)
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.
Flags: needinfo?(mhoye)
Comment hidden (offtopic)
Comment hidden (offtopic)
Comment hidden (offtopic)
Comment hidden (offtopic)
(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).
Reporter

Comment 15

2 years ago
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.
Reporter

Updated

2 years ago
Depends on: ogl-linux-beta
Comment hidden (me-too)

Comment 17

2 years ago
Just FYI: https://chromium-review.googlesource.com/c/532294 this will be [chrome-parity] soon
Comment hidden (obsolete)
Comment hidden (obsolete)
Whiteboard: [parity-chrome][qf] → [parity-chrome]
Comment hidden (advocacy)
Reporter

Updated

Last year
Assignee: jyavenard → nobody
Comment hidden (offtopic)

Comment 23

17 days ago

The dependency of this bug could probably changed from ogl-linux-beta to bug 1491303, as webrender will replace all the old rendering architecture and is already enabled on linux + intel in nightly.

Type: defect → enhancement
Depends on: 1543217, 1554251
No longer depends on: ogl-linux-beta
OS: Unspecified → Linux
Hardware: Unspecified → Desktop
You need to log in before you can comment on or make changes to this bug.