Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: mark@undertone.org
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: btw
Date: Thu, 17 Oct 2002 18:56:40 +0200	[thread overview]
Message-ID: <s5hvg413sxj.wl@alsa2.suse.de> (raw)
In-Reply-To: <20021017152042.GB14352@undertone.org>

At Thu, 17 Oct 2002 10:20:42 -0500,
mark@undertone.org wrote:
> 
> > - whether the files mathing with native format are ok.
> 
> Yup, seems to work fine. To continue the testing from before with this
> newfound pcm stream, the only newfound knowledge is that the "pcm"
> control seems to work.

a good news!


> > - whether the file above with OSS emulation works (which converts
> >   inside the kernel).
> 
> Uh hmm doesn't seem to. I'm truthfully not sure of the most ideal way
> to test this. I tested it by loading up the alsa-oss modules and using
> some oss programs that reference /dev/dsp (which in this case gets
> symlinked to sound/dsp).
 
i guess you got some kernel messages when aplay fails, such like
"cannot set format: ..." ?  could you show the message?


> > i'm not sure what's going on there, but the lsusb output once you sent
> > me contains much more supported formats.
> > and i experienced that the similar phenomenon happened on other
> > usb-audio devices - not the whole descriptors are parsed.
> > the behavior might be changed if you reboot.  sigh...
> 
> I've rebooted many times. Seems consistant.

well, but you got once better results.
possibly this can be a bug of the usb-audio driver.
is the driver built with --with-debug=detect option?
if so, please show the kernel messages, and we get to know what
happened.


> > i guess it's likely a bug of usb controller modules.
> 
> Suck. With the work being put in, I wonder how hard it would be to
> cajole Creative Labs to ship you a free extigy to play with, heh. Who
> knows, they might even end up supplying some specs.

:)

Takashi


-------------------------------------------------------
This sf.net email is sponsored by: viaVerio will pay you up to
$1,000 for every account that you consolidate with us.
http://ad.doubleclick.net/clk;4749864;7604308;v?
http://www.viaverio.com/consolidator/osdn.cfm

  reply	other threads:[~2002-10-17 16:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20021014191214.GB6704@undertone.org>
     [not found] ` <20021014192959.GA6792@undertone.org>
     [not found]   ` <20021014193407.GA6821@undertone.org>
     [not found]     ` <s5h8z106km8.wl@alsa2.suse.de>
2002-10-15 17:57       ` btw mark
2002-10-16 10:15         ` btw Takashi Iwai
2002-10-16 19:40           ` btw mark
2002-10-17  8:26             ` btw Takashi Iwai
2002-10-17 13:42               ` btw mark
2002-10-17 14:30                 ` btw Takashi Iwai
2002-10-17 15:20                   ` btw mark
2002-10-17 16:56                     ` Takashi Iwai [this message]
2002-10-17 14:44                 ` btw mark
2002-10-17 16:31                   ` Patrick Shirkey
2002-10-17 16:32                   ` Patrick Shirkey
2002-10-17 17:08                   ` Takashi Iwai
2002-11-25 13:37                     ` Extigy testing mark
2002-11-25 13:50                       ` Jaroslav Kysela
2002-11-25 14:35                         ` mark

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=s5hvg413sxj.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=mark@undertone.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