Add content type information to encoded images and corresponding rtp extension header

webrtc/modules/video_coding/include/video_coding_defines.h

Index: webrtc/modules/video_coding/include/video_coding_defines.h
diff --git a/webrtc/modules/video_coding/include/video_coding_defines.h b/webrtc/modules/video_coding/include/video_coding_defines.h
index 4ed80a6f81a1ad03b77ee25cc0364440a47a181f..3ae9981d9cda6530d1c42cc09965ee082d3dcc41 100644
--- a/webrtc/modules/video_coding/include/video_coding_defines.h
+++ b/webrtc/modules/video_coding/include/video_coding_defines.h
@@ -62,7 +62,8 @@ struct VCMFrameCount {
 class VCMReceiveCallback {
  public:
   virtual int32_t FrameToRender(VideoFrame& videoFrame,  // NOLINT
-                                rtc::Optional<uint8_t> qp) = 0;
+                                rtc::Optional<uint8_t> qp,
+                                VideoContentType content_type) = 0;

[nisse-webrtc, 2017/04/03 12:07:18]

The implementation of this call uses this info for stats only?

It might make sense to collect content type and the qp value into a struct. Not
sure what qp is used for here, if that's also for stats only?

[ilnik, 2017/04/03 14:03:43]

Yes, stats only. Two parameters do not warrant a separate structure, in my
opinion.

[ilnik, 2017/04/05 11:24:16]

Nisse, do you strongly disagree with leaving it as a two parameters and insist
on adding a structure here?

[nisse-webrtc, 2017/04/05 11:46:36]

I don't insist.

   virtual int32_t ReceivedDecodedReferenceFrame(const uint64_t pictureId) {
     return -1;
   }