From: Daniel Mack <daniel@zonque.org>
To: Andrew Reyes <dsreyes1014@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Behringer Uphoria UMC204 usb audio capture only pops and clicks
Date: Mon, 21 Apr 2014 18:11:11 +0200 [thread overview]
Message-ID: <5355431F.3000501@zonque.org> (raw)
In-Reply-To: <CAEYsuVML1ZFGGP35KB=3im_JTgNSCoNfPg1aMnzT6mjR=u1cJA@mail.gmail.com>
(please do not top-post)
On 04/21/2014 04:17 PM, Andrew Reyes wrote:
> And this is the pastebin link for the stream info set at 48khz:
> http://pastebin.com/ysw6j5uA
Ok, so the actual frequency is close enough to the nominal one. Please
also do the tests wit aplay to see whether your issue can be recovered
by chosing larger buffer sizes. Do you see any messages in dmesg when
these 'clicks and pop' occur?
Also, please try this one:
(while sleep 0.123; do grep 'Momentary freq' /proc/asound/xxx/stream0;
done) | uniq
Thanks,
Daniel
next prev parent reply other threads:[~2014-04-21 16:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 3:12 Behringer Uphoria UMC204 usb audio capture only pops and clicks Andrew Reyes
2014-04-21 13:25 ` Daniel Mack
2014-04-21 14:10 ` Andrew Reyes
2014-04-21 14:17 ` Andrew Reyes
2014-04-21 16:11 ` Daniel Mack [this message]
2014-04-21 16:51 ` Andrew Reyes
2014-04-21 17:49 ` Daniel Mack
2014-04-21 18:33 ` Andrew Reyes
2014-04-21 18:37 ` Daniel Mack
2014-04-21 18:44 ` Andrew Reyes
2014-04-21 18:49 ` Andrew Reyes
2014-04-21 18:54 ` Daniel Mack
2014-04-21 18:56 ` Andrew Reyes
2014-04-21 20:33 ` Andrew Reyes
2014-04-23 14:40 ` Andrew Reyes
2014-04-23 14:59 ` Daniel Mack
2014-04-23 15:40 ` Andrew Reyes
2014-04-23 16:18 ` Andrew Reyes
2014-04-24 14:14 ` Andrew Reyes
2014-04-29 17:53 ` Andrew Reyes
2014-04-29 17:58 ` Daniel Mack
-- strict thread matches above, loose matches on Subject: below --
2014-04-18 4:30 Andrew Reyes
2014-04-16 13:09 Andrew Reyes
2014-04-16 1:44 Andrew Reyes
2014-04-16 8:40 ` Daniel Mack
2014-04-13 23:47 Andrew Reyes
2014-04-12 21:45 Andrew Reyes
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=5355431F.3000501@zonque.org \
--to=daniel@zonque.org \
--cc=alsa-devel@alsa-project.org \
--cc=dsreyes1014@gmail.com \
/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