Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: James Courtier-Dutton <James@superbug.co.uk>,
	alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: A suggestion for better resamplers in alsa.
Date: Mon, 04 Apr 2005 18:10:53 +0200	[thread overview]
Message-ID: <s5hfyy6bjzm.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.HPX.4.33n.0504041709240.17949-100000@studcom.urz.uni-halle.de>

At Mon, 4 Apr 2005 17:49:27 +0200 (METDST),
Clemens Ladisch wrote:
> 
> Takashi Iwai wrote:
> > ...
> > IMO, the only "perfect" solution is to change API to allow variable
> > period sizes.  Otherwise the size mismatch always occurs regardless
> > what trick you apply.
> 
> This is yet another case of a constant-period-size device, like USB or
> ymfpci.
> 
> > However, the variable period size would introduce the significant
> > changes to the core part.
> 
> Maybe we could generalize what usb-usx2y's hwdep does.
> 
> > For example, currently the hw/appl pointers are accumulated until
> > the boundary near to INT_MAX.  The real DMA buffer position in the
> > ringbuffer is calculated as 'hwptr % buffer_size'.  With the
> > variable period size, it's no longer true.
> 
> But buffer_size would remain constant, wouldn't it?

I don't think so (in the above, I suppose the input-hwptr on rate
plugin, not the output-hwptr on the real hardware).


Takashi


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-04-04 16:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-01 20:58 A suggestion for better resamplers in alsa James Courtier-Dutton
2005-04-04 11:11 ` Takashi Iwai
2005-04-04 15:49   ` Clemens Ladisch
2005-04-04 16:10     ` Takashi Iwai [this message]
2005-04-05 19:58       ` James Courtier-Dutton
2005-04-07  7:56         ` Jaroslav Kysela
2005-04-07  8:32           ` Takashi Iwai
2005-04-10  9:15             ` James Courtier-Dutton
2005-04-12 12:12               ` Jaroslav Kysela
2005-04-12 12:24                 ` James Courtier-Dutton
2005-04-12 12:30                   ` Jaroslav Kysela

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=s5hfyy6bjzm.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=James@superbug.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=clemens@ladisch.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox