From: Fredrik Lingvall <fl@signal.uu.se>
To: alsa-devel@lists.sourceforge.net
Subject: Aliasing on ALi5451
Date: Sat, 24 May 2003 10:18:17 +0200 [thread overview]
Message-ID: <3ECF2AC9.8070503@signal.uu.se> (raw)
Hi!
I've tried to do loadspeaker identification using the ALi5451 chipset
in my laptop. I saw a strong drop in the spectrum above ~2kHz when
a ran the ADC:s at 44100 (I used a high quality microphone and a mic
pre-amp). I then wired the audio output directly to the input with
the same result - strong attenuation above 2kHz (I used wideband
white noise as identication signal). Then I generated a chirp signal
(5 sec sine sweep from 0-24kHz using Matlab) at 48kHz sampling rate
which I recorded using Audacity at 8, 44.1, and 48 kHz. There was
clearly freqeuency folding (aliasing) for all sampling freqs except 48 kHz
(see the time-freq plot at:
http://www.signal.uu.se/Staff/fl/chirp_test.jpg).
From the specs of the cs4299 chip (used in ALi 5451) it allways runs
at 48 kHz and uses sample rate converters for the other sampling freqs.
However, the anti-aliasing filters (if there are any) do not seem to adapt
when changing sampling freq. I also checked
cat /proc/asound/5451/pcm0p/sub0/hw_params
and
cat /proc/asound/5451/pcm0c/sub0/hw_params
when playing/recording and the sampling freqs. was correct.
Is this a driver issue or is it just a bad sound chip?
Regards
Fredrik
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
next reply other threads:[~2003-05-24 8:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-24 8:18 Fredrik Lingvall [this message]
[not found] ` <1053786705.876.11.camel@localhost>
2003-05-27 13:09 ` Aliasing on ALi5451 Fredrik Lingvall
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=3ECF2AC9.8070503@signal.uu.se \
--to=fl@signal.uu.se \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.