Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Changes over dmix: 1.0.11rc4 and future
Date: Sat, 01 Apr 2006 14:19:13 -0500	[thread overview]
Message-ID: <1143919154.30769.16.camel@mindpipe> (raw)
In-Reply-To: <s5h64lzalr0.wl%tiwai@suse.de>

On Mon, 2006-03-27 at 18:35 +0200, Takashi Iwai wrote:
> Hi,
> 
> it looks like the 1.0.11rc4 announcement isn't sent out, so here I'd
> like to explain what has been changed over dmix recently.
> 
> As of 1.0.11rc4, dmix accepts more flexible buffer sizes than the
> earlier versions did.  The buffer size is basically arbitrary.  The
> only restriction is that it's aligned to the period size, and the
> minimal periods are two.
> 
> With this change, some applications have positive influences, and some
> have negative.  The regression, for example with speaker-test, happens
> because there was no upper limit of buffer size.  It's already fixed
> in the CVS version (by setting max periods = 1024).
> 
> If you have a problem with dmix what didn't happen ago, try to define
> 
> 	defaults.pcm.dmix_variable_buffer false
> 
> in ~/.asoundrc.
> 

Does not work (alsa-lib and utils from today's CVS):

$ aplay -Dplug:dmix51 /usr/share/sounds/error.wav 
ALSA lib pcm.c:6650:(snd_pcm_slave_conf) Unknown field
variable_buffer_size
aplay: main:547: audio open error: Invalid argument

.asoundrc:

defaults.pcm.dmix_variable_buffer false
pcm.dmix51 {
        type upmix
        slave.pcm {
                type dmix
                ipc_key {
                        @func refer
                        name defaults.pcm.ipc_key
                }
                ipc_gid {
                        @func refer
                        name defaults.pcm.ipc_gid
                }
                slave {
                        pcm "hw:0,0"
                        period_size 512
                        periods 10
                        channels 6
                        variable_buffer_size true
                }
        }
}

Lee



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

  parent reply	other threads:[~2006-04-01 19:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-27 16:35 Changes over dmix: 1.0.11rc4 and future Takashi Iwai
2006-03-28 23:00 ` James Courtier-Dutton
2006-04-01 19:19 ` Lee Revell [this message]
2006-04-03  9:59   ` Takashi Iwai
2006-04-03 16:29     ` Lee Revell
2006-04-03 16:42       ` Takashi Iwai
2006-04-03 17:17 ` Takashi Iwai

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=1143919154.30769.16.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox