From: Adam Rosenberg <adam@alcorn.com>
To: alsa-devel@alsa-project.org
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Clicking and stuttering audio when playing two or more files
Date: Thu, 15 Jul 2010 13:21:47 -0400 [thread overview]
Message-ID: <AANLkTikcthlodljUqW8oA69UYL2znXfTgHbABTRHYwSI@mail.gmail.com> (raw)
I have audio output perfectly from my second CS42448 CODEC now, but
only when one file is playing. When I attempt to play two files, one
or both of the files play with clicking and stuttering. I am also
noticing that the PCM prepare operation is occurring more than once.
What could be causing this problem?
HW settings are:
buffer_bytes_max = 32768
period_bytes min = 8 max = 32768
periods min = 1 max = 4096
PCM runtime is reporting:
frames per period = 1114
periods = 2
total frames = 2228
frame bytes = 8
Thank you,
Adam
next reply other threads:[~2010-07-15 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 17:21 Adam Rosenberg [this message]
2010-07-19 8:59 ` Clicking and stuttering audio when playing two or more files Mark Brown
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=AANLkTikcthlodljUqW8oA69UYL2znXfTgHbABTRHYwSI@mail.gmail.com \
--to=adam@alcorn.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
/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).