New issue 29356 by feedback...@gmail.com: Microphone: Microphone doesn't
work for video chats.
http://code.google.com/p/chromium-os/issues/detail?id=29356
http://feedback.corp.google.com/#/Cluster/2569904
Description:
Mic doesn't work for video chats.
Number of confirmed reports:
5
Total number of reports:
5
Mic doesn't work in Gtalk on ZGB. arecord works fine, so does google voice
search. Everything works on Alex.
Comment #2 on issue 29356 by arsc...@chromium.org: Microphone: Microphone
doesn't work for video chats.
http://code.google.com/p/chromium-os/issues/detail?id=29356
(No comment was entered for this change.)
Noticed this with R19 build "2046.30.0" on ZGB:
1.) Internal mic seems muted with google talk.
2.) External mic works fine with google talk though.
3.) But, the internal mic responds fine to arecord.
Comment #5 on issue 29356 by dgr...@chromium.org: Microphone: Microphone
doesn't work for video chats.
http://code.google.com/p/chromium-os/issues/detail?id=29356
+ajm
I did a capture of the talk plugin when this was happening. Any ideas?
Thanks,
Dylan
Attachments:
echo.dump 176 KB
The capture-side files are empty, meaning capturing isn't occurring at all.
For Googlers, a plugin log file should always be created. Look in
$HOME/.config/google-googletalkplugin. You should find file(s) like
gtalkplugin-cXXXX.log.bz2. Upload the one corresponding to the call
(presumably the latest).
Not sure which errors in there are important, but there seem to be a few
about handle_capture being NULL.
Attachments:
gtalkplugin-c2051245270.log.bz2 5.9 KB
Comment #8 on issue 29356 by angel...@chromium.org: Microphone: Microphone
doesn't work for video chats.
http://code.google.com/p/chromium-os/issues/detail?id=29356
(No comment was entered for this change.)
The first errors about PulseAudio are fine, it just means we're falling
back to ALSA. I think the "handle_capture is now set to NULL" error is
actually erroneous; from the code it looks like it shouldn't be an error
but an info message.
The handle_capture error indicates recording is being stopped a few times,
which might indicate an issue. On the other hand we can call start/stop to
test devices so this might be nothing. I don't see anything else in the log
which could indicate the source of the problem.
We could have one of our TSEs repro and investigate this further. Dylan,
can you CC punya...@webrtc.org on this? Do you have a ZGB he could borrow
for testing?
Comment #10 on issue 29356 by dgr...@chromium.org: Microphone: Microphone
doesn't work for video chats.
http://code.google.com/p/chromium-os/issues/detail?id=29356
Added punya...@webrtc.org. I'm sure we can dig up a ZGB for him to test
with.
Comment #11 on issue 29356 by rajeevku...@chromium.org: Microphone:
Microphone doesn't work for video chats.
http://code.google.com/p/chromium-os/issues/detail?id=29356
(No comment was entered for this change.)
I have now been able to reproduce the same issue after receiving a ChromeOS
canary update. I am currently running:
Version 20.0.1105.0 canary
Platform 2153.0.0 (Official Build) canary-channel x86-zgb_he
Firmware ZGB.03.61.0740.0062G7.010
I do not know how big of a delta it is between this version and the
previous working version, but it would be helpful if someone could
determine any CLs that might have changed to trigger this. The Gtalk plugin
when it was working before and when it stopped working now is the same at
2.8.5 but that could mean that something has changed to uncover something
in the talk plugin which would be helpful to find. I will keep looking into
this to see if our logs shed any more light on this.
/Ray
/Ray
https://feedback.corp.google.com/#/Report/250339243?context=ri
https://feedback.corp.google.com/#/Report/193119355?context=ri
https://feedback.corp.google.com/#/Report/192956180?context=ri
https://feedback.corp.google.com/#/Report/213871979?context=ri
https://feedback.corp.google.com/#/Report/212389074?context=ri
Comment #15 on issue 29356 by dgr...@chromium.org: Microphone: Microphone
doesn't work for video chats.
http://code.google.com/p/chromium-os/issues/detail?id=29356
(No comment was entered for this change.)
I was able to run our internal test application and reproduce the issue
(uploaded the logfile from a loopback test entitled webrtc.txt). We seem to
be able to setup everything normally (no error is reported when choosing
the default device for capture) but once the call is started, we see
numerous logs noting that our capture thread has timed-out waiting for
samples from the soundcard. I see this on the playback side also even
though the playback is working well but this is most likely because this
was in a loopback call.
caputre snd_pcm_wait timeout //log that we see noting that our capture
process has timed-out as it has not received any samples from the soundcard.
This will take further investigation. Unfortunately I will be out of the
office next week until Thursday. But can anyone double check if anything
has changed with respect to the soundcard drivers within the versions where
it was working and not working.
Another datapoint might be good to see what the logs look like when it is
actually working to see.
Attachments:
webrtc.txt 2.6 MB
Ray, can you record the same log while using the external mic? You can get
an analog headset that works with ZGB at tech stop.
It also looks like the code in audio_device_alsa_linux will ensure there
are capture timeouts if it gets back a buffer and period size > 5ms. It is
getting a 46.5 mS buffer in this run, and telling snd_pcm_wait to timeout
after 5ms, not sure that's what's causing the problem, you might have to
give me a hand building GTalk on Monday so I can dig a little deeper.
Thanks.
I will try with an external mic to compare the logs.