Switch WebRTC rendering to asynchronous device info requests. |
|||
Issue descriptionThe fix for Issue 905506 introduced an async version of GetOutputDeviceInfo. We'd like to switch WebRTC-related audio rendering to this async API, to get away from device authorization timeouts.
,
Dec 13
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2d102680df90e4bf54645b0332b78978e0b85172 commit 2d102680df90e4bf54645b0332b78978e0b85172 Author: Olga Sharonova <olka@chromium.org> Date: Thu Dec 13 08:29:23 2018 UMA for TrackAudioRenderer and WebRTCAudioRenderer device status To identify how device authorization timeouts affect WebRTC audio rendering Bug: 914323,913476 Change-Id: Id33846a5dd34be0f35a7a21c414e2df35bdcdd90 Reviewed-on: https://chromium-review.googlesource.com/c/1373760 Reviewed-by: Ilya Sherman <isherman@chromium.org> Reviewed-by: Max Morin <maxmorin@chromium.org> Commit-Queue: Olga Sharonova <olka@chromium.org> Cr-Commit-Position: refs/heads/master@{#616244} [modify] https://crrev.com/2d102680df90e4bf54645b0332b78978e0b85172/content/renderer/media/stream/track_audio_renderer.cc [modify] https://crrev.com/2d102680df90e4bf54645b0332b78978e0b85172/content/renderer/media/webrtc/webrtc_audio_renderer.cc [modify] https://crrev.com/2d102680df90e4bf54645b0332b78978e0b85172/tools/metrics/histograms/histograms.xml
,
Dec 18
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fd0ffefe76fd049836a244d3204f18c72197320c commit fd0ffefe76fd049836a244d3204f18c72197320c Author: Olga Sharonova <olka@chromium.org> Date: Tue Dec 18 18:29:39 2018 UMA for TrackAudioRenderer and WebRTCAudioRenderer device status To identify how device authorization timeouts affect WebRTC audio rendering Bug: 914323,913476 Change-Id: Id33846a5dd34be0f35a7a21c414e2df35bdcdd90 Reviewed-on: https://chromium-review.googlesource.com/c/1373760 Reviewed-by: Ilya Sherman <isherman@chromium.org> Reviewed-by: Max Morin <maxmorin@chromium.org> Commit-Queue: Olga Sharonova <olka@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#616244}(cherry picked from commit 2d102680df90e4bf54645b0332b78978e0b85172) Reviewed-on: https://chromium-review.googlesource.com/c/1382500 Reviewed-by: Olga Sharonova <olka@chromium.org> Cr-Commit-Position: refs/branch-heads/3626@{#436} Cr-Branched-From: d897fb137fbaaa9355c0c93124cc048824eb1e65-refs/heads/master@{#612437} [modify] https://crrev.com/fd0ffefe76fd049836a244d3204f18c72197320c/content/renderer/media/stream/track_audio_renderer.cc [modify] https://crrev.com/fd0ffefe76fd049836a244d3204f18c72197320c/content/renderer/media/webrtc/webrtc_audio_renderer.cc [modify] https://crrev.com/fd0ffefe76fd049836a244d3204f18c72197320c/tools/metrics/histograms/histograms.xml
,
Dec 19
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fd0ffefe76fd049836a244d3204f18c72197320c Commit: fd0ffefe76fd049836a244d3204f18c72197320c Author: olka@chromium.org Commiter: olka@chromium.org Date: 2018-12-18 18:29:39 +0000 UTC UMA for TrackAudioRenderer and WebRTCAudioRenderer device status To identify how device authorization timeouts affect WebRTC audio rendering Bug: 914323,913476 Change-Id: Id33846a5dd34be0f35a7a21c414e2df35bdcdd90 Reviewed-on: https://chromium-review.googlesource.com/c/1373760 Reviewed-by: Ilya Sherman <isherman@chromium.org> Reviewed-by: Max Morin <maxmorin@chromium.org> Commit-Queue: Olga Sharonova <olka@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#616244}(cherry picked from commit 2d102680df90e4bf54645b0332b78978e0b85172) Reviewed-on: https://chromium-review.googlesource.com/c/1382500 Reviewed-by: Olga Sharonova <olka@chromium.org> Cr-Commit-Position: refs/branch-heads/3626@{#436} Cr-Branched-From: d897fb137fbaaa9355c0c93124cc048824eb1e65-refs/heads/master@{#612437} |
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Dec 12