Removing silence trimming from WebRTC quality test.

Removing silence trimming from WebRTC quality test

It turns out PESQ can deal with delays, so we don't need to
silence-trim the files to get them to line up. This solves another
problem where the silence-trimming becomes too aggressive on Windows
with the new ref file.

I also need to monitor if the new ref file, which is a lot lower
in volume than the old one, unfairly punishes the score. The
speaker volume is a bit random on the bots so the recording could
end up being quite low. Tests on my workstation suggests that PESQ
is actually pretty good about ignoring that too though. There will
be a slight effect on the score (like 0.4 MOS), which I think is
acceptable. Otherwise we need to find a way to control the speaker
volume on the bots much more stringently.

BUG=446859
Committed: https://crrev.com/36d358e0cdff201a99501e9c986a8a26f8965a40
Cr-Commit-Position: refs/heads/master@{#314797}

[phoglund_chromium, 2015-02-02 13:36:09]

phoglund@chromium.org changed reviewers:
+ henrika@chromium.org

[phoglund_chromium, 2015-02-04 15:09:22]

ping :)

[henrika (OOO until Aug 14), 2015-02-04 15:24:51]

LGTM

[phoglund_chromium, 2015-02-05 11:56:35]

New patchsets have been uploaded after l-g-t-m from henrika@chromium.org

[phoglund_chromium, 2015-02-05 12:03:57]

The CQ bit was checked by phoglund@chromium.org

[commit-bot: I haz the power, 2015-02-05 12:05:08]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/890893004/80001

[commit-bot: I haz the power, 2015-02-05 13:57:03]

Committed patchset #5 (id:80001)

[commit-bot: I haz the power, 2015-02-05 13:58:04]

Patchset 5 (id:??) landed as
https://crrev.com/36d358e0cdff201a99501e9c986a8a26f8965a40
Cr-Commit-Position: refs/heads/master@{#314797}

[phoglund_chromium, 2015-02-07 12:22:21]

A revert of this CL (patchset #5 id:80001) has been created in
https://codereview.chromium.org/908703002/ by phoglund@chromium.org.

The reason for reverting is: This actually made the score worse by about 0.4 on
all bots except one, and one bot is still not helped by this. I will try to
solve this through other means, like forcing the volume to the right level on
the bots where we get bad scores..