Match existing type usage better.

talk/app/webrtc/test/fakeaudiocapturemodule.cc

Index: talk/app/webrtc/test/fakeaudiocapturemodule.cc
diff --git a/talk/app/webrtc/test/fakeaudiocapturemodule.cc b/talk/app/webrtc/test/fakeaudiocapturemodule.cc
index c6339d3c3f4295d88b6b45abc41cb55a8943fe11..e52b686bc23415b5b8cca75249d2a5290393368e 100644
--- a/talk/app/webrtc/test/fakeaudiocapturemodule.cc
+++ b/talk/app/webrtc/test/fakeaudiocapturemodule.cc
@@ -45,7 +45,7 @@ static const uint32 kAdmMaxIdleTimeProcess = 1000;
 // Constants here are derived by running VoE using a real ADM.
 // The constants correspond to 10ms of mono audio at 44kHz.
 static const int kTimePerFrameMs = 10;
-static const int kNumberOfChannels = 1;
+static const uint8_t kNumberOfChannels = 1;

[juberti1, 2015/06/10 05:40:53]

Generally I think that using sized types for things like this is a bad idea, and
we should use plain old int instead, although I note that the NeedMorePlayData
API expects such a type.

[Peter Kasting, 2015/06/11 04:03:46]

Yes, and that's why I changed this -- all the places it's used it's being passed
to an API expecting a uint8_t.

I could try to change that API, and everyone that calls it and that it calls,
etc. -- I'm not opposed to that, and indeed, doing that sort of thing for other
APIs (with size_t) is what all this work is leading up to -- but that's a bigger
change (I don't know how big without pulling the thread and seeing what
unravels) and I preferred in the meantime to eliminate the compiler downcast
warning and make the type usage consistent today.

So even if I were to make the API change there, I'd still want to do this in the
meantime unless I was making the change now.

Is that OK?

 static const int kSamplesPerSecond = 44000;
 static const int kTotalDelayMs = 0;
 static const int kClockDriftMs = 0;