alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: James Courtier-Dutton <james.dutton@gmail.com>
To: Yiliang Bao <yiliangb@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: What is the required accuracy of audio sampling rate?
Date: Wed, 17 Feb 2010 12:52:57 +0000	[thread overview]
Message-ID: <ad2655cb1002170452s617ada8du1de85aa3baa9c6fb@mail.gmail.com> (raw)
In-Reply-To: <e5baf3861002161558x1d36f74anf63c5db145762668@mail.gmail.com>

On 16 February 2010 23:58, Yiliang Bao <yiliangb@gmail.com> wrote:
> Hi,
>
> I have a PCI-e audio card that does not give very accurate sampling rate
> (about -0.2% error, i.e., if I set the sampling rate to 8K, I got only 7984
> samples per second on average). It caused various synchronization problems
> in applications like gstreamer.
>
> Since there will be some difference from one clock domain to another, I am
> wondering if there is any defined tolerance on the sampling rate, and where
> the right place is to correct this kind of error. I would really appreciate
> if someone can point me to the related documents/links.
>

There is no defined tolerance on sampling rate.
Audio apps should be able to deal with a certain amount of error.
xine uses the system clock for its synchronization, and resamples the
audio output if the audio hardware is running at a different rate.
Other apps might use the audio clock and sync to that. In that case,
it might get the problems you describe.
Try playing your media in xine and see if the problem disappears.

Kind Regards

James

  parent reply	other threads:[~2010-02-17 12:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-16 23:58 What is the required accuracy of audio sampling rate? Yiliang Bao
2010-02-17  3:08 ` pl bossart
2010-02-17 12:52 ` James Courtier-Dutton [this message]
2010-02-17 13:03   ` Jon Smirl
2010-02-17 17:14     ` Yiliang Bao

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=ad2655cb1002170452s617ada8du1de85aa3baa9c6fb@mail.gmail.com \
    --to=james.dutton@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=yiliangb@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;
as well as URLs for NNTP newsgroup(s).