All of lore.kernel.org
 help / color / mirror / Atom feed
From: thomas schorpp <thomas.schorpp@googlemail.com>
To: alsa-devel@alsa-project.org
Subject: Re: [CONF] All C-Media Codecs based 5.1 Channel USB- Headsets
Date: Tue, 06 Nov 2007 09:39:04 +0100	[thread overview]
Message-ID: <47302828.2060703@googlemail.com> (raw)
In-Reply-To: <472D7698.2080700@googlemail.com>

thomas schorpp wrote:
> Report to devlist as requested from USB-Audio.conf header:
> 
> 1. all this headsets with windriver inf files + manual showing c-media 
> driver must have the cm106x series 7.1 channel usb-codec in. there's no 
> other from c-media for the design of 5.1 channel usb headsets available 
> at this time, see:
> 
> http://www.cmedia.com.tw/?q=en/usb_audio
> 
> 2. the headset interface shows up with 8 channels in lsusb -v , 1 8-ch 
> pcm in /proc,
> and must be driven with surround7.1 pcm plug instead of surround5.1 or 
> it will not work. speaker-test program works with -c6 -Dsurround7.1, 
> test with -c8 works too, but shows that no SideL/R -speakers 
> connected/routed/downmixed ( Speedlink Medusa 5.1 Mobile USB Headset, 
> cm106L)
> 
> 3. it works instantly without extra config using programs that allow 
> specifying (-D)surround7.1 like VDR and MPlayer, VLC did not so far 

since yesterday VLC does work fine now with the cm106L device, 
just select the alsa device from the list in VLC config, MPlayer should too, 
then. Noteworthy, especially VLC's software equalizer brings a great 
*music sound quality boost* in, it is amazing! :)
sorry for the misreport, but audio device open errors showed up once, 
don't know the cause.

system is debian lenny (testing).

y
tom

  reply	other threads:[~2007-11-06  8:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-04  7:36 [CONF] All C-Media Codecs based 5.1 Channel USB- Headsets thomas schorpp
2007-11-06  8:39 ` thomas schorpp [this message]
2007-11-06 12:29 ` Takashi Iwai
2007-11-06 18:40   ` thomas schorpp
2007-11-18  4:38     ` thomas schorpp

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=47302828.2060703@googlemail.com \
    --to=thomas.schorpp@googlemail.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 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.