From: Takashi Iwai <tiwai@suse.de>
To: Ihar Filipau <thephilips@gmail.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: dmix produces garbled sound on ARM
Date: Mon, 13 Jun 2016 14:42:10 +0200 [thread overview]
Message-ID: <s5hfush5kgt.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAD08gxJkLYh2VvqVhCu76a=kWUdnkuU7Eoni57bNVUvg0teRnA@mail.gmail.com>
On Mon, 13 Jun 2016 14:32:30 +0200,
Ihar Filipau wrote:
>
> On 6/9/16, Takashi Iwai <tiwai@suse.de> wrote:
> > On Thu, 09 Jun 2016 16:05:42 +0200,
> > Ihar Filipau wrote:
> >>
> >> The only thing so far I have found is `aplay --dump-hw-params`, but it
> >> seem to display the allowed ranges, not the defaults/the params which
> >> are used.
> >
> > You just need to check what "aplay -v ..." shows. For example,
> > % aplay -Dplug:dmix -v foo.wav
>
> I have just retested it with the "aloop", completely without hardware.
> The garbled sound comes from the software, from the dmix/libasound.
> The problem is not related to (sound) hardware.
Still it is likely a driver problem. dmix updates are based on ALSA
PCM slave timer, i.e. it's synced with PCM period elapses. That is,
if the driver updates at a wrong timing, sending the notification
before the sample data has been processed, you'll get the garbled
output as you have.
Takashi
next prev parent reply other threads:[~2016-06-13 12:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 11:38 dmix produces garbled sound on ARM Ihar Filipau
2016-06-09 13:01 ` Takashi Iwai
2016-06-09 13:17 ` Ihar Filipau
2016-06-09 13:25 ` Takashi Iwai
[not found] ` <CAD08gxKw2UK9JJ80Pp5icxLC_k-8dGykhHd3DbUvjPJXUGzVtQ@mail.gmail.com>
[not found] ` <s5hporqe5r2.wl-tiwai@suse.de>
2016-06-10 12:06 ` Ihar Filipau
2016-06-13 12:32 ` Ihar Filipau
2016-06-13 12:42 ` Takashi Iwai [this message]
2016-06-13 14:04 ` Ihar Filipau
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=s5hfush5kgt.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=thephilips@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 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.