Fix audio device excessive logging on Windows

Fix audio device excessive logging on Windows

In the windows audio device implementation, play block size should be
number of samples per 10ms times the number of channels. Meanwhile
RequestPlayoutData is expecting number of samples per channel in a
block, and we should pass in the per channel number here to avoid debug
check.

BUG=webrtc:7627
Review-Url: https://codereview.webrtc.org/2876593003
Cr-Commit-Position: refs/heads/master@{#18088}
Committed: https://chromium.googlesource.com/external/webrtc/+/c4b126d70e0b0f500e9a2d7f164ed016668ebf54

[lliuu, 2017-05-10 23:38:46]

Description was changed from

==========
Fix audio device excessive logging on Windows

In the windows audio device implementation, play block size should be
number of samples per 10ms times the number of channels. Meanwhile
RequestPlayoutData is expecting number of samples per channel in a
block, and we should pass in the per channel number here to avoid debug
check.

BUG=7627
==========

to

==========
Fix audio device excessive logging on Windows

In the windows audio device implementation, play block size should be
number of samples per 10ms times the number of channels. Meanwhile
RequestPlayoutData is expecting number of samples per channel in a
block, and we should pass in the per channel number here to avoid debug
check.

BUG=7627
==========

[lliuu, 2017-05-10 23:38:46]

lliuu@webrtc.org changed reviewers:
+ niklase@chromium.org

[lliuu, 2017-05-10 23:46:51]

The CQ bit was checked by lliuu@webrtc.org to run a CQ dry run

[commit-bot: I haz the power, 2017-05-10 23:46:56]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...

[niklas.enbom, 2017-05-10 23:59:00]

lgtm
On 2017/05/10 23:46:56, commit-bot: I haz the power wrote:
> Dry run: CQ is trying da patch.
> 
> Follow status at:
>
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...

[lliuu, 2017-05-11 00:05:16]

The CQ bit was checked by lliuu@webrtc.org

[lliuu, 2017-05-11 00:05:17]

The patchset sent to the CQ was uploaded after l-g-t-m from
niklas.enbom@webrtc.org
Link to the patchset: https://codereview.webrtc.org/2876593003/#ps20001 (title:
"fix format")

[commit-bot: I haz the power, 2017-05-11 00:05:27]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...

[commit-bot: I haz the power, 2017-05-11 01:08:26]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1494461116926020,
"parent_rev": "a7507ebb1cbec606c127d6db740c34c3e62f063d", "commit_rev":
"c4b126d70e0b0f500e9a2d7f164ed016668ebf54"}

[commit-bot: I haz the power, 2017-05-11 01:08:29]

Description was changed from

==========
Fix audio device excessive logging on Windows

In the windows audio device implementation, play block size should be
number of samples per 10ms times the number of channels. Meanwhile
RequestPlayoutData is expecting number of samples per channel in a
block, and we should pass in the per channel number here to avoid debug
check.

BUG=7627
==========

to

==========
Fix audio device excessive logging on Windows

In the windows audio device implementation, play block size should be
number of samples per 10ms times the number of channels. Meanwhile
RequestPlayoutData is expecting number of samples per channel in a
block, and we should pass in the per channel number here to avoid debug
check.

BUG=7627

Review-Url: https://codereview.webrtc.org/2876593003
Cr-Commit-Position: refs/heads/master@{#18088}
Committed:
https://chromium.googlesource.com/external/webrtc/+/c4b126d70e0b0f500e9a2d7f1...
==========

[commit-bot: I haz the power, 2017-05-11 01:08:30]

Committed patchset #2 (id:20001) as
https://chromium.googlesource.com/external/webrtc/+/c4b126d70e0b0f500e9a2d7f1...

[henrika_webrtc, 2017-05-11 08:29:44]

Description was changed from

==========
Fix audio device excessive logging on Windows

In the windows audio device implementation, play block size should be
number of samples per 10ms times the number of channels. Meanwhile
RequestPlayoutData is expecting number of samples per channel in a
block, and we should pass in the per channel number here to avoid debug
check.

BUG=7627

Review-Url: https://codereview.webrtc.org/2876593003
Cr-Commit-Position: refs/heads/master@{#18088}
Committed:
https://chromium.googlesource.com/external/webrtc/+/c4b126d70e0b0f500e9a2d7f1...
==========

to

==========
Fix audio device excessive logging on Windows

In the windows audio device implementation, play block size should be
number of samples per 10ms times the number of channels. Meanwhile
RequestPlayoutData is expecting number of samples per channel in a
block, and we should pass in the per channel number here to avoid debug
check.

BUG=webrtc:7627

Review-Url: https://codereview.webrtc.org/2876593003
Cr-Commit-Position: refs/heads/master@{#18088}
Committed:
https://chromium.googlesource.com/external/webrtc/+/c4b126d70e0b0f500e9a2d7f1...
==========

[henrika_webrtc, 2017-05-11 08:30:44]

lgtm (FYI, modified the BUG link to webrtc:7627 since it points to a Chrome bug
otherwise)

[niklas.enbom, 2017-05-11 13:41:10]

Henrik, I was agonizing a bit over naming. Do we have any established naming for
multi-channel samples (sometimes called frames)?
On 2017/05/11 08:30:44, henrika_webrtc wrote:
> lgtm (FYI, modified the BUG link to webrtc:7627 since it points to a Chrome
bug
> otherwise)