From: Lennart Poettering <mznyfn@0pointer.de>
To: alsa-devel@alsa-project.org
Subject: Re: Maximum buffer size on HDA
Date: Thu, 19 Jun 2008 19:42:38 +0200 [thread overview]
Message-ID: <20080619174238.GA7022@tango.0pointer.de> (raw)
In-Reply-To: <20080616123740.GA15742@tango.0pointer.de>
On Mon, 16.06.08 14:37, Lennart Poettering (mznyfn@0pointer.de) wrote:
heya!
> > I'm not quite sure what you like to change. Make 1MB limit smaller? Or
> > change the default preallocated size? Or remove preallocation? I think
> > that it might make sense to increase the default preallocation value to
> > 128KB or 192KB.
>
> For PulseAudio it would be of big benefit if we could change the
> default in a way the for the highest sensible sampling rate/number of
> channels/sample type we'd always be able to get a two-second
> buffer. Windows and Mac use 2s of buffer by default, and I think it
> would make sense for PulseAudio to do that too.
>
> i.e. if the soundcard can do 2ch/16bit/44100hz at best I'd like to
> have a buffer size of up to 344KB; if the soundcard can to
> 5.1/32bit/48000 at best then i'd like to have a buffer of up to 2.2MB
> or so.
Takashi, Jarsolav, how can I bribe you into increasing this limit?
What are the implications of this change? (Just wondering if it would
make sense for us to change this limit in the Fedora kernel packages)
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net ICQ# 11060553
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
next prev parent reply other threads:[~2008-06-19 17:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 19:13 Maximum buffer size on HDA Lennart Poettering
2008-06-16 10:32 ` Takashi Iwai
2008-06-16 10:53 ` Jaroslav Kysela
2008-06-16 12:11 ` Takashi Iwai
2008-06-16 12:29 ` Jaroslav Kysela
2008-06-16 12:37 ` Lennart Poettering
2008-06-19 17:42 ` Lennart Poettering [this message]
2008-06-20 7:10 ` Takashi Iwai
2008-06-16 12:42 ` Takashi Iwai
2008-06-16 10:32 ` 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=20080619174238.GA7022@tango.0pointer.de \
--to=mznyfn@0pointer.de \
--cc=alsa-devel@alsa-project.org \
/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.