From: Trent Reed <treed0803@gmail.com>
To: alsa-devel@alsa-project.org
Subject: SND_PCM_STREAM_CAPTURE and SND_PCM_NONBLOCK producing strange artifacts
Date: Tue, 28 Jun 2016 19:27:25 -0700 [thread overview]
Message-ID: <CAL6pMWpW4VMPkaeqUS3DaU4d+fUB2s1i9kpTPkfNPeNjW4gHpQ@mail.gmail.com> (raw)
Hey All,
I've been banging my head against the wall for about a week on this bug.
The following gist shows my sample reproduction code:
https://gist.github.com/TReed0803/985c5d5c3d295245e19006a27be447c3
I'm simply opening up a non-blocking PCM capture stream and writing the
contents of the reads to stdout.
(Originally, I was writing to the playback stream, but I was hearing this
strange static occasionally!)
It's the static I'm trying to debug. It doesn't happen every time. In fact,
sometimes I'll go a few consecutive executions without hearing it.
I was able to capture some of the bad data, and I loaded it up in Audacity
for visualization:
https://drive.google.com/file/d/0B-1aumGKQcQTcUJoZzIwRWhYSFE/view?usp=sharing
It looks like the internal buffer occasionally is sending me more data than
it actually captured, and I end up either reading old PCM data from the
internal ring buffer, or (at the very beginning) a bunch of zeros.
Can anyone help me understand what is going on? What could cause these
definitely incorrect samples to be recorded? (I get the same effect
regardless of hardware, but I will list hardware just in case.)
I hope I have all the information you might need:
Hardware: Samson Meteor Mic (USB-Audio, USB Mixer) [Though, it even happens
with my built-in microphone]
ALSA version: Advanced Linux Sound Architecture Driver Version
k4.4.0-28-generic.
apt-cache policy (installed alsa-lib version): 1.1.0-0ubuntu1
Thanks,
- Trent Reed
next reply other threads:[~2016-06-29 2:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 2:27 Trent Reed [this message]
2016-07-02 21:58 ` SND_PCM_STREAM_CAPTURE and SND_PCM_NONBLOCK producing strange artifacts Trent Reed
2016-07-05 6:52 ` Takashi Iwai
[not found] ` <CAL6pMWpwpgLBmqEhDnqKPvQPYmnSy1S=19m6YL=5YMpHQRfLtw@mail.gmail.com>
2016-07-05 7:38 ` Takashi Iwai
2016-07-05 8:46 ` Trent Reed
2016-08-06 19:13 ` Trent Reed
2016-08-11 14:32 ` Takashi Iwai
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=CAL6pMWpW4VMPkaeqUS3DaU4d+fUB2s1i9kpTPkfNPeNjW4gHpQ@mail.gmail.com \
--to=treed0803@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).