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

Issue 765707 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
OOO Dec 22 - Jan 8
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

WebRTC audio capture broadcasts only less than a second with Alsa

Project Member Reported by jdap...@gmail.com, Sep 15 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.79 Safari/537.36

Steps to reproduce the problem:
Precondition: use Alsa instead of Pulseaudio for audio input.
1. Set up a call with https://appr.tc/ and local microphone using Alsa.
2. Listen to the other peer audio received
3. 

What is the expected behavior?
Audio from chromium is received as expected.

What went wrong?
Only less than a second is received, then no sound anymore.

Did this work before? No 

Chrome version: 61.0.3163.79  Channel: stable
OS Version: Ubuntu 17.04
Flash Version:
 
Labels: TE-NeedsTriageFromMTV
Adding the label 'TE-NeedsTriageFromMTV' as the issue requires ALSA to triage.
Components: Internals>Media>Audio
Components: -Internals>Media>Audio Blink>WebRTC

Comment 4 by guidou@chromium.org, Mar 20 2018

Components: -Blink>WebRTC Blink>WebRTC>Audio

Comment 5 by olka@chromium.org, Apr 5 2018

Cc: grunell@chromium.org ossu@chromium.org olka@chromium.org solenberg@chromium.org maxmorin@chromium.org marinaciocea@chromium.org
Labels: Needs-Feedback
Could you clarify:

1) "Listen to the other peer audio received", "Only less than a second is received, then no sound anymore." 

So the near end experiences a problem with audio playback, not with the microphone - correct?

2) "use Alsa instead of Pulseaudio for audio input"

Is Alsa setup on the near end or on the remote end (peer)?

Thanks!
jdapena: Can you please answer the questions in comment #5?

Comment 7 by jose.dap...@lge.com, Apr 27 2018

Sorry for the delay, here are the answers:



> > 1) "Listen to the other peer audio received", "Only less than a second is received, then no sound anymore." 

> So the near end experiences a problem with audio playback, not with the microphone - correct?

The remote end experiences a problem with audio playback, that is caused by an error capturing the audio in the local peer.

> > 2) "use Alsa instead of Pulseaudio for audio input"

> Is Alsa setup on the near end or on the remote end (peer)?

Near end.

Owner: olka@chromium.org
Status: Assigned (was: Unconfirmed)

Sign in to add a comment