From: Takashi Iwai <tiwai@suse.de>
To: LANGLOIS Olivier PIS -EXT <olivier.pis.langlois@transport.alstom.com>
Cc: Olivier Langlois <olivier@trillion01.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [ISSUE] rtl8192ce appears to interfere with ALSA playback
Date: Thu, 23 Jan 2014 17:52:09 +0100 [thread overview]
Message-ID: <s5htxcusksm.wl%tiwai@suse.de> (raw)
In-Reply-To: <89F8E4011FD7234ABFE48744E300CBC206BCE7E6@041-DB3MPN1-092.041d.mgd.msft.net>
At Thu, 23 Jan 2014 16:50:56 +0000,
LANGLOIS Olivier PIS -EXT wrote:
>
> >
> > But you passed --buffer-size and --period-size options.
>
> only to have the same params with hw:0,0 that I am giving with the dmix setup to reproduce the underruns. Otherwise the numbers below are what I have by letting aplay pick them for me by varying only the device.
>
> I have done a lot of experiments with mildly complex alsa setup during the past holiday [1] to understand that ALSA may come up with different params for different setups but the choosen 16 periods value is puzzling me...
I repeatedly wrote that it's a fixed number.
See src/conf/pcm/dmix.conf.
Takashi
>
> 1.
> http://mailman.alsa-project.org/pipermail/alsa-devel/2013-December/070561.html
>
>
> > >
> > > and I think that usually periods_num ~= buffer_time/period_time or
> > buffer_size/period_size
> > >
> > > aplay -Dhw:0,0 sine_48000.wav
> > >
> > > I have:
> > >
> > > buffer_size : 24000
> > > period_size : 6000
> > > period_time : 125000
> > >
> > > but with the default dmix setup: aplay -v sine_48000.wav:
> > >
> > > buffer_size : 16384
> > > period_size : 1024
> > > period_time : 21333
> >
> > As already mentioned, dmix has the fixed setup for its slave PCM.
> > See src/conf/pcm/dmix.conf.
> >
> >
> > Takashi
>
> ________________________________
> CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
>
next prev parent reply other threads:[~2014-01-23 16:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 6:37 [ISSUE] rtl8192ce appears to interfere with ALSA playback Olivier Langlois
2014-01-15 17:01 ` Larry Finger
2014-01-16 5:25 ` Olivier Langlois
2014-01-16 5:55 ` James Cameron
2014-01-23 8:13 ` Olivier Langlois
2014-01-23 8:13 ` Olivier Langlois
2014-01-23 8:51 ` [alsa-devel] " Takashi Iwai
2014-01-23 8:51 ` Takashi Iwai
2014-01-23 16:15 ` LANGLOIS Olivier PIS -EXT
2014-01-23 16:15 ` [alsa-devel] " LANGLOIS Olivier PIS -EXT
2014-01-23 16:21 ` LANGLOIS Olivier PIS -EXT
2014-01-23 16:28 ` Takashi Iwai
2014-01-23 16:36 ` LANGLOIS Olivier PIS -EXT
2014-01-23 16:40 ` Takashi Iwai
2014-01-23 16:50 ` LANGLOIS Olivier PIS -EXT
2014-01-23 16:52 ` Takashi Iwai [this message]
[not found] ` <89F8E4011FD7234ABFE48744E300CBC206BCE732-mYYER/oPuzr5ytm4Ncodt1/tZ8AoKt9cLnY5E4hWTkheoWH0uzbU5w@public.gmane.org>
2014-01-23 16:29 ` [alsa-devel] " Takashi Iwai
2014-01-23 16:29 ` Takashi Iwai
[not found] ` <s5h1tzyu0em.wl%tiwai-l3A5Bk7waGM@public.gmane.org>
2014-01-24 5:32 ` Olivier Langlois
2014-01-24 5:32 ` Olivier Langlois
2014-01-27 6:32 ` Olivier Langlois
2014-01-27 6:54 ` James Cameron
2014-01-27 7:08 ` Olivier Langlois
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=s5htxcusksm.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=olivier.pis.langlois@transport.alstom.com \
--cc=olivier@trillion01.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.