Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.co.uk>
To: alsa-devel@lists.sourceforge.net
Subject: alsa resampler comstraints.
Date: Thu, 21 Sep 2006 21:54:00 +0100	[thread overview]
Message-ID: <4512FBE8.6060905@superbug.co.uk> (raw)

Hi,

I want to document some of the constraints of the alsa resampler.
Here is what I understand, and I would like someone to verify my 
statements before I document them.

1) The buffer and period sizes for the sound card hardware to resampler 
are limited to the max buffer and period sizes available on the 
hardware. As a result, the available buffer and period sizes vary 
depending on hardware utilised.
2) The resampler converts one hardware period size at a time. This 
results in the buffer and period size constraints explained in (1) 
arriving at the application as a direct ratio of source and destination 
sample rate.
e.g. hardware has 2 periods of 1024 frames running at 48000 Hz.
application will see 2 periods of 1024 * 44100 / 48000 = 940.8. This is 
rounded down to 940 frames. So the user application sees 2 periods of 
940 frames.
If user space asks for 2 periods of 1024 at 44100 hz it will fail.


The above 2 points were true some time ago. Has anything changed?


Kind Regards

James


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

             reply	other threads:[~2006-09-21 20:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-21 20:54 James Courtier-Dutton [this message]
2006-09-22 16:25 ` alsa resampler comstraints Clemens Ladisch

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=4512FBE8.6060905@superbug.co.uk \
    --to=james@superbug.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