Switch browser side audio capture path to use base time primitives.

media/base/audio_parameters.h

Index: media/base/audio_parameters.h
diff --git a/media/base/audio_parameters.h b/media/base/audio_parameters.h
index 68fbd54754f51c9254e0cc827508e2e11d14c05f..ff859b87d0854179ae396f1e303aaed34bd3ccbe 100644
--- a/media/base/audio_parameters.h
+++ b/media/base/audio_parameters.h
@@ -35,14 +35,15 @@ static_assert(AudioBus::kChannelAlignment == PARAMETERS_ALIGNMENT,
 struct MEDIA_EXPORT ALIGNAS(PARAMETERS_ALIGNMENT) AudioInputBufferParameters {
   double volume;
   uint32_t size;
-  uint32_t hardware_delay_bytes;
+  int64_t delay;            // delay in microseconds
+  int64_t delay_timestamp;  // base::TimeTicks in microseconds.
   uint32_t id;
   bool key_pressed;
 };
 struct MEDIA_EXPORT ALIGNAS(PARAMETERS_ALIGNMENT) AudioOutputBufferParameters {
   uint32_t frames_skipped;
-  int64_t delay;
-  int64_t delay_timestamp;
+  int64_t delay;            // delay in microseconds.
+  int64_t delay_timestamp;  // base::TimeTicks in microseconds.

[o1ka, 2017/02/10 13:28:50]

These comments look confusing to me.

[DaleCurtis, 2017/02/11 01:43:13]

Do you have a suggestion? I was trying to indicate exactly what was in the
int64_t values, since they had zero explanation before :)

[o1ka, 2017/02/13 14:00:21]

Now basing on your other replies I got the concept. Something like
"delay in microseconds, relative to |delay_timestamp|"? This would clarify the
relations and differences between the two.

 };
 #undef PARAMETERS_ALIGNMENT
 #if defined(OS_WIN)