[meta] WebRTC AEC quality issues

NEW
Assigned to

Status

()

Core
WebRTC: Audio/Video
4 years ago
3 years ago

People

(Reporter: jesup, Assigned: jesup)

Tracking

(Depends on: 1 bug, Blocks: 1 bug, {meta})

22 Branch
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(blocking-b2g:-)

Details

(Whiteboard: [webrtc][ft:webrtc])

(Assignee)

Description

4 years ago
Metabug for all AEC quality issues.

Upstream has some improvements we'll pick up in the next stable branch import (longer tail, at the cost of more CPU) and other fixes.

Moving the AEC is a primary issue, as is optimizing the input recording delay to SetVQEData().

We also have a number of issues regarding AEC implementation details open with the webrtc.org team.
(Assignee)

Updated

4 years ago
Depends on: 910959
Blocks: 923363

Comment 1

4 years ago
Plus it for v1.3 since it block the webRTC committed feature on audio P2P
blocking-b2g: --- → 1.3+
Whiteboard: [webrtc] → [webrtc][ft:webrtc]
(Assignee)

Comment 2

4 years ago
The meta bug for all AEC quality issues should not block 1.3; specific quality issues with AEC might or might not block (for example, a minor AEC incomplete cancellation when you overload the mic by yelling into it wouldn't block).
No longer blocks: 923363
blocking-b2g: 1.3+ → 1.3?
(In reply to Randell Jesup [:jesup] from comment #2)
> The meta bug for all AEC quality issues should not block 1.3; specific
> quality issues with AEC might or might not block (for example, a minor AEC
> incomplete cancellation when you overload the mic by yelling into it
> wouldn't block).

Agreed - meta bugs in general shouldn't block, only actionable dependencies that are blockers could block the release.
blocking-b2g: 1.3? → -

Updated

4 years ago
Blocks: 970426
(Assignee)

Updated

3 years ago
Blocks: 984889
(Assignee)

Updated

3 years ago
Depends on: 985714
(Assignee)

Updated

3 years ago
No longer blocks: 970426
(Assignee)

Updated

3 years ago
Depends on: 1027713
(Assignee)

Updated

3 years ago
Depends on: 1027731
You need to log in before you can comment on or make changes to this bug.