All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian McMenamin <adrian@mcmen.demon.co.uk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: pointer callback in pcm
Date: Fri, 10 Mar 2006 19:51:01 +0000	[thread overview]
Message-ID: <1142020261.9246.3.camel@localhost.localdomain> (raw)
In-Reply-To: <1141952015.13319.90.camel@mindpipe>

On Thu, 2006-03-09 at 19:53 -0500, Lee Revell wrote:
> On Thu, 2006-03-09 at 22:21 +0000, Adrian McMenamin wrote:
> > The documentation states:
> > 
> > "This callback is called when the PCM middle layer inquires the current
> > hardware position on the buffer."
> > 
> > 
> > Does that mean the position the hardware is at (in its ring buffer in my
> > case) or does it mean the position we are at in the dma buffer.
> > 
> > ie I have a 128k DMA buffer which transfers samples into the 32k
> > hardware memory buffer. Which position am I meant to be reporting?
> > 
> 
> The DMA buffer should be the same size as the hardware buffer, so the
> positions should be the same.
> 
> The pointer callback should return the position of sample that the
> hardware is currently playing.
> 
Thanks. I am sure I am driving you round the twist now, but that (both
buffers being the same size) was a key piece of information I was
unaware of. There are several pints in it if you are ever around in
North London :)

But my basic problem remains - my buffer is 8 periods long and I get to
hear them over and over again :( - nothing new is ever fed into the DMA
buffer and so nothing new therefore ever gets fed into the hardware
buffer.

I start the process by transferring a whole eight periods worth into the
hardware buffer is that a mistake? Should I always be feeding in one
period at a time only?



-------------------------------------------------------
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-10 19:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-09 22:21 pointer callback in pcm Adrian McMenamin
2006-03-10  0:53 ` Lee Revell
2006-03-10 19:51   ` Adrian McMenamin [this message]
2006-03-10 20:16     ` Takashi Iwai
2006-03-10 20:21       ` Adrian McMenamin
2006-03-10 20:23       ` Lee Revell
2006-03-11 11:16     ` James Courtier-Dutton
2006-03-11 11:27       ` Adrian McMenamin
2006-03-11 15:42         ` James Courtier-Dutton
2006-03-11 15:53           ` Adrian McMenamin
2006-03-11 17:30           ` Adrian McMenamin
2006-03-11 18:47             ` James Courtier-Dutton
2006-03-11 19:08               ` Adrian McMenamin
2006-03-11 19:15                 ` James Courtier-Dutton
2006-03-11 19:18                   ` Adrian McMenamin
2006-03-11 19:37                     ` James Courtier-Dutton
2006-03-11 19:55                       ` Adrian McMenamin
2006-03-11 19:26               ` Adrian McMenamin
2006-03-11 19:35                 ` James Courtier-Dutton

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=1142020261.9246.3.camel@localhost.localdomain \
    --to=adrian@mcmen.demon.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --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 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.