Bug 1493397 (dav1d)

Switch AV1 implementation to dav1d

NEW
Unassigned

Status

()

P2
normal
6 months ago
2 days ago

People

(Reporter: TD-Linux, Unassigned)

Tracking

(Depends on: 2 bugs, Blocks: 2 bugs)

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox64 affected)

Details

(URL)

(Reporter)

Description

6 months ago
gotta go fast
(Reporter)

Updated

6 months ago
Blocks: 1493400
(Reporter)

Updated

6 months ago
No longer blocks: 1493400
Depends on: 1493400
Blocks: 1452683
Priority: -- → P2
(Reporter)

Updated

6 months ago
Blocks: 1494493
(Reporter)

Comment 1

5 months ago
External issues in dav1d that need to be solved before it can be the default decoder:

Missing features: https://code.videolan.org/videolan/dav1d/issues/34

Speed vs. libaom: https://code.videolan.org/videolan/dav1d/issues/15

Comment 2

4 months ago
dav1d is fast and covers all the spec:
http://www.jbkempf.com/blog/post/2018/dav1d-toward-the-first-release
(Reporter)

Updated

4 months ago
Depends on: 1511223
(Reporter)

Updated

4 months ago
Depends on: 1511224
(Reporter)

Updated

4 months ago
Depends on: 1509453
Alias: dav1d
Depends on: 1515641
Depends on: 1516235
Depends on: 1515933
Depends on: 1521062
Blocks: 1533092

Is there a timetable for importing the new dav1d 0.2.0 release?

(Reporter)

Comment 4

15 days ago

We're actually on dav1d git at the moment. But yeah we can do an update again, maybe to 0.2.1 that's about to be released. https://bugzilla.mozilla.org/show_bug.cgi?id=1533559

Depends on: 1533742

Updated

4 days ago
Depends on: 1536070

Currently dav1d uses only 1 tilethread in Firefox, making it painfully slow. It should at least use 2, and on systems with 8 or more logical processors 4.

Could you open a new bug about it and CC me? I will take care next.

(In reply to Alex Chronopoulos [:achronop] from comment #6)

Could you open a new bug about it and CC me? I will take care next.

Thanks! https://bugzilla.mozilla.org/show_bug.cgi?id=1536783

Updated

2 days ago
Depends on: 1536783
You need to log in before you can comment on or make changes to this bug.