Wire up bandwidth limitation info to GetStats and adapt_reason.

talk/media/webrtc/webrtcvideoengine2.cc

Index: talk/media/webrtc/webrtcvideoengine2.cc
diff --git a/talk/media/webrtc/webrtcvideoengine2.cc b/talk/media/webrtc/webrtcvideoengine2.cc
index e84cdab60db48f57643f6d164773021626ff8f13..d0e17525e76d4de764abf6476d7783496c6f3dbe 100644
--- a/talk/media/webrtc/webrtcvideoengine2.cc
+++ b/talk/media/webrtc/webrtcvideoengine2.cc
@@ -2156,6 +2156,14 @@ WebRtcVideoChannel2::WebRtcVideoSendStream::GetVideoSenderInfo() {
       }
     }
   }
+
+  // Get bandwidth limitation info from stream_->GetStats().
+  // Input resolution (output from video_adapter) can be further scaled down or
+  // higher video layer(s) can be dropped due to bitrate constraints.
+  // Note, adapt_changes only include changes from the video_adapter.
+  if (stats.bw_limited_resolution)
+    info.adapt_reason = CoordinatedVideoAdapter::ADAPTREASON_BANDWIDTH;

[stefan-webrtc, 2015/12/07 16:02:33]

Now this may overwrite any reason written on line 2155. Should we handle
multiple adapt reasons? Maybe not needed for now, but could be worth commenting
on.

[åsapersson, 2015/12/08 08:58:25]

The video_adapter shows the most limiting reason (or several if having the same
limit). Updated comment that BW will be the most limiting if set and therefore
overwritten.

[åsapersson, 2015/12/11 14:39:38]

Have changed so BW is added (and does not overwrite reasons from video adapter).
PTAL.  

+
   info.ssrc_groups = ssrc_groups_;
   info.framerate_input = stats.input_frame_rate;
   info.framerate_sent = stats.encode_frame_rate;