MEDIASUBTYPE_RGB32 support for Windows

content/browser/renderer_host/media/video_capture_device_client.cc

Index: content/browser/renderer_host/media/video_capture_device_client.cc
diff --git a/content/browser/renderer_host/media/video_capture_device_client.cc b/content/browser/renderer_host/media/video_capture_device_client.cc
index ae599a13564abfbf529571789da93b5b62584fea..73d57a7aa2b15a2e3a123009ace6b5b9d3796f19 100644
--- a/content/browser/renderer_host/media/video_capture_device_client.cc
+++ b/content/browser/renderer_host/media/video_capture_device_client.cc
@@ -163,6 +163,9 @@ void VideoCaptureDeviceClient::OnIncomingCapturedData(
       break;
     case media::PIXEL_FORMAT_ARGB:
       origin_colorspace = libyuv::FOURCC_ARGB;
+#if defined(OS_WIN)
+      flip = true;

[mcasas, 2015/03/27 01:02:11]

Please be sure that devices using PIXEL_FORMAT_ARGB, i.e.
those reporting MEDIASUBTYPE_ARGB32 in [1],  are OK with
this extra flipping.

[1]
https://code.google.com/p/chromium/codesearch#chromium/src/media/video/captur...

[emircan, 2015/03/27 17:50:39]

I see your concern. In order to not change the existing workflow for
PIXEL_FORMAT_ARGB, I defined PIXEL_FORMAT_RGB32 with the same colorspace
conversion and flip.

+#endif
       break;
     case media::PIXEL_FORMAT_MJPEG:
       origin_colorspace = libyuv::FOURCC_MJPG;