From: "John S. Denker" <jsd@monmouth.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: usbaudio won't do 24-bit or 32-bit i/o, and won't do 96000 frames per second
Date: Fri, 06 Dec 2002 08:13:15 -0500 [thread overview]
Message-ID: <3DF0A26B.6060804@monmouth.com> (raw)
In-Reply-To: <Pine.HPX.4.33n.0212060935510.27122-100000@studcom.urz.uni-halle.de>
Clemens Ladisch wrote:
> Now when I look at the specifications at it turns out that
> Creative isn't outright lying, only being _extremely_ misleading
Whaaat?? Hype and deception from Creative Labs???
Apparently that only happens on days when the sun
rises in the east and sets in the west.
> To summarize: Where it matters, the Extigy does neither
> 24 bits nor 96kHz. For professional audio, you have to
> go elsewhere.
Thanks for sorting this out.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-12-06 13:13 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 10:47 sb16 gets wedged when doing overlapped i/o (full duplex) John S. Denker
2002-12-05 11:31 ` usbaudio won't do 24-bit or 32-bit i/o, and won't do 96000 frames per second John S. Denker
2002-12-05 15:19 ` Clemens Ladisch
2002-12-05 19:10 ` John S. Denker
2002-12-06 9:16 ` Clemens Ladisch
2002-12-06 10:09 ` Jaroslav Kysela
2002-12-07 15:05 ` Patrick Shirkey
2002-12-06 13:13 ` John S. Denker [this message]
2002-12-06 14:22 ` many utils fail for extigy (usb) John S. Denker
2002-12-06 6:48 ` usbaudio won't do 24-bit or 32-bit i/o, and won't do 96000 frames per second Patrick Shirkey
2002-12-06 7:12 ` Patrick Shirkey
2002-12-13 18:19 ` Takashi Iwai
2002-12-14 10:48 ` usbaudio won't do 24-bit or 32-bit i/o Patrick Shirkey
2002-12-16 17:19 ` Takashi Iwai
2002-12-16 18:59 ` Patrick Shirkey
2002-12-16 20:11 ` Patrick Shirkey
2002-12-17 15:28 ` Takashi Iwai
2002-12-20 22:00 ` Patrick Shirkey
2002-12-23 13:35 ` Takashi Iwai
2002-12-23 18:58 ` Patrick Shirkey
2002-12-05 11:39 ` sb16 gets wedged when doing overlapped i/o (full duplex) John S. Denker
2002-12-05 11:52 ` hard crash when snd-ice1712 loads John S. Denker
2002-12-05 17:42 ` Jaroslav Kysela
2002-12-05 23:10 ` Scott Bahling
2002-12-05 11:57 ` alsactl and alsamixer fail for extigy John S. Denker
2002-12-09 14:51 ` Takashi Iwai
2002-12-05 12:07 ` sb16 gets wedged when doing overlapped i/o (full duplex) Uros Bizjak
2002-12-05 13:45 ` John S. Denker
2002-12-05 14:55 ` Uros Bizjak
2002-12-05 17:47 ` Jaroslav Kysela
2002-12-05 18:33 ` John S. Denker
2002-12-06 7:14 ` Uros Bizjak
2002-12-06 14:08 ` John S. Denker
2002-12-06 0:41 ` cs4239 errs on full duplex (provoked by overruns?) John S. Denker
2002-12-05 15:23 ` sb16 gets wedged when doing overlapped i/o (full duplex) Paul Davis
2002-12-09 14:30 ` Takashi Iwai
2002-12-09 14:54 ` documentation or lack thereof John S. Denker
2002-12-09 15:05 ` Takashi Iwai
2002-12-09 15:23 ` ljp
2002-12-09 16:23 ` Paul Davis
2002-12-10 17:59 ` Patrick Shirkey
2002-12-10 22:28 ` soundcard matrix: broken links etc John S. Denker
2002-12-11 2:52 ` Patrick Shirkey
2002-12-11 4:05 ` John S. Denker
2002-12-11 5:27 ` Patrick Shirkey
2002-12-14 15:59 ` John S. Denker
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=3DF0A26B.6060804@monmouth.com \
--to=jsd@monmouth.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.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 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.