New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 761716 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

channel counts > 2 doesn't really support for capturing on Samus

Project Member Reported by tingweilin@google.com, Sep 4 2017

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 9592.85.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.112 Safari/537.36
Platform: samus

Example URL:

Steps to reproduce the problem:
1. Open crosh - shell
2. arecord -D hw:1,1 -r 48000 -f S16_LE -c 4 /tmp/cap.wav
3. cras_test_client --playback_f /tmp/cap.wav --num_channels 4 --rate 48000

What is the expected behavior?
Play the sounds just recorded

What went wrong?
The sounds seems to be played twice as fast as the original one.
`arecord -D hw:1,1 --dump-hw-params` shows that channels [2, 4] are supported.
Looks like it still gives sample with channels count as 2.

(Set channel count as 3 can also produce similar problem.)

Did this work before? N/A 

Is it a problem with Flash or HTML5? N/A

Does this work in other browsers? N/A

Chrome version: 61.0.3147  Channel: n/a
OS Version: 9711.0
Flash Version: 

Contents of chrome://gpu:
 
Cc: chinyue@chromium.org dgreid@chromium.org hychao@chromium.org conradlo@chromium.org cychiang@chromium.org
Components: -Internals>Media OS>Kernel>Audio
Does this affect any use case of end users?
I don't think so because most recording usages capture 1 or 2 channels.
So this issue has not been found until tingweilin@ discovered by his new alsa api test tool.

Labels: -Pri-2 Pri-3
Status: Available (was: Unconfirmed)
I see. So Pri 3?
Project Member

Comment 5 by sheriffbot@chromium.org, Sep 5

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment