Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Adrian McMenamin <adrian@mcmen.demon.co.uk>
Cc: Lee Revell <rlrevell@joe-job.com>, alsa-devel@alsa-project.org
Subject: Re: Couple of questions
Date: Fri, 17 Mar 2006 21:29:20 +0100	[thread overview]
Message-ID: <s5hr750stlr.wl%tiwai@suse.de> (raw)
In-Reply-To: <1142627252.9449.9.camel@localhost.localdomain>

At Fri, 17 Mar 2006 20:27:32 +0000,
Adrian McMenamin wrote:
> 
> On Fri, 2006-03-17 at 11:13 +0100, Takashi Iwai wrote:
> 
> > 
> > The period size is same, but the copy is not done like LLLLRRRR.
> > 
> > As default, the whole buffer is divided to number of channels.  For
> > example, using two channels,
> > 
> > 	|LLLLLLL..|RRRRRRR....|
> > 	|<--- buffer_size --->|
> > 
> > and using six channels,
> > 
> > 	|1111....|2222....|.....|6666....|
> > 	|<-------- buffer_size --------->|
> > 
> > where each channel has a length of (period_size * periods) samples.
> > Unless the buffer size is changed, this assignment of each channel
> > also isn't changed.
> > 
> > The above is the default behavior.  You can change the assignment as
> > you like by defining proper copy and silence callback, too.  For
> > mmap, you need to define CHANNEL_INFO ioctl, too.
> > 
> 
> Presumably this is what happens at the start, but when doing a single
> period update presumably it is split LLLLRRRR on non interleaved

No, as I wrote in the above, the assignment of each channel isn't
changed, i.e. the buffer position of each channel remains.

The middle layer handles the whole buffer simply as a bundle of
multiple mono streams.


Takashi


-------------------------------------------------------
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

  reply	other threads:[~2006-03-17 20:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-16  0:01 Couple of questions Adrian McMenamin
2006-03-16 10:42 ` Takashi Iwai
2006-03-16 21:08   ` Adrian McMenamin
2006-03-17  0:10     ` Carlos Munoz
2006-03-17  0:20     ` Lee Revell
2006-03-16 23:34   ` Adrian McMenamin
2006-03-17  0:16     ` Lee Revell
2006-03-17 10:13       ` Takashi Iwai
2006-03-17 20:27         ` Adrian McMenamin
2006-03-17 20:29           ` Takashi Iwai [this message]
2006-03-17 23:29             ` Adrian McMenamin
2006-03-17 23:46               ` Lee Revell
2006-03-17 23:51                 ` Adrian McMenamin
2006-03-17 23:58                   ` Lee Revell
2006-03-18  0:08                     ` Adrian McMenamin
2006-03-18  0:17                       ` Lee Revell
2006-03-18  0:22                         ` Adrian McMenamin
2006-03-18 11:08   ` Adrian McMenamin
2006-03-20 18:11     ` Carlos Munoz

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=s5hr750stlr.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=adrian@mcmen.demon.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=rlrevell@joe-job.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox