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

Issue 907391 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Audio capture on ARM Chromebook uses wrong sample rate

Reported by j...@viviaustralia.com.au, Nov 21

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0
Platform: 11021.56.0 (Official Build) stable-channel hana

Steps to reproduce the problem:
1. Start capturing audio, such as with pp::MediaStreamAudioTrack.
2. Configuration says sample rate is 48000 Hz.
3. Receive buffers normally.
4. Play any normal YouTube video to have regular audio.
5. Start playing a video file with 44100 Hz audio track.

What is the expected behavior?
Continue to receive 48000 Hz audio buffers.

What went wrong?
Received audio buffers claim to be 960 samples of 48000 Hz, but it's actually 960 samples of 44100 Hz sampled audio. This is reflected in the timestamps being 10.9ms (480/44100 * 1000) apart instead of 10ms, only receiving about 90 buffers per second instead of 100, and playing back the buffers at 48000 Hz has the pitch shifted higher, but forcing playback at 44100 Hz sounds mostly normal.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 70.0.3538.76 (Official Build) (32-bit)  Channel: stable
OS Version: 70.0.3538.76 (Official Build) (32-bit)
Flash Version: 31.0.0.122

Version information above is for a Lenovo N23 Yoga (hana), this also happens on a second ARM Chromebook, a Samsung XE303C12 (daisy). Can't get it to happen on any Intel Chromebooks.

In fact, it's also reproducible with Chromecast! The audio playback is higher pitched and constantly skips (since it's expected 48000 Hz). Here's a recording: https://streamable.com/i6kb7

Audio playback on the actual device continues to sound normal.

I'm not 100% on the combination of videos to play, usually takes a few tries, but once it happens it can stay in this state for as long as audio is playing. It's also easier to get to happen after a fresh reboot.
 
Components: -Blink>MediaStream Blink>WebRTC>Audio Blink>GetUserMedia>Mic
Components: -Blink>WebRTC>Audio
Sorry, I should clarify: this isn't when capturing the microphone, but the desktop audio.
Cc: dgreid@chromium.org guidou@chromium.org olka@chromium.org
Owner: hychao@chromium.org
Status: Assigned (was: Unconfirmed)
Assigning to hychao@ since it is related to the native audio later in CrOS. Please reassign if needed.

From the description it seems like there is some sort of correlation/disturbance between audio streams running at different sample rates on some unique platforms.

Sign in to add a comment