Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Fruhwirth Clemens <clemens@endorphin.org>
To: alsa-devel@lists.sourceforge.net
Subject: [ALSA - driver 0000955]: CN-126 - USB 5.1 Audio adapter
Date: Thu, 03 Mar 2005 10:34:37 +0100	[thread overview]
Message-ID: <1109842477.13896.32.camel@ghanima> (raw)

[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]

My USB audio class device doesn't show all mixer controls in ALSA.
For reference, for other users searching this archive, it's a "Creative
USB Sound Blaster Live! 24-bit External". 
(http://creative.com/products/product.asp?category=1&subcategory=206&product=10702&nav=2)

I have added some inspection code to usb-mixer.c, which basically dumps
all class specific USB interface descriptors. 

My card got 2 x OUTPUT_TERMINAL, 2 x INPUT_TERMINAL, 2 x FEATURE_UNIT
for the AudioControl class. But this doesn't make me any wiser.

I wonder why the snd_usb_create_mixer code does only loop over the
OUTPUT_TERMINAL class, even there is support code for all other types in
the parse_audio_unit code, which is called subsequently by
snd_usb_create_mixer.

My aim is to have controls available for the Line-in mixer, both for
recording and for direct re-mixing into the Main Out Plug.

Is there a developer owning such a box, or anyone who can guess what I'm
supposed to do with the additional AudioControl class controls? 

Are there any tools that helps inspecting the USB device, or further
dumping of class-specific content and/or inspection of the USB
flow between a vmware hosted windows system and the linux host system?

Thanks,

What's the reason why Bug#995 is not available to the public? I'm
getting access denied. Otherwise I would have put this message into the
bugtracker.
-- 
http://clemens.endorphin.org, for robots sp4mtrap@endorphin.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2005-03-03  9:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-03  9:34 Fruhwirth Clemens [this message]
2005-03-03 10:35 ` [ALSA - driver 0000955]: CN-126 - USB 5.1 Audio adapter Jaroslav Kysela
2005-03-03 11:35 ` Clemens Ladisch
2005-03-03 15:24   ` Fruhwirth Clemens
2005-03-04  8:31     ` SB Live 24 Ext (was: [ALSA - driver 0000955]: CN-126 - USB 5.1 Audio adapter) Clemens Ladisch
2005-03-04  9:57       ` Fruhwirth Clemens
2005-03-04 11:09         ` Clemens Ladisch
2005-03-04 11:55           ` Fruhwirth Clemens
2005-03-04 18:32     ` [ALSA - driver 0000955]: CN-126 - USB 5.1 Audio adapter Lee Revell
  -- strict thread matches above, loose matches on Subject: below --
2006-03-22  2:28 bugtrack
2005-09-22 12:56 bugtrack
2005-03-02 14:07 bugtrack
2005-03-02 13:19 bugtrack
2005-03-02 11:58 bugtrack
2005-03-02 11:48 bugtrack
2005-03-02 11:46 bugtrack
2005-03-02 11:44 bugtrack
2005-03-02 11:34 bugtrack
2005-03-02  8:28 bugtrack
2005-03-01 23:13 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=1109842477.13896.32.camel@ghanima \
    --to=clemens@endorphin.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox