Confirmed users
35
edits
Media/WebRTC Audio Perf: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 46: | Line 46: | ||
== Ongoing Work == | == Ongoing Work == | ||
== Audio Performance Framework == | === Audio Performance Framework === | ||
<p>{{Bug|909524}} is ongoing effort to provide minimal components that serves as a good starting point | <p>{{Bug|909524}} is ongoing effort to provide minimal components that serves as a good starting point | ||
for carrying out Peer Connection audio quality analysis as part of Mozilla's Talos framework.</p> | for carrying out Peer Connection audio quality analysis as part of Mozilla's Talos framework.</p> | ||
| Line 60: | Line 60: | ||
Following sub-sections explain in details the steps involved for this purpose | Following sub-sections explain in details the steps involved for this purpose | ||
=== Running Browser Based Media Test Automatically === | ==== Running Browser Based Media Test Automatically ==== | ||
<p>[[Talos]] is Mozilla's python performance testing framework that is usable on Windows, Mac and Linux. | <p>[[Talos]] is Mozilla's python performance testing framework that is usable on Windows, Mac and Linux. | ||
Talos provides automated way to start/stop Firefox , perform tests and capture results to be reported to the Mozilla's graphing server across various Firefox builds.</p> | Talos provides automated way to start/stop Firefox , perform tests and capture results to be reported to the Mozilla's graphing server across various Firefox builds.</p> | ||
<p>Talos is used in our setup to run media tests along with other start-up and page-loader performance tests.</p> | <p>Talos is used in our setup to run media tests along with other start-up and page-loader performance tests.</p> | ||
=== Feeding output of <audio> to the Peer Connection === | ==== Feeding output of <audio> to the Peer Connection ==== | ||
<p>Once we have the framework figured out to run automated media-tests, the next step is deciding on how do we insert | <p>Once we have the framework figured out to run automated media-tests, the next step is deciding on how do we insert | ||
input audio file into the WebRTC Peer Connection.</p> | input audio file into the WebRTC Peer Connection.</p> | ||
| Line 102: | Line 102: | ||
</code> | </code> | ||
=== TODO Feature List === | ==== TODO Feature List ==== | ||
These are near term things, if implemented, would improve the framework | These are near term things, if implemented, would improve the framework | ||
#Support different audio formats and lengths | #Support different audio formats and lengths | ||