From: Lee Revell <rlrevell@joe-job.com>
To: Adrian McMenamin <adrian@mcmen.demon.co.uk>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Re: How can I deal with this?
Date: Sun, 19 Mar 2006 14:31:33 -0500 [thread overview]
Message-ID: <1142796695.4532.34.camel@mindpipe> (raw)
In-Reply-To: <1142795771.9700.9.camel@localhost.localdomain>
On Sun, 2006-03-19 at 19:16 +0000, Adrian McMenamin wrote:
> On Sun, 2006-03-19 at 14:11 -0500, Lee Revell wrote:
> > On Sun, 2006-03-19 at 19:01 +0000, Adrian McMenamin wrote:
> > > when I play mono my device has one hardware buffer of size 0x8000, when
> > > I play stereo it has two of size 0x8000
> > >
> > > I have .buffer_bytes_max and _min set to 0x8000
> >
> > Then .buffer_bytes_max should be 0x10000. The buffer and period sizes
> > in your hw_info structure are for the entire buffer, not per channel.
> >
> >
> And double period max too I assume?
>
>
If the hardware can do that, yes.
The hw_info structure should merely specify the hardware characteristics
- you are not trying to change the behavior if the middle layer.
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
next prev parent reply other threads:[~2006-03-19 19:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-19 19:01 How can I deal with this? Adrian McMenamin
2006-03-19 19:11 ` Lee Revell
2006-03-19 19:16 ` Adrian McMenamin
2006-03-19 19:31 ` Lee Revell [this message]
2006-03-19 19:49 ` Adrian McMenamin
2006-03-19 20:33 ` Adrian McMenamin
2006-03-19 20:43 ` Lee Revell
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=1142796695.4532.34.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=adrian@mcmen.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
/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