From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001707]: Better support for new USB-Microphone Samson C01U
Date: Tue, 3 Jan 2006 22:42:27 +0100 [thread overview]
Message-ID: <16de7f6bb723eebced727ab433446918@bugtrack.alsa-project.org> (raw)
The following issue has been SUBMITTED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1707>
======================================================================
Reported By: Toph
Assigned To: Clemens Ladisch
======================================================================
Project: ALSA - driver
Issue ID: 1707
Category: USB - usb-audio
Reproducibility: always
Severity: tweak
Priority: normal
Status: assigned
Distribution: gentoo
Kernel Version: 2.6.15-ck1
======================================================================
Date Submitted: 01-03-2006 22:42 CET
Last Modified: 01-03-2006 22:42 CET
======================================================================
Summary: Better support for new USB-Microphone Samson C01U
Description:
I recently bought this microphone:
http://www.samsontech.com/products/productpage.cfm?prodID=1810&brandID=2
and have been quite pleased to see that it kind of works with alsa. I've
only been puzzled by a few oddities: Although the mic is mono, I get a
stereo input with 2 controls, which did even influence the sound on both
channels separatly, but in a not-so-clear way.
Since neither the windows, nor the OSX usb-audio driver are able to fully
control the device, especially the internal gain-control, Samson has
published a modified driver & tool to control such parameters. I have
investigated that tool with an usb-traffic sniffer (usbsnoop).
I did also do some experiments with the alsa driver to see, what the
controls really do and how the device might be designed internally. I have
found out about everything needed to make the device fully supported, I
just don't really know how to implement it, so I'm hoping someone will
guide and help me. Although I'd really like to, I'm not a kernel hacker.
What I basically want to do is remap and rename the mixer-controls and
output lines alsa exposes. Is that what the quirks are for?
Details about the device and my findings follow below:
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
01-03-06 22:42 Toph New Issue
01-03-06 22:42 Toph Distribution => gentoo
01-03-06 22:42 Toph Kernel Version => 2.6.15-ck1
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2006-01-03 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 21:42 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-04 16:23 [ALSA - driver 0001707]: Better support for new USB-Microphone Samson C01U bugtrack
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=16de7f6bb723eebced727ab433446918@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--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