From: James Courtier-Dutton <James@superbug.co.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Changes over dmix: 1.0.11rc4 and future
Date: Wed, 29 Mar 2006 00:00:42 +0100 [thread overview]
Message-ID: <4429C01A.7040608@superbug.co.uk> (raw)
In-Reply-To: <s5h64lzalr0.wl%tiwai@suse.de>
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.
>
> Also, you can try ALSA CVS version. It includes more fixes about the
> dmix. Or wait for ALSA 1.0.11-final, which (hopefully) will be
> released soon.
>
>
> So far so good. Now, about the future changes.
>
> Currently, dmix forks a resource server to share the opened file
> descriptor. (Don't misunderstand, it's not a mixing server but just
> manages the file descriptor.) This behavior seems causing troubles in
> some applications. I've been trying to reduce this mess.
>
> The below (first one) is a patch to add O_APPEND support to PCM. If a
> PCM is opened with O_APPEND, it shares the alreay opened stream.
> And the second patch is to alsa-lib to use this new O_APPEND feature.
> Since the resource can be shared via O_APPEND, we don't need dmix
> server.
>
> I'm not sure whether it's a 2.6.17 material or a post-2.6.17. Maybe
> we need a bit discussion whether this O_APPEND hack is right or not.
>
> Beware that the patch is against the very latest CVS version. The
> anon tree doesn't have it yet right now.
>
> Any comments or test reports are appreciated.
>
>
> For further implementation, we could get rid of shared memory by a
> small addition to the kernel, too. At least, two different things
> would be needed:
>
> - Missing GET_HW_PARAMS and GET_SW_PARAMS ioctls
> (Why don't we have them?)
> - Anonymous mmap for the shared sum area of dmix
>
> This requires more detailed discussion, I think.
>
>
> Takashi
This all sounds good. I will test the dmix buffer size improvement.
I remember asking for this some time ago.
This might fix problems people are having with Doom3 and the like.
James
-------------------------------------------------------
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
next prev parent reply other threads:[~2006-03-28 23:00 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 [this message]
2006-04-01 19:19 ` Lee Revell
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=4429C01A.7040608@superbug.co.uk \
--to=james@superbug.co.uk \
--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 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.