Rework WebRTC AEC logging
Categories
(Core :: WebRTC: Audio/Video, enhancement, P2)
Tracking
()
People
(Reporter: padenot, Unassigned)
References
(Blocks 3 open bugs)
Details
Reporter | ||
Updated•7 years ago
|
Reporter | ||
Comment 1•7 years ago
|
||
Updated•6 years ago
|
Updated•6 years ago
|
I could not find any documentation on how to make sense out of AEC debug logs. I am trying to figure out if AEC is working for my use case or not. In chrome, we get various audio files, input, reverse, output etc.
Can someone please point me to an appropriate document or maybe give instructions here?
Reporter | ||
Comment 4•5 years ago
|
||
Ok we're here again. It's still blocked by the sandbox, also I hit https://crash-stats.mozilla.org/report/index/86af7ba6-286b-4c00-bd9f-6ecc20200406, and it's still outputting nonsensical files where you have to know the characteristics, etc.
We need a more solid solution, based on https://searchfox.org/mozilla-central/source/dom/media/WavDumper.h probably. I assume there is no filesystem access, so we need to rework it to allow writing in a buffer, and then offer to "download" a zip.
Nils, this is blocking investigation of bug 1627313, that seem important.
Updated•5 years ago
|
Comment 5•5 years ago
|
||
Bumping priority, since it sounds important, and good echo cancellation is a really important quality-of-life thing.
Description
•