Open
Bug 1169328
Opened 9 years ago
Updated 2 years ago
Add audio input/output capture snap-shot feature to about:webrtc
Categories
(Core :: WebRTC: Audio/Video, defect, P3)
Core
WebRTC: Audio/Video
Tracking
()
NEW
Iteration:
41.2 - Jun 8
backlog | webrtc/webaudio+ |
People
(Reporter: pkerr, Unassigned, NeedInfo)
References
(Blocks 1 open bug)
Details
Add logs to about:webrtc to pin down what's going on with the "robotic voice" reports. In particular, I'd like to capture on the receiving side: (1) the input to the decoder, (2) output from the decoder, (3) output of NetEQ (where it goes into media pipeline) -- and on the sending side, I'd like to capture (1) the input into the encoder and (2) output from the encoder (in case it's an encoding issue). This would initially be a capture snap-shot to one or more sample log files triggered from a button on the about:webrtc page. The length of the capture and file creation would be controlled by software. Auto-uploading of the created log files may be also be initiated once capture is complete.
Updated•9 years ago
|
Assignee: nobody → pkerr
Rank: 12
Priority: -- → P1
Reporter | ||
Updated•9 years ago
|
Status: NEW → ASSIGNED
Updated•9 years ago
|
backlog: --- → webRTC+
Updated•9 years ago
|
Rank: 12 → 23
Priority: P1 → P2
Target Milestone: mozilla41 → ---
Comment 1•7 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Comment 2•3 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months.
:jib, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee: paulrkerr → nobody
Status: ASSIGNED → NEW
Flags: needinfo?(jib)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•