Media/WebRTC Audio Perf: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 68: Line 68:
the generated MediaStream is added to the local Peer Connection element via the addStream() API as shown
the generated MediaStream is added to the local Peer Connection element via the addStream() API as shown
below.</p>
below.</p>
<code>
<code>
// localAudio is an <audio> , localPC is a PeerConnection Object
// localAudio is an <audio> , localPC is a PeerConnection Object
Line 78: Line 77:
<br>
<br>
=== Audio Tools - PulseAudio, Sox, PESQ ===
=== Audio Tools - PulseAudio, Sox, PESQ ===
From the previous 2 sub-sections we have the following <br>
<p>From the previous 2 sub-sections we have the following <br>
*A way to run automated browser tests using Talos
*A way to run automated browser tests using Talos
*A way a feeding audio from an input audio file  audio input to the Peer Connection without having to use the GetUserMedia() API
*A way a feeding audio from an input audio file  audio input to the Peer Connection without having to use the GetUserMedia() API
 
</p>
In order to record the output Audio and compute PESQ scores,
<p>PulseAudio's pacmd tool is used to find the right sink to play-out the audio produced by the remote Peer Connection.</p>
 
<p> PulseAudio's parec tool and Sox Recording tool is used to record the audio played out at the sink to generate output recorded audio file <p>
<p> SOX is again used to trim silence at the beginning and end of the recorded  audio file. <p>
<p> Finally PESQ is used to compute the quality scores between the input audio file (original) and the output audio file (recorded) </p>
=== Summary ===
=== Summary ===


Confirmed users
35

edits

Navigation menu