All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ihar Filipau <thephilips@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: dmix produces garbled sound on ARM
Date: Fri, 10 Jun 2016 14:06:31 +0200	[thread overview]
Message-ID: <CAD08gx+mv5GtD=Vc0iw51OeKuzeUwRXHHTZMu--j31xdDWMcbQ@mail.gmail.com> (raw)
In-Reply-To: <s5hporqe5r2.wl-tiwai@suse.de>

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

[ Replying back to the list, since exchange of the lengthy outputs is
over for now. ]

My parameters are nearly identical to yours (except for the
differences which could be attributed to my 32-bit vs your 64-bit
systems, and the hardware S16_LE vs S32_LE). Yet the problem persists.

I have checked the Raspberry Pi forums/mail list and it seems that
"dmix" works fine there. Thus, the problem might be related to the hw
driver.

How can I localize the problem? Is there any way to intercept the data
stream which goes to the sound card, and compare the content between
normal direct playback vs dmix?

P.S. Though the window is closing for my investigations. I'm starting
to prepare a workaround: applications shouldn't keep pcm open all the
time, should open pcm when needed, and they should retry with a delay
if opening pcm failed.

  parent reply	other threads:[~2016-06-10 12:06 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 [this message]
2016-06-13 12:32           ` Ihar Filipau
2016-06-13 12:42             ` Takashi Iwai
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='CAD08gx+mv5GtD=Vc0iw51OeKuzeUwRXHHTZMu--j31xdDWMcbQ@mail.gmail.com' \
    --to=thephilips@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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.