Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Clemens Ladisch" <cladisch@fastmail.net>
To: Grace Baldonasa <gbaldona@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: question about sampling rate
Date: Fri, 11 Aug 2006 19:06:01 +0200	[thread overview]
Message-ID: <1155315961.10237.268179763@webmail.messagingengine.com> (raw)
In-Reply-To: <7034e7b50608091945r39ddaeeevda675f05251be9cb@mail.gmail.com>

Grace Baldonasa wrote:
> I am half way my development. I can stream music using dynamic settings (any
> speaker plugged in to my host be heard of some music when my application is
> streaming some audio data). However, there are still background noise I am
> hearing. Here is how I computed my streaming size:
> 
> sampling rate = 44100
> channel = 2
> bit resolution = 16
> period length = 20 ms
> period size = 3528

bytes

> This period size is used as my buffer size, and this is sliced as it is
> streamed to my device.
> I have not considered any sychronization yet. Here is the speaker
> configuration:
> Synchronization type = adaptive sync
> 
> My understanding is no sync pipe is defined  by the device, therefore I dont
> need to schedule any sync data, am I correct?

Yes.  An adaptive endpoint should be able to work with any sample rate,
as long as it's near 44100.

How do you slice your buffer?


Regards,
Clemens

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  reply	other threads:[~2006-08-11 17:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-12  8:05 question about sampling rate Grace Baldonasa
2006-07-12  8:56 ` Adrian McMenamin
2006-07-12  9:17   ` Grace Baldonasa
2006-07-12  9:37     ` Clemens Ladisch
2006-07-12 10:00       ` Grace Baldonasa
2006-07-14 17:31         ` Clemens Ladisch
2006-07-18  5:13           ` Grace Baldonasa
2006-07-18  7:11             ` Clemens Ladisch
2006-07-18  7:21               ` Grace Baldonasa
2006-07-18 14:34                 ` Clemens Ladisch
2006-07-19  1:27                   ` Grace Baldonasa
2006-07-19 12:29                     ` Clemens Ladisch
2006-08-10  2:45                       ` Grace Baldonasa
2006-08-11 17:06                         ` Clemens Ladisch [this message]
2006-08-31  5:32                           ` Grace Baldonasa
2006-08-31  8:17                             ` Clemens Ladisch
2006-08-31  8:22                               ` Grace Baldonasa
2006-08-31  8:49                                 ` Clemens Ladisch
2006-08-31  9:10                                   ` Grace Baldonasa
2006-08-31  9:50                                     ` Grace Baldonasa
2006-08-31 10:50                                       ` Clemens Ladisch
2006-09-19  9:36                                         ` Grace Baldonasa
2006-10-02  3:53                                           ` Grace Baldonasa
2006-10-04 12:01                                             ` 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=1155315961.10237.268179763@webmail.messagingengine.com \
    --to=cladisch@fastmail.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=gbaldona@gmail.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