From: GitHub issues - reopened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: crackling microphone
Date: Sat, 9 May 2020 07:59:29 +0200 (CEST) [thread overview]
Message-ID: <20200509055929.C8665F8015F@alsa1.perex.cz> (raw)
In-Reply-To: <1589003959919719934-webhooks-bot@alsa-project.org>
alsa-project/alsa-plugins issue #10 was reopened from riddicc:
Hi!
When I send a 800Hz sine wave with rate 12345 to pcm.outmic and
when I arecord from pcm.micend at rate 8000 with 1 channel ([/etc/asound.conf](https://github.com/alsa-project/alsa-plugins/files/4597703/etc-asound-conf.txt)),
then I get a lot of tiny little gaps (see attachment) and a lot of messages like "overrun!!! (at least 0.014 ms long)" (the "ms" vary from 0.008 to 0.043; and arecord continues to record) and sometimes even this error: "arecord: xrun:1672: read/write error, state = RUNNING" (it causes arecord to terminate).
1. > speaker-test -D outmic -t sine -f 800 -c2 -r 12345
2. > arecord -D micend -r 8000 -c 1 -f S16_LE /tmp/bla.wav
twinkle makes even bigger gaps, when I let it use pcm.micend as microphone...
But with hw:Generic,0,0 as mic device twinkle works fine...
https://github.com/LubosD/twinkle/issues/207
"samplerate_best" and "samplerate_order" seems to make it worse...
How can I fix that?
Thx.
Bye.
Issue URL : https://github.com/alsa-project/alsa-plugins/issues/10
Repository URL: https://github.com/alsa-project/alsa-plugins
next parent reply other threads:[~2020-05-09 6:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1589003959919719934-webhooks-bot@alsa-project.org>
2020-05-09 5:59 ` GitHub issues - reopened [this message]
[not found] <1589023625704346895-webhooks-bot@alsa-project.org>
2020-05-09 11:27 ` crackling microphone GitHub issues - reopened
[not found] <1588925673549724102-webhooks-bot@alsa-project.org>
2020-05-08 8:14 ` GitHub issues - edited
[not found] <1588925461132916927-webhooks-bot@alsa-project.org>
2020-05-08 8:11 ` GitHub issues - opened
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200509055929.C8665F8015F@alsa1.perex.cz \
--to=github@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.