From: pl bossart <bossart.nospam@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: Tue, 16 Feb 2010 21:08:15 -0600 [thread overview]
Message-ID: <6160a5131002161908m7c5278fas1291fbd50956f300@mail.gmail.com> (raw)
In-Reply-To: <e5baf3861002161558x1d36f74anf63c5db145762668@mail.gmail.com>
> 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.
Can you be more specific on your sync issues? Generally the audio
clock is used as reference, and video adjusts to it.
> 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.
It really depends on the standard, and if you are slave or master.
Each standard has its own requirements. For example an AES-EBU
interface will require 10ppm for professional uses as a source, and
less as a sink. HDAudio requires the nominal BCLK 24MHz frequency to
be between 23.9976 and 24.0024 MHz. I don't think on an I2S link there
are such requirements, the frequency will depend on how accurate the
audio PLL is.
Note that the actual frequency is only one of the parameters
influencing audio quality, jitter issues are much worse. If your clock
is slightly off but remains stable, you are usually good. If it varies
you'll have real audible quality issues.
- Pierre
next prev parent reply other threads:[~2010-02-17 3:08 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 [this message]
2010-02-17 12:52 ` James Courtier-Dutton
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=6160a5131002161908m7c5278fas1291fbd50956f300@mail.gmail.com \
--to=bossart.nospam@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).