From: Daniel Mack <daniel@caiaq.de>
To: alsa-devel@alsa-project.org
Cc: Tim Ruetz <tim@caiaq.de>
Subject: Digital distortion when converting Mono to Stereo?
Date: Thu, 29 Oct 2009 02:01:18 +0100 [thread overview]
Message-ID: <20091029010117.GO29442@buzzloop.caiaq.de> (raw)
While testing with our ASoC enabled embedded platform, we observed a
strange phenomena with Mono audio files. We used external audio test
equipment for SNR/THD analysis and used a mono wav file (16bit, 44.1
KHz) which plays a simple sweep from ~10Hz to ~20KHz.
As the hardware output is Stereo, an implicit conversion takes places
(don't know which part of ALSA actually does it, though).
Strangely, the measurement showed a phantom frequency which looks like
the sweeping test signal frequency was somehow 'mirrored' at 11.025KHz
(fs/4). This phantom noise becomes stronger the lower its frequency
gets. So while sweeping, those two peaks were approaching each other,
they met at 11KHz, and when the 'real' peak aproached 20KHz, the
phantom was at something like 1KHz and had comparable level than the
'real' signal. All that was much stronger on one channel and barely
there, but still measurable, on the other one.
We first though about an analog filter issue, then suspected the digital
input stream, but eventually it turned out that with the same test
file in stereo, all these effects suddenly went away. So there must be
something in the chain from aplay to the actual PXA SSP ports which adds
considerable digital distortion to one channel when converting from Mono
to Stereo.
I didn't dig any deeper, but still wanted to let you know. Can anyone
think of a possible reason for that? It doesn't harm us in our
application as we will never play Mono audio eventually, but I guess
it could affect others.
Thanks,
Daniel
reply other threads:[~2009-10-29 1:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20091029010117.GO29442@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=alsa-devel@alsa-project.org \
--cc=tim@caiaq.de \
/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.