[Chromecast] Process streams with different post-processing.

chromecast/public/media/media_pipeline_device_params.h

Index: chromecast/public/media/media_pipeline_device_params.h
diff --git a/chromecast/public/media/media_pipeline_device_params.h b/chromecast/public/media/media_pipeline_device_params.h
index 680da27cd25f9761209090867bb07ad37d56b041..3e530fe9a6db22859301418bebf04176025a1297 100644
--- a/chromecast/public/media/media_pipeline_device_params.h
+++ b/chromecast/public/media/media_pipeline_device_params.h
@@ -55,8 +55,18 @@ struct MediaPipelineDeviceParams {
         audio_type(audio_type_in),
         task_runner(task_runner_in) {}
 
+  MediaPipelineDeviceParams(MediaSyncType sync_type_in,
+                            AudioStreamType audio_type_in,
+                            std::string name_in,

[wzhong, 2017/02/22 16:13:01]

const &

[bshaya, 2017/02/22 20:45:25]

Done.

+                            TaskRunner* task_runner_in)
+      : sync_type(sync_type_in),
+        audio_type(audio_type_in),
+        name(name_in),
+        task_runner(task_runner_in) {}
+
   const MediaSyncType sync_type;
   const AudioStreamType audio_type;
+  const std::string name;
 
   // task_runner allows backend implementations to post tasks to the media
   // thread.  Since all calls from cast_shell into the backend are made on