From: James Lehman <james@akrobiz.com>
To: "alsa-devel" <alsa-devel@alsa-project.org>
Subject: CM106L, CM6206, CM6206-LX
Date: Mon, 22 Apr 2024 13:41:02 -0400 [thread overview]
Message-ID: <18f06e59cb2.d58839031301481.5029384157786550072@akrobiz.com> (raw)
In-Reply-To:
Hello everyone.
I have been using CMedia USB sound devices to make laser control signals for many years.
I have sound devices with CM106L, CM6206 and CM6206-LX. Some are populated for 6 channels and some for 8.
The
CM106L chip works perfectly. I can send it a stream of 16-bit data that
uses the full range of -32767 to +32767 and at 100% volume in either
alsamixer or Pulseaudio Volume Control, I get a perfect image.
https://laserboy.org/piDAC/perfect_circle.jpg
If I use a device with a CM6206, I get a very near perfect image (only clipped a tiny bit).
But If I use a CM6206-LX chip, it clips hard.
https://laserboy.org/piDAC/CM6206-LX_100.jpg
Even if I reduce the volume to 50%, it just seems to reduce the clipped signals.
https://laserboy.org/piDAC/CM6206-LX_50.jpg
I'm not sure what is going on here, but it seems like there is some kind of internal digital gain of more than 1.0.
I also notice that lsusb shows exactly the same device ID for both the CM6206 and the CM6206-LX.
.... 0d8c:0102 C-Media Electronics, Inc. CM106 Like Sound Device
And what's really weird is that a genuine CM106L shows up as something else!
.... 0d8c:0006 C-Media Electronics, Inc. Storm HP-USB500 5.1 Headset
Is there something I can do in alsa config to fix this issue?
The
CM106L is long since out of production and it seems like any device
that uses the CM6206 might have the LX version (or not). There's no way to
know until I get them and open them up.
I'm
using this on an Orange Pi Zero 3 4gb running dietpi with the
6.6.16-current-sunxi64 kernel, but that doesn't seem to matter. I get
the same results any other way I try it. The LX version of this chip
clips the same way in Windows too!
Thanks for your time.
James.
reply other threads:[~2024-04-22 17:45 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=18f06e59cb2.d58839031301481.5029384157786550072@akrobiz.com \
--to=james@akrobiz.com \
--cc=alsa-devel@alsa-project.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).