From: Patrick Shirkey <pshirkey@boosthardware.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: status of usb audio driver
Date: Thu, 13 Jun 2002 22:35:44 +0900 [thread overview]
Message-ID: <3D089FB0.5020604@boosthardware.com> (raw)
In-Reply-To: s5hn0tzz5vg.wl@alsa2.suse.de
Takashi Iwai wrote:
>>This card is supposed to be 24bit/96Khz. In windows it works like this:
>>
>>4 i/o channels(2 in, 2 out) at 16bit/48Khz or less
>>3 i/o channels(2 in, 1 out or 1 in, 2 out) at 24bit/48Khz or less
>>1 channel at 24bit/96Khz
>
>
> interesting. i don't find any mono channel on the descriptions.
> well, more investigations are necessary.
>
It is confusing to me also. From reading their docs I thought that the
card was all seperate mono channels lsusb has changed my opinion. I now
belive that Quattro stands for 2 stereo i/o devices not 4 mono i/o devices.
By saying in the docs that it supports 1 channel at 24bit/96Khz I guess
they mean 1 stereo in or 1 stereo out. that is good news to me becasue I
was under the impression that I had bought a turkey with only one mono
i/o channel at 24/96.
>>>i've tested usb mic from Labtec, and it works.
>>>so the problem is specific to the hardware, or multi-channels...
>>>
>>
>>I just remembered that my mouse is a usb mouse too so that is not
>>unexpected.
>
>
> too much bandwidth?
>
Testing again with the new code didn't lock up my mouse and this time
the file actually recorded data although I still cannot capture noise.
Do you have any ideas on how I can adjust the input levels internally
seeing as the card has no apparent internal mixer?
Is this a case of having to write our own mixer device?
Does this part of lsusb have anything to do with mixer controls?
----
wChannelConfig 0x0003
Left Front (L)
Right Front (R)
iChannelNames 0
iTerminal 0
----
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
next prev parent reply other threads:[~2002-06-13 13:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 16:57 status of usb audio driver Takashi Iwai
2002-06-12 5:16 ` Patrick Shirkey
2002-06-12 13:24 ` Takashi Iwai
2002-06-12 14:10 ` Patrick Shirkey
2002-06-12 14:13 ` Takashi Iwai
2002-06-12 14:19 ` Niklas Werner
2002-06-12 14:36 ` Takashi Iwai
2002-06-12 16:00 ` Niklas Werner
2002-06-12 14:55 ` Patrick Shirkey
2002-06-12 16:12 ` Patrick Shirkey
2002-06-12 16:48 ` Patrick Shirkey
2002-06-12 16:59 ` Takashi Iwai
2002-06-12 17:31 ` Patrick Shirkey
2002-06-13 10:39 ` Takashi Iwai
2002-06-13 12:54 ` Patrick Shirkey
2002-06-13 13:05 ` Takashi Iwai
2002-06-13 13:21 ` Niklas Werner
2002-06-13 14:05 ` Takashi Iwai
2002-06-14 8:58 ` Niklas Werner
2002-06-13 13:35 ` Patrick Shirkey [this message]
2002-06-13 13:43 ` Takashi Iwai
2002-06-13 14:58 ` Patrick Shirkey
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=3D089FB0.5020604@boosthardware.com \
--to=pshirkey@boosthardware.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox