All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paulo Marcel Coelho Aragao <pmcaragao-ag@yahoo.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Tips on debugging ALSA driver snd_es18xx
Date: Thu, 15 Dec 2005 17:42:29 -0200	[thread overview]
Message-ID: <20051215194229.GE5793@cortazar> (raw)
In-Reply-To: <s5hvexqz28y.wl%tiwai@suse.de>

Takashi Iwai wrote on Dec, 15:

[...]

> > > Please add this to your ~/.asoundrc:
> > > 
> > > pcm.u8 {
> > > 	type plug
> > > 	slave.pcm {
> > > 		type linear
> > > 		slave {
> > > 			pcm "hw:0"
> > > 			format U8
> > > 		}
> > > 	}
> > > }

[...]

> This configuration forces to use 8bit-unsigned format.  If any other
> formats are given, it's converted to u8 automatically.

This means that the driver processes the data in 8bit-unsigned chunks ?

> > > and try to play some 16-bit file to the ALSA device named "u8" instead 
> > > of the
> > > default one.  If this works, there is a bug in the driver in relation with
> > > 16-bit data.

> > Fantastic, Clemens ! You hit the bull's eye. Now the scenario is:
> > 
> > 1) aplay -Du8 produces sound from 8 or 16-bit data (the same I used before) on 
> >    both speakers

> I guess you're using a mono wav file?

I don't know how to inspect it. Could you give me a hint ? It's 
/usr/share/sounds/alsa/Front_Right.wav from Debian package alsa-utils.

> > 2) xmms and gxine produce sound only on the left speaker. I've attached a file 
> >    with the few config parameters which are explicitly set for gxine (the rest 
> >    is commented out, therefore, default). xmms saves every single parameter, 
> >    so I'm just sending the ALSA stanza.  My eye didn't catch anything that 
> >    might be related to usage of left/right speakers. Just in case, I'm also 
> >    attaching my mixer settings.

> This implies that u8-stereo doesn't work.

Should it work ?

> > 3) speaker-test -Du8 produces what I suppose is pink noise on both speakers, 
> >    but I noticed that its output included only "0 - Front Left"

> It means u8-mono works as expected, at least.

[...]

> > If this is indeed a bug in the driver, should I file a bug in ALSA BTS ?

> As you like.  We can continue the debug session on alsa-devel ML, too.

As long as we get to the bottom of this and squash this bug, the context 
doesn't matter to me. So, grasshopper Paulo asks Masters Takashi and Clemens: 
what's the next step ? I guess the goal is making 16-bit work, right ?

Thanks a lot, Takashi, for spending your time on this
Paulo


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

  reply	other threads:[~2005-12-15 19:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-15  1:34 Tips on debugging ALSA driver snd_es18xx Paulo Marcel Coelho Aragao
2005-12-15  8:27 ` Clemens Ladisch
2005-12-15 11:12   ` Paulo Marcel Coelho Aragao
2005-12-15 11:22     ` Takashi Iwai
2005-12-15 11:46       ` Paulo Marcel Coelho Aragao
2005-12-15 12:40       ` Paulo Marcel Coelho Aragao
2005-12-15 15:25     ` Clemens Ladisch
2005-12-15 16:52       ` Paulo Marcel Coelho Aragao
2005-12-15 17:41         ` Takashi Iwai
2005-12-15 19:42           ` Paulo Marcel Coelho Aragao [this message]
2005-12-16 14:28             ` Paulo Marcel Coelho Aragao
2005-12-22 15:51               ` Takashi Iwai

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=20051215194229.GE5793@cortazar \
    --to=pmcaragao-ag@yahoo.com \
    --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 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.